Clinical
Summary
This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
| Responsible Owner: Patient Care Work Group | Standards Status : Informative |
Compartments
:
Encounter
,
Group
,
Patient
|
Raw XML ( canonical form + also see XML Format Specification )
Encounter-specific care plan for GP visit (id = "gpvisit")
<?xml version="1.0" encoding="UTF-8"?>Represents the flow of a patient within a practice. The plan is created when they arrive and represents the 'care' of the patient over the course of that encounter. They first see the nurse for basic observations (BP, pulse, temp) then the doctor for the consultation and finally the nurse again for a tetanus immunization. As the plan is updated (e.g. a new activity added), different versions of the plan exist, and workflow timings for reporting can be gained by examining the plan history. This example is the version after seeing the doctor, and waiting for the nurse.The plan can either be created 'ad hoc' and modified as the parient progresses, or start with a standard template (which can, of course, be altered to suit the patient. <!-- This is a link to the nurse encounter. The assumption is that all contacts with practitioners are modelled as separate encounters. Ideally, there will be a 'master/parent' encounter that ties them together. If there is a single encounter, then all participants will be linked to that encounter. --> <!-- This activity is for the initial nurse encounter where vitals are taken. It has been completed. --> <!-- This activity is for the encounter with the doctor. It is scheduled, but not yet started, so there is no timing[x] or actionTaken element yet --><CarePlan xmlns="http://hl7.org/fhir"> <id value="gpvisit"/> <text> <status value="additional"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Represents the flow of a patient within a practice. The plan is created when they arrive and represents the 'care' of the patient over the course of that encounter. They first see the nurse for basic observations (BP, pulse, temp) then the doctor for the consultation and finally the nurse again for a tetanus immunization. As the plan is updated (e.g. a new activity added), different versions of the plan exist, and workflow timings for reporting can be gained by examining the plan history. This example is the version after seeing the doctor, and waiting for the nurse.The plan can either be created 'ad hoc' and modified as the parient progresses, or start with a standard template (which can, of course, be altered to suit the patient.</p> </div> </text> <!-- This is the reason for the encounter. It is referenced by the concern --> <contained> <Condition> <id value="p1"/> <clinicalStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/condition-clinical"/> <code value="active"/> </coding> </clinicalStatus> <verificationStatus> <coding> <system value="http://terminology.hl7.org/CodeSystem/condition-ver-status"/> <code value="confirmed"/> </coding> </verificationStatus> <code> <!-- Could coded if we wanted to... --> <text value="Overseas encounter"/> </code> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> </Condition> </contained> <contained> <CareTeam> <id value="careteam"/> <participant id="part1"> <role> <coding> <system value="http://example.org/local"/> <code value="nur"/> </coding> <text value="nurse"/> </role> <member> <reference value="Practitioner/13"/> <display value="Nurse Nancy"/> </member> </participant> <participant id="part2"> <role> <coding> <system value="http://example.org/local"/> <code value="doc"/> </coding> <text value="doctor"/> </role> <member> <reference value="Practitioner/14"/> <display value="Doctor Dave"/> </member> </participant> </CareTeam> </contained> <contained> <Goal> <id value="goal"/> <lifecycleStatus value="planned"/> <description> <text value="Complete consultation"/> </description> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> </Goal> </contained> <contained> <Appointment> <id value="activity-1"/> <status value="fulfilled"/> <description value="Nurse consultation"/> <start value="2013-01-01T10:38:00+00:00"/> <end value="2013-01-01T10:50:00+00:00"/> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> <participant> <actor> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </actor> <required value="true"/> <status value="accepted"/> </participant> <participant> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> <code value="ATND"/> </coding> </type> <actor> <reference value="Practitioner/13"/> <display value="Nurse Nancy"/> </actor> <required value="true"/> <status value="accepted"/> </participant> </Appointment> </contained> <contained> <Appointment> <id value="activity-2"/> <status value="proposed"/> <description value="Doctor Consultation"/> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> <participant> <actor> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </actor> <required value="true"/> <status value="accepted"/> </participant> <participant> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/> <code value="ATND"/> </coding> </type> <actor> <reference value="Practitioner/14"/> <display value="Doctor Dave"/> </actor> <required value="true"/> <status value="accepted"/> </participant> </Appointment> </contained> <status value="active"/> <intent value="plan"/> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> <!-- No end yet as the encounter is still in progress. --> <period> <!-- This is the time the plan started - i.e. when they arrived --> <start value="2013-01-01T10:30:00+00:00"/> </period> <careTeam> <reference value="#careteam"/> </careTeam> <addresses> <reference> <reference value="#p1"/> <display value="obesity"/> </reference> </addresses> <goal> <reference value="#goal"/> </goal> <!-- moved to contained <plannedActivityDetail> <kind value="Appointment"/> <code> <coding> <system value="http://example.org/local"/> <code value="nursecon"/> </coding> <text value="Nurse Consultation"/> </code> <status value="completed"/> <doNotPerform value="false"/> <scheduledPeriod> the nurse saw the patient between 10:38 and 10:50 <start value="2013-01-01T10:38:00+00:00"/> <end value="2013-01-01T10:50:00+00:00"/> </scheduledPeriod> <performer> refer to the participant (the nurse) in this resource <reference value="Practitioner/13"/> <display value="Nurse Nancy"/> </performer> </plannedActivityDetail> --> <activity> <performedActivity> <reference> <!-- This is a link to the nurse encounter. The assumption is that all contacts with practitioners are modelled as separate encounters. Ideally, there will be a 'master/parent' encounter that ties them together. If there is a single encounter, then all participants will be linked to that encounter. --> <reference value="Encounter/example"/> </reference> </performedActivity> <!-- This activity is for the initial nurse encounter where vitals are taken. It has been completed. --> <plannedActivityReference> <reference value="#activity-1"/> </plannedActivityReference> </activity> <!-- moved to contained <plannedActivityDetail> <kind value="Appointment"/> <code> <coding> <system value="http://example.org/local"/> <code value="doccon"/> </coding> <text value="Doctor Consultation"/> </code> <status value="scheduled"/> <doNotPerform value="false"/> <performer> <reference value="Practitioner/14"/> <display value="Doctor Dave"/> </performer> </plannedActivityDetail> --> <activity> <!-- This activity is for the encounter with the doctor --> <plannedActivityReference> <reference value="#activity-2"/> </plannedActivityReference> </activity> </ CarePlan >
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.
FHIR
®©
HL7.org
2011+.
FHIR
Release
4
(Technical
Correction
#1)
(v4.0.1)
R6
hl7.fhir.core#6.0.0-ballot3
generated
on
Fri,
Nov
1,
2019
09:34+1100.
QA
Page
14,
2025
20:58+0000.
Links:
Search
|
Version
History
|
Table
of
Contents
|
Credits
Glossary
|
QA
|
Compare
to
R3
R4
|
Compare
to
R5
|
Compare
to
Last
Ballot
|
|
Propose
a
change