GPConnect Integration Environment 502

GP Connect
,
1

Hello, my team and I are validating our application’s functionality against GPConnect for appointment booking (i.e. searching for free slots).

We have not modified our application yet our requests within the integration environment are now failing. We are making requests to:

https://GPConnect-Win1.itblab.nic.cfh.nhs.uk/gpconnect-demonstrator/v1/fhir/Slot?start=ge2025-05-07&end=le2025-05-14&searchFilter=https://fhir.nhs.uk/Id/ods-organization-code|A20047&searchFilter=https://fhir.nhs.uk/STU3/ValueSet/GPConnect-OrganisationType-1|GP Practice&status=free&_include=Slot:schedule&_include:recurse=Schedule:actor:Practitioner&_include:recurse=Schedule:actor:Location

The response we are getting is:

"data": {
        "id": "58261437-0c2e-4a6f-9b74-b6510c9e1168",
        "issue": [
            {
                "code": "transient",
                "details": {
                    "coding": [
                        {
                            "code": "502",
                            "display": "ERROR_COMMUNICATING_TO_ENDPOINT_URL_https://GPConnect-Win1.itblab.nic.cfh.nhs.uk/gpconnect-demonstrator/v1/fhir/Slot",
                            "system": "http://fhir.nhs.net/ValueSet/gpconnect-schedule-response-code-1-0"
                        }
                    ]
                },
                "diagnostics": "ERROR_COMMUNICATING_TO_ENDPOINT_URL_https://GPConnect-Win1.itblab.nic.cfh.nhs.uk/gpconnect-demonstrator/v1/fhir/Slot",
                "severity": "error"
            }
        ],
        "resourceType": "OperationOutcome"
    }

I am concerned that the integration server is offline as we’ve been experiencing this issue for the past 12 hours despite it being marked as transient.

If anyone has advise on how to check the status of this particular server, or get in contact with the specific team at GPConnect that would be very helpful

2

Good morning Colin, thank you for getting in touch, and sorry that you’re experiencing issues.

I’ve asked the team who support the demonstrator to look into this, and I will reply when I know more.

Thanks,

Ash

3

Hey @ash thank you for looking into things on our behalf. Have you happened to get a response yet? We’re still experiencing the same issue.

If there are any changes we should make on our side we would be happy to (we get this URL from NHS Spine so I’d hope that if it needed to be updated that would do it)..

Best,
Colin

4

Hi Colin

Are you encountering this issue in Integration?

If so, we have been receiving the same response from the Spine Secure Proxy when attempting to perform GP Connect requests that were previously functional. We raised a ticket just over a week ago: CS1058304 Spine Secure Proxy is Returning HTTP Response Code 502 in INTEGRATION for GP Connect Requests.

The latest update from the GP Connect team is that this failure is due to expired certificates, which they are actively working to resolve.

If you would like me to add you to the ticket watch list so you can see the updates, feel free message me your email address.

Kind Regards,

Herjit

{
“id”: “22b19ce7-f588-4afc-b594-db66e298c4b9”,
“issue”: [
{
“code”: “transient”,
“details”: {
“coding”: [
{
“code”: “502”,
“display”: “ERROR_COMMUNICATING_TO_ENDPOINT_URL_https://gpconnect-win1.itblab.nic.cfh.nhs.uk/B82617/STU3/1/gpconnect/structured/fhir/meta”,
“system”: “http://fhir.nhs.net/ValueSet/gpconnect-schedule-response-code-1-0”
}
]
},
“diagnostics”: “ERROR_COMMUNICATING_TO_ENDPOINT_URL_https://gpconnect-win1.itblab.nic.cfh.nhs.uk/B82617/STU3/1/gpconnect/structured/fhir/meta”,
“severity”: “error”
}
],
“resourceType”: “OperationOutcome”
}