Hripcsak G, Ludemann P, et al. Rationale for the Arden Syntax. Computers and Biomedical Research 1994; 27:291-324.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....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 it. 3.1 Value Types ....

George Hripcsak, Peter Ludemann, T. Allan Pryor, Ove B. Wigertz, and Paul D. Clayton. Rationale for the Arden syntax. Computers and Biomedical Research, 27:291--324, 1994.

....[7] However, few current clinical information systems support intervals, and the medical informatics field has no standard means for making temporal queries using intervals. The Arden Syntax, for example, does not provide direct support for intervals, and has limited temporal querying abilities [8]. The Arden Syntax does, however, support a type of query that allows the combination of multiple temporally concurrent data elements into a single list. This process provides a simple way of doing a temporal join, and illustrates that temporal joins are necessary even in instant based databases. ....

Hripcsak G, Ludemann P, Allan Pryor T, Wigertz, OB, Clayton P. Rationale for the Arden Syntax. Computers and Biomedical Research, 1994; 27: 291-324.

....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 additional information like if ....

George Hripcsak, Peter Ludemann, T. Allan Pryor, Ove B. Wigertz, and Paul D. Clayton. Rationale for the Arden syntax. Computers and Biomedical Research, 27:291--324, 1994.

....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 additional information like if ....

George Hripcsak, Peter Ludemann, T. Allan Pryor, Ove B. Wigertz, and Paul D. Clayton. Rationale for the Arden syntax. Computers and Biomedical Research, 27:291-324, 1994.

....state of the world#. A more detailed review is given in #Miksch et al. 1997#. On the other hand, workers in Medicine and Medical Informatics have recognized the importance of protocolbased care to ensure a high quality of care. An important approachwas the de#nition of the Arden syntax #Hripcsak et al. 1994#, which encodes situation action rules. This syntax has signi#cant limitations too: it currently supports only atomic data types, lacks a de#ned semantic for making temporal comparisons or for performing data abstraction, and provides no way to represent clinical guidelines that are more complex ....

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B., and Clayton, P. D. #1994#. Rationale for the Arden syntax. Computers and Biomedical Research, 27:291#324.

....1989] are a superset of the requirements of typical toy domains used in planning research. We have defined a formal syntax for the Asbru language in Backus Naur form [Miksch et al. 1997] The Asbru language combines the flexibility and expressivity of procedural languages (e.g. the Arden syntax [Hripcsak et al. 1994]) with the semantic clarity of declaratively expressed knowledge roles. These roles (e.g. preferences and intentions) are specific to the ontology of the methods performing the guideline support tasks. 2.3.1 Time Annotation The time annotation we use allows a representation of uncertainty in ....

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B., and Clayton, P. D. (1994). Rationale for the Arden Syntax. Computers and Biomedical Research, 27:291-324.

....and medical informatics have recognized the importance of protocol based care to ensure a high quality of care since the 1970s. A group of investigators, working through the American Society for Testing and Materials (ASTM) has defined a standard procedural language, known as the Arden syntax [Hripcsak et al. 1994]. The Arden syntax encodes situationaction rules. Developers of the Arden syntax have promoted this Pascal like language because of the pressing needs to facilitate exchange of guidelines among health care institutions using existing software technology. This new standard has significant ....

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B., and Clayton, P. D. (1994). Rationale for the Arden Syntax. Computers and Biomedical Research, 27:291-324.

....straightforward plan execution without interruption or later adaptation according to changes in the environment. in: AI Communications, 4, 1999 14 According to our requirements we have chosen three most promising approaches to compare: # The Arden Syntax and the Medical Logic Modules (MLMs) [26]; # the EON approach [48; 76] # the GLIF (GuideLine Interchange Format) Approach [52] Other candidates were excluded from the detailed comparison because of space limitations, such as: # the MBTA (Modeling Better Treatment Advice) system [4] which aims to support the automation of ....

....the features with the requirements defined in Section 2.2. 5.1. Arden Syntax and Medical Logic Modules (MLMs) General Design. A group of investigators, working for the American Society for Testing and Materials (ASTM) have defined a standard procedural language, known as the Arden syntax [26]. The Arden syntax encodes situation action rules. Developers of the Arden syntax have promoted this Pascal like language because of the pressing needs to facilitate exchange of protocols among health care institutions using existing software technology. The Arden syntax is mostly used for alert ....

[Article contains additional citation context not shown here]

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B. and Clayton, P. D.: Rationale for the Arden Syntax. Computers and Biomedical Research, 27 (1994), 291-324.

....skeletal plan support ontology. We used this ontology for generating an automated knowledge acquisition tool by employing the PROTG II framework s tools (Musen, et al. 1995) The Asbru language combines the flexibility and expressivity of standard procedural languages (e.g. the ARDEN syntax (Hripcsak, et al. 1994) in the clinical domain) with the semantic clarity of declaratively expressed knowledge roles in the task specific ontology. Asbru can be used to design specific plans as well as support the performance of different reasoning and executing tasks. Similar assumptions were made in the PROPEL ....

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B., and Clayton, P. D. (1994). Rationale for the Arden Syntax. Computers and Biomedical Research, 27:291-324.

....state of the world) A more detailed review is given in (Miksch et al. 1997) On the other hand, workers in Medicine and Medical Informatics have recognized the importance of protocolbased care to ensure a high quality of care. An important approach was the definition of the Arden syntax (Hripcsak et al. 1994), which encodes situation action rules. This syntax has significant limitations too: it currently supports only atomic data types, lacks a defined semantic for making temporal comparisons or for performing data abstraction, and provides no way to represent clinical guidelines that are more complex ....

Hripcsak, G., Ludemann, P., Pryor, T. A., Wigertz, O. B., and Clayton, P. D. (1994). Rationale for the Arden syntax. Computers and Biomedical Research, 27:291--324.

No context found.

Hripcsak G, Ludemann P, et al. Rationale for the Arden Syntax. Computers and Biomedical Research 1994; 27:291-324.

No context found.

Hripcsak G, Ludemann P, Allan Pryor T, Wigertz, OB, Clayton P. Rationale for the arden syntax. Computers and Biomedical Research, 1994; 27: 291-324.

No context found.

Hripcsak G, Ludemann P, Pryor TA, Weigertz OB, Clayton PD. Rationale for the Arden syntax. Computers and Biomedical Research, 1994; 7(4):291-324.

No context found.

291--324.

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