Stream: implementers
Topic: RelatedPerson employer
Bo Pritchard (Jul 19 2018 at 11:14):
How would I include an employer in the RelatedPerson resource?
I see the Patient does this by means of Contact.Relationship.Coding.Code = "E"
RelatedPerson doesn't have a Contact construct that I can see. Is this what an extension would be used for?
Thanks for any help
Grahame Grieve (Jul 19 2018 at 11:16):
I'm not sure why you want to put an employer in a related person - is this an individual or an orgnization?
Bo Pritchard (Jul 19 2018 at 11:26):
An individual. The use case would be determining a guarantor's employer
Account.Guarantor.Party.RelatedPerson
Is there another way I'd want to go about that?
Grahame Grieve (Jul 19 2018 at 11:28):
ok so you're read this bit: http://build.fhir.org/patient.html#contact
Grahame Grieve (Jul 19 2018 at 11:28):
but anyway, the RelatedPerson can be an employer - use this code for the relationship:
Grahame Grieve (Jul 19 2018 at 11:29):
http://build.fhir.org/patient.html#contact
Grahame Grieve (Jul 19 2018 at 11:29):
is that what you were asking about?
Bo Pritchard (Jul 19 2018 at 11:30):
I understand, but the Account.Guarantor.Party isn't always a Patient, correct?
Bo Pritchard (Jul 19 2018 at 11:31):
It can also be a RelatedPerson? Such as a spouse, parent, etc. And in that case, how would you designate the employer for that RelatedPerson who is also the Guarantor of an Account?
Grahame Grieve (Jul 19 2018 at 11:34):
I'm not sure I understand the question. The Guarantor.party can be a RelatedPerson and that can be an employer
Grahame Grieve (Jul 19 2018 at 11:34):
or is your issue that they are the employer of someone else?
Bo Pritchard (Jul 19 2018 at 11:39):
Patient is John Brown, age 5.
His Account.Guarantor is his father David Brown (RelatedPerson)
I need to know David Brown's employer, since he is responsible for payment.
Does that make sense?
Thanks for your patience. I'm quite new into FHIR.
Grahame Grieve (Jul 19 2018 at 11:40):
You might be new but this is not simple question! @Cooper Thompson @Brian Postlethwaite this has pssed my limited knowledge
Bo Pritchard (Jul 19 2018 at 14:05):
Anyone have a thought on this?
Lloyd McKenzie (Jul 19 2018 at 14:50):
Guarantor is typically conveyed using Account, not as a relationship. Someone is a guarantor for a particular account, not for a particular patient "overall". On the other hand, once a mother, pretty much always a mother. The relationship isn't limited by account/encounter.
Lloyd McKenzie (Jul 19 2018 at 14:51):
The other consideration is that RelatedPereson is relavant as an "actor" - someone who's going to perform/author/otherwise act.
Bo Pritchard (Jul 19 2018 at 14:55):
The other consideration is that RelatedPereson is relavant as an "actor" - someone who's going to perform/author/otherwise act.
Understood. But the crux of my question is how do I communicate the Guarantor's employer?
Lloyd McKenzie (Jul 19 2018 at 15:06):
If the organization responsible for payment is the father's employer, then the Guarantor on Account would be the employer organization directly.
Lloyd McKenzie (Jul 19 2018 at 15:07):
If there's a fallback relationship where the father is on the hook and if he doesn't pay, then the employer is on the hook, you would list both as guarantors.
Bo Pritchard (Jul 19 2018 at 15:11):
The father is the Guarantor and responsible for payment.
Employer is a simply a datapoint for the Guarantor.
Lloyd McKenzie (Jul 19 2018 at 15:28):
Right now, that would probably be an extension.
Bo Pritchard (Jul 19 2018 at 16:09):
Could you show me an example of what that might look like? I scoured https://www.hl7.org/fhir/ without success.
Lloyd McKenzie (Jul 19 2018 at 17:37):
<RelatedPerson>
<extension url="http://someorg.com/foo/bar/StructureDefinition/employerName">
<valueString value="John Smith"/>
</extension>
<patient>
<reference value="Patient/1"/>
</patient>
<relationship>
<text value="mother"/>
</relationship>
...
</RelatedPerson>
Benjamin Flessner (Aug 06 2018 at 18:43):
@Bo Pritchard We're also looking at implementing guarantor.employer, and it's going to look very similar to Lloyd's example, but instead of <valueString value="John Smith">, we'll be creating an extension that uses <valueReference reference="Organization/123" /> and then sending the organization as a separate resource. That way we can convey employer Name, Address, and PhoneNumber in a single extension.
Brian Postlethwaite (Aug 07 2018 at 03:05):
And you can include the display value to have the org name in place too.
Last updated: Apr 12 2022 at 19:14 UTC
