Event versioning

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Conformance
    • Hide

      Accept proposed resolution for these issues: 

      FHIR-25860, FHIR-25845, FHIR-25654, FHIR-25887, FHIR-25866 with: 

      We will create a standard extension in the FHIR CapabilityStatement to define:

      1) the list of supported events

      2) the hub.url

      This extension will be made available by the Hub at a url ending in /metadata. We will defer the event versioning. We will look for the need to define a FHIRcast version within the this extension.

      We will update the "alternate launch scenarios" page to describe sharing the url to the FHIR capability statement in lieu of the hub url.

       

      Isaac Vetter:Eric Martin

      Approved - 10-0-0

      Show
      Accept proposed resolution for these issues:  FHIR-25860 ,  FHIR-25845 ,  FHIR-25654 ,  FHIR-25887 ,  FHIR-25866  with:  We will create a standard extension in the FHIR CapabilityStatement to define: 1) the list of supported events 2) the hub.url This extension will be made available by the Hub at a url ending in /metadata. We will defer the event versioning. We will look for the need to define a FHIRcast version within the this extension. We will update the "alternate launch scenarios" page to describe sharing the url to the FHIR capability statement in lieu of the hub url.   Isaac Vetter:Eric Martin Approved - 10-0-0
    • Isaac Vetter/Eric Martin: 10-0-0

      There can be multiple versions of an event. How does an application know which version is used in an implementation?

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: