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

Remove version number from meta.profile requirement

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US CARIN Blue Button (FHIR)
    • 1.1.0
    • Financial Mgmt
    • C4BB Coverage
      C4BB ExplanationOfBenefit Inpatient Institutional
      C4BB ExplanationOfBenefit Outpatient Institutional
      C4BB ExplanationOfBenefit Pharmacy
      C4BB ExplanationOfBenefit Professional NonClinician
      C4BB Organization
      C4BB Patient
      C4BB Practitioner
    • Hide

      To reduce the challenge and burden of requiring the full version in the meta.profile (which means any small technical correction is a breaking change), the requirement will be changed to remove the slicing requirements on all profiles and create an invariant that requires a pattern starting with the profile canonical with a version starting with "2.0."

       

      For example, on the coverage profile

      .meta.profile.exists($this.startsWith('http://hl7.org/fhir/us/carin-bb/StructureDefinition/C4BB-Coverage|2.0.'))

      Show
      To reduce the challenge and burden of requiring the full version in the meta.profile (which means any small technical correction is a breaking change), the requirement will be changed to remove the slicing requirements on all profiles and create an invariant that requires a pattern starting with the profile canonical with a version starting with "2.0."   For example, on the coverage profile .meta.profile.exists($this.startsWith('http://hl7.org/fhir/us/carin-bb/StructureDefinition/C4BB-Coverage|2.0.'))
    • Corey Spears / Jeff Brown : 13-0-0
    • Correction
    • Non-compatible

    Description

      Remove version number from meta.profile requirement.

      Requiring version number in the meta.profile means that technical corrections are not possible. With version umber required, it is not possible to issue something as small as a typo fix in narrative guidance because the version number would change, which is a breaking change and all resources that previously exist would not be conformant (even without an changes to any data represented in the instances).

      Attachments

        Activity

          People

            Unassigned Unassigned
            corey_spears Corey Spears
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: