HL7 Belgium FHIR specifications
0.1 - QA review

This page is part of the HL7 Belgium FHIR Specifications (v2020May: QA Preview) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

StructureDefinition: CommunicationLogicalModel

This is the Logical Data Model for Communications. Communications can be:

  • Messages between healthcare professionals
  • Messages between professionals and the patient
  • A journal of notes and communications about a patient, a patient’s care or a healthcare team’s activities.

This Logical Data Model is compatible with both FHIR Communication and KMEHR Diary Note, namely the selection of attributes that are supported, and the maximum length of the payload (320 characters).

The official URL for this profile is: 

https://www.hl7belgium.org/fhir/StructureDefinition/be-model-communication

Formal Views of Profile Content

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

This structure is derived from Element

Summary

Mandatory: 0 element (1 nested mandatory element)
Must-Support: 6 elements

Structures

This structure refers to these other structures:

This structure is derived from Element

NameFlagsCard.TypeDescription & Constraintsdoco
.. BECommunication 0..*ElementCommunication
... identifier S0..*IdentifierIdentifier for this communication
... status S1..1codeStatus of the communication
... validated S0..1codeValidation status
... basedOn 0..*Reference()The trigger for this communication
... inReponseTo 0..*Reference(https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-communication)Communication for which this communication is a response
... sender S0..*Reference(BePatient | Person | Practitioner)Sender of the communication
... recipient 0..*Reference(Group | Person | Patient | Practitioner | PractitionerRole)Recipient(s) of the communication
... topic 0..*CodeableConceptTopic of the communication
Binding: CommunicationTopic (example)
... context 0..*BackboneElementThe context (e.g. subject) for this communications
.... patient 0..*Reference(BePatient)The patient or subject of care
... content S0..*BackboneElementMessage payload
.... text 0..*stringCommunication text
.... attachment 0..*AttachmentAttachment (e.g. image)
.... link 0..*Reference()Link to message content - an attachment, an online video, a document in another server or vault

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. BECommunication I0..*ElementCommunication
... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
... identifier S0..*IdentifierIdentifier for this communication
... status S1..1codeStatus of the communication
... dateTimeEntered S0..*dateTimeTime and Date of Communication entered
... basedOn 0..*Reference()The trigger for this communication
... inReponseTo 0..*Reference(https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-communication)Communication for which this communication is a response
... sender S0..*Reference(BePatient | Person | Practitioner)Sender of the communication
... recipient 0..*Reference(Group | Person | Patient | Practitioner | PractitionerRole)Recipient(s) of the communication
... topic 0..*CodeableConceptTopic of the communication
Binding: CommunicationTopic (example)
... context 0..*BackboneElementThe context (e.g. subject) for this communications
.... patient 0..*Reference(BePatient)The patient or subject of care
... content S0..*BackboneElementMessage payload
.... text 0..*stringCommunication text
.... attachment 0..*AttachmentAttachment (e.g. image)
.... link 0..*Reference()Link to message content - an attachment, an online video, a document in another server or vault

doco Documentation for this format

This structure is derived from Element

Summary

Mandatory: 0 element (1 nested mandatory element)
Must-Support: 6 elements

Structures

This structure refers to these other structures:

Differential View

This structure is derived from Element

NameFlagsCard.TypeDescription & Constraintsdoco
.. BECommunication 0..*ElementCommunication
... identifier S0..*IdentifierIdentifier for this communication
... status S1..1codeStatus of the communication
... validated S0..1codeValidation status
... basedOn 0..*Reference()The trigger for this communication
... inReponseTo 0..*Reference(https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-communication)Communication for which this communication is a response
... sender S0..*Reference(BePatient | Person | Practitioner)Sender of the communication
... recipient 0..*Reference(Group | Person | Patient | Practitioner | PractitionerRole)Recipient(s) of the communication
... topic 0..*CodeableConceptTopic of the communication
Binding: CommunicationTopic (example)
... context 0..*BackboneElementThe context (e.g. subject) for this communications
.... patient 0..*Reference(BePatient)The patient or subject of care
... content S0..*BackboneElementMessage payload
.... text 0..*stringCommunication text
.... attachment 0..*AttachmentAttachment (e.g. image)
.... link 0..*Reference()Link to message content - an attachment, an online video, a document in another server or vault

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. BECommunication I0..*ElementCommunication
... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
... identifier S0..*IdentifierIdentifier for this communication
... status S1..1codeStatus of the communication
... dateTimeEntered S0..*dateTimeTime and Date of Communication entered
... basedOn 0..*Reference()The trigger for this communication
... inReponseTo 0..*Reference(https://www.ehealth.fgov.be/standards/fhir/StructureDefinition/be-communication)Communication for which this communication is a response
... sender S0..*Reference(BePatient | Person | Practitioner)Sender of the communication
... recipient 0..*Reference(Group | Person | Patient | Practitioner | PractitionerRole)Recipient(s) of the communication
... topic 0..*CodeableConceptTopic of the communication
Binding: CommunicationTopic (example)
... context 0..*BackboneElementThe context (e.g. subject) for this communications
.... patient 0..*Reference(BePatient)The patient or subject of care
... content S0..*BackboneElementMessage payload
.... text 0..*stringCommunication text
.... attachment 0..*AttachmentAttachment (e.g. image)
.... link 0..*Reference()Link to message content - an attachment, an online video, a document in another server or vault

doco Documentation for this format

 

​Other representations of profile: Schematron

Terminology Bindings

Terminology Bindings

PathConformanceValueSet
BECommunication.topicexampleCommunicationTopic

Constraints

Constraints

IdPathDetailsRequirements