StructureDefinition-2.16.840.1.113883.10.20.22.4.19

Sourcehl7.cda.us.ccda#current:Consolidated CDA Release 2.1 StructureDefinition Publication (v5.0.0)
resourceTypeStructureDefinition
id2.16.840.1.113883.10.20.22.4.19
canonicalhttp://hl7.org/cda/us/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.4.19
version2.1
statusdraft
publisherHealth Level Seven
nameIndicationV3
titleIndication (V3)
date2023-08-24T14:33:15+00:00
descriptionThis template represents the rationale for an action such as an encounter, a medication administration, or a procedure. The id element can be used to reference a problem recorded elsewhere in the document, or can be used with a code and value to record the problem. Indications for treatment are not laboratory results; rather the problem associated with the laboratory result should be cited (e.g., hypokalemia instead of a laboratory result of Potassium 2.0 mEq/L). Use the Drug Monitoring Act [templateId 2.16.840.1.113883.10.20.22.4.123] to indicate if a particular drug needs special monitoring (e.g., anticoagulant therapy). Use Precondition for Substance Administration (V2) [templateId 2.16.840.1.113883.10.20.22.4.25.2] to represent that a medication is to be administered only when the associated criteria are met. Many templates in C-CDA R2.1 reference the Indications V2 Template. In the next C-CDA release we will update those templates to reference the Indications V3 template. The Reason 2.16.840.1.113883.10.20.24.3.88:2023-05-01 should used to represent the justification for an action, or for not performing an action, such as patient, system, or non-problem/diagnosis medical-related reasons Immunization Refusal Reason 2.16.840.1.113883.10.20.22.4.53 should be used to represent the rationale for the patient declining an immunization as the value set is crafted for the immunization use case.
jurisdictionsus
fhirVersion5.0.0
kindlogical
abstractfalse
sdTtypehttp://hl7.org/cda/stds/core/StructureDefinition/Observation
derivationconstraint
basehttp://hl7.org/cda/stds/core/StructureDefinition/Observation
Usages
Name Flags Card. Type Description & Constraints doco
. . Observation CDAR2.Observation XML Namespace: urn:hl7-org:v3
This logical model cannot be the target of a reference
. . . classCode 1..1 classCode
Fixed Value: OBS
. . . moodCode 1..1 moodCode
Fixed Value: EVN
. . . Slices for templateId 1 .. Slice: Unordered, Open by value:root, value:extension
. . . . templateId:templateId1 1..1 templateId
. . . . . root 1..1 root
Required Pattern: 2.16.840.1.113883.10.20.22.4.19
. . . . . extension 1..1 extension
Required Pattern: 2023-05-01
. . . id 1..* If the id element is used to reference a problem recorded elsewhere in the document then this id must equal another entry/id in the same document instance. Application Software must be responsible for resolving the identifier back to its original object and then rendering the information in the correct place in the containing section's narrative text. Its purpose is to obviate the need to repeat the complete XML representation of the referred to entry when relating one entry to another.
. . . code 1..1 code
Binding: Problem Type (SNOMEDCT) ( example )
. . . statusCode 1..1 statusCode
. . . . code 1..1 code
Fixed Value: completed
. . . effectiveTime 0..1 effectiveTime
. . . value 0..1 value
Binding: Problem ( example )

doco Documentation for this format

Produced 08 Sep 2023