...
| Code Block | ||
|---|---|---|
| ||
<annotations path="[openEHR-EHR-COMPOSITION.report.v1]/content[openEHR-EHR-SECTION.adhoc.v1 and name/value='Imaging diagnostics']/items[openEHR-EHR-SECTION.adhoc.v1 and name/value='Echocardiogram']/items[openEHR-EHR-OBSERVATION.imaging_exam_uk.v0]/data[at0001]/events[at0002]/data[at0003]/items[openEHR-EHR-CLUSTER.imaging_location_gel.v0]/items[at0002]"> <items> <item> <key>Notes.Authors Note</key> <value>GEL::33645.1</value> </item> </items> </annotations> |
This is used for a number of purposes including GUI hints but I don't think that is particularly sensible. The example above though it says 'Author's note' is actually mappings to the Genomics England master dataset metadata code.
I think this is supported ok in AD.
I think this is supported ok in AD.
Candidate Solution
From monday discussion: paths to unconstrained RM elements with visibility marker and optional aliases on a per language basis.
| Code Block |
|---|
rm_visibility = < ["/path/to[at0012]/archetype/node[at124]/path/to/rm/attribute"] = < visibility = <"show"> alias = < –- optional ["en"] = <"name in english"> ["de"] = <"name in german"> > > ["/path/to[at0013]/archetype/node[at124]/path/to/rm/attribute"] = < visibility = <"hide"> > > |
Alternative (TB):
| Code Block |
|---|
rm_visibility = <
["/path/to[at0012]/archetype/node[at124]/path/to/rm/attribute"] = <
visibility = <"show">
alias = <[local::al12]>
>
["/path/to[at0013]/archetype/node[at124]/path/to/rm/attribute"] = <
visibility = <"hide">
>
>
terminology
term_definitions = <
["al12en"] = <
["enad12"] = <
text = <"name in english">
["de"] English">
description = <"description in English">
>
...
>
["de"] = <
["ad12"] = <
text = <"name in german">
German">
description = <"description in German">
>
...
>
>
|