STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

5.24 Resource CommunicationRequest - Content

Patient Care Work GroupMaturity Level: 1Compartments: Device, Encounter, Patient, Practitioner, RelatedPerson

A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition.

5.24.1 Scope and Usage

This resource is a record of a request for a communication to be performed. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, and devices. Uses of communication request include:

  • A computer-based decision-support system requesting a reminder or alert be delivered to a responsible provider
  • A physician requesting notification from the nurse if a patient's temperature exceeds a value
  • A monitoring system or a provider requesting a staff member or department to notify a public health agency of a patient presenting with a communicable disease reportable to the public health agency
  • A computer-based decision-support system proposes to send educational material to a patient

5.24.2 Boundaries and Relationships

This resource is a record of a request. It does not represent the actual flow of communication. The use of CommunicationRequest excludes requests for referrals which are covered by the ReferralRequest resource. It also excludes requests for therapy or counseling which would be handled by the ProcedureRequest resource. The performance of a CommunicationRequest may result in a Communication resource.

This resource is referenced by CarePlan, ClinicalImpression and Communication

5.24.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CommunicationRequest ΣDomainResourceA request for information to be sent to a receiver
... identifier Σ0..*IdentifierUnique identifier
... category Σ0..1CodeableConceptMessage category
... sender Σ0..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Message sender
... recipient Σ0..*Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Message recipient
... payload Σ0..*BackboneElementMessage payload
.... content[x] Σ1..1Message part content
..... contentStringstring
..... contentAttachmentAttachment
..... contentReferenceReference(Any)
... medium Σ0..*CodeableConceptA channel of communication
v3 Code System ParticipationMode (Example)
... requester Σ0..1Reference(Practitioner | Patient | RelatedPerson)An individual who requested a communication
... status ?! Σ0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed
CommunicationRequestStatus (Required)
... encounter Σ0..1Reference(Encounter)Encounter leading to message
... scheduled[x] Σ0..1When scheduled
.... scheduledDateTimedateTime
.... scheduledPeriodPeriod
... reason Σ0..*CodeableConceptIndication for message
... requestedOn Σ0..1dateTimeWhen ordered or proposed
... subject Σ0..1Reference(Patient)Focus of message
... priority Σ0..1CodeableConceptMessage urgency
DiagnosticOrderPriority (Example)

doco Documentation for this format

UML Diagram

CommunicationRequest (DomainResource)A unique ID of this request for reference purposes. It must be provided if user wants it returned as part of any output, otherwise it will be autogenerated, if needed, by CDS system. Does not need to be the actual ID of the source systemidentifier : Identifier [0..*]The type of message to be sent such as alert, notification, reminder, instruction, etccategory : CodeableConcept [0..1]The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communicationsender : Reference [0..1] « Device|Organization|Patient|Practitioner| RelatedPerson »The entity (e.g. person, organization, clinical information system, or device) which is the intended target of the communicationrecipient : Reference [0..*] « Device|Organization|Patient| Practitioner|RelatedPerson »A channel that was used for this communication (e.g. email, fax)medium : CodeableConcept [0..*] « Codes for communication mediums such as phone, fax, email, in person, etc. (Strength=Example)v3 Code System ParticipationM...?? »The responsible person who authorizes this order, e.g. physician. This may be different than the author of the order statement, e.g. clerk, who may have entered the statement into the order entry applicationrequester : Reference [0..1] « Practitioner|Patient|RelatedPerson »The status of the proposal or order (this element modifies the meaning of other elements)status : code [0..1] « The status of the communication. (Strength=Required)CommunicationRequestStatus! »The encounter within which the communication request was createdencounter : Reference [0..1] « Encounter »The time when this communication is to occurscheduled[x] : Type [0..1] « dateTime|Period »The reason or justification for the communication requestreason : CodeableConcept [0..*]The time when the request was maderequestedOn : dateTime [0..1]The patient who is the focus of this communication requestsubject : Reference [0..1] « Patient »Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routinepriority : CodeableConcept [0..1] « Codes indicating the relative importance of a communication request. (Strength=Example)DiagnosticOrderPriority?? »PayloadThe communicated content (or for multi-part communications, one portion of the communication)content[x] : Type [1..1] « string|Attachment|Reference(Any) »Text, attachment(s), or resource(s) to be communicated to the recipientpayload[0..*]

XML Template

<CommunicationRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Unique identifier --></identifier>
 <category><!-- 0..1 CodeableConcept Message category --></category>
 <sender><!-- 0..1 Reference(Device|Organization|Patient|Practitioner|
   RelatedPerson) Message sender --></sender>
 <recipient><!-- 0..* Reference(Device|Organization|Patient|Practitioner|
   RelatedPerson) Message recipient --></recipient>
 <payload>  <!-- 0..* Message payload -->
  <content[x]><!-- 1..1 string|Attachment|Reference(Any) Message part content --></content[x]>
 </payload>
 <medium><!-- 0..* CodeableConcept A channel of communication --></medium>
 <requester><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson) An individual who requested a communication --></requester>
 <status value="[code]"/><!-- 0..1 proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed -->
 <encounter><!-- 0..1 Reference(Encounter) Encounter leading to message --></encounter>
 <scheduled[x]><!-- 0..1 dateTime|Period When scheduled --></scheduled[x]>
 <reason><!-- 0..* CodeableConcept Indication for message --></reason>
 <requestedOn value="[dateTime]"/><!-- 0..1 When ordered or proposed -->
 <subject><!-- 0..1 Reference(Patient) Focus of message --></subject>
 <priority><!-- 0..1 CodeableConcept Message urgency --></priority>
</CommunicationRequest>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. CommunicationRequest ΣDomainResourceA request for information to be sent to a receiver
... identifier Σ0..*IdentifierUnique identifier
... category Σ0..1CodeableConceptMessage category
... sender Σ0..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Message sender
... recipient Σ0..*Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Message recipient
... payload Σ0..*BackboneElementMessage payload
.... content[x] Σ1..1Message part content
..... contentStringstring
..... contentAttachmentAttachment
..... contentReferenceReference(Any)
... medium Σ0..*CodeableConceptA channel of communication
v3 Code System ParticipationMode (Example)
... requester Σ0..1Reference(Practitioner | Patient | RelatedPerson)An individual who requested a communication
... status ?! Σ0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed
CommunicationRequestStatus (Required)
... encounter Σ0..1Reference(Encounter)Encounter leading to message
... scheduled[x] Σ0..1When scheduled
.... scheduledDateTimedateTime
.... scheduledPeriodPeriod
... reason Σ0..*CodeableConceptIndication for message
... requestedOn Σ0..1dateTimeWhen ordered or proposed
... subject Σ0..1Reference(Patient)Focus of message
... priority Σ0..1CodeableConceptMessage urgency
DiagnosticOrderPriority (Example)

doco Documentation for this format

UML Diagram

CommunicationRequest (DomainResource)A unique ID of this request for reference purposes. It must be provided if user wants it returned as part of any output, otherwise it will be autogenerated, if needed, by CDS system. Does not need to be the actual ID of the source systemidentifier : Identifier [0..*]The type of message to be sent such as alert, notification, reminder, instruction, etccategory : CodeableConcept [0..1]The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communicationsender : Reference [0..1] « Device|Organization|Patient|Practitioner| RelatedPerson »The entity (e.g. person, organization, clinical information system, or device) which is the intended target of the communicationrecipient : Reference [0..*] « Device|Organization|Patient| Practitioner|RelatedPerson »A channel that was used for this communication (e.g. email, fax)medium : CodeableConcept [0..*] « Codes for communication mediums such as phone, fax, email, in person, etc. (Strength=Example)v3 Code System ParticipationM...?? »The responsible person who authorizes this order, e.g. physician. This may be different than the author of the order statement, e.g. clerk, who may have entered the statement into the order entry applicationrequester : Reference [0..1] « Practitioner|Patient|RelatedPerson »The status of the proposal or order (this element modifies the meaning of other elements)status : code [0..1] « The status of the communication. (Strength=Required)CommunicationRequestStatus! »The encounter within which the communication request was createdencounter : Reference [0..1] « Encounter »The time when this communication is to occurscheduled[x] : Type [0..1] « dateTime|Period »The reason or justification for the communication requestreason : CodeableConcept [0..*]The time when the request was maderequestedOn : dateTime [0..1]The patient who is the focus of this communication requestsubject : Reference [0..1] « Patient »Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routinepriority : CodeableConcept [0..1] « Codes indicating the relative importance of a communication request. (Strength=Example)DiagnosticOrderPriority?? »PayloadThe communicated content (or for multi-part communications, one portion of the communication)content[x] : Type [1..1] « string|Attachment|Reference(Any) »Text, attachment(s), or resource(s) to be communicated to the recipientpayload[0..*]

XML Template

<CommunicationRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Unique identifier --></identifier>
 <category><!-- 0..1 CodeableConcept Message category --></category>
 <sender><!-- 0..1 Reference(Device|Organization|Patient|Practitioner|
   RelatedPerson) Message sender --></sender>
 <recipient><!-- 0..* Reference(Device|Organization|Patient|Practitioner|
   RelatedPerson) Message recipient --></recipient>
 <payload>  <!-- 0..* Message payload -->
  <content[x]><!-- 1..1 string|Attachment|Reference(Any) Message part content --></content[x]>
 </payload>
 <medium><!-- 0..* CodeableConcept A channel of communication --></medium>
 <requester><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson) An individual who requested a communication --></requester>
 <status value="[code]"/><!-- 0..1 proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed -->
 <encounter><!-- 0..1 Reference(Encounter) Encounter leading to message --></encounter>
 <scheduled[x]><!-- 0..1 dateTime|Period When scheduled --></scheduled[x]>
 <reason><!-- 0..* CodeableConcept Indication for message --></reason>
 <requestedOn value="[dateTime]"/><!-- 0..1 When ordered or proposed -->
 <subject><!-- 0..1 Reference(Patient) Focus of message --></subject>
 <priority><!-- 0..1 CodeableConcept Message urgency --></priority>
</CommunicationRequest>

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.24.3.1 Terminology Bindings

PathDefinitionTypeReference
CommunicationRequest.category Codes for general categories of communications such as alerts, instruction, etc.UnknownNo details provided yet
CommunicationRequest.medium Codes for communication mediums such as phone, fax, email, in person, etc.Examplev3 Code System ParticipationMode
CommunicationRequest.status The status of the communication.RequiredCommunicationRequestStatus
CommunicationRequest.reason Codes for describing reasons for the occurrence of a communication.UnknownNo details provided yet
CommunicationRequest.priority Codes indicating the relative importance of a communication request.ExampleDiagnosticOrderPriority

Notes to reviewers:

At this time, the code bindings are placeholders to be fleshed out upon further review by the community.

5.24.3.2 CommunicationRequest.sender and CommunicationRequest.recepient

CommunicationRequest.sender and CommunicationRequest.recipient allow Patient|Practitioner|RelatedPerson - but it is not unusual to have a communication target - even a defined one - where it is unknown what kind of role the person is playing.

If the communication request is to or from an individual, whose role is not known (practitioner, patient or related person), - for example, only email address is captured in the system; then RelatedPerson should be used by default.

5.24.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
categorytokenMessage categoryCommunicationRequest.category
encounterreferenceEncounter leading to messageCommunicationRequest.encounter
(Encounter)
identifiertokenUnique identifierCommunicationRequest.identifier
mediumtokenA channel of communicationCommunicationRequest.medium
patientreferenceFocus of messageCommunicationRequest.subject
(Patient)
prioritytokenMessage urgencyCommunicationRequest.priority
recipientreferenceMessage recipientCommunicationRequest.recipient
(Device, Patient, Organization, Practitioner, RelatedPerson)
requesteddateWhen ordered or proposedCommunicationRequest.requestedOn
requesterreferenceAn individual who requested a communicationCommunicationRequest.requester
(Patient, Practitioner, RelatedPerson)
senderreferenceMessage senderCommunicationRequest.sender
(Device, Patient, Organization, Practitioner, RelatedPerson)
statustokenproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failedCommunicationRequest.status
subjectreferenceFocus of messageCommunicationRequest.subject
(Patient)
timedateWhen scheduledCommunicationRequest.scheduledDateTime