| Name | Flags | Card. | Type |
Description & Constraints
|
|---|---|---|---|---|
Observation
|
||||
classCode
|
1..1 | Required Pattern: OBS | ||
|
moodCode
|
1..1 | Required Pattern: EVN | ||
|
negationInd
|
0..1 | The negationInd is used to indicate the absence of the condition in observation/value. A negationInd of "true" coupled with an observation/value of SNOMED code 64572001 "Disease (disorder)" indicates that the patient has no known conditions. | ||
Slices for templateId
|
Slice: Unordered, Open by value:root, value:extension | |||
templateId:primary
|
1..1 | |||
root
|
1..1 | Required Pattern: 2.16.840.1.113883.10.20.22.4.4 | ||
extension
|
1..1 | Required Pattern: 2015-08-01 | ||
|
id
|
1..* | |||
|
code
|
C | 1..1 |
Binding:
Problem Type (SNOMEDCT)
( preferred
) 1198-32950: If code is selected from ValueSet Problem Type (SNOMEDCT) urn:oid:2.16.840.1.113883.3.88.12.3221.7.2 **DYNAMIC**, then it **SHALL** have at least one [1..*] translation, which **SHOULD** be selected from ValueSet Problem Type (LOINC) urn:oid:2.16.840.1.113762.1.4.1099.28 **DYNAMIC** (CONF:1198-32950) (CONF:1198-32950). |
|
|
statusCode
|
1..1 | |||
code
|
1..1 | Required Pattern: completed | ||
|
effectiveTime
|
1..1 | If the problem is known to be resolved, but the date of resolution is not known, then the high element **SHALL** be present, and the nullFlavor attribute **SHALL** be set to 'UNK'. Therefore, the existence of a high element within a problem does indicate that the problem has been resolved. | ||
|
low
|
1..1 | The effectiveTime/low (a.k.a. "onset date") asserts when the condition became biologically active. | ||
|
high
|
0..1 | The effectiveTime/high (a.k.a. "resolution date") asserts when the condition became biologically resolved. | ||
|
value
|
1..1 | http://hl7.org/fhir/cda/StructureDefinition/CD | Binding: Problem ( preferred ) | |
|
code
|
0..1 | A negationInd of "true" coupled with an observation/value/@code of SNOMED code 64572001 "Disease (disorder)" indicates that the patient has no known conditions. | ||
|
qualifier
|
0..* |
The observation/value and all the qualifiers together (often referred to as a post-coordinated expression) make up one concept. Qualifiers constrain the meaning of the primary code, and cannot negate it or change its meaning. Qualifiers can only be used according to well-defined rules of post-coordination and only if the underlying code system defines the use of such qualifiers or if there is a third code system that specifies how other code systems may be combined.
For example, SNOMED CT allows constructing concepts as a combination of multiple codes. SNOMED CT defines a concept "pneumonia (disorder)" (233604007) an attribute "finding site" (363698007) and another concept "left lower lobe of lung (body structure)" (41224006). SNOMED CT allows one to combine these codes in a code phrase, as shown in the sample XML. |
||
|
Slices for translation
|
Slice: Unordered, Open by | |||
|
translation:alt
|
0..* | |||
|
code
|
0..1 | |||
|
author
|
0..* | http://hl7.org/fhir/cda/StructureDefinition/Author | ||
|
Slices for entryRelationship
|
Slice: Unordered, Open by profile:observation | |||
entryRelationship:age
|
0..1 | |||
typeCode
|
1..1 | Required Pattern: SUBJ | ||
|
inversionInd
|
1..1 | Required Pattern: true | ||
|
observation
|
1..1 | http://hl7.org/fhir/cda/StructureDefinition/Observation | ||
|
entryRelationship:prognosis
|
0..1 | |||
|
typeCode
|
1..1 | Required Pattern: REFR | ||
|
observation
|
1..1 | http://hl7.org/fhir/cda/StructureDefinition/Observation | ||
|
entryRelationship:priority
|
0..* | |||
|
typeCode
|
1..1 | Required Pattern: REFR | ||
|
observation
|
1..1 | http://hl7.org/fhir/cda/StructureDefinition/Observation | ||
|
entryRelationship:status
|
0..1 | |||
|
typeCode
|
1..1 | Required Pattern: REFR | ||
|
observation
|
1..1 | http://hl7.org/fhir/cda/StructureDefinition/Observation | ||
|
Documentation for this format
|
||||