Stream: implementers
Topic: Patient.link.type
Craig Newman (Jun 12 2020 at 21:14):
@Sarah Gaunt and I were looking at Patient.link as a way to link a mother's Patient resource to a RelatedPerson resource for a mother to her child. This seems to be a valid use case based on the fact that Patient.link.other allows a reference to a RelatedPerson and the mother/newborn linking section 8.1.9 includes this in the example. But all of the descriptions of .link and all of the values in the Required value set for Patient.link.type only seem to deal with Patient-to-Patient linkages. Can someone confirm that .link is the right way to link a Patient and RelatedPerson resource when both resources are for the same individual (as opposed to using Person)? And if so, is seealso the right link type?
Lloyd McKenzie (Jun 12 2020 at 21:43):
@Brian Postlethwaite
John Moehrke (Jun 13 2020 at 12:56):
I put in a CR last year asking for this clarification -- https://jira.hl7.org/browse/FHIR-23009
Craig Newman (Jun 15 2020 at 14:10):
Brian's response in the Jira ticket seems in line with what we need to do.
The intent is that these are links to the SAME individual, including where the individual has mutliple patient resources, and multiple relatedperson resources.
For example, Brian as a Patient can link to Brian as a RelatedPerson (patient = Ethan, Relationship = father).
(as demonstrated in the examples in the section of the spec http://hl7.org/fhir/patient.html#maternity)
We will propose the text to clarify this in the spec page, to ensure it's not miss-interpreted
Craig Newman (Jun 15 2020 at 14:10):
The only remaining question may be the right "type" to use. Is "seealso" appropriate?
Last updated: Apr 12 2022 at 19:14 UTC
