Stream: implementers
Topic: DeviceComponent removed
Sathish Tiptur (Jan 25 2019 at 09:19):
I see that the DeviceComponent resource is removed from the latest version of FHIR. We were leveraging the information in "Devices on FHIR - Point-of-Care Device General Implementation Guide" (https://simplifier.net/guide/DevicesonFHIR-Point-of-CareDeviceGeneralImplementationGuide/Home) to represent vitals coming from a patient monitoring device. This guide mapped the FHIR resources, Device, DeviceComponent and DeviceMetric to the IEEE device model that consists of Medical Device System (MDS), Virutal Medical Device (VMD), Channel and Metric. The IEEE device model components mapping to DeviceComponent can be found at https://simplifier.net/guide/DevicesonFHIR-Point-of-CareDeviceGeneralImplementationGuide/DeviceComponentProfiles. I would like to understand what was the reason for removal of DeviceComponent resource and are there any efforts to map the FHIR resources to the IEEE device model? Any insights on this topic would be very valuable to me. Thanks!
Michel Rutten (Jan 25 2019 at 09:26):
Hi @Sathish Tiptur, I think that the devices working group decided to merge the DeviceComponent and Device resources into one for R4, because they were quite similar and overlapping. @Todd Cooper @John Rhoads @Stefan Karl @Brian Reinhold ?
Stefan Karl (Jan 25 2019 at 10:14):
Hi Sathish, as Michel mentioned Device and DeviceComponent have been merged with R4. The updated Point-of-Care Device Implementation Guide can be found here: http://hl7.org/fhir/uv/pocd/2018Sep/
Medical device components are now represented by Device resources linked together by their parent reference.
Sathish Tiptur (Jan 25 2019 at 10:28):
Thank you @Stefan Karl and @Michel Rutten !!
Mikael Rinnetmäki (Jan 25 2019 at 12:00):
I came across this topic during this week too, and noticed the R4 text for Device (https://www.hl7.org/fhir/device.html) talks of DeviceComponent, although there is no DeviceComponent resource in that version of the spec
In FHIR, the "Device" is the "administrative" resource for the device (it does not change much and has manufacturer information etc.), whereas the DeviceComponent and DeviceMetric (which is really a kind of DeviceComponent) [...]
Stefan Karl (Jan 25 2019 at 12:12):
Hi Mikael, this is indeed out of date. There is a tracker item #19650, which needs to be applied.
Brian Reinhold (Jan 25 2019 at 12:33):
Expanding on Stefan's statement ...with the parent reference one can still represent the PoCD hierarchy. The nice thing is that PHD now is just like PoCD but without ever having a parent (there is only a single Device resource).
John Rhoads (Jan 28 2019 at 14:48):
@Sathish Tiptur @Michel Rutten That's pretty much the case. I can give more detail if you want, but basically in R4 the DeviceComponent resource's capabilities got refactored into an enhanced Device resource. DeviceComponent's main design goal was to allow nesting of components of composite devices. The changes in Device allow this to be done with Device. To get the thinking behind this, look at the detailed differences between Device in R3 and R4.@Sathish Tiptur @MichelRutten That's pretty much the case. I can give more detail if you want, but basically in R4 the DeviceComponent resource's capabilities got refactored into an enhanced Device resource. DeviceComponent's main design goal was to allow nesting of components of composite devices. The changes in Device allow this to be done with Device. To get the thinking behind this, look at the detailed differences between Device in R3 and R4.
Last updated: Apr 12 2022 at 19:14 UTC
