DK MedCom acknowledgement
2.0.1 - Release
DK MedCom acknowledgement
2.0.1 - Release
This page is part of the DK MedCom Acknowledgement (v2.0.1: Release) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions 
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.
| MedComAcknowledgementMessage |
Base resource for all MedCom Acknowledgement messages. |
| MedComAcknowledgementMessageHeader |
A resource that describes a reponse to a message that is exchanged as a MedCom messgage within Danish healthcare |
| MedComAcknowledgementOperationOutcome |
This profile provides detailed information about the outcome of an attempted system operation, such as delivering a message. It shall only be used when the attempt fails. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Message Header for an empty message. Valid only if used in a bundle (message) |
Message Header for an empty message. Valid only if used in a bundle (message). |
| Message header for care communication message. Valid only if used in a bundle (message). |
Message header for care communication message. Valid only if used in a bundle (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 |
| Provenance information for an Acknowledgement message - CareCommunication. Valid only if used in a bundle (message) |
Provenance information for an Acknowledgementmessage - CareCommunication. 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. |
| Provenance information for an Acknowledgement message - CareCommunication. Valid only if used in a bundle (message) |
Provenance information for an Acknowledgementmessage - CareCommunication. Valid only if used in a bundle (message). |
| Provenance information for an Acknowledgement message - CareCommunication. Valid only if used in a bundle (message) |
Provenance information for an Acknowledgementmessage - CareCommunication. Valid only if used in a bundle (message). |
| MedComAcknowledgementOperationOutcome - Severity is 'information' |
Example of an error operationOutcome. Valid only if used in a Bundle (message). |
| Example Acknowledgement message - Ok |
Example Acknowledgement message - Ok |
| Acknowledgement MessageHeader - ok message |
Acknowledgement MessageHeader - ok message. Valid only if used in a Bundle (message). |
| Acknowledgement MessageHeader - fatal-error message |
Acknowledgement MessageHeader - fatal-error message. Valid only if used in a Bundle (message). |
| Example Acknowledgement message - Fatal error |
Example Acknowledgement message - Fatal error |
| MedComAcknowledgementOperationOutcome - Severity is 'error' |
Example of an error operationOutcome. Valid only if used in a Bundle (message). |
| MedComAcknowledgementOperationOutcome - Severity is 'error' |
Example of an error operationOutcome. Valid only if used in a Bundle (message). |
| Acknowledgement MessageHeader - transient-error message |
Acknowledgement MessageHeader - transient-error message. Valid only if used in a Bundle (message). |
| Example Acknowledgement message - Transient error |
Example Acknowledgement message - Transient error |
| Example of a sender organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| eb26be85-fdb7-454d-a980-95cba6d1745b |
Example of an emty message. |