# A005 Get Referral Error - Returing 500 Timeout

**URL:** <https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197>\
**Category:** e-Referral Service FHIR API\
**Tags:** fhir, api, integration\
**Created:** [10 August 2026 07:37 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197 "2026-08-10T07:37:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jawad\_Ahmad](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@Jawad\_Ahmad](https://developer.community.nhs.uk/u/Jawad_Ahmad)\
**Post date:** [10 August 2026 07:37 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197/1 "2026-08-10T07:37:58Z")

</div>

Hi Team.

On Friday, i noticed A005 Get Referral Endpoint stopped working on INT Environment. Other APIs seems to be working fine.

I tried again today and still the same issue. Can i please get an update that if this is a known issue and being worked upon ?

Regards.  
Jawad

---

<div class="post-metadata">

**Author:** ![Chris\_Beresford](https://avatars.discourse-cdn.com/v4/letter/c/cab0a1/32.png) [@Chris\_Beresford](https://developer.community.nhs.uk/u/Chris_Beresford)\
**Post date:** [10 August 2026 10:01 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197/2 "2026-08-10T10:01:28Z")

</div>

I had this response to a similar query from ITOC:

‘The INT environment was down due to a change as advertised on our forward schedule of change on our webiste. The environment has had issues following the change and and is still down. The issues are currently being investigated.’

---

<div class="post-metadata">

**Author:** ![tony.marsh1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tony.marsh1/32/855_2.png) [@tony.marsh1](https://developer.community.nhs.uk/u/tony.marsh1)\
**Post date:** [10 August 2026 12:27 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197/3 "2026-08-10T12:27:27Z")

</div>

Hi, I’ve let our delivery partner know about the issue today, to allow investigation - I’ll ask them to post back here.

---

<div class="post-metadata">

**Author:** ![Thomas\_Hague](https://avatars.discourse-cdn.com/v4/letter/t/b38774/32.png) [@Thomas\_Hague](https://developer.community.nhs.uk/u/Thomas_Hague)\
**Post date:** [10 August 2026 13:03 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197/4 "2026-08-10T13:03:51Z")

</div>

Hi, there was an RFC planned for Friday that was unfortunately delayed, due to an issue that we are still trouble shooting. The deployment of a new release into eRS-INT completed successfully, however we were unable to complete smoke testing due to issues when communicating with PDS.

We believe this issue relates to the Spine Internet Gateway changes in this release, and we are working ITOC and DIR to investigate this and resolve.

This means eRS-INT is currently unavailable, and we’ve kept the front doors closed to limit user access at this time.

---

<div class="post-metadata">

**Author:** ![Thomas\_Hague](https://avatars.discourse-cdn.com/v4/letter/t/b38774/32.png) [@Thomas\_Hague](https://developer.community.nhs.uk/u/Thomas_Hague)\
**Post date:** [11 August 2026 09:34 UTC](https://developer.community.nhs.uk/t/a005-get-referral-error-returing-500-timeout/14197/5 "2026-08-11T09:34:13Z")

</div>

Hi, we’ve now successfully completed smoke testing for the new release and INT should now be back up and running.