Stream: implementers
Topic: Identifying application in Composition resource
Slaven Hrkac (Dec 14 2016 at 14:12):
Is there any way to identify sender (application) through FHIR in Composition resource?
John Moehrke (Dec 14 2016 at 14:31):
The Composition is the document. It might be sent numerous times, each time it is delivered the wrapper that carries it will have the kind of data you are asking about. See DocumentReference, DocumentManifest, MessageHeader, and the REST interaction...
Slaven Hrkac (Dec 14 2016 at 15:26):
Thank you. Actually, the Composition is in Bundle wrapper, which is root of my message. I need to identify sender of that Bundle. Imagine client-server architecture where every client has it's unique ID. Can I force a client to introduce himself with that ID through message? My beginner FHIR knowledge level doesn't allow me to find that information anywhere else than here. Thanks in advance.
John Moehrke (Dec 14 2016 at 15:32):
yes the Composition is a Bundle... that is the document wrapper. You need a communication wrapper, which might be a Message in the case of push, or REST in query/response, or DocumentReference in a document exchange.
Grahame Grieve (Dec 14 2016 at 20:06):
I think you are mizing language. Do you mean 'author' rather then 'sender'? If you do, then Composition.author. If you doin't, what do you mean?
Slaven Hrkac (Dec 14 2016 at 21:10):
Thank you guys. I imagined field 'author' to be reserved for physical person who used some system (client application) to create and send message to my server. How to force client side to send unique identifier for application?
Grahame Grieve (Dec 14 2016 at 21:11):
Author can be a Device. You can require that a device author be present, but that wouldn't mean that clients would have to make them unique
Slaven Hrkac (Dec 14 2016 at 21:29):
Can you link me to some example on web? It would be easier for me to understand by example.
Lloyd McKenzie (Dec 15 2016 at 16:01):
@Slaven Hrkac Documents have no notion of "sending". Documents are persistence-centric. As John M. said, once created a document might be sent to many systems over a period of many years. Nothing in a document will tell you who sent it or where it was sent - anymore than a PDF can tell you who emailed it. To track the transmission of documents, you need some sort of a wrapping layer. You could use FHIR messaging. You could use SMTP or SOAP. You can also record actions that happen to documents RESTfully using Provenance.
Last updated: Apr 12 2022 at 19:14 UTC
