# Advice Conversation **URL:** \ **Category:** e-Referral Service FHIR API\ **Created:** [17 June 2024 16:52 UTC](https://developer.community.nhs.uk/t/advice-conversation/994 "2024-06-17T16:52:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gareth.perkins](https://avatars.discourse-cdn.com/v4/letter/g/8baadc/32.png) [@gareth.perkins](https://developer.community.nhs.uk/u/gareth.perkins)\ **Post date:** [17 June 2024 16:52 UTC](https://developer.community.nhs.uk/t/advice-conversation/994/1 "2024-06-17T16:52:17Z")
We are implementing functionality similar to the Advice Conversation functionality in ERS (using A025 - Retrieve advice and guidance conversation). When viewing a conversation the ERS implementation displays a nice human readable name to display participants in the conversation, however in tour test environment we see something similar to PractitionerRole/021600556514.R68.SERVICE-PROVIDER-CLINICIAN for each participant. Is this something we can get from the ERS API and how would we go about achieving the same? ---
**Author:** ![adam.oldfield](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adam.oldfield/32/327_2.png) [@adam.oldfield](https://developer.community.nhs.uk/u/adam.oldfield)\ **Post date:** [18 June 2024 07:06 UTC](https://developer.community.nhs.uk/t/advice-conversation/994/2 "2024-06-18T07:06:35Z")
Hi @gareth.perkins, The reference to the `PractitionerRole` resource (i.e. PractitionerRole/021600556514.R68.SERVICE-PROVIDER-CLINICIAN) will be resolvable in the bundle if you search the bundle for a `fullUrl` that ends with that string. The `PractitionerRole` will break down the practitioner, organization and Business Function. However, e-RS does not return a human readable display value for the practitioner - this is not data owned by the e-RS, it is owned by SDS team. Currently you would to use the [Spine Directory Service - LDAP API](https://digital.nhs.uk/developer/api-catalogue/spine-directory-service-ldap) to source this data. However it is worth engaging with the SDS team to understand your options. Thanks. ---
**Author:** ![tc1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tc1/32/83_2.png) [@tc1](https://developer.community.nhs.uk/u/tc1)\ **Post date:** [18 August 2026 13:45 UTC](https://developer.community.nhs.uk/t/advice-conversation/994/3 "2026-08-18T13:45:17Z")
> [@adam.oldfield](#): > > Currently you would to use the > [Spine Directory Service - LDAP API](https://digital.nhs.uk/developer/api-catalogue/spine-directory-service-ldap)to source this data. However it is worth engaging with the SDS team to understand your options. Is this still the case ? We’re trying to connect to eRS as an ISV, and can’t really present the sender, requestor of a conservation’s item as just being by “long random string at ODS code”. It looks like 2 years ago there was some attempt to get an API to convert these abstract references into real human readable details : [How do we retrieve referring clinician from the referral? - #2 by kevin.mayfield1](https://developer.community.nhs.uk/t/how-do-we-retrieve-referring-clinician-from-the-referral/876/2) Has that progressed for instance ? The form no longer exists. ---
**Author:** ![tc1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tc1/32/83_2.png) [@tc1](https://developer.community.nhs.uk/u/tc1)\ **Post date:** [28 August 2026 14:32 UTC](https://developer.community.nhs.uk/t/advice-conversation/994/4 "2026-08-28T14:32:26Z")
Details of how to do this with the current (late 2026) version of the API are here : > [@How do we retrieve referring clinician from the referral?](https://developer.community.nhs.uk/t/how-do-we-retrieve-referring-clinician-from-the-referral/876/12): > > Hi @Sarah_Bucknall - thanks for chipping in. Maybe I’m asking the wrong thing, or quoteing the wrong part of the eRS API response slight_smile Each conversation entry of resourceType=Communication seems to have a sender prop that boils down to something like refererence=PractitionerRole/555384914100.H3G9K.SERVICE-PROVIDER-CLINICIAN right ? Those are in turn listed as resourceType=PractitionerRole entries, which include entries like { "practitioner": { "identifier": { "system…