eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-communication-request

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-request Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-communication-request

Introduction

The CommunicationRequest resource allows for changes in the way the eHealth Infrastructure creates Communications (of profile ehealth-message).

Scope and Usage

The eHealth Infrastructure generates Communications (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 an unexpected time
  • A reminder that a measurement is expected to be submitted
  • A CarePlan or EpisodeOfCare has been created or updated
  • A reminder that an order in the SSL domain is to be delivered (requires additional configuration in the SSL Contract)

The default behaviour and controllability for the different Communication scenarios differ. An overview of how to control the different Communication generation can be found here.

The CommunicationRequest is used to customize how and when Communications are created by the infrastructure:

  • CommunicationRequest can in some scenarios specify suppression of a specific Communication for CareTeams and/or Patients
  • CommunicationRequest can in some scenarios specify overriding of medium and/or payload for Patient Communications

If multiple CommunicationRequests for the same recipient are found the most recent (by occurrencePeriod.start) with status active takes precedence. If multiple CommunicationRequest resources are the most recent and active, any CommunicationRequest with doNotPerform = true takes precedence.

Suppression of Communications

When the infrastructure by default creates Communication for either a Patient or CareTeam, it may be possible to suppress creation for a specific recipient. An overview of when suppression is possible is given here. A CommunicationRequest states suppression when:

  • doNotPerform is set to true

See the other requirements for a CommunicationRequest to take effect here.Updating doNotPerform to false or removing the attribute disables the specified suppression of the Communication. Alternatively, the CommunicationRequest lifecycle can be adjusted by setting a status value other than active.

Override medium and payload

In some scenarios it is possible to use CommunicationRequest to override some default values of the Communication:

  • medium overrides the Communication medium.
  • payload overrides the Communication payload.

Boundaries and Relationships

A CommunicationRequest is related to Communication (ehealth-message) and in some cases EpisodeOfCare (ehealth-episode-of-care) or ServiceRequest (ehealth-serviceRequest).

Usage:

  • This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

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

This structure is derived from CommunicationRequest

NameFlagsCard.TypeDescription & Constraintsdoco
.. CommunicationRequest 0..*CommunicationRequestA request for information to be sent to a receiver
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... episodeOfCare 0..1Reference(EpisodeOfCare)Associated Encounter episode of care
URL: http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare
... basedOn 0..1Reference(Resource)Fulfills plan or proposal
... priority 0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required)
... medium 0..*CodeableConceptA channel of communication
Binding: MessageMedium (required)
... subject 1..1Reference(Patient)Focus of message
... recipient 0..*Reference(Patient | CareTeam) {r}Message recipient

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
CommunicationRequest.categoryrequiredMessageCategory
http://ehealth.sundhed.dk/vs/message-category
from this IG
CommunicationRequest.priorityrequiredRequestPriority
http://hl7.org/fhir/ValueSet/request-priority
from the FHIR Standard
CommunicationRequest.mediumrequiredMessageMedium
http://ehealth.sundhed.dk/vs/message-medium
from this IG

 

Other representations of profile: CSV, Excel, Schematron