DK MedCom Messaging
2.0.0 - Release
DK MedCom Messaging
2.0.0 - Release
This page is part of the DK MedCom Messaging (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| MedComMessagingMessage |
Base resource for all MedCom messages. |
| MedComMessagingMessageHeader |
MessageHeader for MedCom messages |
| MedComMessagingOrganization |
A formally recognized organizations registered for exchanging messages within Danish healthcare, registered with a SOR identifier issued by The Danish Health Data Authority |
| MedComMessagingProvenance |
Provenance information about the messages preceeding the current message |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| MedComDestinationUseExtension |
Indicates whether the use of a destination in a MedCom message header is as a primary or a carbon copy recipient of the message |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Aros Burn Center |
A core organization with a SOR identifier. |
| Bundle used in an empty message. |
Example of an empty message. |
| CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message |
CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message |
| Eric Flame |
Patient with a managing organization. Valid only if used in a bundle (message). |
| Example of a reciever organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| Example of a sender organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| Example of a service provider organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| MessageHeader for a Acknowledgement message. Valid only if used in a bundle (message) |
MessageHeader for a Acknowledgement message. Valid only if used in a bundle (message). NB: An Acknowledgement message shall use an AcknowledgementMessageHeader, as some elements and invariants are missing. |
| MessageHeader for a CareCommunication message. Valid only if used in a bundle (message) |
MessageHeader for a CareCommunication message. Valid only if used in a bundle (message). NB: A CareCommunication message shall use a CareCommunicationMessageHeader, as some elements and invariants are missing. |
| MessageHeader for a HospitalNotification message. Valid only if used in a bundle (message) |
MessageHeader for a HospitalNotification message. Valid only if used in a bundle (message). NB: A HospitalNotification message shall use a HospitalNotificationMessageHeader, as some elements and invariants are missing. |
| MessageHeader for an empty message. Valid only if used in a bundle (message) |
MessageHeader for an empty message. Valid only if used in a bundle (message). |
| Simple practitioner with a name |
Simple practitioner with a name |