eHealth Infrastructure
10.0.0 - release Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 10.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

Resource Profile: ehealth-carecommunication

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication Version: 10.0.0
Active as of 2026-08-05 Computable Name: ehealth-carecommunication

Introduction

An Ehealth-CareCommunication is an FUT abstraction of a MedCom CareCommunication. This is needed to support communication through the VANS network with parties outside the FUT infrastructure, as well as inside FUT. The Ehealth-CareCommunication's primary feature is to enable communication in relation to several images of different file types.

Remarks about status and administrative-status

  • status:
    • A message is considered "not yet sent" when it has one of the following status and can freely transition from one to another: 'preparation', 'on-hold', 'not-done', 'entered-in-error'
    • A message is considered "being sent" when created or patched into status 'in-progress' and cannot be patched further or deleted by the sender
    • The server will automatically transition a message from 'in-progress' to 'completed' when it has been sent successfully (happens when the Vans-Relay has received a positive acknowledgement on the send message)
    • The server will automatically transition a message from 'in-progress' to 'stopped' if it could not be sent (happens when the Vans-Relay has received a negative acknowledgement on the send message, or at 3 failed attempts at sending)
    • The client can never create or patch a message into status 'completed' or 'stopped'
    • The sender cannot patch, only delete messages with status 'stopped'
    • The sender cannot patch or delete messages with status 'completed'
    • The recipient can patch /received and administrative-status on messages with status 'completed'
  • administrative-status (extension): Makes it possible for the message recipient to indicate the state of a message. A message may hold an administrative status that defines the last action the recipient took on the message in question. At first, the message has administrative-status "activate". The recipient may mark the message as read by setting administrative-status "read". If the recipient considers the message a sort of "task", the message may also be updated with administrative-status "complete" when the task is done, or "reactivate" if the task was not complete anyway.

Search parameters

The following custom search parameters may be used when searching for ehealth-CareCommunication instances:

  • administrativeStatus: Specify the desired administrative status using system and code (eg. "http://ehealth.sundhed.dk/cs/administrative-status" and "read")
  • careCommunicationSenderPractitioner: Specify an absolute reference to the Practitioner that must be the sender of the message (the Practitioner linked in the sender extension)
  • careCommunicationSenderCareTeam: Specify an absolute reference to the CareTeam that is the sender of the message (the CareTeam linked in the sender extension)
  • communicationCategory: Specify the desired category using system and code (eg. "http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category" and "nursing")
  • topic: Specify the desired topic. For CareCommunication the topic is provided as free text (topic.text), so use a text search

Scope and Usage

In the eHealth Infrastructure the ehealth-CareCommunication resource is used in conjunction with the following resources:

  • Patient
    • As a subject of a message
  • PractitionerRole
    • As specific sender/recipient of a message
  • Practitioner
    • the Practitioner of the PractitionerRole
  • CareTeam
    • as specific sender/recipient of a message
  • Organization
    • as sender/recipient of a message

note on sender: The sender of a message is structured as a complex extension, holding a reference to the sending PractitionerRole, the linked Practitioner and optional CareTeam. If a CareTeam is present, that CareTeam is considered the specific sender, not the PractitionerRole. PractitionerRole is still required, since every message has to have a PractitionerRole representing that message.

General rules

  • The sender/receiver Organizations have to have both a SOR and GLN (EAN) identifier to be eligible for VANS communication.
  • If the message type is Forward, you as a sender have to pick which payloads should be included in the message.
  • If the message type is Reply, the message will be populated automatically with all prior payloads of the given conversation.
  • The Communication identifier is the same for all Ehealth-CareCommunications of the same conversation. A new Communication Id is needed for a Forward message type, even though bundles from a prior conversation are included.
  • The MessageHeader identifier is set for received messages, as client-side assignment of id's is not possible. For messages sent from the FUT infrastructure, it is not needed. The reasoning for the use of this identifier is that the correlating MedCom model for Ehealth-CareCommunications identifies specific messages based on the MessageHeader identifier.
  • inResponseTo has to be included for Reply messages. It points to the previous MessageHeader identifier in the conversation if present, otherwise Ehealth-CareCommunication.id.
  • If category is other, the topic.text element has to be populated.
  • recipient can be excluded, which means the message is considered sent to the destination organization.

Usages:

  • CapabilityStatements using this Profile: patient
  • This Profile is not used by any profiles in this Specification

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
.... identifier:communicationId SΣC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value SΣ 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
Example General: 123456
.... identifier:messageHeaderId SΣ 0..1 Identifier The ID of the originating MessageHeader resource
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value SΣ 1..1 string The value that is unique
Example General: 123456
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status ?!SΣ 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... coding SΣ 1..1 Coding Code defined by a terminology system
..... system SΣ 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... code SΣ 1..1 code Symbol in syntax defined by the system
... priority SΣ 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... subject SΣ 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
.... text SΣ 1..1 string Plain text representation of the concept.
... encounter SΣ 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] 1..1 Message part content
...... contentString string
...... contentAttachment Attachment
...... contentReference Reference(Resource)
.... payload:string 1..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Closed by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] S 1..1 Attachment Message part content
...... contentType SΣ 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
Example General: text/plain; charset=UTF-8, image/png
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url SΣ 0..1 url Shall be present if the attachment is a link to a web page.
Example General: http://www.acme.com/logo-small.png
...... title SΣ 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
Example General: Official Corporate Logo
...... creation SΣ 0..1 dateTime The time the attachment was created

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​use Base required IdentifierUse 📍4.0.1 FHIR Std.
Communication.status Base required EventStatus 📍4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.topic Base example CommunicationTopic 📍4.0.1 FHIR Std.
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... Slices for identifier S 1..2 Identifier Unique identifier
Slice: Unordered, Open by value:system
.... identifier:communicationId SC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... use 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... system S 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value S 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
.... identifier:messageHeaderId S 0..1 Identifier The ID of the originating MessageHeader resource
..... system S 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value S 1..1 string The value that is unique
... basedOn 0..0 Request fulfilled by this communication
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status S 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... coding S 1..1 Coding Code defined by a terminology system
..... system S 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... code S 1..1 code Symbol in syntax defined by the system
... priority S 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... subject S 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
.... text S 1..1 string Plain text representation of the concept.
... encounter S 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... sender 0..0 Message sender
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:string 1..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Open by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... content[x] S 1..1 Attachment Message part content
...... contentType S 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url S 0..1 url Shall be present if the attachment is a link to a web page.
...... title S 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
...... creation S 0..1 dateTime The time the attachment was created

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... Slices for identifier SΣ 1..2 Identifier Unique identifier
Slice: Unordered, Open by value:system
.... identifier:communicationId SΣC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... type Σ 0..1 CodeableConcept Description of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value SΣ 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
Example General: 123456
..... period Σ 0..1 Period Time period when id is/was valid for use
..... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
.... identifier:messageHeaderId SΣ 0..1 Identifier The ID of the originating MessageHeader resource
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
..... type Σ 0..1 CodeableConcept Description of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value SΣ 1..1 string The value that is unique
Example General: 123456
..... period Σ 0..1 Period Time period when id is/was valid for use
..... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
... instantiatesCanonical Σ 0..* canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status ?!SΣ 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.
... statusReason Σ 0..1 CodeableConcept Reason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... coding SΣ 1..1 Coding Code defined by a terminology system
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... system SΣ 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... version Σ 0..1 string Version of the system - if relevant
..... code SΣ 1..1 code Symbol in syntax defined by the system
..... display Σ 0..1 string Representation defined by the system
..... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
.... text Σ 0..1 string Plain text representation of the concept
... priority SΣ 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... medium 0..* CodeableConcept A channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject SΣ 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ 0..* Coding Code defined by a terminology system
.... text SΣ 1..1 string Plain text representation of the concept.
... about 0..* Reference(Resource) Resources that pertain to this communication
... encounter SΣ 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... sent 0..1 dateTime When sent
... received 0..1 dateTime When received
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... reasonCode Σ 0..* CodeableConcept Indication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Why was communication done?
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:All Slices Content/Rules for all slices
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] 1..1 Message part content
...... contentString string
...... contentAttachment Attachment
...... contentReference Reference(Resource)
.... payload:string 1..* BackboneElement Message payload
..... id 0..1 string Unique id for inter-element referencing
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Closed by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... id 0..1 string Unique id for inter-element referencing
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] S 1..1 Attachment Message part content
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... contentType SΣ 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
Example General: text/plain; charset=UTF-8, image/png
...... language Σ 0..1 code Human language of the content (BCP-47)
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding

Example General: en-AU
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url SΣ 0..1 url Shall be present if the attachment is a link to a web page.
Example General: http://www.acme.com/logo-small.png
...... size Σ 0..1 unsignedInt Number of bytes of content (if url provided)
...... hash Σ 0..1 base64Binary Hash of the data (sha-1, base64ed)
...... title SΣ 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
Example General: Official Corporate Logo
...... creation SΣ 0..1 dateTime The time the attachment was created
... note 0..* Annotation Comments made about the communication

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Communication.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.identifier:communicationId.​type Base extensible IdentifierType 📍4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​use Base required IdentifierUse 📍4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​type Base extensible IdentifierType 📍4.0.1 FHIR Std.
Communication.status Base required EventStatus 📍4.0.1 FHIR Std.
Communication.statusReason Base example CommunicationNotDoneReason 📍4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.medium Base example ParticipationMode 📦3.0.0 THO v7.3
Communication.topic Base example CommunicationTopic 📍4.0.1 FHIR Std.
Communication.reasonCode Base example SNOMED CT Clinical Findings 📍4.0.1 FHIR Std.
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG
Communication.payload:attachment.​content[x].language Base preferred Common Languages 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')

This structure is derived from Communication

Summary

Mandatory: 18 elements(6 nested mandatory elements)
Must-Support: 34 elements
Prohibited: 3 elements

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Communication.identifier
  • The element 1 is sliced based on the value of Communication.payload
  • The element 1 is sliced based on the value of Communication.payload.content[x]

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
.... identifier:communicationId SΣC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value SΣ 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
Example General: 123456
.... identifier:messageHeaderId SΣ 0..1 Identifier The ID of the originating MessageHeader resource
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value SΣ 1..1 string The value that is unique
Example General: 123456
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status ?!SΣ 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... coding SΣ 1..1 Coding Code defined by a terminology system
..... system SΣ 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... code SΣ 1..1 code Symbol in syntax defined by the system
... priority SΣ 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... subject SΣ 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
.... text SΣ 1..1 string Plain text representation of the concept.
... encounter SΣ 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] 1..1 Message part content
...... contentString string
...... contentAttachment Attachment
...... contentReference Reference(Resource)
.... payload:string 1..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Closed by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] S 1..1 Attachment Message part content
...... contentType SΣ 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
Example General: text/plain; charset=UTF-8, image/png
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url SΣ 0..1 url Shall be present if the attachment is a link to a web page.
Example General: http://www.acme.com/logo-small.png
...... title SΣ 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
Example General: Official Corporate Logo
...... creation SΣ 0..1 dateTime The time the attachment was created

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​use Base required IdentifierUse 📍4.0.1 FHIR Std.
Communication.status Base required EventStatus 📍4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.topic Base example CommunicationTopic 📍4.0.1 FHIR Std.
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')

Differential View

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... Slices for identifier S 1..2 Identifier Unique identifier
Slice: Unordered, Open by value:system
.... identifier:communicationId SC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... use 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... system S 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value S 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
.... identifier:messageHeaderId S 0..1 Identifier The ID of the originating MessageHeader resource
..... system S 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value S 1..1 string The value that is unique
... basedOn 0..0 Request fulfilled by this communication
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status S 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... coding S 1..1 Coding Code defined by a terminology system
..... system S 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... code S 1..1 code Symbol in syntax defined by the system
... priority S 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... subject S 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
.... text S 1..1 string Plain text representation of the concept.
... encounter S 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... sender 0..0 Message sender
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:string 1..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Open by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... content[x] S 1..1 Attachment Message part content
...... contentType S 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url S 0..1 url Shall be present if the attachment is a link to a web page.
...... title S 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
...... creation S 0..1 dateTime The time the attachment was created

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication C 0..* Communication A record of information transmitted from a sender to a receiver
Constraints: stopped-status-statusReason, only-asap-or-routine, topic-required-when-category-other, priority-category-invariant, atLeastOnePayloadString, payloadAttachment-contentType-required, no-standard-sender, sender-required-based-on-messagetype, sender-contactPoint-required-based-on-messagetype, reply-requires-inResponseTo, forward-prohibits-inResponseTo
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... Slices for extension 4..* Extension Extension
Slice: Unordered, Open by value:url
.... extension:sender S 0..1 (Complex) Sender Extension, contains the sending PractitionerRole, Practitioner and CareTeam.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender
.... extension:destination S 1..1 Reference(Organization) Organization receiving the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-destination
.... extension:origin S 1..1 Reference(Organization) Reference to the sending organization of the message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-origin
.... extension:messageType S 1..1 Coding Message type
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type
Binding: Message Type ValueSet (required)
.... extension:administrativeStatus 1..1 Coding The administrative status of how a message recipient has handled a message
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-administrative-status
Binding: Administrative Status (required)
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... Slices for identifier SΣ 1..2 Identifier Unique identifier
Slice: Unordered, Open by value:system
.... identifier:communicationId SΣC 1..1 Identifier The communication identifier
Constraints: uuidv4
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required)
..... type Σ 0..1 CodeableConcept Description of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/id/ehealth-carecommunication-identifier
..... value SΣ 1..1 string UUID v4 in URN form (urn:uuid:<uuid>)
Example General: 123456
..... period Σ 0..1 Period Time period when id is/was valid for use
..... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
.... identifier:messageHeaderId SΣ 0..1 Identifier The ID of the originating MessageHeader resource
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... use ?!Σ 0..1 code usual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
..... type Σ 0..1 CodeableConcept Description of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
..... system SΣ 1..1 uri The namespace for the identifier value
Required Pattern: http://ehealth.sundhed.dk/fhir/system/medcom-message-header-id
..... value SΣ 1..1 string The value that is unique
Example General: 123456
..... period Σ 0..1 Period Time period when id is/was valid for use
..... assigner Σ 0..1 Reference(Organization) Organization that issued id (may be just text)
... instantiatesCanonical Σ 0..* canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... inResponseTo S 0..1 Reference(Communication) references the Ehealth-CareCommunication Communication.id, which this message is a response to.
... status ?!SΣ 1..1 code preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.
... statusReason Σ 0..1 CodeableConcept Reason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.
... category S 1..1 CodeableConcept Message category
Binding: eHealth CareCommunication Categories (required)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... coding SΣ 1..1 Coding Code defined by a terminology system
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
..... system SΣ 1..1 uri Identity of the terminology system
Required Pattern: http://ehealth.sundhed.dk/cs/ehealth-carecommunication-category
..... version Σ 0..1 string Version of the system - if relevant
..... code SΣ 1..1 code Symbol in syntax defined by the system
..... display Σ 0..1 string Representation defined by the system
..... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
.... text Σ 0..1 string Plain text representation of the concept
... priority SΣ 0..1 code Only used when the category is 'regarding referral', see priority-category-invariant.
Binding: eHealth CareCommunication Priorities (required)
... medium 0..* CodeableConcept A channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject SΣ 1..1 Reference(Patient) Focus of message
... topic S 0..1 CodeableConcept Must be added when category is "other". Topic must be added in the text-element.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ 0..* Coding Code defined by a terminology system
.... text SΣ 1..1 string Plain text representation of the concept.
... about 0..* Reference(Resource) Resources that pertain to this communication
... encounter SΣ 0..1 Reference(Encounter) Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... sent 0..1 dateTime When sent
... received 0..1 dateTime When received
... recipient S 0..1 Reference(CareTeam | PractitionerRole) The recieving actor of the message
... reasonCode Σ 0..* CodeableConcept Indication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Why was communication done?
... Slices for payload 1..* BackboneElement Message payload
Slice: Unordered, Open by type:$this.content
.... payload:All Slices Content/Rules for all slices
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] 1..1 Message part content
...... contentString string
...... contentAttachment Attachment
...... contentReference Reference(Resource)
.... payload:string 1..* BackboneElement Message payload
..... id 0..1 string Unique id for inter-element referencing
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... Slices for content[x] 1..1 string Message part content
Slice: Unordered, Closed by type:$this
..... Slices for content[x] Content/Rules for all slices
...... content[x]:contentString S 1..1 string Message part content
.... payload:attachment 0..* BackboneElement Message payload
..... id 0..1 string Unique id for inter-element referencing
..... Slices for extension 2..* Extension Extension
Slice: Unordered, Open by value:url
..... Slices for extension Content/Rules for all slices
...... extension:date S 1..1 dateTime Payload dateTime
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-datetime
...... extension:identifier S 1..1 Identifier Identifier Extension
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-payload-identifier
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... content[x] S 1..1 Attachment Message part content
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... contentType SΣ 0..1 code The content type shall be present when the content is an attachment included in the data element.
Binding: eHealth CareCommunication Attachment MIME Types (required)
Example General: text/plain; charset=UTF-8, image/png
...... language Σ 0..1 code Human language of the content (BCP-47)
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding

Example General: en-AU
...... data S 0..1 base64Binary Shall be present and contain the base64 encoded content of the attachment.
...... url SΣ 0..1 url Shall be present if the attachment is a link to a web page.
Example General: http://www.acme.com/logo-small.png
...... size Σ 0..1 unsignedInt Number of bytes of content (if url provided)
...... hash Σ 0..1 base64Binary Hash of the data (sha-1, base64ed)
...... title SΣ 1..1 string Note: it is not allowed for the system to automatically include '.filetype' in the title.
Example General: Official Corporate Logo
...... creation SΣ 0..1 dateTime The time the attachment was created
... note 0..* Annotation Comments made about the communication

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Communication.language Base preferred Common Languages 📍4.0.1 FHIR Std.
Communication.identifier:communicationId.​use Base required IdentifierUse 📦4.0.1 FHIR Std.
Communication.identifier:communicationId.​type Base extensible IdentifierType 📍4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​use Base required IdentifierUse 📍4.0.1 FHIR Std.
Communication.identifier:messageHeaderId.​type Base extensible IdentifierType 📍4.0.1 FHIR Std.
Communication.status Base required EventStatus 📍4.0.1 FHIR Std.
Communication.statusReason Base example CommunicationNotDoneReason 📍4.0.1 FHIR Std.
Communication.category Base required eHealth CareCommunication Categories 📦10.0.0 This IG
Communication.priority Base required eHealth CareCommunication Priorities 📦10.0.0 This IG
Communication.medium Base example ParticipationMode 📦3.0.0 THO v7.3
Communication.topic Base example CommunicationTopic 📍4.0.1 FHIR Std.
Communication.reasonCode Base example SNOMED CT Clinical Findings 📍4.0.1 FHIR Std.
Communication.payload:attachment.​content[x].contentType Base required eHealth CareCommunication Attachment MIME Types 📦10.0.0 This IG
Communication.payload:attachment.​content[x].language Base preferred Common Languages 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
atLeastOnePayloadString error Communication At least one payload segment shall have a message text (payload.contentString) payload.contentString.exists()
forward-prohibits-inResponseTo error Communication If messageType is 'forward-message', inResponseTo SHALL be empty. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'forward-message').exists() implies inResponseTo.empty()
no-standard-sender error Communication The standard Communication.sender element SHALL NOT be used. Use the ehealth-carecommunication-sender extension instead. sender.empty()
only-asap-or-routine error Communication priority must be either 'asap' or 'routine' priority.empty() or priority = 'asap' or priority = 'routine'
payloadAttachment-contentType-required error Communication contentType SHALL be present when the attachment content is in the data element. It is not required for url-only attachments. payload.contentAttachment.data.exists() implies payload.contentAttachment.contentType.exists()
priority-category-invariant error Communication Priority must not be present when category is not 'regarding-referral'. category.coding.code = 'regarding-referral' or priority.empty()
reply-requires-inResponseTo error Communication If messageType is 'reply-message', inResponseTo SHALL be populated. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'reply-message').exists() implies inResponseTo.exists()
sender-contactPoint-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must carry a contactPoint. If 'forward', it may be absent. Mirrors MedCom's required authorContact on the outbound message. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').extension('contactPoint').exists()
sender-required-based-on-messagetype error Communication If messagetype is 'new' or 'reply', the sender extension must be present. If 'forward', sender may be absent. extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-message-Type').value.where(code = 'new-message' or code = 'reply-message').exists() implies extension('http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-carecommunication-sender').exists()
stopped-status-statusReason error Communication If status is 'stopped', statusReason must be either 'system-error' or 'recipient-unavailable'. status != 'stopped' or statusReason.coding.where(code = 'system-error' or code = 'recipient-unavailable').exists()
topic-required-when-category-other error Communication topic must be present when category is 'other'. iif(category.coding.code != 'other', true, category.coding.code = 'other' and topic.exists())
uuidv4 error Communication.identifier:communicationId identifier.value SHALL be a valid UUID v4 in URN form (urn:uuid:<uuid>) value.matches('^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$')

This structure is derived from Communication

Summary

Mandatory: 18 elements(6 nested mandatory elements)
Must-Support: 34 elements
Prohibited: 3 elements

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Communication.identifier
  • The element 1 is sliced based on the value of Communication.payload
  • The element 1 is sliced based on the value of Communication.payload.content[x]

 

Other representations of profile: CSV, Excel, Schematron