2015May core #989 - 18-24 months is too fast

XMLWordPrintableJSON

    • Type: Comment
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Mgmt Group
    • Timelines (see versions) [deprecated]
    • 1.8.2
    • Hide

      The relase timeline must be a balance between the need to support additional requirements and provide guidances that improves interoperability and the need to give implementers sufficient time to adapt. Once FHIR content becomes normative, there will not be breaking changes within a resource. Even prior to going normative, the FHIR Maturity Model ensures that breaking change proposals for "mature" resources face increased scrutiny. The specific timelines will evolve based on implementer need. The timelines documented in the specification are to set implementer expectations and, at present, the FMG considers them to be a reasonable expectation to set.

      Show
      The relase timeline must be a balance between the need to support additional requirements and provide guidances that improves interoperability and the need to give implementers sufficient time to adapt. Once FHIR content becomes normative, there will not be breaking changes within a resource. Even prior to going normative, the FHIR Maturity Model ensures that breaking change proposals for "mature" resources face increased scrutiny. The specific timelines will evolve based on implementer need. The timelines documented in the specification are to set implementer expectations and, at present, the FMG considers them to be a reasonable expectation to set.
    • Brian Post./Hans: 5-0-0

      Existing Wording: New versions of FHIR will be published on a release cycle of aproximately 18-24 months.

      Comment:

      While this timeline is good to incorporate changes in the core specification, it may be difficult for the implementers to keep up with. If each of these releases include "breaking changes" as described in version history, that will likely have significant impact to the implementers and hence to interoperability.

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

              Created:
              Updated:
              Resolved: