Stream: implementers
Topic: MedicationAdministration R2:R3
Grahame Grieve (Jan 02 2017 at 05:04):
any thoughts how a MedicationAdministration.dosage.rate[x] that is a Range gets converted from R2 to R3? @Melva Peters @John Hatem @Scott Robertson
Grahame Grieve (Jan 02 2017 at 10:11):
also, what happened to MedicationOrder.dateEnded/ReasonEnded?
Grahame Grieve (Jan 02 2017 at 17:17):
further, MedicationOrder.dispenseRequest.medication[x] has been removed. What is the intent with this? There's an R2 example making use of this...?
Melva Peters (Jan 02 2017 at 20:49):
@Grahame Grieve we removed the MedicationOrder.dispenseRequest.medication[x] as we believed it was duplicated MedicationOrder.medication[x] - we didn't think there was a use case for having a different medication in the dispenseRequest. Are we expected to do something about the example in R2?
Melva Peters (Jan 02 2017 at 20:50):
@Grahame Grieve MedicationOrder.dateEnded/ReasonEnded would be covered as part of eventHistory (references Provenance) so they were removed.
Melva Peters (Jan 02 2017 at 20:57):
@Grahame Grieve for MedicationAdministration.dosage.rate we fixed this in R3 - since this is an event, we don't believe that you should include a range in the medicationadministration dosage. You wouldn't say "I gave this drug 2-4mg per hour", you would say "I gave this drug 2mg per hour".
Grahame Grieve (Jan 02 2017 at 22:15):
Thanks @Melva Peters. You can't do anything about the R2 example. I've made a note about this in the R2:R3 transforms. Same for the others. I'd like for someone from the FHIr-I to talk to PHx about the forward references to Provenance in San Antonio. (@Lloyd McKenzie is there an opportunity?)
Lloyd McKenzie (Jan 03 2017 at 03:11):
Our session w/ pharmacy is Tue Q2. Ewout is scheduled to be with them. (I'm teaching that quarter). We can also discuss it some in the general Mon Q3/Q4 Workflow session.
Melva Peters (Jan 03 2017 at 17:54):
@Grahame Grieve Grahame, is there something specific that needs to be discussed in San Antonio? We discussed this approach with Lloyd previously and this was determined to be the best approach for the usecase. @Lloyd McKenzie
Grahame Grieve (Jan 03 2017 at 20:03):
well, Provenance is expected to point to the resource that changes, not the other way around
Grahame Grieve (Jan 03 2017 at 20:03):
there's a number of reasons for that.
Grahame Grieve (Jan 03 2017 at 20:04):
I'm not sure what the use case would be that makes 2 medication resources different
Lloyd McKenzie (Jan 03 2017 at 21:02):
That would still be the case. Request.history points to "old" provenances, not the Provenance for the current change. (You'd grab that one with a reverse include)
Grahame Grieve (Jan 03 2017 at 21:06):
I'n very unconvinced by that. I think we need plenty more discussion about this. But maybe we can leave them for R3 for discussion. Good to add a note about this if we do that
Lloyd McKenzie (Jan 03 2017 at 21:14):
There's not really any choice. The "current" provenance has to point to the version that was created - so the resource version must be created before the provenance version. Which means the resource can't point to the current provenance.
Grahame Grieve (Jan 03 2017 at 21:15):
that's not what I'm not convinced about. It's the whole event history bit. I note that there's event history inside encounter, but it was removed from DiagnosticOrder
Lloyd McKenzie (Jan 03 2017 at 21:42):
It wasn't a pattern we'd talked about for Event, only Requests. Encounter status history should probably be handled the same way, though the amount of information they care about is much less than what we were tracking other places.
Last updated: Apr 12 2022 at 19:14 UTC
