Id2.16.840.1.113883.10.20.22.4.68Effective Date2014‑06‑09
Statusretired RetiredVersion Label2.1
NameFunctionalStatusProblemObservationDEPRECATEDDisplay NameFunctional Status Problem Observation (DEPRECATED)
Description
A functional status problem observation is a clinical statement that represents a patient’s functional perfomance and ability. THIS TEMPLATE HAS BEEN DEPRECATED IN C-CDA R2 AND MAY BE DELETED FROM A FUTURE RELEASE OF THIS IMPLEMENTATION GUIDE. USE OF THIS TEMPLATE IS NOT RECOMMENDED. *Reason for deprecation*: Functional Status Problem Observation has been merged, without loss of expressivity, into Functional Status Observation (2.16.840.1.113883.10.20.22.4.67:2014-06-09).
ContextParent nodes of template element with id 2.16.840.1.113883.10.20.22.4.68
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 5 transactions and 8 templates, Uses 0 templates
Used by as NameVersion
2.16.840.1.113883.3.1937.99.3.4.31Transactionfinal Transfer Summary (V2)2015‑08‑01
2.16.840.1.113883.3.1937.99.3.4.25Transactionfinal Discharge Summary (V3)2015‑08‑01
2.16.840.1.113883.3.1937.99.3.4.22Transactionfinal Consultation Note (V3)2015‑08‑01
2.16.840.1.113883.3.1937.99.3.4.23Transactionfinal Continuity of Care Document (CCD) (V3)2015‑08‑01
2.16.840.1.113883.3.1937.99.3.4.30Transactionfinal Referral Note (V2)2015‑08‑01
2.16.840.1.113883.3.51.60.2.4linkpending BC CDA ClinicalDocumentDischargeSummary (V3) (2.1)2019‑03‑19 14:15:51
2.16.840.1.113883.10.20.22.1.2linkdraft Continuity of Care Document (CCD) (V3) (2.1)2015‑08‑01
2.16.840.1.113883.10.20.22.1.4linkdraft Consultation Note (V3) (2.1)2015‑08‑01
2.16.840.1.113883.10.20.22.1.8linkdraft Discharge Summary (V3) (2.1)2015‑08‑01
2.16.840.1.113883.10.20.22.1.13linkdraft Transfer Summary (V2) (2.1)2015‑08‑01
2.16.840.1.113883.10.20.22.1.14linkdraft Referral Note (V2) (2.1)2015‑08‑01
2.16.840.1.113883.10.20.22.2.14Containmentdraft Functional Status Section (V2) (2.1)2014‑06‑09
2.16.840.1.113883.10.20.22.2.14Containmentpending Functional Status Section (V2) (2.1)2019‑03‑16 20:25:20
RelationshipSpecialization: template 2.16.840.1.113883.10.12.303 CDA Observation (2005‑09‑07)
ref
ad1bbr-

Version: template 2.16.840.1.113883.10.20.22.4.68 Functional Status Problem Observation (2013‑01‑31)
ItemDTCardConfDescriptionLabel
cda:observation
FuncdotsATED
@classCode
cs1 … 1FOBSCONFdots4282
 SHALL contain exactly one [1..1] @classCode="OBS" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-14282).
@moodCode
cs1 … 1FEVNCONFdots4283
 SHALL contain exactly one [1..1] @moodCode="EVN" Event (CodeSystem: ActMood urn:oid:2.16.840.1.113883.5.1001 STATIC) (CONF:1098-14283).
@negationInd
bl0 … 1 MAY contain zero or one [0..1] @negationInd (CONF:1098-14307).CONFdots4307
cda:templateId
II1 … 1MC-CDA R1.1 templateId root without an extensionCONFdots2936
@root
uid1 … 1F2.16.840.1.113883.10.20.22.4.68
cda:templateId
II1 … 1MSHALL contain exactly one [1..1] templateId (CONF:1098-14312) such that itCONFdots4312
@root
uid1 … 1F2.16.840.1.113883.10.20.22.4.68CONFdots4313
 SHALL contain exactly one [1..1] @root="2.16.840.1.113883.10.20.22.4.68" (CONF:1098-14313).
@extension
st1 … 1F2014-06-09CONFdots2601
 SHALL contain exactly one [1..1] @extension="2014-06-09" (CONF:1098-32601).
cda:id
II1 … *SHALL contain at least one [1..*] id (CONF:1098-14284).CONFdots4284
cda:code
CD1 … 1MSHALL contain exactly one [1..1] code (CONF:1098-14314).CONFdots4314
@code
CONF1 … 1F248536006
@codeSystem
1 … 1F2.16.840.1.113883.6.96
cda:text
0 … 1RSHOULD contain zero or one [0..1] text (CONF:1098-14304).CONFdots4304
cda:reference
0 … 1RThe text, if present, SHOULD contain zero or one [0..1] reference (CONF:1098-15552).CONFdots5552
@value
0 … 1 The reference, if present, SHOULD contain zero or one [0..1] @value (CONF:1098-15553).CONFdots5553
 Schematron assertrolered error 
 testnot(@value) or starts-with(@value, '#') 
 MessageThis reference/@value SHALL begin with a '#' and SHALL point to its corresponding narrative (using the approach defined in CDA Release 2, section 4.3.5.1) 
cda:statusCode
CS1 … 1MSHALL contain exactly one [1..1] statusCode (CONF:1098-14286).CONFdots4286
@code
CONF1 … 1Fcompleted
cda:effectiveTime
IVL_TS0 … 1RSHOULD contain zero or one [0..1] effectiveTime (CONF:1098-14287).CONFdots4287
cda:low
1 … 1RThe effectiveTime, if present, SHALL contain exactly one [1..1] low (CONF:1098-26456).

The value of effectiveTime/low represents onset date.		CONFdots6456
cda:high
0 … 1RThe effectiveTime, if present, MAY contain zero or one [0..1] high (CONF:1098-26457).

If the problem is resolved, record the resolution date in effectiveTime/high. If the problem is known to be resolved but the resolution date is not known, use @nullFlavor="UNK". If the problem is not resolved, do not include the high element.		CONFdots6457
cda:value
CD1 … 1MSHALL contain exactly one [1..1] value with @xsi:type="CD", where the code SHOULD be selected from ValueSet Problem urn:oid:2.16.840.1.113883.3.88.12.3221.7.4 DYNAMIC (CONF:1098-14291).CONFdots4291
@nullFlavor
cs0 … 1 This value MAY contain zero or one [0..1] @nullFlavor (CONF:1098-14292).CONFdots4292
 ConstraintIf the diagnosis is unknown or the SNOMED code is unknown, @nullFlavor SHOULD be “UNK”. If the diagnosis is known but the code cannot be found in the Value Set, @nullFlavor SHOULD be “OTH” and the known diagnosis code SHOULD be placed in the translation element
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.3.88.12.3221.7.4 Problem (DYNAMIC)
cda:methodCode
0 … 1MAY contain zero or one [0..1] methodCode (CONF:1098-14316).CONFdots4316