Communication resource (Task Notification) example
- Morten Sams
- John Schneider
- Ole Hedegaard
NOTICE: This page contains examples that are not up-to-date. For the latest examples, see https://docs.ehealth.sundhed.dk/latest-released/ig/StructureDefinition-ehealth-message.html
The latest documentation for the Communication resource is found here:
When the Processing Service has created a new Task it can, if defined in the rules, generate notifications for the Practitioners of the responsible CareTeams.
The following is an example of a notification pointing to a newly created Task.
Points of Interest:
status
Status is completed when the Processing Service has created the notification.
medium
The channel that the notification is sent through. In the example below, it is sent as an SMS.
recipient
A reference to the Practitioner that is to receive the notification. This is determined from the CareTeam relations on the CarePlan that is in context.
The Processing Service uses the "shadow Practitioner profiles", maintained at logon, to be able to address Practitioners individually.
ehealth-communication-recipientCareTeam
A recipientCareTeam has recently been added but not in a released version. The following snippet shows how this is defined
"ehealth-communication-recipientCareTeam": [
{
"reference": "https://vendortest2.ehealth.sundhed.dk/organization/fhir/CareTeam/60"
}
]
subject
A reference to the Patient.
context
A reference to the Episode Of Care.
topic
A reference to the Task that the Communication resource is notifying about.
sender
A reference to the Organization that is legally responsible for the patient's Episode of Care (managingOrganization)
payload
The contents of the notification
Communication Resource for Task notification in JSON
{
"resourceType": "Communication",
"id": "message-nemsms-notification",
"meta": {
"profile": [
"http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-message"
]
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: message-nemsms-valid</p><p><b>meta</b>: </p><p><b>status</b>: completed</p><p><b>category</b>: Besked <span style=\"background: LightGoldenRodYellow\">(Details : {http://ehealth.sundhed.dk/message-category code 'message' = 'message)</span></p><p><b>medium</b>: NemSMS <span style=\"background: LightGoldenRodYellow\">(Details : {http://ehealth.sundhed.dk/message-medium code 'nemsms' = 'nemsms)</span></p><p><b>recipient</b>: <a href=\"http://practitioner.ehealth.sundhed.dk/Practitioner/123\">http://practitioner.ehealth.sundhed.dk/Practitioner/123</a></p><p><b>sent</b>: Dec 12, 2018 6:01:10 PM</p><p><b>received</b>: Dec 12, 2018 6:01:11 PM</p><p><b>sender</b>: <a href=\"http://patient.ehealth.sundhed.dk/Patient/XXX\">http://patient.ehealth.sundhed.dk/Patient/XXX</a></p><h3>Payloads</h3><table class=\"grid\"><tr><td>-</td><td><b>Content[x]</b></td></tr><tr><td>*</td><td>Dit Care Team har modtaget en ny opgave. Den er nu tilgængelig via opgaveoversigten.</td></tr></table></div>"
},
"status": "completed",
"category": [
{
"coding": [
{
"system": "http://ehealth.sundhed.dk/message-category",
"code": "notification"
}
],
"text": "Notifikation"
}
],
"medium": [
{
"coding": [
{
"system": "http://ehealth.sundhed.dk/message-medium",
"code": "nemsms"
}
],
"text": "NemSMS"
}
],
"recipient": [
{
"reference": "https://vendortest2.ehealth.sundhed.dk/organization/fhir/Practitioner/59"
}
],
"subject": {
"reference": "https://vendortest2.ehealth.sundhed.dk/trifork-fhir-server/Patient/203"
},
"context": {
"reference": "https://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/EpisodeOfCare/67"
},
"topic": [
{
"reference": "https://vendortest2.ehealth.sundhed.dk/hapi-fhir-server/fhir/Task/269"
}
],
"sent": "2018-12-12T18:01:10-08:00",
"received": "2018-12-12T18:01:11-08:00",
"sender": {
"reference": "https://vendortest2.ehealth.sundhed.dk/organization/fhir/Organization/58"
},
"payload": [
{
"contentString": "Der er nye målinger der skal behandles af dit team."
}
]
}