Ruby implementation of openEHR

h1. YADL

h2. Background

ADL is one of the openEHR official formalism to express archetype, defined as "ADL 1.4"http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/adl1.4.pdf
Many archetypes are registered on "Clinical Knowledge Manager":http://www.openehr.org/knowledge/ shown such as bellow:

archetype (adl_version=1.4)
openEHR-EHR-OBSERVATION.sample.v1

concept
[at0000] -- sample archetype
language
original_language = <[ISO_639-1::ja]>
description
original_author = <
["name"] = <"">
>
details = <
["ja"] = <
language = <[ISO_639-1::ja]>
purpose = <"">
use = <"">
misuse = <"">
>
>
lifecycle_state = <"0">
other_contributors = <>
other_details = <
["references"] = <"">
["MD5-CAM-1.0.1"] = <"F5DEA5434726E79CFB3CEA0A7796E501">
>

definition
OBSERVATION[at0000] matches { -- sample archetype
data matches {
HISTORY[at0001] matches { -- Event Series
events cardinality matches {1..; unordered} matches {
EVENT[at0002] occurrences matches {0..1} matches { -- Any event
data matches {
ITEM_TREE[at0003] matches { -- Tree
items cardinality matches {0..; unordered} matches {
ELEMENT[at0004] occurrences matches {0..1} matches { -- Description
value matches {
DV_TEXT matches {*}
}
}
}
}
}
}
}
}
}
}

ontology
term_definitions = <
["ja"] = <
items = <
["at0000"] = <
text = <"sample archetype">
description = <"sample archetype to discuss its formalism.">
>
["at0001"] = <
text = <"Event Series">
description = <"@ internal @">
>
["at0002"] = <
text = <"Any event">
description = <"">
>
["at0003"] = <
text = <"Tree">
description = <"@ internal @">
>
["at0004"] = <
text = <"Description">
description = <"">
>
>
>
>

Otherwise, ADL is not so common formalism such as XML or OWL.
XML serialisation is considered more popular alternative to express archetype.
XML form of archetype is shown bellow

<?xml version="1.0"?>



ISO_639-1

ja



0
F5DEA5434726E79CFB3CEA0A7796E501



ISO_639-1

ja







openEHR-EHR-OBSERVATION.sample.v1

1.4
at0000

OBSERVATION

true
true
false
false
1
1

at0000

data

true
true
false
false
1
1

... snips ...

Description
*

XML form is exploding by tags and lacks simplicity of ADL formalism.
YAML form is remarked as easy and simple formalism, which is recognised te be an alternative for XML.
Sample YAML form is considered as bellow:

arhetype:
archetype_id: openEHR-EHR-OBSERVATION.sample.v1
concept:
at0000: sample archetype
language:
original_language: [ISO_639-1::ja]
description:
..snips..

YAML format is more similar to ADL than XML and seems very comprehensive form. So our project will challenge to implement YADL(Yet another ADL) as alternative formalism for archetype and our Ruby implementation.

h2. Methods

We should implement YAML scheme to express archetype as cADL and YAML instance to express dADL.

h2. Result

on going.