eHealth Infrastructure - Local Development build (v2.3.0). See the Directory of published versions
Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-communication-request | Version: 2.3.0 | |||
Active as of 2022-09-27 | Computable Name: ehealth-communication-request |
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.
In the eHealth Infrastructure, automated processing generates Communication (of profile ehealth-message
) in the following cases:
By default, the Communication is created with recipient set to the one or more CareTeam associated with the CarePlan referencing the ServiceRequest for which the measurement was made.
The CommunicationRequest is used to customize how and when Communications are created by automated processing:
If multiple CommunicationRequests for the same recipient are found, then only the newest is considered valid.
When automated processing creates Communication about a specific ServiceRequest and Patient, the CareTeam is not set as recipient when a CommunicationRequest exists where:
basedOn
references the ServiceRequestrecipient
references the CareTeamreasonCode
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 ServiceRequest. In case no remaining CareTeam are referenced from the CarePlan, no Communication is created.
When automated processing creates Communication about a specific ServiceRequest and Patient, additional Communication with the Patient as recipient is created if a CommunicationRequest exists where:
basedOn
references the ServiceRequestrecipient
references the PatientreasonCode
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.
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).A CommunicationRequest is related to Communication (ehealth-message
), Task (ehealth-task
), and ServiceRequest (ehealth-serviceRequest
).
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
Other representations of profile: CSV, Excel, Schematron
Path | Conformance | ValueSet |
CommunicationRequest.language | preferred | CommonLanguages Max Binding: AllLanguages |
CommunicationRequest.status | required | RequestStatus |
CommunicationRequest.statusReason | example | |
CommunicationRequest.category | required | MessageCategory |
CommunicationRequest.priority | required | RequestPriority |
CommunicationRequest.medium | required | MessageMedium |
CommunicationRequest.reasonCode | example | ActReason |