This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Arden Syntax:Implementation Guide"
Jump to navigation
Jump to search
Line 34: | Line 34: | ||
How to use Arden to deliver decision support in particular clinical or administrative scenarios | How to use Arden to deliver decision support in particular clinical or administrative scenarios | ||
− | * [[Drug-Disease Interaction | + | * [[drug_disease_interaction_use_case|Drug-Disease Interaction]] |
* immunizations | * immunizations | ||
* hospital admission quality indicators | * hospital admission quality indicators |
Revision as of 04:03, 16 November 2013
Implementation Guide Arden Syntax
This page will collect material for a Arden Syntax implementation guide.
Later, the documents will be finalized using the following Google Document: Link
General Outline
Arden Syntax: Context and History
Arden Syntax: Context and History
Syntax Description Part
Syntax Description (see also How-To)
Basic tasks (by example)
Programming / Engineering Use Cases (how to implement ...):
Every use case should contain at least one example MLM.
- decision trees/tables
- production system
- state machines / transitions
- guidelines
- fuzzy control
- use of external knowledge bases
- creation and maintenance of documents (e.g., CHICA system)
- (any other ideas ?)
Clinical Use Cases
How to use Arden to deliver decision support in particular clinical or administrative scenarios
- Drug-Disease Interaction
- immunizations
- hospital admission quality indicators
- population-based decision support (e.g., infection control)
Future of Arden Syntax
TODO: add content
FAQ
References: Arden Syntax
Chapter that might be included
Dialects
Implementations
- available implementations of Arden Syntax - available compilers etc. -> see "The Arden Syntax standard for clinical decision support: experiences and directions", Samwald et. al.
Applications
- available implementations based on Arden Syntax) -> see "The Arden Syntax standard for clinical decision support: experiences and directions", Samwald et. al.