2.16.840.1.113883.10.22.4.40

Comments on this page

Template IPSPlannedEncounter

An Encounter is an interaction between a patient and care provider(s) for the purpose of providing healthcare-related service(s). Healthcare services include health assessment. Examples: outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, or telephone call.

Actual version

Id	2.16.840.1.113883.10.22.4.40	Effective Date	2020‑05‑08 18:18:38
Status	Under pre-publication review	Version Label	TI-2020
Name	IPSPlannedEncounter	Display Name	IPS Planned Encounter
Description An Encounter is an interaction between a patient and care provider(s) for the purpose of providing healthcare-related service(s). Healthcare services include health assessment. Examples: outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, or telephone call.
Context	Parent nodes of template element with id 2.16.840.1.113883.10.22.4.40
Classification	CDA Entry Level Template
Open/Closed	Open (other than defined elements are allowed)
Relationship	Adaptation: template 1.3.6.1.4.1.19376.1.5.3.1.4.14 IHE Encounters (2017‑03‑22 15:35:30) ref IHE-PCC- Adaptation: template 2.16.840.1.113883.10.20.1.25 (DYNAMIC) Adaptation: template 2.16.840.1.113883.10.20.1.21 Encounter activity (DYNAMIC) ref ccd1-
Example	Example <encounter classCode="ENC" moodCode="cs">   <templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.14"/>  <templateId root="2.16.840.1.113883.10.20.1.21"/>  <templateId root="2.16.840.1.113883.10.20.1.25"/>  <id root="1.2.3.999" extension="--example only--"/>  <code/>  <text>     <reference value="tel:+1-12345678"/>  </text>  <effectiveTime>     <low value="20170413114059"/>  </effectiveTime>  <priorityCode/>  <performer>     <time/>  </performer>  <participant typeCode="LOC">     <participantRole classCode="SDLOC"/>    <id/>    <code/>    <addr/>    <telecom/>    <playingEntity classCode="PLC">       <name/>    </playingEntity>  </participant></encounter>
Item DT Card Conf Description Label hl7:encounter (IPS...ter) @classCode cs 0 … 1 F ENC @moodCode cs 1 … 1 R   CONF @moodCode shall be "APT" or @moodCode shall be "ARQ" or @moodCode shall be "PRP" hl7:templateId II 1 … 1 M (IPS...ter) @root uid 1 … 1 F 2.16.840.1.113883.10.22.4.40 hl7:id II 0 … * R (IPS...ter) hl7:code CD 1 … 1 R (IPS...ter) hl7:text ED 0 … 1 R The <text> element if present points to the text describing the problem being recorded; including any dates, comments, et cetera. The <reference> contains a URI in value attribute. This URI points to the free text description of the problem in the document that is being described.</reference></text> (IPS...ter)   Example <text>   <reference value="#problem-1"/></text> hl7:reference TEL 1 … 1 M (IPS...ter) @value url 1 … 1 R When used it shall refer to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1 hl7:effectiveTime IVL_TS 0 … 1 (IPS...ter) hl7:priorityCode CE 0 … 1 (IPS...ter) hl7:performer 0 … * (IPS...ter) hl7:time 0 … 1 (IPS...ter) hl7:participant 0 … * (IPS...ter) @typeCode cs 1 … 1 F LOC hl7:participantRole 1 … 1 M (IPS...ter) @classCode cs 1 … 1 F SDLOC hl7:id 0 … * (IPS...ter) hl7:code 0 … 1 (IPS...ter) hl7:addr 0 … * (IPS...ter) hl7:telecom 0 … * (IPS...ter) hl7:playingEntity 1 … 1 M (IPS...ter) @classCode cs 1 … 1 F PLC hl7:name 1 … * R (IPS...ter)

List of all versions of this template

• 2020-05-08 18:18:38 (Under pre-publication review)