Hi,
I have a patient in the INT environment with two referrals:
000049798111 - no attachments
000049799640 - one attachment
When calling A007 for the referral 000049798111, I receive HTTP 404. The URL being called is:
https://int.api.service.nhs.uk/referrals/FHIR/STU3/ReferralRequest/000049798111/$ers.generateCRI
However calling the same URL for the referral 000049799640 works correctly.
The only difference I can see is that the one that does not work has no attachments - is this enough to cause a 404?
The HTTP request that resulted in a 404 was made at around 11:54 today (18th March 2025) and the response header included this, if it’s any use:
X-Request-ID: 6cb8e08c-fbe4-4030-9ca0-a949b97a9ca1-1
Many thanks,
Chris
Hi @chris.pursey,
You can only generate the the PDF if there is Referrer Clinical Information associated with the request. The request must also not be Cancelled.
@zubeir.tai it looks like detail is not outlined in the documentation, we should consider adding it.
Thanks,
Adam.
Thanks @adam.oldfield.
Does “Referrer Clinical Information” mean it has at least one attachment? Or can that information be provided in other ways?
Just making sure I fully understand this requirement.
Hi Chris,
There are two ways to associate Referrer Clinical Information to a request. Please see guidance here.
Both methods allow unstructured referrer clinical attachments to be associated, these take the form of referrer attachments that are visible on the request (i.e. via “Retrieve referral request (A005, FHIR STU3)”).
An “Integrated primary care system” can also upload structured clinical information. This information can only be received via the API via “Retrieve clinical information (A007, FHIR STU3)”.
You could infer that if either the clinicalInfoFirstSubmitted or clinicalInfoLastUpdated fields are set and there are no attachments, then it must have structured clinical information attached from an integrated referrer system.
Regards,
Adam.
1 Like