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

Remove required binding on procedure and condition

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive with Modification
    • 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

        Issue Links

          is voted on by

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-14910 Negative - Drew Torres : 2021-Jan-FHIR US CORE R1 STU2 STU

          • Closed
          relates to

          Change Request - A request for a change that is more than a simple Technical Correction to one of HL7's specifications FHIR-29563 Extensible bindings including broad SNOMED CT value sets are nonsensical

          • Medium - Has the potential to affect progress.
          • Published

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: