DK MedCom Carecommunication
3.0.0 - release Denmark flag

This page is part of the DK MedCom CareCommunication (v3.0.0: 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

Table of Contents

...0 Table of Contents
...1 Home
...2 Downloads
...3 Extensions
...4 Profiles
....5 Artifacts Summary
....5.1 MedComCareCommunication
....5.2 MedComCareCommunicationMessage
....5.3 MedComCareCommunicationMessageHeader
....5.4 Bruno Test Elmer
....5.5 Bruno Test Elmer
....5.6 Bruno Test Elmer
....5.7 Bruno Test Elmer
....5.8 Bruno Test Elmer
....5.9 Bruno Test Elmer
....5.10 Bruno Test Elmer
....5.11 Bruno Test Elmer
....5.12 Bruno Test Elmer
....5.13 Bruno Test Elmer
....5.14 Cancel CareCommunication message
....5.15 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.16 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.17 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.18 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.19 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.20 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
....5.21 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message being forwarded
....5.22 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to new message
....5.23 CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-message
....5.24 Example of a reciever organization with a SOR and an EAN identifier.
....5.25 Example of a reciever organization with a SOR and an EAN identifier.
....5.26 Example of a reciever organization with a SOR and an EAN identifier.
....5.27 Example of a reciever organization with a SOR and an EAN identifier.
....5.28 Example of a reciever organization with a SOR and an EAN identifier.
....5.29 Example of a reciever organization with a SOR and an EAN identifier.
....5.30 Example of a reciever organization with a SOR and an EAN identifier.
....5.31 Example of a reciever organization with a SOR and an EAN identifier.
....5.32 Example of a reciever organization with a SOR and an EAN identifier.
....5.33 Example of a reciever organization with a SOR and an EAN identifier.
....5.34 Example of a reciever organization with a SOR and an EAN identifier.
....5.35 Example of a recipient in terms of a careteam.
....5.36 Example of a sender in terms of a careteam.
....5.37 Example of a sender organization with a SOR and an EAN identifier.
....5.38 Example of a sender organization with a SOR and an EAN identifier.
....5.39 Example of a sender organization with a SOR and an EAN identifier.
....5.40 Example of a sender organization with a SOR and an EAN identifier.
....5.41 Example of a sender organization with a SOR and an EAN identifier.
....5.42 Example of a sender organization with a SOR and an EAN identifier.
....5.43 Example of a sender organization with a SOR and an EAN identifier.
....5.44 Example of a sender organization with a SOR and an EAN identifier.
....5.45 Example of a sender organization with a SOR and an EAN identifier.
....5.46 Example of a sender organization with a SOR and an EAN identifier.
....5.47 Forward CareCommunication message
....5.48 Instance of a MessageHeader resource used in a forward message.
....5.49 Instance of a MessageHeader resource used in a modify message.
....5.50 Instance of a MessageHeader resource used in a new message with attachment.
....5.51 Instance of a MessageHeader resource used in a new message with formatted message text.
....5.52 Instance of a MessageHeader resource used in a new message with journal note in message text.
....5.53 Instance of a MessageHeader resource used in a new message with priority.
....5.54 Instance of a MessageHeader resource used in a new message with sender and recipient.
....5.55 Instance of a MessageHeader resource used in a new message.
....5.56 Instance of a MessageHeader resource used in a reply message.
....5.57 Instance of a MessageHeader resource used in a reply to an OIOXML message.
....5.58 Instance of a MessageHeader resource used in a retract message.
....5.59 Instance of Communication resource used in a cancel message.
....5.60 Instance of Communication resource used in a forward message.
....5.61 Instance of Communication resource used in a modify message.
....5.62 Instance of Communication resource used in a new message.
....5.63 Instance of Communication resource used in a new message.
....5.64 Instance of Communication resource used in a new message. The message includes a journal note and author information in the messagetext.
....5.65 Instance of Communication resource used in a new message. The message includes a sender and recipient.
....5.66 Instance of Communication resource used in a new message. The message includes an pdf-attachment and author information as structured data.
....5.67 Instance of Communication resource used in a new message. The message includes priority.
....5.68 Instance of Communication resource used in a new message. The messagetext includes XHTML-subset formatting.
....5.69 Instance of Communication resource used in a reply message.
....5.70 Instance of Communication resource used in a reply message. A reply to an OIOXML message
....5.71 MedCom Core Encounter
....5.72 Modify CareCommunication message
....5.73 New CareCommunication message.
....5.74 New CareCommunication message. Including an attachment
....5.75 New CareCommunication message. Including journal note in the message text.
....5.76 New CareCommunication message. Including priority
....5.77 New CareCommunication message. Including sender and recipient
....5.78 New CareCommunication message. Including XHTML-formatted message text
....5.79 PractitionerRole with a role and reference to a practitioner
....5.80 PractitionerRole with a role and reference to a practitioner
....5.81 PractitionerRole with a role and reference to a practitioner
....5.82 PractitionerRole with a role and reference to a practitioner
....5.83 PractitionerRole with a role and reference to a practitioner
....5.84 PractitionerRole with a role and reference to a practitioner
....5.85 PractitionerRole with a role and reference to a practitioner
....5.86 PractitionerRole with a role and reference to a practitioner
....5.87 PractitionerRole with a role and reference to a practitioner
....5.88 PractitionerRole with a role and reference to a practitioner
....5.89 PractitionerRole with a role and reference to a practitioner
....5.90 PractitionerRole with a role and reference to a practitioner
....5.91 PractitionerRole with a role and reference to a practitioner
....5.92 Reply CareCommunication message
....5.93 Reply CareCommunication message. Reply to OIOXML Message
....5.94 Simple practitioner with a name
....5.95 Simple practitioner with a name
....5.96 Simple practitioner with a name
....5.97 Simple practitioner with a name
....5.98 Simple practitioner with a name
....5.99 Simple practitioner with a name
....5.100 Simple practitioner with a name
....5.101 Simple practitioner with a name
....5.102 Simple practitioner with a name
....5.103 Simple practitioner with a name
....5.104 Simple practitioner with a name
....5.105 Simple practitioner with a name
....5.106 Simple practitioner with a name