Provide guidance on declaring conformance to this specification/

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Infrastructure & Messaging
    • (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
    • Enhancement
    • Compatible, substantive

      Since both Hub and App implementers have a choice of implementations and events, it's useful to include a specification that describes how to declare conformance. Presumably Apps will support a predefined set of events. Driving applications may be expected to support a minimum set of set of events. Each *s*ystem should declares those options (events, protocol) using the same standard approach/format\.

            Assignee:
            Isaac Vetter
            Reporter:
            Kenneth Rubin
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: