This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Arden Syntax:Implementation Guide"

From HL7Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 2 users not shown)
Line 12: Line 12:
 
=== Syntax Description Part ===
 
=== Syntax Description Part ===
  
[[Arden_Syntax:Implementation_Guide:Syntax_Description| Syntax Description]]
+
[[Arden_Syntax:Implementation_Guide:Syntax_Description| Syntax Description]] (see also [http://www.medexter.com/downloads/category/5-arden-syntax?download=2:arden-syntax How-To])
 
 
basically taken from [http://www.medexter.com/downloads/category/5-arden-syntax?download=2:arden-syntax Medexters How-To]
 
  
 
=== Basic tasks (by example) ===
 
=== Basic tasks (by example) ===
 
+
[[Arden_Syntax:Implementation_Guide:Basic_Tasks| Basic tasks]]
* common tasks (e.g. search a list for a specific value, sort a list of objects etc.)
 
* small snippets of MLM code on how to solve specific problems (e.g. in former versions it was not possible to convert a String into a Date, this section should explain on how to do this)
 
** calculate the current age in years from a given birthday
 
* [[Arden_Syntax:Implementation_Guide:MLM_to_MLM_interaction| MLM to MLM interaction]] (call sub MLM, import MLM)
 
** 5 example MLMs showing 'call sub MLMs' and 'import from other MLMs', taken from 'VHA CHIO Innovation project "Enhanced Clinical Decision Support for CPRS': [https://sites.google.com/site/enhancedcprscds/arden-knowledge-base/SampleMLM_from_22.06.2011.zip?attredirects=0&d=1 Link]
 
* create complex knowledge bases with MLMs
 
  
 
=== Programming / Engineering Use Cases (how to implement ...): ===
 
=== Programming / Engineering Use Cases (how to implement ...): ===
 +
[[Arden_Syntax:Implementation_Guide:Engineering_Use_Cases| Engineering Use Cases]]
  
Every use case should contain at least one example MLM.
+
=== Clinical Use Cases ===
 +
[[Arden_Syntax:Implementation_Guide:Clinical_use_cases| Clinical use cases]]
  
* decision trees/tables
+
=== Arden Syntax related to other formalism or artifacts ===
* production system
+
[[Arden_Syntax:Implementation_Guide:Comparision_to_Others| Comparision to others]]
* 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
+
=== Curly brace based mappings to data models ===
 +
[[Arden_Syntax:Implementation_Guide:CB_model_mapping| Mapping to data models]]
  
* immunizations
+
=== Future of Arden Syntax ===
* hospital admission quality indicators
 
* population-based decision support (e.g., infection control)
 
  
 +
TODO: add content
  
 
=== FAQ ===
 
=== FAQ ===

Latest revision as of 21:06, 17 September 2014

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)

Basic tasks

Programming / Engineering Use Cases (how to implement ...):

Engineering Use Cases

Clinical Use Cases

Clinical use cases

Arden Syntax related to other formalism or artifacts

Comparision to others

Curly brace based mappings to data models

Mapping to data models

Future of Arden Syntax

TODO: add content

FAQ

FAQ

References: Arden Syntax

References

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.