Skip to end of metadata
Go to start of metadata

Value sets

  • Created: Extended Pregnancy Status 2.16.840.1.113762.1.4.1099.24
    • Published in VSAC on 11/9/2018
  • Modified: Patient Education 2.16.840.1.113883.11.20.9.34
  • Modified: Substance-Reactant for Intolerance 2.16.840.1.113762.1.4.1010.1

Other comments were made in the November errata list that relate to value sets, but don't require direct modifications to the value sets. For example, some value sets simply needed to be imported into Trifolia so that the Trifolia export aligns with the value set definition that already exist in VSAC.

Errata list (from 2018Dec_C-CDAR2.1_Errata_list.xlsx)

LRN R2.1 Errata
QA of IG CommentsPILOT Auto UpdateCommentTemplateIdValue Set IDSummary descriptionErrata Release DatePrior textAfter UpdateSearchable CONF #CommentsQA StatusBrett Response
okEasy Yes1619urn:hl7ii:2.16.840.1.113883.10.20.22.4.12:2014-06-09 Procedure Activity Act (V2) The cardinality is wrong - should be 0..* (which would make these the same as the cardinality for Author Participation in Procedure Activity Procedure)9/9/2018SHOULD contain at least one [1..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32477). SHOULD contain zero or many [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32477).32477
okEasy Yes1619urn:hl7ii:2.16.840.1.113883.10.20.22.4.13:2014-06-09 Procedure Activity Observation (V2) The cardinality is wrong - should be 0..* (which would make these the same as the cardinality for Author Participation in Procedure Activity Procedure)9/9/2018SHOULD contain at least one [1..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32478).SHOULD contain zero or many [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-32478).32478
okValue SetConstraint did not change. VSAC updated to include new code. Similar issue to Patient Education on row 8.Yes1608urn:hl7ii:2.16.840.1.113883.10.20.22.4.27:2014-06-09 Vital Sign Observation (V2)Vital Sign Result Type urn:oid:2.16.840.1.113883.3.88.12.80.62Add the methodless code for head circumference 9843-4 Head Occipital-frontal circumference. Do not remove the existing method-specific code because of the existing use of this code within this value set. We should not call this a "legacy code" because it is an active code, but it is a type of "legacy use" of the code. By keeping this code we are not encouraging, or would be supportive of, adding method-specific codes for other "vital sign" observations. The expectation is that the codes included in the value set should be methodless as a rule.6/14/20185. SHALL contain exactly one [1..1] code (CONF:1098-7301). a. This code SHOULD contain zero or one [0..1] @code, which SHOULD be selected from ValueSet Vital Sign Result Type urn:oid:2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:1098-32934).5. SHALL contain exactly one [1..1] code (CONF:1098-7301). a. This code SHOULD contain zero or one [0..1] @code, which SHOULD be selected from ValueSet Vital Sign Result Type urn:oid:2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:1098-32934).32934Constraint did not change. VSAC updated to include new code.
okValue Set Yes1610urn:hl7ii:2.16.840.1.113883.10.20.22.4.52:2015-08-01 Immunization Activity (V3)urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 SPL Drug Route of Administration Terminology Change the Medication Route FDA value set to use the value set defined in VSAC called "SPL Drug Route of Administration Terminology"6/12/2018MAY contain zero or one [0..1] routeCode, which SHALL be selected from ValueSet Medication Route FDA urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 DYNAMIC (CONF:1198-8839). Value Set: Medication Route FDA urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 Route of Administration value set is based upon FDA Drug Registration and Listing Database (FDA Orange Book) which are used in FDA Structured Product Labeling (SPL). Value Set Source: https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.113883.3.88.12.3221.8.7MAY contain zero or one [0..1] routeCode, which SHALL be selected from ValueSet SPL Drug Route of Administration Terminology urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 DYNAMIC (CONF:1198-8839). Value Set: SPL Drug Route of Administration Terminology urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 (Clinical Focus: The set of route of administration concepts that may be used in structured product labeling.),(Data Element Scope: Ordered, administered, medication route),(Inclusion Criteria: Selected concepts that are descendent of C38114 as determined by the FDA. These concepts are linked to "SPL Drug Route of Administration Terminology (Code C54455)" by Concept_In_Subset.),(Exclusion Criteria: As determined by the FDA those routes not to be used in SPL (navigational concepts, etc.)) This value set was imported on 7/25/2018 with a version of 20180521. Value Set Source: https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.3.88.12.3221.8.7/expansion32960Constraint's requirements did not actually change, but the constraint reflecst the updated name of the value set.
okValue SetAttempted to reach out to OPA to see if they would add "Possibly Pregnant" to their "Pregnancy Status" value set. No response. Had to create a new value set in VSAC and update the constraint to reference the new value set.Yes1599urn:oid:2.16.840.1.113883.10.20.15.3.8 Pregnancy Observationurn:oid:2.16.840.1.113762.1.4.1099.24 Extended Pregnancy StatusAdd a new value set to VSAC that represents Pregnancy Status, with an additional code for "Possibly Pregnant". Update the constraint to reference the new value set from VSAC.11/8/20187. SHALL contain exactly one [1..1] value with @xsi:type="CD" (CONF:81-457). a. This value SHALL contain exactly one [1..1] @code="77386006" Pregnant (CodeSystem: SNOMED CT urn:oid:2.16.840.1.113883.6.96) (CONF:81-26460).SHALL contain exactly one [1..1] value with @xsi:type="CD", where the code SHALL be selected from ValueSet Extended Pregnancy Status urn:oid:2.16.840.1.113762.1.4.1099.24 DYNAMIC (CONF:81-457).457Attempted to reach out to OPA to see if they would add "Possibly Pregnant" to their "Pregnancy Status" value set. No response. Had to create a new value set in VSAC and update the constraint to reference the new value set.
okValue SetPrior VS was def version 20151210 and expansion version 20180615 done against Snomed CT version 2018-03 New VS is def version 20181103 and expansion version 20181120 done against Snomed CT version 2018-09 No way to know to update the whole value set, and no way to tell how different the new VS expansion is from the prior VS expansion.Yes1583urn:hl7ii:2.16.840.1.113883.10.20.22.4.20:2014-06-09 Instruction V2urn:oid:2.16.840.1.113883.11.20.9.34 Patient EducationAdd "Education with explicit context (situation)" code to existing "Patient Education" value set.4/12/20184. SHALL contain exactly one [1..1] code, which SHOULD be selected from ValueSet Patient Education urn:oid:2.16.840.1.113883.11.20.9.34 DYNAMIC (CONF:1098-16884).4. SHALL contain exactly one [1..1] code, which SHOULD be selected from ValueSet Patient Education urn:oid:2.16.840.1.113883.11.20.9.34 DYNAMIC (CONF:1098-16884).16884No changes needed to constraint, just added a code to the value set.
okValue Set Yes1594 1595 1596 urn:oid:2.16.840.1.113762.1.4.1010.1 Substance-Reactant for IntoleranceModify the value set to limit the possibly codes. The value set is too broad in its current state.11/8/2018 No constraint changes necessary. Only updated the value set.
okValue Set Yes1527 1423urn:hl7ii:2.16.840.1.113883.10.20.22.4.38:2015-08-01 Social History Observation (V3)urn:oid:2.16.840.1.113883.3.88.12.80.60 Social History TypeUse the Social History Type value set in VSAC. Add the codes that are listed for the value set in the IG to the value set in VSAC.11/8/2018Value Set: Social History Type Set Definition 2.16.840.1.113883.3.88.12.80.60 STATIC 2008-12-18 Code System(s): SNOMED CT 2.16.840.1.113883.6.965. SHALL contain exactly one [1..1] code, which SHOULD be selected from ValueSet Social History Type urn:oid:2.16.840.1.113883.3.88.12.80.60 STATIC 2008-12-18 (CONF:1198-8558). Value Set: Social History Type urn:oid:2.16.840.1.113883.3.88.12.80.60 (Clinical Focus: Classification of questions bearing on a patient's behavior, achievement, and exogenous health factors),(Data Element Scope: ),(Inclusion Criteria: ),(Exclusion Criteria: ) This value set was imported on 11/5/2018 with a version of 20180917. Value Set Source: https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.3.88.12.80.60/expansion8558No change to constraints necessary. Only updated the value set to use the one from VSAC.
okValue Set Yes1512urn:hl7ii:2.16.840.1.113883.10.20.22.4.61:2015-08-01 Policy Activity (V3) Update the in-line example in the IG for the Policy Activity template to use the correct code system name.11/8/2018<code code="12" displayName="Medicare Secondary Working Aged Beneficiary or Spouse with Employer Group Health Plan" codeSystemName="ASC X12" codeSystem="2.16.840.1.113883.6.255.1336"><code code="12" displayName="Medicare Secondary Working Aged Beneficiary or Spouse with Employer Group Health Plan" codeSystemName="Insurance Type Code" codeSystem="2.16.840.1.113883.6.255.1336"> No change to constraints. Just updating the example for the template to be accurate.In the example, the codeSystemName is codeSystemName="Source of Payment Typology (PHDSC)">, but in VSAC the CodeSystemName is SOP. Which is right?
okharder Yes1506urn:hl7ii:2.16.840.1.113883.10.20.22.1.10:2015-08-01 Unstructured Document (V3) The constraint is hand-written and use an incosistent format for the date compared to the automatically generated constraint prose. Update the constraint so that it uses a consistent date format for the value set. The value of @mediaType, if present, SHALL be drawn from the value set 2.16.840.1.113883.11.20.7.1 SupportedFileFormats STATIC 20100512 (CONF:1198-7623).The value of @mediaType, if present, SHALL be drawn from the ValueSet SupportedFileFormats urn:oid:2.16.840.1.113883.11.20.7.1 STATIC 2010-05-12 (CONF:1198-7623).7623 This requires constraint logic to be written
okhardersuch that it changes are harder to implement in Art Décor. Assistance required. Not sure how this would affect MDHT.Yes1501urn:oid:2.16.840.1.113883.10.20.22.4.130 Nutrition Recommendation All entryRelationship constraints in the template are now branched, including the "such that it" text. MAY contain zero or more [0..*] entryRelationship (CONF:1098-32382). MAY contain zero or more [0..*] entryRelationship (CONF:1098-32384). MAY contain zero or more [0..*] entryRelationship (CONF:1098-32386). MAY contain zero or more [0..*] entryRelationship (CONF:1098-32388). MAY contain zero or more [0..*] entryRelationship (CONF:1098-32390). MAY contain zero or more [0..*] entryRelationship (CONF:1098-32632).MAY contain zero or more [0..*] entryRelationship (CONF:1098-32382) such that it MAY contain zero or more [0..*] entryRelationship (CONF:1098-32384) such that it MAY contain zero or more [0..*] entryRelationship (CONF:1098-32386) such that it MAY contain zero or more [0..*] entryRelationship (CONF:1098-32388) such that it MAY contain zero or more [0..*] entryRelationship (CONF:1098-32390) such that it MAY contain zero or more [0..*] entryRelationship (CONF:1098-32632) such that it32382 32384 32386 32388 32390 32632 "such that it" changes are harder to implement in Art Décor. Assistance required.
okeasy Yes1486urn:hl7ii:2.16.840.1.113883.10.20.22.2.20:2015-08-01 Past Medical History (V3) Fix section name in C-CDA to state 'Past Medical History' instead of 'History of Past Illness Section (V3)' History of Past Illness Section (V3)Past Medical History (V3)
okDuplicate No1480 Duplicate of comment #849 which was implemented in a previous errata update.
okNo impact on Art DécorConstraints are not modified. This was an update to a hand-generated table that was incorrect.No927 Fix the document summary table (Table #1) so that it has the correct required vs. optional sections for Consultation Note. Several sections for Consultation note are showing required, when they are optional. Required: Assessment and Plan Section (V2), Assessment Section, and Plan of Treatment Section (V2)Optional: Assessment Section Assessment and Plan Section (V2) Plan of Treatment Section (V2) Constraints are not modified. This was an update to a hand-generated table that was incorrect.
okNo impact on Art DécorConstraints are not modified. This was an update to a hand-generated table that was incorrect.No928 Fix the document summary table (Table #1) so that it has the correct required vs. optional sections for History and Physical Document. Several sections for History and Physical Document are showing required, when they are optional. Required: Chief Complaint and Reason for Visit Section** Chief Complaint Section** Reason for Visit Section**Optional: Chief Complaint Section Chief Complaint and Reason for Visit Section Reason for Visit Section Constraints are not modified. This was an update to a hand-generated table that was incorrect.
okNo impact on Art DécorConstraints are not modified. This was an update to a hand-generated table that was incorrect.No929 Fix the document summary table (Table #1) so that it has the correct required vs. optional sections for Consultation Note. The "Reason for Visit" section for Consultation note are showing required, when they are optional. Required: Reason for Visit SectionOptional: Reason for Visit Section Constraints are not modified. This was an update to a hand-generated table that was incorrect.
okmediumNeed to see what we are up against when we attemp to implement.Yes995urn:hl7ii:2.16.840.1.113883.10.20.22.4.54:2014-06-09 Immunization Medication Information (V2) Change SHALL to SHOULD for lotNumberText. Add guidance that lotNumberText should be included if known. It may not be known for historical immunizations, planned immunizations, or refused/deferred immunizations. This manufacturedMaterial SHALL contain exactly one [1..1] lotNumberText (CONF:1098-9014).lotNumberText should be included if known. It may not be known for historical immunizations, planned immunizations, or refused/deferred immunizations. b. This manufacturedMaterial SHOULD contain zero or one [0..1] lotNumberText (CONF:1098-9014).9014Need to see what we are up against when we attemp to implement.


  • No labels