FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 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

Patient Care Work GroupMaturity Level: 2 Trial UseCompartments: Device, Encounter, Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the CommunicationRequest resource.

CommunicationRequest
Definition

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.

Control1..1
CommunicationRequest.identifier
Definition

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 system.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Summarytrue
CommunicationRequest.basedOn
Definition

A plan or proposal that is fulfilled in whole or in part by this request.

Control0..*
TypeReference(Any)
Requirements

Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.

Alternate Namesfulfills
Summarytrue
CommunicationRequest.replaces
Definition

Completed or terminated request(s) whose function is taken by this new request.

Control0..*
TypeReference(CommunicationRequest)
Requirements

Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.

Alternate Namessupersedes; prior
Summarytrue
Comments

The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.

CommunicationRequest.groupIdentifier
Definition

A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.

Control0..1
TypeIdentifier
Alternate NamesgrouperId
Summarytrue
Comments

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

CommunicationRequest.status
Definition

The status of the proposal or order.

Control1..1
Terminology BindingRequestStatus (Required)
Typecode
Is Modifiertrue
Summarytrue
Comments

This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid.

CommunicationRequest.category
Definition

The type of message to be sent such as alert, notification, reminder, instruction, etc.

Control0..*
Terminology BindingCommunicationCategory (Example)
TypeCodeableConcept
Comments

There may be multiple axes of categorization and one communication request may serve multiple purposes.

CommunicationRequest.priority
Definition

Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine.

Control0..1
Terminology BindingRequestPriority (Required)
Typecode
Meaning if MissingIf missing, this task should be performed with normal priority
Summarytrue
CommunicationRequest.medium
Definition

A channel that was used for this communication (e.g. email, fax).

Control0..*
Terminology Bindingv3 Code System ParticipationMode (Example)
TypeCodeableConcept
CommunicationRequest.subject
Definition

The patient or group that is the focus of this communication request.

Control0..1
TypeReference(Patient | Group)
Alternate Namespatient
CommunicationRequest.recipient
Definition

The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication.

Control0..*
TypeReference(Device | Organization | Patient | Practitioner | RelatedPerson | Group | CareTeam)
CommunicationRequest.topic
Definition

The resources which were related to producing this communication request.

Control0..*
TypeReference(Any)
CommunicationRequest.context
Definition

The encounter or episode of care within which the communication request was created.

Control0..1
TypeReference(Encounter | EpisodeOfCare)
Alternate Namesencounter
Summarytrue
CommunicationRequest.payload
Definition

Text, attachment(s), or resource(s) to be communicated to the recipient.

Control0..*
CommunicationRequest.payload.content[x]
Definition

The communicated content (or for multi-part communications, one portion of the communication).

Control1..1
Typestring|Attachment|Reference(Any)
[x] NoteSee Choice of Data Types for further information about how to use [x]
CommunicationRequest.occurrence[x]
Definition

The time when this communication is to occur.

Control0..1
TypedateTime|Period
[x] NoteSee Choice of Data Types for further information about how to use [x]
Alternate Namestiming
Summarytrue
CommunicationRequest.authoredOn
Definition

For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.

Control0..1
TypedateTime
Alternate NamescreatedOn
Summarytrue
CommunicationRequest.sender
Definition

The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication.

Control0..1
TypeReference(Device | Organization | Patient | Practitioner | RelatedPerson)
CommunicationRequest.requester
Definition

The individual who initiated the request and has responsibility for its activation.

Control0..1
Alternate Namesauthor
Summarytrue
InvariantsDefined on this element
cmr-1: onBehalfOf can only be specified if agent is practitioner or device (expression : (agent.resolve() is Practitioner) or (agent.resolve() is Device) or onBehalfOf.exists().not(), xpath: contains(f:agent/f:reference/@value, '/Practitioner/') or contains(f:agent/f:reference/@value, '/Device/') or not(exists(f:onBehalfOf)))
CommunicationRequest.requester.agent
Definition

The device, practitioner, etc. who initiated the request.

Control1..1
TypeReference(Practitioner | Organization | Patient | RelatedPerson | Device)
Summarytrue
CommunicationRequest.requester.onBehalfOf
Definition

The organization the device or practitioner was acting on behalf of.

Control0..1
TypeReference(Organization)
Requirements

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request.

Summarytrue
InvariantsAffect this element
cmr-1: onBehalfOf can only be specified if agent is practitioner or device (expression : (agent.resolve() is Practitioner) or (agent.resolve() is Device) or onBehalfOf.exists().not(), xpath: contains(f:agent/f:reference/@value, '/Practitioner/') or contains(f:agent/f:reference/@value, '/Device/') or not(exists(f:onBehalfOf)))
CommunicationRequest.reasonCode
Definition

Describes why the request is being made in coded or textual form.

Control0..*
Terminology Bindingv3 Code System ActReason (Example)
TypeCodeableConcept
Summarytrue
Comments

Textual reasons can be caprued using reasonCode.text.

CommunicationRequest.reasonReference
Definition

Indicates another resource whose existence justifies this request.

Control0..*
TypeReference(Condition | Observation)
Summarytrue
CommunicationRequest.note
Definition

Comments made about the request by the requester, sender, recipient, subject or other participants.

Control0..*
TypeAnnotation