Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts

BMC Medical Informatics and Decision Making

Correspondence

Prakash M Nadkarni¹  Ganesh Krishnan²  Patricia Williams²  Robert Enberg²  Hemant Shah²  Raymond D Allard² 

[1] Center for Medical Informatics, Yale University Medical School, New Haven, USA;Henry Ford Health System, Detroit, USA;

关键词: Clinical Decision Support System;    Computerize Physician Order Entry;    Enterprise Resource Planning;    Computerize Provider Order Entry;    Guideline System;   

DOI  :  10.1186/1472-6947-12-16

 received in 2011-08-04, accepted in 2012-03-09,  发布年份 2012

来源: Springer

【 摘 要 】

BackgroundA large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system.MethodsIn addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org).ResultsThe sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context.ConclusionsWhen analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.

【 授权许可】

CC BY   
© Shah et al; licensee BioMed Central Ltd. 2012