We're updating the issue view to help you get more done.Learn more

Allow term bindings to paths in archetypes

In the current ADL specifications, term bindings are shown as being
only to single terms. However, mappings of external terms should be
allowed to whole paths or path patterns, to allow for the binding of
pre-coordinated external terms, such as in LOINC. A siingle LOINC term
will usually bind to a whole path in an archetype, e.g. the path for
"5 minute body temperature recording". This can also happen with Snomed-ct
codes.

Status

Assignee

JeffJ

Reporter

(Sam Heard) inactive

Change Description

Changes made: - in the ADL manual, Term_bindings section, the description should allow bindings like the following: ["LNC205"] = < items = < ["/data[at0002]/events[at0003]/data[at0001]/item[at0004]"] = <[LNC205::8310-5]> ["/data[at0002]/events[at0005]/data[at0001]/item[at0004]"] = <[LNC205::8321-2]> > > - in the AOM, the function ARCHETYPE_ONTOLOGY.term_binding should be adjusted so that the second argument is not a code, but a string that can be a code or a path (in the future, this will probably be further adjusted to a string that is always a proper Xpath-style pattern).

Approved By

PG

Components

Fix versions

Priority

Trivial