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

Remove required binding on procedure and condition

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      US Core (FHIR)
    • Raised in Version:
      3.2.0
    • Work Group:
      Cross-Group Projects
    • Related Artifact(s):
      USCoreProcedureProfile
      USCoreCondition
    • Related Page(s):
      (many)
    • Resolution Description:
      Hide

      Will update to extensible.

      Improve guidance (https://build.fhir.org/ig/HL7/US-Core/conformance-expectations.html):

      • FHIR base documentation on extensible: http://hl7.org/fhir/R4/terminologies.html#extensible
      • Conformance in base requires even free text conceptual overlaps to be non-conformant if the coded value is not included.
      • Will add text that US Core understands the base FHIR core requirement but gives flexibility that sometimes folks cannot fully comply because they have text only - that this is sometimes necessary and expected for legacy data.
      • For newly recorded, non legacy data, a system SHOULD meet the conformance of the value set?
      Show
      Will update to extensible. Improve guidance ( https://build.fhir.org/ig/HL7/US-Core/conformance-expectations.html): FHIR base documentation on extensible: http://hl7.org/fhir/R4/terminologies.html#extensible Conformance in base requires even free text conceptual overlaps to be non-conformant if the coded value is not included. Will add text that US Core understands the base FHIR core requirement but gives flexibility that sometimes folks cannot fully comply because they have text only - that this is sometimes necessary and expected for legacy data. For newly recorded, non legacy data, a system SHOULD meet the conformance of the value set?
    • Resolution Vote:
      Floyd Eisenberg / Brett Marquard: 8-1-0
    • Change Category:
      Correction
    • Change Impact:
      Non-substantive

      Description

      Making this binding required will cause an unnecessary burden for implementers to map content that historically not been mapped for no additional benefit. For example, I will not have to map thousands of free-text procedures for no additional value. 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              atorres Drew Torres
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: