Stream: implementers
Topic: Device Dispense / Delivery
Jose Costa Teixeira (Jul 15 2019 at 14:07):
From recent discussions I do not think we have clear decision how to handle delivery ("dispensing") of a device.
Jose Costa Teixeira (Jul 15 2019 at 14:09):
I recall that Supply was supposed to possibly include a patient, but this is being challenged.
OTOH, we have MedicationDispense but not an equivalent for Device.
Jose Costa Teixeira (Jul 15 2019 at 14:10):
How can we capture who/where/when dispenses a device (Dispense = taking something that was in stock and assign / give reserve for a patient) ?
Jose Costa Teixeira (Jul 18 2019 at 07:47):
This is a hard requirement for traceability of medical devices, so I would want to have our resources in the right direction.
Jose Costa Teixeira (Jul 18 2019 at 07:51):
I see some options
1. We use SupplyDelivery for Dispensing of a Device - this means that SupplyDelivery must support subject/patient
2. We add a resource, in line with MedicationDispense, but for Device (sounds silly)
3. We add an extension (to what resource?
a)Device?
b) Procedure?
c) An extension on MedicationDispense to support things that are not meds sounds strange - unless we reconsider that medicationDispense is actually a ProductDispense, which could work if the WGs agree.
d) Or we add an extension to SupplyDelivery)
4. We really do something with ProductDispense
Jose Costa Teixeira (Jul 18 2019 at 07:55):
I would go for 1, unless 3c or 3d are workable even if in the long term
Jose Costa Teixeira (Jul 18 2019 at 07:56):
I think this should be a careful and future-looking decision, to avoid that we have to redesign international interface specifications.
Jose Costa Teixeira (Jul 18 2019 at 07:57):
@Hans Buitendijk dropping this here for discussing in the Product calls
@Eric Haas @Lloyd McKenzie for additional advice.
Lloyd McKenzie (Jul 18 2019 at 15:12):
SupplyDelivery excludes patient to avoid overlap with DeviceUseStatement. If we add it back, we need to revisit the other.
Jose Costa Teixeira (Jul 18 2019 at 22:12):
agree we need to consider the impact and avoid regressions. ~
DeviceUseStatement seems closer to MedicationUsage than MedicationDispense, so I would not mind having both notions "reported usage" and a "dispense" for device as we have for medication. Those are different purposes and we can keep them separate.
Jose Costa Teixeira (Sep 02 2019 at 09:01):
@Lloyd McKenzie Is Atlanta a good time to start opening that discussion?
At this moment, for "device dispense" we would be using SupplyDelivery, because that is the information we need to convey. The other group that was looking at this reached the same conclusion - perhaps they saw this thread.
Jose Costa Teixeira (Sep 02 2019 at 09:01):
agree we should have a proper dsicussion and overview of what resources to use for what - not sure what is the right timing and forum
Jose Costa Teixeira (Sep 15 2019 at 11:19):
During this week, do we have an opportunity to look at "Device Delivery"? I'd like to gather some group wisdom, we don't need a decision.
Jose Costa Teixeira (Sep 15 2019 at 11:19):
Use Case / Need: We need (e.g. for implantable device record) the notion of "dispense" for device - who&when dispensedwhat for whom.
Jose Costa Teixeira (Sep 15 2019 at 11:22):
Gap:
This should be achievable by extending or profiling some resource, so I would like to know how.
Jose Costa Teixeira (Sep 15 2019 at 11:26):
Status:
I'd consider that "SupplyDelivery" can do it, because SupplyDelivery has a reference to Patient, to support "named deliveries" in the supply chain.
But we wanted to take "patient" out of SupplyDelivery, IIRC to retarger it only to bulk supplies.
This means we should rediscuss our approach.
Jose Costa Teixeira (Sep 15 2019 at 11:30):
Options:
1. SupplyDelivery includes Patient information for this case.
2. A new core resource called DeviceDispense. I don't see a need for that
3. Reuse MedicationDispense for devices. I don't like that option, because most likely it would flood the very specific resource with an entire new scope.
4. DeviceUseStatement - it's not really what we want to convey and I would not do that..
5...?
Jose Costa Teixeira (Sep 15 2019 at 11:33):
Side note: If we had an abstract/pattern "ProductDelivery" which at this moment gets instanciated with MedicationDispense, I feel the discussion would be easier. Not because we'd have a model, but because we'd better agree on what we are talking about.
Jose Costa Teixeira (Sep 15 2019 at 11:44):
I am using Dispense as "the act of assigning a physical product occurrence to a patient" i.e. when someone says "from the 100 devices we have, this patient will get THIS one".
Jose Costa Teixeira (Sep 15 2019 at 11:46):
my oversimplified mind model looks a bit like this:
pasted image
Last updated: Apr 12 2022 at 19:14 UTC
