%0 Journal Article %1 Shah2012 %A Shah, H %A Allard, R D %A Enberg, R %A Krishnan, G %A Williams, P %A Nadkarni, P M %D 2012 %J BMC Med Inform Decis Mak %K guideline requirements software_engineering %P 16-16 %R 10.1186/1472-6947-12-16 %T Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts %U http://www.ncbi.nlm.nih.gov/pubmed/22405400 %V 12 %X A 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.In 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).The 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.When 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.

@article{Shah2012, abstract = {A 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.In 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).The 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.When 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.}, added-at = {2012-11-28T15:34:05.000+0100}, author = {Shah, H and Allard, R D and Enberg, R and Krishnan, G and Williams, P and Nadkarni, P M}, biburl = {https://www.bibsonomy.org/bibtex/2f3dd601963fe801bc3efe686f7f40d88/rhatko}, description = {Requirements for guidelines systems... [BMC Med Inform Decis Mak. 2012] - PubMed - NCBI}, doi = {10.1186/1472-6947-12-16}, groups = {public}, interhash = {83a8430a2e2719b14de845f156886cba}, intrahash = {f3dd601963fe801bc3efe686f7f40d88}, journal = {BMC Med Inform Decis Mak}, keywords = {guideline requirements software_engineering}, pages = {16-16}, pmid = {22405400}, timestamp = {2012-12-06T10:42:14.000+0100}, title = {Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts}, url = {http://www.ncbi.nlm.nih.gov/pubmed/22405400}, username = {rhatko}, volume = 12, year = 2012 }