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

Remove required binding on procedure and condition

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 3.2.0 [deprecated]
    • Cross-Group Projects
    • US Core Condition Profile [deprecated]
      US Core Procedure Profile
    • (many)
    • 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?
    • Floyd Eisenberg / Brett Marquard: 8-1-0
    • Correction
    • 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

        1. image-2021-03-04-08-58-08-986.png
          image-2021-03-04-08-58-08-986.png
          136 kB
        2. image-2021-03-04-09-02-27-518.png
          image-2021-03-04-09-02-27-518.png
          158 kB

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: