# PDS FHIR API - Internal Server Error in INT

**URL:** <https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509>\
**Category:** Personal Demographics Service (PDS)\
**Tags:** integration, pds, spine, fhir, testing\
**Created:** [3 December 2024 17:27 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509 "2024-12-03T17:27:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dunmail](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/dunmail/32/126_2.png) [@dunmail](https://developer.community.nhs.uk/u/dunmail)\
**Post date:** [3 December 2024 17:27 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/1 "2024-12-03T17:27:51Z")

</div>

From mid-afternoon today (3rd Dec) we’ve seen all requests to PDS FHIR API in INT returning Internal Server Error. For example:

```auto
{
    "timestamp": "2024-12-03T16:07:36.369Z",
    "level": "ERROR",
    "requestId": "010db179-3849-4a04-af5d-7e6dbf6f123f",
    "message": {
        "errorType": "Error",
        "errorMessage": "Internal Server Error",
        "status": 500,
        "response": {
            "req": {
                "method": "GET",
                "url": "https://int.api.service.nhs.uk/personal-demographics/FHIR/R4/Patient/9729565341",
                "headers": {
                    "x-request-id": "b1334aa1-a1c5-4413-a792-fac68310170b",
                    "nhsd-end-user-organisation-ods": "8HV05",
                    "authorization": "Bearer <deleted>"
                }
            },
            "header": {
                "date": "Tue, 03 Dec 2024 16:07:36 GMT",
                "content-type": "application/json",
                "content-length": "837",
                "connection": "close",
                "server": "nginx",
                "x-request-id": "b1334aa1-a1c5-4413-a792-fac68310170b",
                "strict-transport-security": "max-age=31536000; includeSubDomains"
            },
            "status": 500,
            "text": "\n {\n \"resourceType\": \"OperationOutcome\",\n \"issue\": [\n {\n \"severity\": \"error\",\n \"code\": \"unknown\",\n \"details\": {\n \"coding\": [\n {\n \"system\": \"https://fhir.nhs.uk/R4/CodeSystem/Spine-ErrorOrWarningCode\",\n \"version\": \"1\",\n \"code\": \"UNKNOWN_ERROR\",\n \"display\": \"Unknown Error\"\n }\n]\n },\n \"diagnostics\": \"An unknown error occurred processing this request. Contact us for assistance diagnosing this issue: https://digital.nhs.uk/developer/help-and-support. (Message ID: rrt-6125041795813384709-b-geu2-74205-3218282-1)\"\n }\n ]\n }\n "
        }
    }
}

```

Does anyone know who is responsible for maintaining and supporting the INT environment?  
Is the problem related to Major Incident INC0255818?

---

<div class="post-metadata">

**Author:** ![dunmail](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/dunmail/32/126_2.png) [@dunmail](https://developer.community.nhs.uk/u/dunmail)\
**Post date:** [4 December 2024 09:28 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/2 "2024-12-04T09:28:47Z")

</div>

Requests are working again as of 0915 today 👍

---

<div class="post-metadata">

**Author:** ![david.hamill1](https://avatars.discourse-cdn.com/v4/letter/d/f475e1/32.png) [@david.hamill1](https://developer.community.nhs.uk/u/david.hamill1)\
**Post date:** [5 December 2024 15:04 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/3 "2024-12-05T15:04:45Z")

</div>

FYI: I believe this was due to a scheduled upgrade (CHG0069216) to INT

---

<div class="post-metadata">

**Author:** ![dunmail](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/dunmail/32/126_2.png) [@dunmail](https://developer.community.nhs.uk/u/dunmail)\
**Post date:** [5 December 2024 16:27 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/4 "2024-12-05T16:27:22Z")

</div>

Are details of planned engineering work shared anywhere so that we can plan for the downtime?

---

<div class="post-metadata">

**Author:** ![dunmail](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/dunmail/32/126_2.png) [@dunmail](https://developer.community.nhs.uk/u/dunmail)\
**Post date:** [11 February 2025 16:05 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/5 "2025-02-11T16:05:16Z")

</div>

@david.hamill1 Are details of planned engineering work shared anywhere so that we can plan for the downtime?

---

<div class="post-metadata">

**Author:** ![kitty.shen](https://avatars.discourse-cdn.com/v4/letter/k/4af34b/32.png) [@kitty.shen](https://developer.community.nhs.uk/u/kitty.shen)\
**Post date:** [11 February 2025 16:19 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/6 "2025-02-11T16:19:05Z")

</div>

At the moment, we’re not aware of any upcoming planned downtime. However, we recognize the importance of ensuring that engineering work and service interruptions are communicated effectively. We’ll check whether we can find any formal communication channels for the downtime notice.

Many thanks.

---

<div class="post-metadata">

**Author:** ![dunmail](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/dunmail/32/126_2.png) [@dunmail](https://developer.community.nhs.uk/u/dunmail)\
**Post date:** [11 February 2025 16:42 UTC](https://developer.community.nhs.uk/t/pds-fhir-api-internal-server-error-in-int/3509/7 "2025-02-11T16:42:48Z")

</div>

That would be much appreciated!