Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28079

Comment on errata 3.1.1: Smoking Status value set and binding

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 3.1.0 [deprecated]
    • Cross-Group Projects
    • Profiles and Extensions
    • Hide

      Current resolution based on CGP discussion 16 July 2020 is to roll back the binding to preferred (from required) with a Max binding in the current errata package. And to consider the appropriate set of codes going forward. The change makes the binding a "should". As informational - the Max binding extension elementdefinition.maxValueSet - I.e., use the preferred set but requires SNOMED (the Max). Will create a new tracker for future definition of preferred codes.

      Show
      Current resolution based on CGP discussion 16 July 2020 is to roll back the binding to preferred (from required) with a Max binding in the current errata package. And to consider the appropriate set of codes going forward. The change makes the binding a "should". As informational - the Max binding extension elementdefinition.maxValueSet - I.e., use the preferred set but requires SNOMED (the Max). Will create a new tracker for future definition of preferred codes.
    • Brett Marquard/Eric Haas: 10-0-1
    • Correction
    • Compatible, substantive

    Description

      The errata changed the value set definition for the Value Set USCoreSmokingStatusObservationCodes To be all of SCT. That is an improper CLD for this value set and is a poor approach to meet the desired outcome. The proper way to do this would be:

      1. If possible, identify the additional codes that were needed that were not available and add them to the existing (prior) value set. This is not required but should be easy given the problem was there are codes that were not available.
      2. Use preferred binding strength for this improved value set.
      3. create a MAX minding to all of SCT. for the element.

      The change as it stands is very problematic and is NOT CONFORMANT to proper standards for value set definitions.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rob_McClure Rob McClure
            Rob McClure
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: