FHIR Chat · MDM Message Type

Stream: v2 to FHIR

Topic: MDM Message Type

Louis Gordon (Oct 09 2018 at 17:26):

Thinking about getting my feet wet lately and many of our own use cases and how FHIR plays into them.

What resource do you think would make sense for a v2 MDM message?

René Spronk (Oct 10 2018 at 11:30):

http://build.fhir.org/documentreference.html

Nick Hatt (Oct 10 2018 at 13:00):

I'll add http://build.fhir.org/diagnosticreport.html and http://build.fhir.org/observation.html to the list. DocumentReference contains or points to all the information in PID, PV1, and TXA. That should meet most dictation workflows. MDM messages with ORC/OBR segments and discrete OBX segments might need the extra resources.

Louis Gordon (Oct 10 2018 at 19:25):

Thanks guys!

John Moehrke (Oct 12 2018 at 15:15):

I think Rene's mention of DocumentReference is that is where the original v2 message can be archived. That original v2 message could (should) be decomposed into more discrete FHIR Resources like DiagnosticReport, Observation, etc... All of those FHIR Resources should be pointed at by a Provenance.target, with Provenance.entity pointing at the DocumentReference that points at a Binary that holds the original v2 message. This would be the most formal and complete. Lesser solutions can be done too. (Note the same is true if a CDA is imported and decomposed, and also a FHIR Document... really anything that is imported and decomposed into FHIR Resources where the original imported object needs to be maintained with Provenance and metadata.