eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
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 |
The CommunicationRequest resource allows for changes in the way the eHealth Infrastructure creates Communications (of profile ehealth-message
).
The eHealth Infrastructure generates Communications (of profile ehealth-message
) in the following cases:
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:
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.
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 trueSee 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.
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.A CommunicationRequest is related to Communication (ehealth-message
) and in some cases EpisodeOfCare (ehealth-episode-of-care
) or ServiceRequest (ehealth-serviceRequest
).
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
Other representations of profile: CSV, Excel, Schematron