Stream: implementers
Topic: Additional string to device resource
Lauri Karppinen (Oct 01 2020 at 08:21):
What would be the best way to add additional information to device resource. I would like to add string about calibration code to the resource. Calibration code in our case is information that is used to tie a packet of flow transducers to the device. We have a lot of other information about the device planned for device resource such as: manufacturer, serialNumber, modelNumber, patient, type and version.
I know there is a DeviceMetric resource but there is no place to store a string about calibration. In addition to that we have no other use for DeviceMetric resource. DeviceMetric seems more like resource to store information about time and type of calibration. Maybe it’s more about “action” calibration rather than just a code what was used to calibrate the device? Code that we would like to store is just one string and it would seem useless to add complete resource to just one string.
There is a property element in device resource. Could this be used to store this information?
Original plan was to add extension just to tell the calibration code but now we are reconsidering that is that the best way to do this? If extension is ok this would still probably be the most simple way to do this?
John Moehrke (Oct 01 2020 at 12:13):
seems Device.property would work. It is a rather unconstrained set of key value pairs
Mikael Rinnetmäki (Oct 20 2020 at 08:24):
Lauri Karppinen said:
I know there is a DeviceMetric resource but there is no place to store a string about calibration.
I thought https://www.hl7.org/fhir/devicemetric-definitions.html#DeviceMetric.calibration is meant for just this purpose.
Mikael Rinnetmäki (Oct 20 2020 at 08:24):
But yes, it seems there is no place for the actual calibration value.
Lauri Karppinen (Nov 11 2020 at 09:20):
John Moehrke said:
seems Device.property would work. It is a rather unconstrained set of key value pairs
Seems like device.property is still in progress? In https://www.hl7.org/fhir/device.html “DeviceDefinitionPropetyCode (Extensible)” can not be clicked. Are these codes still undefined or is there somekind of bug? Suggestion of @John Moehrke seem like a valid idea to use device.property to store this information. I’m still not sure did I understand the idea correctly. Should I just use device.property.type and use text element of codable concept? If there is some example of device resource which could be helpful can You please point me to that? I’ve only found very few device examples and they have a very little information in them.
Lloyd McKenzie (Nov 11 2020 at 14:40):
@Todd Cooper @John Rhoads ?
Last updated: Apr 12 2022 at 19:14 UTC
