Loading...

XML

Word

Printable

JSON

Specification:

US Hybrid/Intermediary Exchange (FHIR)
Raised in Version:

0.1.0
Work Group:

FHIR Infrastructure
Related URL:
http://hl7.org/fhir/us/exchange-routing/2022Jan/use-cases.html#asynchronous-scenario
Related Page(s):

Use Cases and Roles
Related Section(s):
2.6.1
Grouping:
- async-handling
Scheduling:
- block-vote-1
Resolution Description:

Hide

Added the following statement to the referenced step:

The returned content location URL(s) may contain the public FHIR service base URL used to initiate the asynchronous exchange process-~~so that retrieval of the content also flows through the intermediary~~-but that is not required.

Show
Added the following statement to the referenced step: The returned content location URL(s) may contain the public FHIR service base URL used to initiate the asynchronous exchange process- so that retrieval of the content also flows through the intermediary -but that is not required.
Resolution Vote:
Frank McKinney / Christiaan Knaap: 11-0-0
Change Category:
Clarification
Change Impact:
Non-substantive
Applied for Version:

0.1.0

In the last bullet,

The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination

add that the retrieval can also be done using the inbound gateway intermediary

This is specified in the link but not on this page.

is voted on by

BALLOT-27354 Affirmative - Linda Michaelsen : 2022-Jan-FHIR IG EXCH ROUTE R1 STU