BCDA-7446 - update content-type header for OperationOutcome responses to fhir+json #873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
https://jira.cms.gov/browse/BCDA-7446
🛠 Changes
Changed Content-Type header for OperationOutcome error responses from application/json to application/fhir+json in both v1+v2 of the BCDA API
ℹ️ Context for reviewers
From: https://build.fhir.org/ig/HL7/bulk-data/export.html#response---error-status-1
According to the Bulk FHIR Export IG, OperationOutcome responses should respond with Content-Type of application/fhir+json. This is a one line change that will enhance the conformance of the BCDA application with respect to the bulk FHIR IG.
✅ Acceptance Validation
Unit test on requests.api updated to check for the applicable content-type header in the case of an OperationOutcome response.
🔒 Security Implications
If any security implications apply, add Jason Ashbaugh (GitHub username: StewGoin) as a reviewer and do not merge this PR without his approval.