From 48f22f542e6d145774a6d6d55e34c7843a60b2db Mon Sep 17 00:00:00 2001
From: Jack Plowman <62281988+JackPlowman@users.noreply.github.com>
Date: Fri, 28 Jun 2024 12:56:32 +0100
Subject: [PATCH 1/3] NPA-2806 Add mime type to acceptable list

---
 proxies/live/apiproxy/targets/target.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proxies/live/apiproxy/targets/target.xml b/proxies/live/apiproxy/targets/target.xml
index 2dba3f7..e19d43c 100644
--- a/proxies/live/apiproxy/targets/target.xml
+++ b/proxies/live/apiproxy/targets/target.xml
@@ -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>

From 559fa56726dff40e87b28b3587c45b3bcde6a518 Mon Sep 17 00:00:00 2001
From: Jack Plowman <62281988+JackPlowman@users.noreply.github.com>
Date: Fri, 28 Jun 2024 13:53:13 +0100
Subject: [PATCH 2/3] NPA-2806 Update Spec with new content type

---
 specification/validated-relationships-service-api.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/specification/validated-relationships-service-api.yaml b/specification/validated-relationships-service-api.yaml
index efe8f54..331ba12 100644
--- a/specification/validated-relationships-service-api.yaml
+++ b/specification/validated-relationships-service-api.yaml
@@ -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

From ca71b654a2cf6479705a5ce4084c8a91a46a2e40 Mon Sep 17 00:00:00 2001
From: Jack Plowman <62281988+JackPlowman@users.noreply.github.com>
Date: Fri, 28 Jun 2024 14:05:24 +0100
Subject: [PATCH 3/3] NPA-2806 Fix typo in spec

---
 specification/validated-relationships-service-api.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specification/validated-relationships-service-api.yaml b/specification/validated-relationships-service-api.yaml
index 331ba12..393789f 100644
--- a/specification/validated-relationships-service-api.yaml
+++ b/specification/validated-relationships-service-api.yaml
@@ -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.