Stream: implementers
Topic: RelatedPerson relation
Tommy Vu (Dec 20 2021 at 05:10):
Hello,
RelatedPerson resource just support only Patient as 1..1 description . How can i represent 1 RelatedPerson with multiple Patients
thanks
Josh Mandel (Dec 20 2021 at 05:20):
You would have a distinct RelatedPerson representing the person's relationship to each Patient. If you want to avoid duplicating the details you could consider populating them into a Person resource, but a bit of duplication is probably okay here.
https://build.fhir.org/relatedperson.html#scope has some relevant content
Tommy Vu (Dec 20 2021 at 07:44):
thanks @Josh Mandel
Can you give me a simple example such as RealtedPerson relatedMother have two patients patientSon and patientDaughter ?
René Spronk (Dec 20 2021 at 07:53):
You'd have RelatedMother1 and RelatedMother2 with the same content except for their respective relationships with PatientSon and PatientDaughter.
René Spronk (Dec 20 2021 at 07:54):
RelatedMother1 and RelatedMother2 are played by the same Person resource, so some data will be on Person and won't have to be duplicated.
Tommy Vu (Dec 20 2021 at 07:55):
thanks @René Spronk
Lloyd McKenzie (Dec 20 2021 at 15:22):
The general philosophy is that RelatedPerson is "owned" by a particular Patient record. There's an extension that allows you to assert that a RelatedPerson for one Patient corresponds to a different Patient record (if an organizations capabilities and privacy policies allow). Person allows maintaining shared demographics across Patient, RelatedPerson and even Practitioner resources.
John Moehrke (Dec 20 2021 at 15:34):
In a harmonious family, they all know about each other... the model is designed such that Privacy can be implemented. Some relationships must not be known by peers.
Last updated: Apr 12 2022 at 19:14 UTC
