Stream: implementers
Topic: FHIR Direct Message
Kesara Liyanage (Apr 02 2019 at 13:05):
how are FHIR resources handled in Direct Message?
John Moehrke (Apr 02 2019 at 13:53):
FHIR to Direct is just another mime-type.
Grahame Grieve (Apr 02 2019 at 18:57):
there's a white paper about this: http://healthintersections.com.au/direct-fhir-paper.pdf. @Luis Maas is this the most recent work on that subject?
Luis Maas (Apr 05 2019 at 14:55):
No more recent general whitepapers that I am aware of. Since Direct is payload agnostic, there is nothing special needed to transmit FHIR Resources over Direct. As @John Moehrke states, the correct MIME type should be used to tag the FHIR content, e.g. application/fhir+json, etc. Variations on this theme have been tested successfully at various FHIR connecathons, e.g. the Direct/Certificates track. For identifying workflows or more complex FHIR transactions, the IG for Expressing Context in Direct Messages may also be of interest. I can
try to dig up a link from a 2018 webinar on this topic or some related HIMSS whitepapers, too, if there is interest. @Kesara Liyanage, are there additional questions or a specific use case you are trying to solve?
Luis Maas (Apr 05 2019 at 15:14):
Also, there is a previous thread that may be of interest which includes discussion on identifying the FHIR version as part of the MIME Content-Type tag
Last updated: Apr 12 2022 at 19:14 UTC
