...
| Resource Definition | Description |
|---|---|
| Alert | The primary alert resource element representing a particular alert (note) about a patient. |
| identifier [1..*] identifier | One or more identifiers which can be used to reference the alert. Note: This has a different cardinality than FHIR |
category [1..1] | Identifies the category of the alert (example: administrative, clinical, etc.). Note: This has a different cardinality and value set binding than FHIR. See XXXX for value set members. |
| status [1..1] code {http://hl7.org/fhir/alert-status} | Identifies the status of the alert. This element is bound to the http://hl7.org/fhir/alert-status value set defined at http://hl7.org/implement/standards/fhir/alert-status.html and shall carry a value of active, inactive or "entered in error". |
subject [1..1] | Identifies the subject (patient) for which the alert applies. |
author [1..1] | Identifies the clinician, patient, or device which was responsible for the authoring of the alert. |
| note [1..1] string | The textual content of the note. |
The Alert Publisher shall include all resources referenced in the subject and author attributes as contained resources (see http://www.hl7.org/implement/standards/fhir/references.html#contained)
2.4.2.2.1
...
Example
An example alert published instructing any provider to double check the patient's weight and blood pressure on during their next care visit in FHIR JSON:
{
"resourceType": "Alert",
"contained": [
{
"resourceType": "Patient",
"id": "Patient1",
"identifier": [
{
"use": "usual",
"system": "urn:oid:LOCAL IDENTIFIERS OID",
"value": "LOCAL IDENTIFIER"
}
]
},
{
"resourceType": "Device",
"id": "Device1",
"identifier": [
{
"use": "usual",
"system": "urn:oid:OPENHIE DEVICES OID",
"value": "OPENHIE DEVICE ID"
}
],
"type": {
"coding": [
{
"system": "local",
"code": "icp",
"display": "Integrated Care Pathways Workflow Host"
}
],
"text": "ICP Host"
},
"manufacturer" : "OpenHIM",
"model" : "v1.0"
}
],
"text": {
"status": "generated",
"div": "<div><b>From ICP-WHO-304:</b> Patient underweight for this stage of pregnancy, please double check weight next visit"
},
"category": {
"coding": [
{
"system": "local",
"code": "clinical",
"display": "Clinical Alert"
}],
"text": "Clinical Alert"
},
"status": "active",
"subject": {
"reference": "#Patient1",
"display": "Mosa Mengasube"
},
"author": {
"reference": "#Device1",
"display": "OpenHIM ICP"
},
"note": "Patient underweight for this stage of pregnancy, please double check weight next visit"
}
...
2.4.2.3. Targeting Alerts
The basic FHIR Alert resource may be a generic Alert about the patient (example: "Someone please verify the Patient's addressweight") or, in the context of OpenHIEfor certain alert types, may need to be a targeted alert (example: "CHW X, please see patient Y because they haven't had an antenatal care visit in over 6 months"). In order to facilitate the latter use case, OpenHIE's the Alert Publisher may convey an intended recipient of the alert in the extension "Intended Recipient".