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

Clarify Guidance for missing data for Coding data type element

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 4.0.0
    • Cross-Group Projects
    • General Guidance
    • Missing Data
    • Hide

      change:

      For coded data elements:

      • example, preferred, or extensible binding strengths (CodeableConcept datatypes):
        • if the source systems has text but no coded data, only the text element is used.
        • if there is neither text or coded data:
          • use the appropriate “unknown” concept code from the value set if available
          • if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System.

      to

      For coded data elements:

      • example, preferred, or extensible binding strengths (CodeableConcept or Coding datatypes):
        • if the source systems has text but no coded data, only the text element is used.
          • if there is neither text or coded data:
            • use the appropriate “unknown” concept code from the value set if available
            • if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System.
      • this means that text only data would be treated as `display` element when using it in Coding.
      Show
      change: For coded data elements: example , preferred , or extensible binding strengths (CodeableConcept datatypes): if the source systems has text but no coded data, only the text element is used. if there is neither text or coded data: use the appropriate “unknown” concept code from the value set if available if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System . to For coded data elements: example , preferred , or extensible binding strengths (CodeableConcept or Coding datatypes): if the source systems has text but no coded data, only the text element is used. if there is neither text or coded data: use the appropriate “unknown” concept code from the value set if available if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System . this means that text only data would be treated as `display` element when using it in Coding.
    • Eric Haas/Brett Marquard: 26-0-1
    • Clarification
    • Compatible, substantive

    Description

      The guidance around how to handle missing data does not include Coding datatype elements (encounter.class).  Request the guidance be updated to include Coding datatypes.

       

      For coded data elements:

      • examplepreferred, or extensible binding strengths (CodeableConcept and Coding datatypes):
        • if the source systems has text but no coded data, only the text element is used.
        • if there is neither text or coded data:
          • use the appropriate “unknown” concept code from the value set if available
          • if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System.

      Attachments

        Activity

          People

            ehaas Eric Haas
            ellennies_cerner Ellen Nies
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: