eHealth Infrastructure
2.10.0 - release

eHealth Infrastructure - Local Development build (v2.10.0). See the Directory of published versions

Resource Profile: ehealth-communication

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication Version: 2.10.0
Active as of 2023-10-24 Computable Name: ehealth-communication

Introduction

The FHIR resource Communication is a record of a communication. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver.

This profile, the ehealth-communication, is intended for use of the FHIR Communication for capturing an annotation about a measurement. Such an annotation could for example describe circumstances about a particular Observation, QuestionnaireResponse or Media submitted by a Patient.

Scope and Usage

In the eHealth infrastructure, the annotation is defined using the following elements:

  • sender refers to the creator and owner of the annotation
  • ehealth-communication-senderCareTeam has same function as sender but is used where the creator and owner is one or more CareTeams
  • recipient refers to the entities allowed to read the annotation
  • ehealth-communication-recipientCareTeam has same function as recipient but is used where the allowed reading entity is one or more CareTeams
  • ehealth-restriction-category indicates, when ehealth-communication-senderCareTeam and/or ehealth-communication-recipientCareTeam refer to one or more CareTeams, what workflow areas/responsibilities of members of those CareTeams that the annotation is relevant for.
  • topic refers to the measurement which the annotation is about. This can be zero or more Observation, zero or more QuestionnaireResponse and zero or more Media. At least one of Observation, QuestionnaireResponse or Media should be referred for the annotation to make sense.
  • payload contains the annotation text itself

Boundaries and Relationships

In scope of the eHealth infrastructure, FHIR Communication is also used in the profile ehealth-message where a FHIR Communication captures written communication in the form of messages, notifications and advises. The ehealth-message profile is also used for personal notes.

A personal note differ from an annotation in that the latter is specific for measurements where the former has broader scope.

Usage:

  • This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

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

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... recipientCareTeam 0..*Reference()CareTeam message recipient
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-recipientCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... basedOn 0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf 0..*Reference(Resource) {r}Part of this action
... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... subject 1..1Reference(ehealth-patient) {r}Focus of message
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonReference 0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?
... payload
.... contentString 1..1stringMessage part content

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)
NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... senderCareTeam 0..*Reference(ehealth-careteam) {r}CareTeam message sender
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-senderCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... basedOn Σ0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf Σ0..*Reference(Resource) {r}Part of this action
... status ?!Σ1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.

... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... subject Σ1..1Reference(ehealth-patient) {r}Focus of message
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonReference Σ0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Communication.statusrequiredEventStatus
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)
NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... recipientCareTeam 0..*Reference()CareTeam message recipient
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-recipientCareTeam
... senderCareTeam 0..*Reference(ehealth-careteam) {r}CareTeam message sender
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-senderCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierUnique identifier
... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf Σ0..*Reference(Resource) {r}Part of this action
... inResponseTo 0..*Reference(Communication)Reply to
... status ?!Σ1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.

... statusReason Σ0..1CodeableConceptReason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.

... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... priority Σ0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): Codes indicating the relative importance of a communication.

... medium 0..*CodeableConceptA channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.


... subject Σ1..1Reference(ehealth-patient) {r}Focus of message
... topic 0..1CodeableConceptDescription of the purpose/content
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.

... about 0..*Reference(Resource)Resources that pertain to this communication
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... sent 0..1dateTimeWhen sent
... received 0..1dateTimeWhen received
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonCode Σ0..*CodeableConceptIndication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.


... reasonReference Σ0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?
... payload 0..*BackboneElementMessage payload
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... Slices for content[x] 1..1stringMessage part content
Slice: Unordered, Closed by type:$this
..... content[x]:contentString 1..1stringMessage part content
... note 0..*AnnotationComments made about the communication

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Communication.statusrequiredEventStatus
Communication.statusReasonexampleCommunicationNotDoneReason
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)
Communication.priorityrequiredRequestPriority
Communication.mediumexampleParticipationMode
Communication.topicexampleCommunicationTopic
Communication.reasonCodeexampleSNOMEDCTClinicalFindings

Differential View

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... recipientCareTeam 0..*Reference()CareTeam message recipient
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-recipientCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... basedOn 0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf 0..*Reference(Resource) {r}Part of this action
... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... subject 1..1Reference(ehealth-patient) {r}Focus of message
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonReference 0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?
... payload
.... contentString 1..1stringMessage part content

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... senderCareTeam 0..*Reference(ehealth-careteam) {r}CareTeam message sender
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-senderCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... basedOn Σ0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf Σ0..*Reference(Resource) {r}Part of this action
... status ?!Σ1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.

... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... subject Σ1..1Reference(ehealth-patient) {r}Focus of message
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonReference Σ0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Communication.statusrequiredEventStatus
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Communication 0..*CommunicationA record of information transmitted from a sender to a receiver
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 2..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 1..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... recipientCareTeam 0..*Reference()CareTeam message recipient
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-recipientCareTeam
... senderCareTeam 0..*Reference(ehealth-careteam) {r}CareTeam message sender
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-senderCareTeam
... restrictionCategory 1..*CodeableConceptRestriction category
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-restriction-category
Binding: Restriction Category (required)
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierUnique identifier
... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(Resource) {r}Request fulfilled by this communication
... partOf Σ0..*Reference(Resource) {r}Part of this action
... inResponseTo 0..*Reference(Communication)Reply to
... status ?!Σ1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required): The status of the communication.

... statusReason Σ0..1CodeableConceptReason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.

... category 1..*CodeableConceptMessage category
Binding: Communication Category (required)
... priority Σ0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): Codes indicating the relative importance of a communication.

... medium 0..*CodeableConceptA channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.


... subject Σ1..1Reference(ehealth-patient) {r}Focus of message
... topic 0..1CodeableConceptDescription of the purpose/content
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.

... about 0..*Reference(Resource)Resources that pertain to this communication
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... sent 0..1dateTimeWhen sent
... received 0..1dateTimeWhen received
... recipient 0..*Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message recipient
... sender 0..1Reference(ehealth-device | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r}Message sender
... reasonCode Σ0..*CodeableConceptIndication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.


... reasonReference Σ0..*Reference(ehealth-condition | ehealth-observation) {r}Why was communication done?
... payload 0..*BackboneElementMessage payload
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... Slices for content[x] 1..1stringMessage part content
Slice: Unordered, Closed by type:$this
..... content[x]:contentString 1..1stringMessage part content
... note 0..*AnnotationComments made about the communication

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Communication.statusrequiredEventStatus
Communication.statusReasonexampleCommunicationNotDoneReason
Communication.categoryrequiredCommunicationCategory (a valid code from Communication Category)
Communication.priorityrequiredRequestPriority
Communication.mediumexampleParticipationMode
Communication.topicexampleCommunicationTopic
Communication.reasonCodeexampleSNOMEDCTClinicalFindings

 

Other representations of profile: CSV, Excel, Schematron