2015May core #739 - Move extensions to core

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • Defining Extensions
    • 1.16.1.2
    • Hide

      this will obviously be a big focus as we move forward past DSTU 2, but there's nothing we can do about it now

      Show
      this will obviously be a big focus as we move forward past DSTU 2, but there's nothing we can do about it now
    • James Agnew / Grahame Grieve: 4-0-0
    • Enhancement

      Existing Wording: To minimize complexity for implementers, HL7 will not elevate content defined in an HL7-approved extension to be content defined in a core resource in future versions of the resource once that resource is normative.

      Comment:

      Based upon this statement, which we totally agree with, and the size of the DSTU 2 Ballot registry of extensions: time to undertake the evaluation of the existing set of extensions. Count of FHIR Core extensions is already close to 375, which we think is suggestive that many of these would be better represented as elements or attributes in existing resources. Evaluation now, before resources become normative, could save many future issues and discussions.

            Assignee:
            Unassigned
            Reporter:
            gcole
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: