DK MedCom Carecommunication
4.0.2 - release
DK MedCom Carecommunication
4.0.2 - release
DK MedCom Carecommunication, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 4.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-medcom-carecommunication/ and changes regularly. 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.
| MedComCareCommunication |
Care related communication between two or more parties in Danish healthcare |
| MedComCareCommunicationMessage |
The CareCommunication is used to ensure secure electronic communication of personally identifiable information and is most often used for ad hoc communication between parties in Danish Healthcare. However, the CareCommunication shall only be used in areas where no other MedCom standard is available, and it must not be used for cases with an acute nature. |
| MedComCareCommunicationMessageDefinition |
The MessageDefinition for a CareCommunication messsage. |
| MedComCareCommunicationMessageHeader |
Message header for care communication message |
| MedComCareCommunicationProvenance |
Provenance information about the current and preceeding message. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| 1st message - Bruno Test Elmer |
1st message - Patient described with minimal information. Valid only if used in a Bundle. |
| 1st message - Bruno Test Elmer |
1st message - Patient described with minimal information. Valid only if used in a Bundle. |
| 1st message - Example of a reciever organization with a SOR and an EAN identifier. |
1st message - Example of an organization with a SOR and an EAN identifier. |
| 1st message - Example of a reciever organization with a SOR and an EAN identifier. |
1st message - Example of an organization with a SOR and an EAN identifier. |
| 1st message - Example of a sender organization with a SOR and an EAN identifier. |
1st message - Example of an organization with a SOR and an EAN identifier. |
| 1st message - Example of a sender organization with a SOR and an EAN identifier. |
1st message - Example of an organization with a SOR and an EAN identifier. |
| 1st message - Instance of Communication resource used in a new message. |
1st message - Content of care communication message. Valid only if used in a bundle (message) - new message |
| 1st message - Instance of a MessageHeader resource used in a new message. |
1st message - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message). |
| 1st message - New CareCommunication message. |
1st message - Example of a CareCommunication new message. |
| 1st message - The Provenance instance is only valid if used in a bundle (message) - new message |
1st message - The Provenance instance is only valid if used in a bundle (message) - new message |
| 2nd message - Instance of Communication resource used in a reply message. |
2nd message - Content of care communication message. Valid only if used in a bundle (message) - reply message |
| 2nd message - Instance of a MessageHeader resource used in a reply message. |
2nd message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message). |
| 2nd message - Reply CareCommunication message |
2nd message - Example of a reply to a CareCommunication message. |
| 2nd message - The Provenance instance is only valid if used in a bundle (message) - reply to new message |
2nd message - The Provenance instance is only valid if used in a bundle (message) - reply to new message |
| 3rd message - Bruno Test Elmer |
3rd message - Patient described with minimal information. Valid only if used in a Bundle. |
| 3rd message - Example of a reciever organization with a SOR and an EAN identifier. |
3rd message - Example of an organization with a SOR and an EAN identifier. |
| 3rd message - Example of a sender organization with a SOR and an EAN identifier. |
3rd message - Example of an organization with a SOR and an EAN identifier. |
| 3rd message - Instance of Communication resource used in a reply message. |
3rd message - Content of care communication message. Valid only if used in a bundle (message) - reply message |
| 3rd message - Instance of a MessageHeader resource used in a reply message. |
3rd message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message). |
| 3rd message - Reply CareCommunication message |
3rd message - Example of a reply to a CareCommunication message. |
| 3rd message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded |
3rd message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded |
| 4th message - Forward CareCommunication message |
4th message - Example of a forward CareCommunication message. |
| 4th message - Instance of Communication resource used in a forward message. |
4th message - Content of care communication message. Valid only if used in a bundle (message) - forward message |
| 4th message - Instance of a MessageHeader resource used in a forward message. |
4th message - Example of a MessageHeader in a forward CareCommunication message. Valid only if used in a bundle (message). |
| 4th message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded |
4th message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded |
| 5th message - Instance of Communication resource used in a reply message. |
5th message - Content of CareCommunication message. Valid only if used in a bundle (message) - reply message |
| 5th message - Instance of a MessageHeader resource used in a reply message. |
5th message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message). |
| 5th message - Reply CareCommunication message |
5th message - Example of a reply CareCommunication message. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| CareCommunication Flow 1 Bundle |
CareCommunication Flow 1 Bundle |
| CareCommunication Flow 1 Communication |
CareCommunication Flow 1 Communication |
| CareCommunication Flow 1 MessageHeader |
CareCommunication Flow 1 MessageHeader |
| CareCommunication Flow 1 Patient |
CareCommunication Flow 1 Patient |
| CareCommunication Flow 1 Practitioner |
CareCommunication Flow 1 Practitioner |
| CareCommunication Flow 1 PractitionerRole author |
CareCommunication Flow 1 PractitionerRole author |
| CareCommunication Flow 1 Provenance |
CareCommunication Flow 1 Provenance |
| CareCommunication Flow 1 Receiver Organization |
CareCommunication Flow 1 Receiver Organization |
| CareCommunication Flow 1 Sender Organization |
CareCommunication Flow 1 Sender Organization |
| 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 |
| CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-message |
CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-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 reciever organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| 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 reciever organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| 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 reciever organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| 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 reciever organization with a SOR and an EAN identifier. |
Example of an organization with a SOR and an EAN identifier. |
| Example of a recipient in terms of a careteam. |
Example of a recipient in terms of a careteam. |
| 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 sender 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 sender 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 sender 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. |
| Instance of Communication resource used in a new message. |
Content of care communication message. Valid only if used in a bundle (message) - new message |
| Instance of Communication resource used in a new message. The message includes a journal note and author information in the messagetext. |
Content of care communication message. Valid only if used in a bundle (message) - new message with attachment |
| Instance of Communication resource used in a reply message. A reply to an OIOXML message |
Content of care communication message. Valid only if used in a bundle (message). |
| Instance of a MessageHeader resource used in a new message with journal note in message text. |
Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message). |
| Instance of a MessageHeader resource used in a new message. |
Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message). |
| Instance of a MessageHeader resource used in a reply to an OIOXML message. |
MessageHeader for CareCommunication reply to an OIOXML message. Valid only if used in a bundle (message). |
| MedCom Core Encounter |
Example of a simple MedCom Core Encounter |
| MedCom Core Encounter |
Example of a simple MedCom Core Encounter |
| MedCom Core Encounter |
Example of a simple MedCom Core Encounter |
| New CareCommunication message. |
Example of a CareCommunication new message. |
| New CareCommunication message. Including journal note in the message text. |
Example of a CareCommunication new message with journal note in the message text. |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |
| Receive_Tek-A |
Receive_Tek-A |
| Receive_Tek-A - Communication |
Receive_Tek-A - Communication |
| Receive_Tek-A - MessageHeader |
Receive_Tek-A - MessageHeader |
| Receive_Tek-A - Patient |
Receive_Tek-A - Patient |
| Receive_Tek-A - Provenance |
Receive_Tek-A - Provenance |
| Receive_Tek-A - Receiver |
Receive_Tek-A - Receiver |
| Receive_Tek-A - Sender |
Receive_Tek-A - Sender |
| Receive_Tek-A - practitioner |
Receive_Tek-A - practitioner |
| Receive_Tek-A - practitionerRole |
Receive_Tek-A - practitionerRole |
| Receive_Tek-B |
Receive_Tek-B |
| Receive_Tek-B - Communication |
Receive_Tek-B - Communication |
| Receive_Tek-B - MessageHeader |
Receive_Tek-B - MessageHeader |
| Receive_Tek-B - Patient |
Receive_Tek-B - Patient |
| Receive_Tek-B - Provenance |
Receive_Tek-B - Provenance |
| Receive_Tek-B - Receiver |
Receive_Tek-B - Receiver |
| Receive_Tek-B - Sender |
Receive_Tek-B - Sender |
| Receive_Tek-B - practitioner |
Receive_Tek-B - practitioner |
| Receive_Tek-B - practitionerRole |
Receive_Tek-B - practitionerRole |
| Receive_Tek-C |
Receive_Tek-C |
| Receive_Tek-C - Communication |
Receive_Tek-C - Communication |
| Receive_Tek-C - MessageHeader |
Receive_Tek-C - MessageHeader |
| Receive_Tek-C - Patient |
Receive_Tek-C - Patient |
| Receive_Tek-C - Provenance |
Receive_Tek-C - Provenance |
| Receive_Tek-C - Receiver |
Receive_Tek-C - Receiver |
| Receive_Tek-C - Sender |
Receive_Tek-C - Sender |
| Receive_Tek-C - practitioner |
Receive_Tek-C - practitioner |
| Receive_Tek-C - practitionerRole |
Receive_Tek-C - practitionerRole |
| Receive_Tek-D |
Receive_Tek-D |
| Receive_Tek-D - Communication |
Receive_Tek-D - Communication |
| Receive_Tek-D - MessageHeader |
Receive_Tek-D - MessageHeader |
| Receive_Tek-D - Patient |
Receive_Tek-D - Patient |
| Receive_Tek-D - Provenance |
Receive_Tek-D - Provenance |
| Receive_Tek-D - Receiver |
Receive_Tek-D - Receiver |
| Receive_Tek-D - Sender |
Receive_Tek-D - Sender |
| Receive_Tek-D - practitioner |
Receive_Tek-D - practitioner |
| Receive_Tek-D - practitionerRole |
Receive_Tek-D - practitionerRole |
| Receive_Tek-E-new-parallel - Bruno Test Elmer |
Receive_Tek-E-new-parallel - Patient described with minimal information. Valid only if used in a Bundle. |
| Receive_Tek-E-new-parallel - Example of a reciever organization with a SOR and an EAN identifier. |
Receive_Tek-E-new-parallel - Example of an organization with a SOR and an EAN identifier. |
| Receive_Tek-E-new-parallel - Example of a sender organization with a SOR and an EAN identifier. |
Receive_Tek-E-new-parallel - Example of an organization with a SOR and an EAN identifier. |
| Receive_Tek-E-new-parallel - Instance of Communication resource used in a new message. |
Receive_Tek-E-new-parallel - Content of care communication message. Valid only if used in a bundle (message) - new message |
| Receive_Tek-E-new-parallel - Instance of a MessageHeader resource used in a new message. |
Receive_Tek-E-new-parallel - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message). |
| Receive_Tek-E-new-parallel - New CareCommunication message. |
Receive_Tek-E-new-parallel - Example of a CareCommunication new message. |
| Receive_Tek-F-reply-parallel - Instance of Communication resource used in a reply message. |
Receive_Tek-F-reply-parallel - Content of care communication message. Valid only if used in a bundle (message) - reply message |
| Receive_Tek-F-reply-parallel - Instance of a MessageHeader resource used in a reply message. |
Receive_Tek-F-reply-parallel - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message). |
| Receive_Tek-F-reply-parallel - Reply CareCommunication message |
Receive_Tek-F-reply-parallel - Example of a reply to a CareCommunication message. |
| Reply CareCommunication message. Reply to OIOXML Message |
Example of a reply to an OIOXML message. |
| Send-A-new |
Send-A-new |
| Send-A-new - Communication |
Send-A-new - Communication |
| Send-A-new - MessageHeader |
Send-A-new - MessageHeader |
| Send-A-new - Patient |
Send-A-new - Patient |
| Send-A-new - Provenance |
Send-A-new - Provenance |
| Send-A-new - Receiver |
Send-A-new - Receiver |
| Send-A-new - Sender |
Send-A-new - Sender |
| Send-A-new - Sender Careteam |
Send-A-new - Sender Careteam |
| Send-A-new - practitioner |
Send-A-new - practitioner |
| Send-A-new - practitionerRole |
Send-A-new - practitionerRole |
| Send-A-new - specifik Receiver practitioner |
Send-A-new - specifik Receiver practitioner |
| Send-A-new - specifik Receiver practitionerRole |
Send-A-new - specifik Receiver practitionerRole |
| Send-B-new |
Send-B-new |
| Send-B-new - Communication |
Send-B-new - Communication |
| Send-B-new - MessageHeader |
Send-B-new - MessageHeader |
| Send-B-new - Patient |
Send-B-new - Patient |
| Send-B-new - Provenance |
Send-B-new - Provenance |
| Send-B-new - Receiver |
Send-B-new - Receiver |
| Send-B-new - Sender |
Send-B-new - Sender |
| Send-B-new - practitioner |
Send-B-new - practitioner |
| Send-B-new - practitionerRole |
Send-B-new - practitionerRole |
| Send-C-new |
Send-C-new |
| Send-C-new - Communication |
Send-C-new - Communication |
| Send-C-new - MessageHeader |
Send-C-new - MessageHeader |
| Send-C-new - Patient |
Send-C-new - Patient |
| Send-C-new - Provenance |
Send-C-new - Provenance |
| Send-C-new - Receiver |
Send-C-new - Receiver |
| Send-C-new - Sender |
Send-C-new - Sender |
| Send-C-new - practitioner |
Send-C-new - practitioner |
| Send-C-new - practitionerRole |
Send-C-new - practitionerRole |
| Send-D-new |
Send-D-new |
| Send-D-new - Communication |
Send-D-new - Communication |
| Send-D-new - MessageHeader |
Send-D-new - MessageHeader |
| Send-D-new - Patient |
Send-D-new - Patient |
| Send-D-new - Provenance |
Send-D-new - Provenance |
| Send-D-new - Receiver |
Send-D-new - Receiver |
| Send-D-new - Sender |
Send-D-new - Sender |
| Send-D-new - practitioner |
Send-D-new - practitioner |
| Send-D-new - practitionerRole |
Send-D-new - practitionerRole |
| Send-E-forward |
Send-E-forward |
| Send-E-forward - Communication |
Send-E-forward - Communication |
| Send-E-forward - MessageHeader |
Send-E-forward - MessageHeader |
| Send-E-forward - MessageHeader |
Send-E-forward - MessageHeader |
| Send-E-forward - Patient |
Send-E-forward - Patient |
| Send-E-forward - Provenance |
Send-E-forward - Provenance |
| Send-E-forward - Provenance |
Send-E-forward - Provenance |
| Send-E-forward - Receiver |
Send-E-forward - Receiver |
| Send-E-forward - Sender |
Send-E-forward - Sender |
| Send-E-forward - practitioner |
Send-E-forward - practitioner |
| Send-E-forward - practitioner |
Send-E-forward - practitioner |
| Send-E-forward - practitionerRole |
Send-E-forward - practitionerRole |
| Send-E-forward - practitionerRole |
Send-E-forward - practitionerRole |
| Send-F-new |
Send-F-new |
| Send-Tek-A-new |
Send-Tek-A-new |
| Send-Tek-A-new - Communication |
Send-Tek-A-new - Communication |
| Send-Tek-A-new - Encounter |
Send-Tek-A-new - Encounter |
| Send-Tek-A-new - MessageHeader |
Send-Tek-A-new - MessageHeader |
| Send-Tek-A-new - Patient |
Send-Tek-A-new - Patient |
| Send-Tek-A-new - Provenance |
Send-Tek-A-new - Provenance |
| Send-Tek-A-new - Receiver |
Send-Tek-A-new - Receiver |
| Send-Tek-A-new - Sender |
Send-Tek-A-new - Sender |
| Send-Tek-A-new - practitioner |
Send-Tek-A-new - practitioner |
| Send-Tek-A-new - practitionerRole |
Send-Tek-A-new - practitionerRole |
| Send-Tek-B-new |
Send-Tek-B-new |
| Send-Tek-B-new - Communication |
Send-Tek-B-new - Communication |
| Send-Tek-B-new - Encounter |
Send-Tek-B-new - Encounter |
| Send-Tek-B-new - MessageHeader |
Send-Tek-B-new - MessageHeader |
| Send-Tek-B-new - Patient |
Send-Tek-B-new - Patient |
| Send-Tek-B-new - Provenance |
Send-Tek-B-new - Provenance |
| Send-Tek-B-new - Receiver |
Send-Tek-B-new - Receiver |
| Send-Tek-B-new - Sender |
Send-Tek-B-new - Sender |
| Send-Tek-B-new - practitioner |
Send-Tek-B-new - practitioner |
| Send-Tek-B-new - practitionerRole |
Send-Tek-B-new - practitionerRole |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| Simple practitioner with a name |
Simple practitioner with a name |
| receive-C-forward-receive_C-forward |
receive_C-forward |
| receive-Tek-G |
receive-Tek-G |
| receive-Tek-G - Communication |
receive-Tek-G - Communication |
| receive-Tek-G - MessageHeader |
receive-Tek-G - MessageHeader |
| receive-Tek-G - Patient |
receive-Tek-G - Patient |
| receive-Tek-G - Provenance |
receive-Tek-G - Provenance |
| receive-Tek-G - Receiver |
receive-Tek-G - Receiver |
| receive-Tek-G - Sender |
receive-Tek-G - Sender |
| receive-Tek-G - practitioner |
receive-Tek-G - practitioner |
| receive-Tek-G - practitionerRole |
receive-Tek-G - practitionerRole |
| receive-Tek-H - Instance of Communication resource used in a reply message. |
receive-Tek-H - Content of care communication message. Valid only if used in a bundle (message) - reply message |
| receive-Tek-H - Instance of a MessageHeader resource used in a reply message. |
receive-Tek-H - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message). |
| receive-Tek-H - Reply CareCommunication message |
receive-Tek-H - Example of a reply to a CareCommunication message. |
| receive-Tek-I - Example of a reciever organization with a SOR and an EAN identifier. |
receive-Tek-I - Example of an organization with a SOR and an EAN identifier. |
| receive-Tek-I - Example of a sender organization with a SOR and an EAN identifier. |
receive-Tek-I - Example of an organization with a SOR and an EAN identifier. |
| receive-Tek-I - Instance of Communication resource used in a new message. |
receive-Tek-I - Content of care communication message. Valid only if used in a bundle (message) - new message |
| receive-Tek-I - Instance of a MessageHeader resource used in a new message. |
receive-Tek-I - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message). |
| receive-Tek-I - New CareCommunication message. |
receive-Tek-I - Example of a CareCommunication new message. |
| receive-Tek-I - Peter Hansen |
receive-Tek-I - Patient described with minimal information. Valid only if used in a Bundle. |
| receive-Tek-J-duplicate |
receive-Tek-J-duplicate |
| receive-Tek-J-duplicate - Communication |
receive-Tek-J-duplicate - Communication |
| receive-Tek-J-duplicate - MessageHeader |
receive-Tek-J-duplicate - MessageHeader |
| receive-Tek-J-duplicate - Patient |
receive-Tek-J-duplicate - Patient |
| receive-Tek-J-duplicate - Provenance |
receive-Tek-J-duplicate - Provenance |
| receive-Tek-J-duplicate - Receiver |
receive-Tek-J-duplicate - Receiver |
| receive-Tek-J-duplicate - Sender |
receive-Tek-J-duplicate - Sender |
| receive-Tek-J-duplicate - practitioner |
receive-Tek-J-duplicate - practitioner |
| receive-Tek-J-duplicate - practitionerRole |
receive-Tek-J-duplicate - practitionerRole |
| receive-Tek-K-dublicate |
receive-Tek-K-dublicate |
| receive-Tek-M-new-dublicate-inv |
receive-Tek-M-new-dublicate-inv |
| receive-Tek-M-new-dublicate-inv - Communication |
receive-Tek-M-new-dublicate-inv - Communication |
| receive-Tek-M-new-dublicate-inv - MessageHeader |
receive-Tek-M-new-dublicate-inv - MessageHeader |
| receive-Tek-M-new-dublicate-inv - Patient |
receive-Tek-M-new-dublicate-inv - Patient |
| receive-Tek-M-new-dublicate-inv - Provenance |
receive-Tek-M-new-dublicate-inv - Provenance |
| receive-Tek-M-new-dublicate-inv - Receiver |
receive-Tek-M-new-dublicate-inv - Receiver |
| receive-Tek-M-new-dublicate-inv - Sender |
receive-Tek-M-new-dublicate-inv - Sender |
| receive-Tek-M-new-dublicate-inv - practitioner |
receive-Tek-M-new-dublicate-inv - practitioner |
| receive-Tek-M-new-dublicate-inv - practitionerRole |
receive-Tek-M-new-dublicate-inv - practitionerRole |
| receive-Tek-N-dublicate-invalid |
receive-Tek-N-dublicate-invalid |
| receive-Tek-O-invalid |
receive-Tek-O-invalid |
| receive-Tek-O-invalid - Communication |
receive-Tek-O-invalid - Communication |
| receive-Tek-O-invalid - MessageHeader |
receive-Tek-O-invalid - MessageHeader |
| receive-Tek-O-invalid - Patient |
receive-Tek-O-invalid - Patient |
| receive-Tek-O-invalid - Provenance |
receive-Tek-O-invalid - Provenance |
| receive-Tek-O-invalid - Receiver |
receive-Tek-O-invalid - Receiver |
| receive-Tek-O-invalid - Sender |
receive-Tek-O-invalid - Sender |
| receive-Tek-O-invalid - practitioner |
receive-Tek-O-invalid - practitioner |
| receive-Tek-O-invalid - practitionerRole |
receive-Tek-O-invalid - practitionerRole |
| receive_A-new |
receive_A-new |
| receive_A-new - Communication |
receive_A-new - Communication |
| receive_A-new - MessageHeader |
receive_A-new - MessageHeader |
| receive_A-new - Patient |
receive_A-new - Patient |
| receive_A-new - Provenance |
receive_A-new - Provenance |
| receive_A-new - Receiver |
receive_A-new - Receiver |
| receive_A-new - Sender |
receive_A-new - Sender |
| receive_A-new - Sender Careteam |
receive_A-new - Sender Careteam |
| receive_A-new - practitioner |
receive_A-new - practitioner |
| receive_A-new - practitionerRole |
receive_A-new - practitionerRole |
| receive_A-new - specifik Receiver practitioner |
receive_A-new - specifik Receiver practitioner |
| receive_A-new - specifik Receiver practitionerRole |
receive_A-new - specifik Receiver practitionerRole |
| receive_B-reply |
receive_B-reply |
| receive_B-reply |
receive_B-reply |
| receive_B-reply |
receive_B-reply |
| receive_C-forward |
receive_C-forward |
| receive_C-forward |
receive_C-forward |
| receive_C-forward |
receive_C-forward |
| receive_C-forward - Patient |
receive_C-forward - Patient |
| receive_C-forward - Provenance |
receive_C-forward - Provenance |
| receive_C-forward - Receiver |
receive_C-forward - Receiver |
| receive_C-forward - Sender |
receive_C-forward - Sender |
| receive_C-forward - practitioner |
receive_C-forward - practitioner |
| receive_C-forward - practitionerRole |
receive_C-forward - practitionerRole |
| receive_Tek-L-dublicate |
receive_Tek-L-dublicate |
| receive_Tek-L-dublicate - Communication |
receive_Tek-L-dublicate - Communication |
| receive_Tek-L-dublicate - MessageHeader |
receive_Tek-L-dublicate - MessageHeader |
| receive_Tek-L-dublicate - Patient |
receive_Tek-L-dublicate - Patient |
| receive_Tek-L-dublicate - Provenance |
receive_Tek-L-dublicate - Provenance |
| receive_Tek-L-dublicate - Receiver |
receive_Tek-L-dublicate - Receiver |
| receive_Tek-L-dublicate - Sender |
receive_Tek-L-dublicate - Sender |
| receive_Tek-L-dublicate - practitioner |
receive_Tek-L-dublicate - practitioner |
| receive_Tek-L-dublicate - practitionerRole |
receive_Tek-L-dublicate - practitionerRole |