The specification does not address how to access data in the FHIR server.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • SMART Web Messaging (FHIR)
    • 0.1.0
    • FHIR Infrastructure
    • (NA)
    • Why
    • Hide

      Captured in notes here: https://confluence.hl7.org/pages/viewpage.action?pageId=104570456#SMARTWebMessagingBallotReconciliationCC20210305-Proposal:

      Proposal

      Describe the fhir.* message group as a way to interact with a FHIR server that is equivalent to FHIR HTTP API supporting create, read, update, delete, patch, operations, etc. e.g. patient match, etc. We could use http://hl7.org/fhir/bundle-definitions.html#Bundle.entry.request and a Resource as the data model for requests; and http://hl7.org/fhir/bundle-definitions.html#Bundle.entry.response for responses. (as described in Bas' FHIR-29350, which would be marked Persuasive with Mod) and make it clear that this is an optional feature.  An EHR not wishing to support this is free to omit from their implementation.

      Show
      Captured in notes here:  https://confluence.hl7.org/pages/viewpage.action?pageId=104570456#SMARTWebMessagingBallotReconciliationCC20210305-Proposal: Proposal Describe the fhir.* message group as a way to interact with a FHIR server that is equivalent to FHIR HTTP API supporting create, read, update, delete, patch, operations, etc. e.g. patient match, etc. We could use  http://hl7.org/fhir/bundle-definitions.html#Bundle.entry.request  and a Resource as the data model for requests; and  http://hl7.org/fhir/bundle-definitions.html#Bundle.entry.response  for responses. (as described in Bas'  FHIR-29350 , which would be marked Persuasive with Mod) and make it clear that this is an optional feature.  An EHR not wishing to support this is free to omit from their implementation.
    • Bas van den Heuvel / Carl Anderson: 7-0-0
    • Enhancement
    • Compatible, substantive

      I assume this is not done through scratchpad/, why not include a fhir/ with the same interface?

      Existing Wording:

      • Interacting with the EHR’s FHIR server through this messaging channel (enabling applications that cannot access the FHIR server directly, e.g. those hosted on the internet).

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

              Created:
              Updated:
              Resolved: