Lucila Ohno-Machado, John H. Gennari, Shawn Murphy, Nilesh L. Jain, Samson W. Tu, Diane E. Oliver, and Edward Pattison-Gordon. The GuideLine Interchange Format: A model for representing guidelines. Journal of American Medical Informatics Association, 5(4):357-- 372, 1998. 19  Home/Search   Document Details and Download   Summary   Related Articles   Check

....There is also a strict distinction between diagnosis and treatment phases in PROforma, which is the reason for parameter input during plan execution not being supported in this interface. To the best of our knowledge, there is no runtime support appropriate for the medical sta# for either GLIF [5] or the Arden Syntax [2] 3 Data Acquisition Two di#erent types of data are acquired by AsbrUI: Entries in the patient record and parameters. These two value types (and also others) are described in section 3.1, the graphical interfaces for their input are presented in the two sections following ....

Lucila Ohno-Machado, John H. Gennari, Shawn Murphy, Nilesh L. Jain, Samson W. Tu, Diane E. Oliver, Edward Pattison-Gordon, Robert A. Greenes, Edward H. Shortli#e, and G. Octo Barnett. The guideline interchange format: A model for representing guidelines. JAMIA, 5(4):357--372, 1998.

.... scenarios that drive decision making and structures guidelines as a set of choices for the physician which have to be made between alternative actions[5] The current study focuses on the Guideline Interchange Format (GLIF) a 4 representational language developed by the InterMed Collaboratory[6]. The InterMed Collaboratory consists of informatics researchers from Columbia University, Harvard University, McGill University, and Stanford University, where the principle mandate for InterMed s participants has been to join in the development of a sharable computerinterpretable guideline ....

....clinical guidelines that could be downloaded by healthcare organizations, adapted to their local setting, and implemented in their institutional CPR systems. The original GLIF specification published in 1998, GLIF version 2. 0 (GLIF2) consists of two parts: the GLIF model and the GLIF syntax[6]. The GLIF model consists of a set of classes for guideline entities, attributes of those classes and data types for the attribute values. A particular guideline encoded in GLIF is represented as an object consisting of a name, a list of authors, a characterization of the guideline s intention, a ....

[Article contains additional citation context not shown here]

Ohno-Machado L, Gennari J, Murphy S, Jain N, Tu S, Oliver D, et al. The guideline interchange format: A model for representing guidelines. Journal of the American Medical Informatics Association 1998;5(4):357-372.

....[11] knowledge acquisition tool that provides support for entering and editing MLMs. MEDAILLE has a syntax checker and an integrated terminology. Translation of MLMs into an executable form can be done by a number of compilers [12, 13] 7 GLIF2 We have carried out the development of GLIF [14] through the formation of the InterMed Collaboratory, a consortium of medical informatics groups at Harvard, Stanford, and Columbia universities. GLIF is designed to allow exchange of computer interpretable guidelines among institutions and computer based applications. Unlike the Arden Syntax, it ....

....alerts and reminders. Like the Arden Syntax, GLIF encoded guidelines are stored as text files for sharing. GLIF has an object oriented model that consists of a set of classes for guideline entities, attributes for those classes, and data types for the attribute values. GLIF2, published in 1998 [14], represented guidelines as flowcharts of guideline steps such as clinical actions and decisions. However, the attributes of structured constructs were defined only as free text strings, and such guidelines could not be used for computer based execution that requires automatic inference. GLIF3 ....

Ohno-Machado L, Gennari JH, Murphy S, Jain NL, Tu SW, Oliver DE, et al. The GuideLine Interchange Format: A Model for Representing Guidelines. Journal of the American Medical Informatics Association 1998;5(4):357-372.

....There is also a strict distinction between diagnosis and treatment phases in PROforma, which is the reason for parameter input during plan execution not being supported in this interface. To the best of our knowledge, there is no runtime support appropriate for the medical sta# for either GLIF [4] or the Arden Syntax [2] 3 Data Acquisition Two di#erent types of data are acquired by AsbrUI: Entries in the patient record and parameters. Patient Record. In Asbru, the patient record not only contains information like the name, date of birth, etc. of the patient, but can also contain ....

Lucila Ohno-Machado, John H. Gennari, Shawn Murphy, Nilesh L. Jain, Samson W. Tu, Diane E. Oliver, Edward Pattison-Gordon, Robert A. Greenes, Edward H. Shortli#e, and G. Octo Barnett. The guideline interchange format: A model for representing guidelines. JAMIA, 5(4):357--372, 1998.

....They differ from the Asgaard system mostly concerning the context sensitive data abstraction, modelling of the temporal dimension, and the integration of the whole range of task specific problem solving methods around a uniform representation. Comparable approaches are PROforma [5] GLIF [6], EON [7] and work by Quaglini et al. 8] While these projects share many features with Asgaard, they do not provide equal facilities for temporal data abstraction and continual support of both diagnosis and treatment. There are several projects dealing with temporal data abstraction with some ....

Ohno-Machado L., Gennari JH, Murphy S, Jain NL, Tu SW, Oliver DE, Pattison-Gordon E, Greenes RA, Shortliffe EH, Barnett GO. The GuideLine Interchange Format: a model for representing guidelines. J Am Med Inf 1998: 5(4), pp. 357-372.

.... have been represented and specified using a number of methods. Miksch [17] describes some of the methods, including: 1) Free text; 2) Medical logic modules 3) Decision tables and 4) Flowcharts. Among these methods, medical logic modules might be of particular interest. Ohno Machado et al. [21] describes it as . software modules, written in Arden Syntax, that, when implemented in a clinical information system, run on databases of patient data and typically provide alerts or reminders for clinicians . There are a number of clinical practice guideline and protocol models and systems ....

....in a clinical information system, run on databases of patient data and typically provide alerts or reminders for clinicians . There are a number of clinical practice guideline and protocol models and systems that have been implemented over the past five years. Some of these include GLIF [21]; Asgaard Asbru [27] EON system [19] and ProForma [9] In the domain of test ordering, Wijk et al. [29, 30] have developed a protocol based decision support system called BloodLink Guideline whose objective is to help the clinician in the management of test ordering. The system developed in [29] ....

Ohno-Machado L, Gennari J H, Murphy S, Jain N H, Tu S W, Oliver DE, Pattison-Gordon E, Greenes RA, Shortliffe EH, Barnett GO (1998). The GuideLine Interchange Format: A Model for Representing Guidelines. JAMIA Vol.5 No.4: pp357-372.

....There is also a strict distinction between diagnosis and treatment phases in PROforma, which is the reason for parameter input during plan execution not being supported in this interface. To the best of our knowledge, there is no runtime support appropriate for the medical sta for either GLIF [4] or the Arden Syntax [2] 3 Data Acquisition Two di erent types of data are acquired by AsbrUI: Entries in the patient record and parameters. Patient Record. In Asbru, the patient record not only contains information like the name, date of birth, etc. of the patient, but can also contain ....

Lucila Ohno-Machado, John H. Gennari, Shawn Murphy, Nilesh L. Jain, Samson W. Tu, Diane E. Oliver, Edward Pattison-Gordon, Robert A. Greenes, Edward H. Shortlie, and G. Octo Barnett. The guideline interchange format: A model for representing guidelines. JAMIA, 5(4):357-372, 1998.

.... composition, state transition diagram protocol patient record model EON [14,15] decision step action, activity scenario, activity state no flowchart subguideline EPR ontology PROforma [16] decision action, enquiry n a task state constraints satisfaction graph plan n a GLIF [17,18] decision step action step patient state step no flowchart subguideline three layer domain ontology Asbru [19] condition, preference plan temporal patterns plan state plan body plan n a GUIDE [20] decision task, wait, monitor (implicit) n a flowchart task relational PRODIGY ....

....different guideline models. Arden Syntax has a logic slot, which is used to encode the decision criteria of a Medical Logic Module (MLM) and an action slot, which is used to encode the clinical task that should be performed [12] GLIF has a decision step, an action step, and a patient state step [17,18], which correspond to decision, action and patient state. Arden Syntax does not have a primitive to represent patient state or execution state [12] Its ability to represent complex clinical guidelines directly, which usually consist of multiple decisions, actions and patient states, is thus ....

[Article contains additional citation context not shown here]

Ohno-Machado L, Gennari JH, Murphy S, Jain NL, Tu SW, Oliver DE, et al. The GuideLine Interchange Format: a model for representing guidelines. J Am Med Inform Assoc 1998;5(4):357-72.

....for protocolbased care [8] It is a time oriented, intention based, skeletal plan specification language. Asbru is an interesting language in a case study on critiquing because it is much more detailed and formalised than other protocol representation languages, such as PROforma [3] or GLIF [6]. This makes Asbru in principle an attractive candidate for protocol improvement because the additional details in an Asbru representation will help to expose potential problems in the original protocol. In Asbru, protocols are expressed as plan schemata defined at various levels of detail, ....

L. Ohno-Machado, J. Gennari, S. Murphy, N. Jain, S. Tu, D. Oliver, E. Pattison-Gordon, R. Greenes, E. Shortliffe, and G. Octo Barnett. Guideline Interchange Format: a model for representing guidelines. J. of the American Medical Informatics Association, 5(4):357--372, 1998.

....or local system environments. GLIF. InterMed is a joint project of medical informatics groups at Harvard, Columbia, and Stanford Universities, along with other participants, which has been working on GLIF since 1996. A specification for GLIF version 2. 0 (GLIF2) was published in 1998 [2]. Prototype tools for authoring, navigating, server support, and execution have been developed [3, 4] GLIF3 [5] is an evolving version of GLIF, intended to more completely address implementation (see www.glif.org) GLIF is based on an object oriented logical model of concepts, and has an ....

Ohno-Machado L, Gennari JH, Murphy S, Jain NL, Tu SW, Oliver DE, et al. The GuideLine Interchange Format: A Model for Representing Guidelines. Journal of the American Medical Informatics Association 1998;5(4):357-372.

No context found.

Lucila Ohno-Machado, John H. Gennari, Shawn Murphy, Nilesh L. Jain, Samson W. Tu, Diane E. Oliver, and Edward Pattison-Gordon. The GuideLine Interchange Format: A model for representing guidelines. Journal of American Medical Informatics Association, 5(4):357-- 372, 1998. 19

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC