Generic_entry would greatly benefit from a "meaning" attribute

Description

When dealing with integration of other artifacts, having kind of an optional "meaning" archetype in the GENERIC_ENTRY class, in a similar way 13606 entry has (see 13606 part 3) would ease the transformation of clinical models between any other standard and openEHR, while keeping all the semantics (e.g. something was originally a CDA Observation, or even a MedicationAdministration FHIR resource). With this we could separate the original "class" of the model and still being able to copy the source model terminology bindings if available (no need to add some term bindings in addition to the ones the source class may have)

Environment

None

Status

Reporter

Diego Bosca

Labels

None

Components

Affects versions

RM Release 1.0.4

Priority

Minor
Configure