Issue with Advice and Guidance Worklist API – 500 Error in Integration Environment

e-Referral Service (e-RS) e-Referral Service FHIR API
1

I’m currently encountering an issue when attempting to use the API to connect to the A024 Advice and Guidance worklists within the integration environment.

When making the request the API consistently returns a 500 Internal Server Error, without any additional information indicating what may be incorrect in the payload.

However, I’ve noticed some unexpected behaviour:

  • If I remove all Advice and Guidance requests via the portal (resulting in an empty list), the same API call returns a 200 OK response.

  • In this case, the response contains an empty list as expected.

This suggests that the issue may be related to how existing Advice and Guidance requests are being handled by the API, rather than the request structure itself.

Could you please confirm:

  • Whether this is a payload issue

  • If there are any known issues with the Advice and Guidance worklist API in the integration environment?

  • Whether this might be related to your ongoing updates or changes to Advice and Guidance functionality?

Please let me know if you need any further details from my side.

2

Hi Ryan,

Thanks for posting and welcome to the community - if you could post the following, someone will take a look for you as soon as they are able:

  • Application ID

  • X-Correlation-ID

  • X-Request-ID

  • Date and time the call was made

3

Hey Tony

Thank you for the response, here are the details

Application-ID - aa784280-b4b6-45f0-b196-625e201781b5
Date - 10 Apr 2026 08:04:36
X-Request-ID - ac4fbd27-4bd8-4cc3-b2a9-d06fd816d98c-1
X-Correlation-ID - dbd415ae-7d01-48a2-8d70-eb1a085ce96b

4

@George_Craft Please could you take a look at this one please? :slight_smile:

5

I am looking into this now.

6

Good afternoon, I am currently waiting to hear back from another team member regarding this problem, I will update as soon as I have heard back.

7

Thanks for the update George, Please do let me know once you’ve heard back, I’d appreciate any assistance on this.

1 Like
8

Hi Ryan, just following up on this now, can you confirm whether this is still an issue? A few changes have been rollbacked since that may have solved this issue.

9

Hey George,

Unfortunately the same issue, i could supply additional logs if that would help? Or is this an environmental issue with the ongoing integration changes?

Thanks

10

Hi Ryan, any additional logs you have would be appreciated, I will continue looking into this now.

11

Hi Ryan, I believe I have found the issue. From the logs I can see, when the API was called, it attempted to return two A&G referrals (refId= 8235595 and 8235616), both related to service with ID=6711004. However, in this service, the field “referral_letter_required” has a null value, causing the search for these particular referrals to return a 500 error message, it is expected for this field to be either true or false. Please let me know if this is something you could configure yourself or would need help changing. :slight_smile:

1 Like