This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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 R3 R2
Encounter to GP (Primary care Practitioner) (id = "gpvisit")
<CarePlan xmlns="http://hl7.org/fhir"> <id value="gpvisit"/> <text> <status value="additional"/> <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div> </text> <contained> <Condition><!-- This is the reason for the encounter. It is referenced by the concern --> <id value="p1"/> <subject> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </subject> <code><!-- Could coded if we wanted to... --> <text value="Overseas encounter"/> </code> <status value="confirmed"/> </Condition> </contained> <patient> <reference value="Patient/100"/> <display value="Peter James Chalmers"/> </patient> <status value="active"/> <period><!-- This is the time the plan started - i.e. when they arrived --> <start value="2013-01-01T10:30:00+00:00"/> </period><!-- No end yet as the encounter is still in progress. --> <concern> <reference value="#p1"/> <display value="obesity"/> </concern> <participant id="part1"> <role> <coding> <system value="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="local"/> <code value="doc"/> </coding> <text value="doctor"/> </role> <member> <reference value="Practitioner/14"/> <display value="Doctor Dave"/> </member> </participant> <goal> <description value="Complete consultation"/> </goal> <activity> <status value="completed"/> <prohibited value="false"/> <actionResulting><!-- 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"/> </actionResulting> <simple><!-- This activity is for the initial nurse encounter where vitals are taken. It has been completed. --> <category value="encounter"/> <code> <coding> <system value="local"/> <code value="nursecon"/> </coding> <text value="Nurse Consultation"/> </code> <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> </simple> </activity> <activity> <status value="scheduled"/> <prohibited value="false"/> <simple><!-- 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 --> <category value="encounter"/> <code> <coding> <system value="local"/> <code value="doccon"/> </coding> <text value="Doctor Consultation"/> </code><!-- The status is 'scheduled' so the doctor knows the patient is waiting. --> <performer><!-- refer to the participant (the nurse) in this resource --> <reference value="Practitioner/14"/> <display value="Doctor Dave"/> </performer> </simple> </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.