Skip to main content

Table 2 Sample metadata entries of selected form components depicted in Figure 3

From: Towards plug-and-play integration of archetypes into legacy electronic health record systems: the ArchiMed experience

Type

Label

Path

PAGE

Body mass index

[@archetype_node_id = ‘openEHR-EHR-OBSERVATION.body_mass_index.v1’ and @xsi:type = ‘OBSERVATION’]

TEXT_OBJECT

history

[@archetype_node_id = ‘openEHR-EHR-OBSERVATION.body_mass_index.v1’ and @xsi:type = ‘OBSERVATION’]/data[@archetype_node_id = ‘at0001’ and @xsi:type = ‘HISTORY’]

TEXT_OBJECT

origin

[@archetype_node_id = ‘openEHR-EHR-OBSERVATION.body_mass_index.v1’ and @xsi:type = ‘OBSERVATION’]/data[@archetype_node_id = ‘at0001’ and @xsi:type = ‘HISTORY’]/origin[@xsi:type = ‘DV_DATE_TIME’]

ENTRY_FIELD

value

[@archetype_node_id = ‘openEHR-EHR-OBSERVATION.body_mass_index.v1’ and @xsi:type = ‘OBSERVATION’]/data[@archetype_node_id = ‘at0001’ and @xsi:type = ‘HISTORY’]/origin[@xsi:type = ‘DV_DATE_TIME’]/value[@xsi:type = ‘DATE_TIME’]

  1. Column Type depicts the ArchiMed data model class corresponding to the particular archetype node. Column Label holds the component’s label in the form. Column Path holds the path of the archetype node (in XPath format), from which the form component is derived. Components origin and value are not addressed in the archetype, but have to be considered in the form and the EHR extract as they are mandatory attributes of the RM.
Back to article page

BMC Medical Informatics and Decision Making

ISSN: 1472-6947

Contact us