search

inferno-framework / uds-plus-test-kit

Apache License 2.0
2 stars 2 forks source link

$import operation response #23

Open cooperthompson opened 2 months ago

cooperthompson commented 2 months ago

Currently, the Inferno test kit will return an HTML page in response to the $import operation. It still isn't super clear to me that this is not valid, since the $import operation doesn't define any outputs. And the FHIR core spec doesn't really have any clear language on what the response should be in those cases.

But there is at least some folks that think it isn't expected: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Allowed.20responses.20for.20FHIR.20Operations

My suggestion is that Inferno just return a raw HTTP status code without any content, instead of returning an HTML page.

cooperthompson commented 2 months ago

Also, the UDS spec says the response to the $import operation should include a Content-Location header for the endpoint the submitter should use to poll for the import job status.

ljtucker commented 1 month ago

The POST tests in the UDS+ Inferno Test Kit (e.g., Receive UDS+ Import Manifest via POST request, which is one of our first requests when a UDS+ Volunteer Tester is practicing connectivity) are only acting as a rudimentary data receiver compared to the UDS+ Sandbox (which actually tests against an endpoint (valid conformant server/s). These tests are not a valid test of the FHIR submission process, but an initial practice run to see if your synthetic test data is healthy and likely ready for submitting to the UDS+ sandbox. If you are looking for a JSON response instead of HTML, then we advise obtaining access to the UDS+ sandbox.

FYI @arscan