Stream: implementers
Topic: Handling Practitioner and Related Person resource merges
Keerthivasan Ramanathan (Aug 15 2020 at 07:32):
Hi all,
We have merge functionality for Patient resource by leveraging patient.link property. but, how do we handle merges with Practitioners and Related Persons? or if its allowed to have dups for Practioners and Related Persons, how its been generally handled?
Keerthivasan Ramanathan (Aug 16 2020 at 12:37):
@Lloyd McKenzie Can you help with this question?
Keerthivasan Ramanathan (Aug 17 2020 at 05:39):
@Jens Villadsen Can you guide me on this, if possible?
Jens Villadsen (Aug 17 2020 at 06:30):
I believe that is very focused on you own business logic, how to handle merges.
Keerthivasan Ramanathan (Aug 18 2020 at 07:33):
I can handle the business logic for merge. I don't see any property like Patient.link for Practitioner, RelatedPerson resources. so, I just wanted to ask if there is any fields for referring.
Lloyd McKenzie (Aug 23 2020 at 23:01):
Patient merges are a common issue - so Patient.link is considered part of 'core'. On the other hand, merges of Practitioners and RelatedPerson are not as much of a commonly handled issue, so there's no standard element. However, we could define a standard extension if you wanted to propose one.
Lloyd McKenzie (Aug 23 2020 at 23:01):
(Use the 'propose a change' link.)
Vassil Peytchev (Aug 25 2020 at 16:21):
Another possible way to address that is via Person.link to link the two Practitioners or RelatedPersons...
Last updated: Apr 12 2022 at 19:14 UTC
