This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
(v4.3.0:
R4B
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R4B
R4
R3
R2
| Patient Care Work Group | Maturity Level : N/A | Standards Status : Informative | Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson |
Raw XML ( canonical form + also see XML Format Specification )
An example of an alert message (id = "example")
<?xml version="1.0" encoding="UTF-8"?> <Communication xmlns="http://hl7.org/fhir"> <id value="example"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">Patient has very high serum potassium</div> </text> <identifier> <type> <text value="Paging System"/> </type> <system value="urn:oid:1.3.4.5.6.7"/> <value value="2345678901"/> </identifier> <instantiatesUri value="http://example.org/hyperkalemia"/> <partOf><display value="Serum Potassium Observation"/> </partOf> <status value="completed"/> <category> <coding> <system value="http://acme.org/messagetypes"/> <code value="Alert"/> </coding> <text value="Alert"/> </category> <medium> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationMode"/> <code value="WRITTEN"/> <display value="written"/> </coding> <text value="written"/> </medium> <subject><reference value="Patient/example"/> </subject> <encounter><reference value="Encounter/example"/> </encounter> <sent value="2014-12-12T18:01:10-08:00"/> <received value="2014-12-12T18:01:11-08:00"/> <recipient><reference value="Practitioner/example"/> </recipient> <sender><reference value="Device/f001"/> </sender> <payload> <contentString value="Patient 1 has a very high serum potassium value (7.2 mmol/L on 2014-Dec-12 at 5:55 pm)"/> </payload> <payload> <!-- Reference to the lab result --> <contentReference> <display value="Serum Potassium Observation"/> </contentReference> </payload> </ Communication >
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.