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

How to handle versioning of FHIR and FHIRcast events

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Event format [deprecated]
      Event library [deprecated]
    • Hide

      As of the publication of STU3 FHIRcast, all events's current version is named as published (e.g. Patient-open version 1.1 is named Patient-open, Encounter-open 1.0 is named Encounter-open). 

      In the future, when we make a breaking change to e.g. Encounter-open, the new version of Encounter-open will be named Encounter-open-<version>. 

      We will add a section to the Event library stating the following:

      1. add version to event format:
            <eventname> regular --> latest version according to the spec version
            <eventname>-v<version> --> specific version.

      We will add to the Conformance section that Conformance.eventssupport will hold both  the regular and all version specific eventNames and add an example showing this.

       

      Show
      As of the publication of STU3 FHIRcast, all events's current version is named as published (e.g. Patient-open version 1.1 is named Patient-open, Encounter-open 1.0 is named Encounter-open).  In the future, when we make a breaking change to e.g. Encounter-open, the new version of Encounter-open will be named Encounter-open-<version>.  We will add a section to the Event library stating the following: add version to event format:     <eventname> regular --> latest version according to the spec version     <eventname>-v<version> --> specific version. We will add to the Conformance section that Conformance.eventssupport will hold both  the regular and all version specific eventNames and add an example showing this.  
    • Eric Martin/Paulius Galinauskas: 6-0-0
    • Enhancement
    • Compatible, substantive
    • current

    Description

      The current specification does not address how to handle (breaking changes) of the event definitions and/or changes in the FHIR specification that would trigger such change (such as a name change of a resource).

      Attachments

        Activity

          People

            bvdh Bas van den Heuvel
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: