Details
-
Change Request
-
Resolution: Persuasive
-
Highest
-
US Hybrid/Intermediary Exchange (FHIR)
-
0.1.0
-
FHIR Infrastructure
-
Use Cases and Roles
-
2.6.1
-
-
Frank McKinney / Christiaan Knaap: 11-0-0
-
Correction
-
Non-substantive
-
0.1.0
Description
The Asynchronous Scenario section oversimplifies the async flow. The steps that currently say:
- The destination processes the request and returns its response to the intermediary. The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which the response data will be available
- ...
- The originator later retrieves the response data using the address previously returned in the Content-Location parameter of the initial response from the destination
... should be changed to:
- The destination processes the request and returns the location to poll for status to the intermediary. The destination responds with an HTTP status code of 202 Accepted, and an HTTP header containing a Content-Location parameter that specifies the URL at which status of the request will be available
- The originator polls for status until the server responds with a "completed" HTTP status code 200 and body containing one or more URLs at which to retrieve the response data
- ...
- The originator
laterretrieves the response data using the URL(s)previouslyreturned in the completed status responseContent-Location parameter of the initial responsefrom the destination
Attachments
Issue Links
- is voted on by
-
BALLOT-27247 Affirmative - Frank McKinney : 2022-Jan-FHIR IG EXCH ROUTE R1 STU
- Closed
- relates to
-
FHIR-34490 Clarify scope of async workflow
- Published
-
FHIR-35142 Add missing Asynchronous Scenario step on Specification page
- Published
-
FHIR-35387 Response from the intermediary does not match that of the destination in the diagram.
- Published
-
FHIR-34490 Clarify scope of async workflow
- Published
-
FHIR-35142 Add missing Asynchronous Scenario step on Specification page
- Published