2015May sdc #68 - When will extensions move to core?

XMLWordPrintableJSON

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

      When the decision is made to move a given resource to be normative, the core elements and extensions will be re-evaluated based on usage to date and some elements may move at that time. Until the DSTU phase is complete, existing extensions will remain extensions in the absense of compelling evidence of widespread use

      Show
      When the decision is made to move a given resource to be normative, the core elements and extensions will be re-evaluated based on usage to date and some elements may move at that time. Until the DSTU phase is complete, existing extensions will remain extensions in the absense of compelling evidence of widespread use
    • James Agnew / Grahame Grieve: 4-0-0
    • Clarification

      Proposed Wording: Note that, unlike in many other specifications, there can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core simplicity for everyone.

      Comment:

      What does it take for an extension to be added to a resource. We are in DSTU2 and already have a lot of Patient and Observation extensions already. Should they be added to FHIR Normative 1? Are they forever extensions. Please explain if extensions are intended to be permanent.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: