FHIR Chat · MedicationOrder to MedicationRequest convertion · implementers

Stream: implementers

Topic: MedicationOrder to MedicationRequest convertion


view this post on Zulip Hugo Soares (Apr 05 2017 at 14:21):

Hi,
I am migrating a Messaging implementation of MedicationOrder exchange from a DSTU2 context to STU3.

I need to exchange a medication request cancellation (status = cancelled) and inform an HIS about the reason , the date and who cancelled the request.

I thought I would just use the MedicationRequest.eventHistory and put that information on a Provenance resource but it seems that the eventHistory "SHALL NOT include the Provenance associated with this current version of the resource".

Since we are implementing pure message exchange, we do not have a way to query provenance records as the standard seems to sugest.

I dont see how I can fully represent a cancelled MedicationRequest on a single exchange...

How would you guys do this?

view this post on Zulip Lloyd McKenzie (Apr 05 2017 at 14:34):

You can still send the Provenance for this version in your message, but the "current" Provenance would point to the current MedicationRequest rather than the other way around

view this post on Zulip Hugo Soares (Apr 05 2017 at 14:38):

wouldn't that go against wait is in here ?
https://www.hl7.org/fhir/STU3/medicationrequest-definitions.html#MedicationRequest.eventHistory

view this post on Zulip Hugo Soares (Apr 05 2017 at 14:42):

Are you recomending me to use a standalone Provenance resource and link it to my MedicationRequest via Provenance.target ?

view this post on Zulip Yunwei Wang (Apr 05 2017 at 15:07):

My understanding is that you should have multiple Provenance instance. One targets to current version, others target to previous versions. And you only need to include Provenance for previous versions in eventHistory.

view this post on Zulip Lloyd McKenzie (Apr 05 2017 at 15:08):

The way Provenance works is that each Provenance points to the version of a resource whose creation is described by the Provenance. EventHistory points to "past" Provenances that are relevant in understanding the history of the resource. The EventHistory can't include the "current" Provenance because the version of the resource needs to be created before the Provenance can be created that points to it.

view this post on Zulip Hugo Soares (Apr 05 2017 at 15:24):

Got it. Thank you for your inputs

view this post on Zulip Lloyd McKenzie (Apr 05 2017 at 15:27):

np


Last updated: Apr 12 2022 at 19:14 UTC