Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NPA-2806 Support application/fhir+json; charset=utf-8 Content Type #90

Merged
merged 3 commits into from
Jun 28, 2024
Merged

NPA-2806 Support application/fhir+json; charset=utf-8 Content Type #90

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
48f22f5
NPA-2806 Add mime type to acceptable list
JackPlowman Jun 28, 2024
559fa56
NPA-2806 Update Spec with new content type
JackPlowman Jun 28, 2024
ca71b65
NPA-2806 Fix typo in spec
JackPlowman Jun 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion proxies/live/apiproxy/targets/target.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
</Step>
<Step>
<Name>RaiseFault.415UnsupportedMediaType</Name>
<Condition>request.verb = "POST" and request.header.Content-Type != "application/fhir+json"</Condition>
<Condition>request.verb = "POST" and request.header.Content-Type != "application/fhir+json" or request.verb = "POST" and request.header.Content-Type != "application/fhir+json; charset=utf-8"</Condition>
</Step>
<Step>
<Name>SetRequestAWSMimeType</Name>
Expand Down
5 changes: 4 additions & 1 deletion specification/validated-relationships-service-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ paths:
description: |
## Overview
For any new access request, the necessary details should be collected from a user facing service e.g.
Proxy Access Service and submitted as a QuestionaireResponse.
Proxy Access Service and submitted as a QuestionnaireResponse.

For the most part demographics information doesn't need to be provided in the access request since it can be pulled from PDS.

Expand All @@ -175,6 +175,9 @@ paths:
application/fhir+json:
schema:
$ref: '#/components/schemas/QuestionnaireResponse'
application/fhir+json; charset=utf-8:
schema:
$ref: '#/components/schemas/QuestionnaireResponse'
responses:
'200':
description: Request was received successfully for processing
Expand Down