Hello,
We’re seeing the following errors when attempting to connect with ersFHIR. This is against ASID 200000002454. We are also experiencing the same against ASID: 200000002456
Please can someone advise on what is causing this?
Hi @Chris_Pratt,
Can you please provide all/some of the following to help us trace your request:
- Application ID
- X-Correlation-ID / X-Request-ID of the affected request/response
Also please provide details of:
- The Request URL, headers and payload
- The Response status, headers and payload
@Daniel_McAdam FYI.
Regards,
Adam.
Hi @adam.oldfield @Daniel_McAdam
Thanks for taking a look. I’ve reproduced the error again this morning. Here’s the info requested. Please let me know if there’s anything else you need.
Application ID: saas-qa-v9-2-ers
ASID: 200000002454
Request X-Correlation-ID: d25d4e66-a134-47e4-8daf-ce378133c908
GET https://int.api.service.nhs.uk/referrals/FHIR/R4/PractitionerRole Accept: / X-Correlation-Id: d25d4e66-a134-47e4-8daf-ce378133c908 Accept-Encoding: gzip
Response message
HTTP/1.1 403 Unauthorized
Date: Mon, 12 May 2025 10:50:11 GMT
Content-Type: application/fhir+json
Content-Length: 411
Connection: keep-alive
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Correlation-ID: fe09e041-f910-4e54-ae36-ca5437c69ca0
{ “resourceType”: “OperationOutcome”, “meta”: { “lastUpdated”: “2025-05-12T10:50:11.587Z”, “profile” : [ “OperationOutcome - FHIR v4.0.1” ] }, “issue”: [ { “severity”: “error”, “code”: “forbidden”, “details”: { “coding”: [ { “system”: “https://fhir.nhs.uk/CodeSystem/NHSD-API-ErrorOrWarningCode”, “code”: “ACCESS_DENIED” } ] }, “diagnostics”: “ASID is not configured in the application” } ] }
@nhserspartners @lucy.killick1 As discussed, could you assist Chris with this please?
Hi @Chris_Pratt,
Application ID: saas-qa-v9-2-ers
ASID: 200000002454
Request X-Correlation-ID: d25d4e66-a134-47e4-8daf-ce378133c908
Tracing X-Correlation-ID =d25d4e66-a134-47e4-8daf-ce378133c908 I can see that the request is related to Application ID 6c628c42-7039-4a8f-92be-3a9012312ebf .
This application is named nervecentre-cis2 not saas-qa-v9-2-ers (which has Application ID 9405a178-cf4e-4895-9fc8-ea2c85cbc2d6).
Are you intentionally using a different Application or is this a configuration error?
If you want to use 6c628c42-7039-4a8f-92be-3a9012312ebf then we will need to configure it with your ASID.
Thanks,
Adam.
Thanks for taking a look @adam.oldfield, much appreciated. Looks like there’s been a config error here on NHS-E side. Below is the required config, taken from our original support request on 2 April and allegedly double checked on 8 May.
Please could you update the ASID binding to the correct application IDs, as detailed here, for both ASID 200000002454 and ASID 200000002456.
1.
ASIDs
200000002454
Application Name:
saas-qa-v9-2-ers
Application ID:
9405a178-cf4e-4895-9fc8-ea2c85cbc2d6
Endpoint
t3.saas-qa-v9-2.saas.nervecentre.thirdparty.nhs.uk
2.
ASIDs
200000002456
Application Name:
saas-qa-master-ers
Application ID:
bf1684c9-ae24-4a10-b174-60879855c0b3
Endpoint
t3.saas-qa-master.saas.nervecentre.thirdparty.nhs.uk
Thanks,
Chris
Hi @Chris_Pratt,
The Applications you have listed have been configured with the ASIDs provided.
However, the request you made with X-Correlation-ID=d25d4e66-a134-47e4-8daf-ce378133c908 (from your message above) was not in the context of either of the Application IDs you listed.
The request that failed was called in the context of Application ID 6c628c42-7039-4a8f-92be-3a9012312ebf which is named nervecentre-cis2.
Can you check the API Key you are providing is associated with the correct Application ID?
Thanks,
Adam.
Aha! Thanks @adam.oldfield
We’ve made a change to the way we configure our app names and associated API keys in our system which may have resulted in it sending the wrong API key.
Correcting the config and retesting…
@adam.oldfield Just a quick update - I’ve now retested and we’re up and running. Thank you for your help and assistance.
1 Like