Stream: implementers
Topic: MessageHeader.destination.receiver
Jeremy Chapman (Sep 11 2019 at 22:24):
I've been looking at the MessageHeader.destation.reciever documentation, and noticing that it is a reference to a Practitioner or PractitionerRole or Organization. Because it's a reference the resource being referenced is not actually enforced via schema. Is it a bad thing to reference a CareTeam or RelatedPerson etc?
Second to that, why would the documentation not allow the same choices as Communication.recipient, which documents Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson, Group, CareTeam, HealthcareService as possible referenced resources?
Grahame Grieve (Sep 11 2019 at 22:37):
1. yes that would be a bad thing
2. because classically this hasn't happened when messaging. Do you have use cases?
Jeremy Chapman (Sep 11 2019 at 22:47):
Well this came about because I was considering a message scenario where I was attaching a document. So I was assuming a a message bundle with a focus on a Communication resource containing a contentReference in the payload. I was suggested to me that the focus should potentially be a DocumentReference instead, because that can encapsulate a reference to a document and references to related attachments which I needed.
The issue for me became that I needed a place to put the recipients that I would have put in Communication.recipient. MessageHeader.destination.receiver seemed the obvious place, except for the cardinality of 0..1 and the fact that the documentation states that the possible receivers don't allow for CareTeam, which I would need.
Eric Haas (Sep 11 2019 at 22:58):
Face thus same dilemma for da Vinci alerts as well
Eric Haas (Sep 11 2019 at 23:00):
We will be looking communication vis a vis messaging next week at the Hl7 wgm and I will bring this up. It won’t change anytime right now though
Lloyd McKenzie (Sep 11 2019 at 23:39):
You could include an extension instead of a value that included references to other resources as a short-term solution.
Jeremy Chapman (Sep 12 2019 at 15:11):
Should I submit a change request for this?
Lloyd McKenzie (Sep 12 2019 at 17:49):
You could. Also provide your use-case for the expansion of the list of resources.
Last updated: Apr 12 2022 at 19:14 UTC
