Hello Team,
We are currently testing eRS integration with our RAS system. As part of this effort, we are trying to generate test referrals in INT and sync them in RAS system. Unfortunately, we have run into (403) Forbidden error.
I am posting the correlation IDs from our testing today as advised by NHS Partners team (we have an ongoing email chain with them).
Some relevant information for reference:
API we are trying to call – A005
The response being received - ‘Forbidden. Check Endpoint configuration or role selected
The remote server returned an error: (403) Forbidden.’
I don’t seem to be able to find your request from the Correlation/Request-IDs provided.
However, I do see a request for the quoted UBRN at 12:07 with Request Id d0b3f66b-345e-4a83-9e3e-350979502f8e-1.
This response returned HTTP 422 with error code NO_RELATIONSHIP.
This indicates that the Organisation configured (O0H1S) for application-restricted access does not have a legitimate relationship with the referral.
The LR rules can be complex, but in its simplest form for a providing organisation to have access to a referral it needs to be booked or deferred to a service at the Organisation.
What is the state of the referral you are trying to access?
Hello Adam,
That is pretty much in line with what we also noticed from the email chain with NHS Partners.
Looks like the ‘app-restricted-ods-code’ on the GOSH Cadence App Restricted app is set to ‘QWO’. However, the GOSH ODS code we are testing with is RP4. Could this be updated?
To answer your question, the test referral has been sent to a test RP4 service. My guess is - The referral status at this point could be ‘AWAITING_TRIAGE’. I cannot confirm this for sure until I am on-site since I am unable to connect with eRS ‘INT’ remotely.
Hey Tony, thought I had replied to this. My bad! We did test this last week, and this seems to have fixed the problem. Thanks for your support with this.
