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

Which FHIR version should be used in the context?

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Conformance
    • Hide

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

      1) the list of supported events

      2) the hub.url

       

      The FHIR version used in notifications should be identified alongside the OAuth2 app registration. Further, by defining the specific FHIR server in use for the given integration, the app may more dynamically learn the Hub's capabilities.

       

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

      Show
      We will create a standard extension in the FHIR CapabilityStatement to define: 1) the list of supported events 2) the hub.url   The FHIR version used in notifications should be identified alongside the OAuth2 app registration. Further, by defining the specific FHIR server in use for the given integration, the app may more dynamically learn the Hub's capabilities.   We will update the "alternate launch scenarios" page to describe sharing the url to the FHIR capability statement in lieu of the hub url.

    Description

      Which FHIR version should be used in the context?

      Existing Wording:

      The context is an array of named FHIR resources (similar to CDS Hooks's context field) that describe the current content of the user's session.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: