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