Pan-Canadian eReferral-eConsult (CA:eReC)
DFT - The specification is currently in development and subject to change. For a full list of available versions, see the Directory of published versions
http://hl7.org/fhir/StructureDefinition/Communication
Communication resource is used to achieve the bi-directional communication between two systems. The Communication resource can be used to ask questions regarding a referral, request a referral be updated with missing information, or request additional information not covered by the specific referral dataset.
MessageHeader, ServiceRequest, Task
Communication | C | Communication | |
id | Σ | 0..1 | string |
meta | S Σ | 0..1 | Meta |
id | 0..1 | string | |
extension | C | 0..* | Extension |
versionId | Σ | 0..1 | id |
lastUpdated | Σ | 0..1 | instant |
source | Σ | 0..1 | uri |
profile | S Σ | 0..* | canonical(StructureDefinition) |
security | Σ | 0..* | CodingBinding |
tag | Σ | 0..* | Coding |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | C | 0..* | Extension |
modifierExtension | ?! C | 0..* | Extension |
identifier | Σ | 0..* | Identifier |
instantiatesCanonical | Σ | 0..* | canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) |
instantiatesUri | Σ | 0..* | uri |
basedOn | S Σ | 1..1 | Reference(ServiceRequest) |
id | 0..1 | string | |
extension | C | 0..* | Extension |
reference | S Σ C | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | S Σ | 0..1 | Identifier |
id | 0..1 | string | |
extension | C | 0..* | Extension |
use | S Σ ?! | 1..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
system | S Σ | 1..1 | uri |
value | S Σ | 1..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
display | Σ | 0..1 | string |
partOf | Σ | 0..* | Reference(Resource) |
inResponseTo | S | 0..* | Reference(Communication) |
status | S Σ ?! | 1..1 | codeBindingFixed Value |
statusReason | Σ | 0..1 | CodeableConcept |
category | 0..* | CodeableConceptBinding | |
priority | Σ | 0..1 | codeBinding |
medium | 0..* | CodeableConcept | |
subject | S Σ | 0..1 | Reference(Patient) |
id | 0..1 | string | |
extension | C | 0..* | Extension |
reference | S Σ C | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | S Σ | 0..1 | Identifier |
id | 0..1 | string | |
extension | C | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
system | S Σ | 1..1 | uri |
value | S Σ | 1..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
display | Σ | 0..1 | string |
topic | 0..1 | CodeableConcept | |
about | 0..* | Reference(Resource) | |
encounter | Σ | 0..1 | Reference(Encounter) |
sent | S | 0..1 | dateTime |
received | S | 0..1 | dateTime |
recipient | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Group | CareTeam | HealthcareService) | |
sender | S | 0..1 | Reference(PractitionerRole | HealthcareService) |
id | 0..1 | string | |
extension | C | 0..* | Extension |
reference | S Σ C | 0..1 | string |
type | Σ | 0..1 | uriBinding |
identifier | S Σ | 0..1 | Identifier |
id | 0..1 | string | |
extension | C | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
system | S Σ | 1..1 | uri |
value | S Σ | 1..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
display | Σ | 0..1 | string |
reasonCode | Σ | 0..* | CodeableConcept |
reasonReference | Σ | 0..* | Reference(Condition | Observation | DiagnosticReport | DocumentReference) |
payload | S | 0..* | BackboneElement |
id | 0..1 | string | |
extension | C | 0..* | Extension |
modifierExtension | Σ ?! C | 0..* | Extension |
content[x] | S | 1..1 | |
contentString | string | ||
contentAttachment | Attachment | ||
note | 0..* | Annotation |
Communication | Communication | ||
meta | S | ||
profile | S | ||
basedOn | S | 1..1 | Reference(ServiceRequest) |
reference | S | ||
identifier | S | ||
use | S | 1.. | |
system | S | 1.. | |
value | S | 1.. | |
inResponseTo | S | ||
status | S | BindingFixed Value | |
category | Binding | ||
subject | S | Reference(Patient) | |
reference | S | ||
identifier | S | ||
system | S | 1.. | |
value | S | 1.. | |
sent | S | ||
received | S | ||
sender | S | Reference(PractitionerRole | HealthcareService) | |
reference | S | ||
identifier | S | ||
system | S | 1.. | |
value | S | 1.. | |
payload | S | ||
content[x] | S | ||
contentString | string | ||
contentAttachment | Attachment |
Communication resource is used to achieve the bi-directional communication between two systems. The Communication resource can be used to ask questions regarding a referral, request a referral be updated with missing information, or request additional information not covered by the specific referral dataset.
Although the Communication resource has the ability to carry attachments as .payload.content
, it SHALL NOT be used to attach .supportingInfo
to a ServiceRequest. (Use the DocumentReference resource for this purpose.)
In communication messages the Communication
resource SHALL contain:
payload.contentString
containing a question or comment as text, and/orpayload.contentAttachment
containing a .url to retrieve an attachment or .datacategory
is a coded element typically containing rfi
(request for information) or gen
(general communication)basedOn
, sender
, subject
containing references to the ServiceRequest, PractitionerRole sending the Communication and Patient respectivelyWhen responding to a communication received, the Communication
will also contain:
inResponseTo
referencing the Communication receivedpayload.contentString
containing a text response, and/orpayload.contentAttachment
containing a .url to retrieve an attachment or .data.id
Bundle.entry.fullUrl
).identifier
identifier.system
and identifier.value
SHALL be mustSupport whenever there is a reference or identifier present.basedOn
.reference
to a resource included in the message as a Bundle.entry
, or.identifier
populated with the use
, system
and value
elements populated with the official ServiceRequest.identifier
received from the Source SysteminResponseTo
reference
:
Bundle.entry
MessageHeader.focus
and the one it is .inResponseTo
as Bundle entries allows a the system receiving the message to correctly associate with one another on the receiving system.status
.category
Used to indicate the category of Communication
Use of values
"gen" when sending general communications
"plan" when sending plan of care on service completion
"rfi" when sending a request for information
.subject
ServiceRequest.subject
(e.g.: where the Communication.category
is "plan").sent
.received
MessageHeader.focus
on the "add-communication" event.sender
.reference
a resource included in the message as a Bundle.entry
.payload.content
.payload.contentString
per Communication instance.payload.contentAttachment
per Communication instance.payload.contentString
.payload.contentAttachment
for each attachment.payload
.payload.contentString
).payload.contentAttachment
)NOTE: Although sending base64 encoded
.payload.contentAttachment.data
is supported, implementers of Direct Messaging SHOULD make binary attachments be made available to retrieve from a server using a.payload.contentAttachment.url
to reduce message sizes