• Content
• Detailed Descriptions
• Examples
• Example operations
• XML
• JSON

StructureDefinition: ehealth-communication-request

Introduction

The CommunicationRequest resource allows for change in the way eHealth automated processing creates Communication (of profile ehealth-message) as a result of a submitted measurement or lack thereof for a particular Patient and context.

Scope and Usage

In the eHealth Infrastructure, automated processing generates Communication (of profile ehealth-message) in the following cases:

• Automated processing has been performed on a submitted measurement - whether zero, one or more Communication are created depends on the automated processing rules involved.
• A measurement is missing, that is, expected measurement has not been submitted
• A measurement has been submitted at unexpected time

By default, the Communication is created with recipient set to the one or more CareTeam associated with the CarePlan referencing the ProcedureRequest for which the measurement was made.

The CommunicationRequest is used to customize how and when Communications are created by automated processing:

• For a CareTeam, the CommunicationRequest specifies suppression of setting the CareTeam as recipient of Communication
• For a Patient, the CommunicationRequest specifies additional creation of Communication with the Patient as recipient

If multiple CommunicationRequests for the same recipient are found, then only the newest is considered valid.

Suppression of setting a CareTeam as recipient in Communication

When automated processing creates Communication about a specific ProcedureRequest and Patient, the CareTeam is not set as recipient when a CommunicationRequest exists where:

• basedOn references the ProcedureRequest
• recipient references the CareTeam
• reasonCode matches the Communication reasonCode (of the Communication created for CareTeam).
• priority matches the Task priority (of the Task created for CareTeam).
• status is ‘suspended’

Setting the status to any other value than ‘suspended’ disables the specified suppression of Communication with the CareTeam as recipient. The Communication is created with recipient set as the remaining one or more CareTeam referenced from the CarePlan referencing the ProcedureRequest. In case no remaining CareTeam are referenced from the CarePlan, no Communication is created.

Creation of Communication with Patient as recipient

When automated processing creates Communication about a specific ProcedureRequest and Patient, additional Communication with the Patient as recipient is created if a CommunicationRequest exists where:

• basedOn references the ProcedureRequest
• recipient references the Patient
• reasonCode matches the Communication reasonCode (of the Communication created for CareTeam).
• priority matches the Task priority (of the Task created for CareTeam).
• status is ‘active’

Setting the status to ‘suspended’ disables the specified creation of Communication with the Patient as recipient.

Override medium and payload

It is possible to use CommunicationRequest to override some default values of the Communication:

• medium of the Communication (created for the Patient or Careteam) overrides the Communication medium (of the Communication created for CareTeam).
• payload of the Communication (created for the Patient) overrides the Communication payload (of the Communication created for CareTeam).

Boundaries and Relationships

A CommunicationRequest is related to Communication (ehealth-message), Task (ehealth-task), and ProcedureRequest (ehealth-procedureRequest).

Formal Views of Profile Content

The official URL for this profile is:

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-request

This profile builds on CommunicationRequest.

This profile was published on Tue Oct 27 14:11:48 UTC 2020 as a draft by ehealth.sundhed.dk.

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

 

Terminology Bindings

Path	Conformance	ValueSet
CommunicationRequest.language	extensible	Common Languages Max Binding: All Languages
CommunicationRequest.status	required	RequestStatus
CommunicationRequest.category	example	MessageCategory
CommunicationRequest.priority	required	RequestPriority
CommunicationRequest.medium	example	MessageMedium
CommunicationRequest.reasonCode	example	v3 Code System ActReason

Constraints

Id	Path	Details	Requirements
dom-2	CommunicationRequest	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-1	CommunicationRequest	If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty()
dom-4	CommunicationRequest	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3	CommunicationRequest	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource : contained.where(('#'+id in %resource.descendants().reference).not()).empty()
ele-1	CommunicationRequest.payload	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
ele-1	CommunicationRequest.requester	All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count())
cmr-1	CommunicationRequest.requester	onBehalfOf can only be specified if agent is practitioner or device : (agent.resolve() is Practitioner) or (agent.resolve() is Device) or onBehalfOf.exists().not()

.