As described in https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/538935313/Behind+the+Scenes#Overview-of-Communication-produced-by-the-Infrastructure, the eHealth Infrastructure automatically creates FHIR Communication (of profile https://docs.ehealth.sundhed.dk/latest-releasedfhir/ig/StructureDefinition-ehealth-message.html ) in various situations.
It is possible to control if and how these FHIR Communication are created through use of FHIR CommunicationRequest (https://docs.ehealth.sundhed.dk/latest-released/igfhir/StructureDefinition-ehealth-communication-request.html ).
| Info |
|---|
In the descriptions below, the terms opt-in and opt-out are used with the following meaning:
A CareTeam must be involved in an EpisodeOfCare or CarePlan in order to opt-in for Communication referring the EpisodeOfCare and/or CarePlan and/or ServiceRequest. |
...
subject= Patient referenceoccurrencePeriod.start= start of period for which the control appliesoccurrencePeriod.end= end of period for which the control applies, if known. Otherwise it can be left empty.status=activewhen control is in effect. Can be set to other values as appropriate (one ofdraft | active | on-hold | revoked | completed).doNotPerform=false(or unset) for opt-in or override of medium/payload,truein order to opt-out (that is, to suppress creation)
| Info |
|---|
For eHealth Infrastructure up to Release 13, |
...
CommunicationRequest subject shall not be set for control of message creation regarding:
Automated creation of
mediumnemsmsCommunication when Communication with categorymessageand Patient asrecipientcreatedReminder about appointment
How to set remaining elements of the CommunicationRequest vary with situation, see below.
| Info |
|---|
The |
Controlling Message Creation with Patient as Recipient
...
recipient= Patient referencecategory= <depending on situation>reasonCode= <depending on situation>episodeOfCare= <depending on situation>basedOn= <depending on situation>priority= <depending on situation>
...
Situation
...
Created by Default
...
Opt-in Supported
...
Opt-out Supported
...
Payload and Medium Overridable
...
Element category
...
Element reasonCode
...
Element episodeOfCare
...
Element basedOn
...
Element priority
...
Unexpected measurement submitted
...
No
...
Yes
...
No
...
Yes
...
message
...
UnexpectedMeasuringResolving
...
ServiceRequest reference
...
routine
...
Missing measurement determined
...
No
...
Yes
...
No
...
Yes
...
message
...
MissingMeasurementResolving
...
ServiceRequest reference
...
routine
...
Reminder to submit measurement (about to be created)
...
Yes
...
No
...
Yes
...
No
...
advice
...
EpisodeOfCare reference
...
Communication created by triage (or other infrastructure rules)
...
No
...
Yes
...
No
...
Yes
...
depends on rule
...
depends on rule
...
ServiceRequest reference
...
depends on rule
...
EpisodeOfCare created/changed (in team, status, scheduledStatus or scheduledTeam)
...
Yes
...
No
...
Yes
...
No
...
message
...
EpisodeOfCare reference
...
CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam)
...
Yes
...
No
...
Yes
...
No
...
message
...
EpisodeOfCare reference
...
Reminder about appointment
...
Yes
...
No
...
No
...
No
...
Message category Communication with Patient as recipient created
...
Yes
...
No
...
No
...
No
...
Situation | Created by Default | Opt-in Supported | Opt-out Supported | Payload and Medium Overridable | Element category | Element reasonCode | Element episodeOfCare | Element basedOn | Element priority |
|---|---|---|---|---|---|---|---|---|---|
Unexpected measurement submitted | No | Yes | No | Yes |
|
| ServiceRequest reference | ||
Missing measurement determined | No | Yes | No | Yes |
|
| ServiceRequest reference | ||
Reminder to submit measurement (about to be created) | Yes | No | Yes | Yes |
|
| EpisodeOfCare reference | ||
Communication created by triage (or other infrastructure rules) | No | Yes | No | Yes |
| Depends on rule | ServiceRequest reference | Depends on rule | |
EpisodeOfCare created | No | Yes | No | Yes |
|
| |||
EpisodeOfCare changed (in team, status, scheduledStatus or scheduledTeam) | No | Yes | No | Yes |
|
| EpisodeOfCare reference | ||
CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam) | No | Yes | No | Yes |
|
| EpisodeOfCare reference | ||
Reminder about appointment | Yes | No | Yes | Yes |
|
| EpisodeOfCare reference (optional) If specified, the CommunicationRequest is specific to Appointment referencing the EpisodeOfCare. See section on scope of message creation control below. | ||
Automated creation of | No | Yes | No | Only |
| Same as ehealth-message ( |
optional) When omitted, it corresponds to match on all ehealth-message reasonCodes. See section on scope of message creation control below. | EpisodeOfCare reference (optional) |
If specified, the CommunicationRequest is specific to Communication resources referencing the EpisodeOfCare. See section on scope of message creation control below. |
| Info |
|---|
Currently, no infrastructure rules (see Library Resources) cause creation of Communication. Neither with Patient or CareTeam as recipient. |
...
recipient= CareTeam referencecategory= <depending on situation>reasonCode= <depending on situation>episodeOfCare= <depending on situation>basedOn= <depending on situation>priority= <depending on situation>
...
Situation | Created by Default | Opt-in Supported | Opt-out Supported | Payload and Medium Overridable | Element category | Element reasonCode | Element episodeOfCare | Element basedOn | Element priority |
|---|---|---|---|---|---|---|---|---|---|
Unexpected measurement submitted | No | Yes | No | No |
|
| ServiceRequest reference | ||
Missing measurement determined | Yes | No | Yes | No |
|
| ServiceRequest reference | ||
Communication created by triage (or other infrastructure rules) | Yes | No | Yes | No | depends on rule | depends on rule | ServiceRequest reference | depends on rule | |
EpisodeOfCare created | Yes | No | Yes | No |
|
| |||
EpisodeOfCare changed (in team, status, scheduledStatus or scheduledTeam) | Yes | No | Yes | No |
|
| EpisodeOfCare reference | ||
CarePlan created/changed (in careTeam, status, scheduledStatus or scheduledTeam) | Yes | No | Yes | No |
|
| EpisodeOfCare reference | ||
Reminder about appointment | No | Yes | No | Only |
|
| EpisodeOfCare reference (optional) If specified, the CommunicationRequest is specific to Appointment referencing the EpisodeOfCare. See section on scope of message creation control below. |
Scope of the Message Creation Control
...
Search Algorithms for CommunicationRequest applied in the Infrastructure
...
Ending a Message Creation Control
...
To remove the effect of a CommunicationRequest, perform a CommunicationRequest Update and set the status to completed. If the CommunicationRequest uses occurrencePeriod and has no occurrencePeriod.end, it would be consistent to set it to time of completing the CommunicationRequest.