Guideline execution engine
The engine's main function is to manage instances of executed guidelines of individual patients.
Delivering the inferred engine recommendations or impacts to the host Clinical information system has to carefully respect current workflow of the clinicians (physicians, nurses, clerks, etc.)
Architecture of Guideline Execution Engine
The following modules are generally needed for any engine
- interface to Clinical Information System
- new guidelines loading module
- guideline interpreter module
- clinical events parser
- alert/recommendations dispatch
Guideline Interchange Format
The format has several versions as it has been improved. In 2003 GLIF3 was introduced.
- Electronic medical record
- Clinical practice guideline
- Medical algorithm
- Arden syntax
- Healthcare workflow
- "Guideline Representation Page: GLIF 2.0, 3.4, 3.5 Specifications". Stanford University, School of Medicine, InterMed Collaboratory.
- Wang D, Peleg M, Tu SW, et al. (October 2004). "Design and implementation of the GLIF3 guideline execution engine". J Biomed Inform 37 (5): 305–18. doi:10.1016/j.jbi.2004.06.002. PMID 15488745. (PDF)
- Ram P, Berg D, Tu S, et al. (2004). "Executing clinical practice guidelines using the SAGE execution engine". Stud Health Technol Inform 107 (Pt 1): 251–5. PMID 15360813.
- Tu SW, Campbell J, Musen MA (2003). "The structure of guideline recommendations: a synthesis". AMIA Annu Symp Proc: 679–83. PMC 1480008. PMID 14728259. (PDF)
- Tu SW, Musen MA (1999). "A flexible approach to guideline modeling". Proc AMIA Symp: 420–4. PMC 2232509. PMID 10566393. (PDF)