Hi,
I need to download the documents for a “related UBRN”. I think this is where a referral has been triaged by a central referral office and then forwarded to a trust.
Where is the related UBRN stored? I’m sure in the past I’ve seen this in the A005 response, but I’m struggling to see it in the schema.
Can you point me in the right direction please?
Thanks
Jim
Typically, having posted my topic, I saw the “Related Request” example in the documentation!
Sorry to be a pain.
Jim
Hello no problem at all, any related UBRNs to a request are referenced within the supportingInfo attribute of the ReferralRequest. As you mentioned this is detailed within the Retrieve referral request (A005) documentation:
"supportingInfo": [
{
"reference": "ReferralRequest/000000070004"
}
]
With a separate Reference object being included for each related Referral.
I think this solves your question? Though I think you may have solved your own question anyway 
.
Hi Jack,
You’ve opened a can of worms with the statement “each related referral”.
How many related referrals can there be? What is a scenario where there is more than one related referral? If there is more than one, can this be a chain of referrals? How is the chain shown in the supportingInfo?
I might need to have a meeting with Zubeir to discuss. Let me know what’s the best way forward here.
Thanks
Jim
I believe there can be any number of related Referrals, as it’s possible that an onward Referral can itself be onward referred, creating a chain of Referrals within the pathway. The chain would be displayed as an array of Reference objects, each one representing a separate Referral within the chain.
It might be worth reaching out to @zubeir.tai, to run through some of the business flows that utilise this functionality, and how they fit into your use-case.
Thanks,
Jack.
Thanks Jack, I need to have a chat with Zubeir as you suggest.
@jim.brock There is also further information about this on Retrieve clinical referral information as a service provider.
Note that the supportingInfo may also reference an A&G Request (CommunicationRequest) if the referral was converted from and A&G request. See section 2.3 for that part.
Thanks Adam!
If the referral has been converted from an A&G Request, the A&G conversation is in the attachments of the converted referral I believe. I’m only going to process ReferralRequests in the supporting info to get attachments from the previous referral.
If an A&G request is converted to a referral, does it get a new UBRN?
Jim
Hi @jim.brock,
If the referral has been converted from an A&G Request, the A&G conversation is in the attachments of the converted referral I believe.
I believe this is only the case if a provider converts the A&G request to a referral, in this case a PDF of the conversation is automatically added by the e-RS as the as the “Referral Letter”/Referrer Clinical Information.
However, if the referrer does the conversion this isn’t done automatically. It is down to the referrer to add whatever clinical information they deem appropriate. @zubeir.tai can you confirm this?
I’m only going to process ReferralRequests in the supporting info to get attachments from the previous referral.
Given the above the advice is to follow the guidance in 2.3. i.e. when supportingInfo includes a referance to a CommunicationRequest then A024/25/42 should be used to get the related information.
If an A&G request is converted to a referral, does it get a new UBRN?
No, the conversion maintains the same UBRN. Both GET ReferralRequest/X and GET CommunicationRequest/X will be valid (where X is the UBRN).
@Nitish_Rastogi @Daniel_McAdam FYI
Regards,
Adam.
Yes, that’s correct. When a service provider clinician converts an A&G request, a PDF summary is automatically attached to the newly created referral. This is not the case if a referring clinical converts.
No, the same UBRN is persisted.