DK EHMI Terminology
1.0.2 - draft
DK EHMI Terminology, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 1.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-ehmi-terminology/ and changes regularly. See the Directory of published versions
| Official URL: http://medcomehmi.dk/ig/terminology/ValueSet/ehmi-delivery-status-rest-object-roles-valueset | Version: 1.0.2 | |||
| Draft as of 2025-11-11 | Computable Name: EhmiDeliveryStatusRestObjectRolesVS | |||
The role that the given Object played in the Audit Event recorded
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/object-role version 📦1.1.0| Code | Display | Definition |
| 4 | Domain Resource | A logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources. |
| 20 | Job | An order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS. |
Expansion performed internally based on codesystem AuditEventEntityRole v1.1.0 (CodeSystem)
This value set contains 2 concepts
| System | Code | Display (da) | JSON | XML |
http://terminology.hl7.org/CodeSystem/object-role | 4 | |||
http://terminology.hl7.org/CodeSystem/object-role | 20 |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |