GP Connect API Get Capability Statement Returning 404 for Organisation Code B82617 in INTEGRATION

GP Connect
, , ,
1

When performing a ‘get capability statement’ HTTP request for GP connect test organisation code B82617 at:

…we are being met with a 404 HTTP response code and the Spine Secure Proxy is returning a REFERENCE_NOT_FOUND error code in the OperationOutcome resource.

Our requests are well formed and in line with the requirements specification. They have functioned historically without failure. No changes have been made to our system and we have validated our requests to ensure they are still good. An example of a failed request has been provided at the bottom of this post.

This issue combined with *gpconnect-integration-environment-502* have left us being unable to perform integration testing since the beginning of May.

We would appreciate support from NHSE to help resolve this issue. We have logged the following ticket with the service desk:

  • CS1095782 Spine Secure Proxy is Returning HTTP Response Code 404 in INTEGRATION for GP Connect Get Capability Statement Requests

Example of a failed request occurring on 09-Jun-2025 at 09:53:

GPC Get Capability Statement - HTTP Request - Headers

Ssp-TraceID: a68a235d-2344-40b8-952a-d6b43348358f
Ssp-From:200000002450
Ssp-To: 200000001329
Ssp-InteractionID: urn:nhs:names:services:gpconnect:structured:fhir:rest:read:metadata-1
Content-Type: application/fhir+json
Accept: application/fhir+json
Authorization:
eyJ0eXAiOiJKV1QiLCJhbGciOiJub25lIn0.eyJpc3MiOiJodHRwOi8vZ3BjLWludC04amswOS5haXJlbG9naWNsaW1pdGVkLnRoaXJkcGFydHkubmhzLnVrLyIsInN1YiI6IjEiLCJhdWQiOiJodHRwczovL2dwY29ubmVjdC13aW4xLml0YmxhYi5uaWMuY2ZoLm5ocy51ay9CODI2MTcvU1RVMy8xL2dwY29ubmVjdC9zdHJ1Y3R1cmVkL2ZoaXIiLCJleHAiOiIxNzQ5NDU5NDk3IiwiaWF0IjoiMTc0OTQ1OTE5NyIsInJlYXNvbl9mb3JfcmVxdWVzdCI6ImRpcmVjdGNhcmUiLCJyZXF1ZXN0ZWRfc2NvcGUiOiJvcmdhbml6YXRpb24vKi5yZWFkIiwicmVxdWVzdGluZ19kZXZpY2UiOnsicmVzb3VyY2VUeXBlIjoiRGV2aWNlIiwiaWRlbnRpZmllciI6W3sic3lzdGVtIjoiaHR0cHM6Ly9teS1hcGkuYWlyZWdsdS5jb20iLCJ2YWx1ZSI6ImFjY3JlZGl0YXRpb24tc3RhZyJ9XSwibW9kZWwiOiJBaXJlQ29uc3VsdCIsInZlcnNpb24iOiIxLjAuMCJ9LCJyZXF1ZXN0aW5nX29yZ2FuaXphdGlvbiI6eyJyZXNvdXJjZVR5cGUiOiJPcmdhbml6YXRpb24iLCJpZGVudGlmaWVyIjpbeyJzeXN0ZW0iOiJodHRwczovL2ZoaXIubmhzLnVrL0lkL29kcy1vcmdhbml6YXRpb24tY29kZSIsInZhbHVlIjoiOEpLMDkifV0sIm5hbWUiOiJBaXJlIExvZ2ljIERlbW8gTkhTIFRydXN0In0sInJlcXVlc3RpbmdfcHJhY3RpdGlvbmVyIjp7InJlc291cmNlVHlwZSI6IlByYWN0aXRpb25lciIsImlkIjoiMSIsImlkZW50aWZpZXIiOlt7InN5c3RlbSI6Imh0dHBzOi8vZmhpci5uaHMudWsvSWQvc2RzLXVzZXItaWQiLCJ2YWx1ZSI6IjEyMzQ1Njc4OTAxMiJ9LHsic3lzdGVtIjoiaHR0cHM6Ly9maGlyLm5ocy51ay9JZC9zZHMtcm9sZS1wcm9maWxlLWlkIiwidmFsdWUiOiIxMjM0NTY3ODkwMTIifSx7InN5c3RlbSI6Imh0dHBzOi8vb3JhbmdlLnRlc3RsYWIubmhzLnVrL2dwY29ubmVjdC1kZW1vbnN0cmF0b3IvSWQvbG9jYWwtdXNlci1pZCIsInZhbHVlIjoiMTIzNDU2Nzg5MDEyIn1dLCJuYW1lIjpbeyJmYW1pbHkiOiJTdXJuYW1lIChUQkQpIiwiZ2l2ZW4iOlsiR2l2ZW4gbmFtZSAoVEJEKSJdLCJwcmVmaXgiOlsiRHIiXX1dfX0.

GPC Get Capability Statement - HTTP Query String
https://proxy.int.spine2.ncrs.nhs.uk/https://gpconnect-win1.itblab.nic.cfh.nhs.uk/B82617/STU3/1/gpconnect/structured/fhir/meta

GPC Get Capability Statement - HTTP Response - Body

{
  "resourceType": "OperationOutcome",
  "meta": {
    "profile": [
      "https://fhir.nhs.uk/STU3/StructureDefinition/GPConnect-OperationOutcome-1"
    ]
  },
  "issue": [
    {
      "severity": "error",
      "code": "invalid",
      "details": {
        "coding": [
          {
            "system": "https://fhir.nhs.uk/STU3/CodeSystem/Spine-ErrorOrWarningCode-1",
            "code": "REFERENCE_NOT_FOUND",
            "display": "REFERENCE_NOT_FOUND"
          }
        ]
      },
      "diagnostics": "Request contains invalid resource (/B82617/STU3/1/gpconnect/fhir/meta)"
    }
  ]
}
2

Hello herjit.sehgal. Thank you for getting in touch about this, I will ask the appropriate team to investigate and come back to you with an update.

Ash

1 Like