Stream: implementers
Topic: DeviceMetric resource
Hannu Hyttinen (Sep 06 2019 at 06:42):
I am looking for a way to store changing device information (like settings, parameters, status changes) to the PHR. Current PHR is using STU3, but hopefully R4 in the future.
In my understanding DeviceMetric is the resource designed for this purpose, but it seems to be quite limited. I can store status change by this resource, but I do not know how to store the information itself (like reason of status change or possible new settings/parameters or information, that sterile part of the device has changed).
What is good way to store information like this? Should I use for example some extension?
Grahame Grieve (Sep 06 2019 at 06:51):
@Ewout Kramer I'm not sure where we got with this?
Ewout Kramer (Sep 09 2019 at 14:45):
I haven't met with Devices for a while, but I cannot recall that there is work on the parameters side. Best is probably for Hannu to explain his case on gForge, so we can discuss it in the upcoming Atlanta WGM. @Hannu Hyttinen - if you're not familiar with gForge, we can enter a request for change on your behalf.
Hannu Hyttinen (Sep 11 2019 at 06:56):
I'm not familiar with gForge yet, but I'd like to learn it. What would it sound like if I put the following enhancement issues on gForge?
We suggest the adding a new item for device operational status to the DeviceMetric resource. Currently, this information can be provided by the statusReason item of the Device resource.
We look at this from the perspective of an insulin pump. We understand that a new device should be defined as a Device item when it is added to the system. At this point the status of the devices is for example “in stock | in use”. When an insulin pump defined in the system is in use, its operational status changes quite often. This status can be “online | paused | standby | offline | not-ready | transduc-discon | hw-discon | off”
The current implementation does not support thinking like this, as the exact state of the device can only be described in the Device item. The current implementation leads to a situation where the entire Device item has to be updated quite often in case of insulin pump.
Grahame Grieve (Sep 11 2019 at 07:07):
that's the sort of thing to put on gForge. @Todd Cooper should there be more discussion or a better place?
Todd Cooper (Sep 11 2019 at 15:28):
Yep, that is the PERFECT place to put the proposal. We will be reviewing these in Atlanta. If you are at the FHIR CAT this Saturday / Sunday, stop by! We're around all week (through Friday afternoon) too, including some who have worked with insulin pumps.
Mikael Rinnetmäki (Sep 13 2019 at 04:46):
@Todd Cooper I'd be very interested in cooperation around modeling insulin pump data in FHIR. Please ask the people you referred to whether there could be some kind of a task force, work group, or chat stream for that?
Hannu Hyttinen (Sep 16 2019 at 12:01):
gForge item #24449 added.
Last updated: Apr 12 2022 at 19:14 UTC
