Stream: implementers
Topic: calibration code device resource
Lauri Karppinen (Oct 09 2018 at 06:32):
Hi! I need to put calibration code of our device in device resource. Can't find any appropriate field for that. Anyone have any suggestions how should I do this? Have been trying to find loinc/snomed code for calibration but with no success. Thanks!
Lloyd McKenzie (Oct 09 2018 at 14:11):
@Todd Cooper ?
Todd Cooper (Oct 09 2018 at 14:22):
Yup ... but I’m standing on a street corner downtown D.C. right now :sunglasses: Can you provide an example of the type of device and the data you are looking to exchange?
Todd Cooper (Oct 10 2018 at 12:54):
@Lauri Karppinen Let me know if you still need guidance - with the background I mentioned, it should be pretty obvious.
Lauri Karppinen (Oct 11 2018 at 05:25):
Help is still very much appreciated @Todd Cooper . Device we use is spirometer. It was quite easy to find definition that it's spirometry device but I could not find any field for calibration code.
Grahame Grieve (Oct 11 2018 at 05:26):
what's a 'calibration code'?
Grahame Grieve (Oct 11 2018 at 05:26):
(and I know what calibration itself is)
Lauri Karppinen (Oct 11 2018 at 11:01):
what's a 'calibration code'?
Each lot of flow transducers has a specific Calibration code. It's used to calibrate the device to set of flow transducers. I have not implemented this yet. In current plan of device resource it is as a "text" of "note". Will change it before implementing if there is a better option. In DeviceMetric I found calibration field but there is only options: type, state and time. Can't put any value there. @Todd Cooper @Grahame Grieve
Grahame Grieve (Oct 11 2018 at 16:53):
used to calibrate the device
it's a command to calibrate? A notification that calibration is required? A statement that it's ok?
Todd Cooper (Oct 17 2018 at 00:08):
Sorry for the delay ... again ... @Lauri Karppinen Ahhhh ... the ol' "spirometer" question ... let me ping @John Rhoads who I believe spent quite a bit of time in a past life with these devices and is one of our co-authors on a Point-of-Care Device FHIR Implementation Guide, along with @Stefan Karl . They should be able answer your question from a deeper experience base.
Todd Cooper (Oct 17 2018 at 00:13):
Note also that DeviceMetric is essentially metadata for a parameter that is then realized in Observation instances. I would think that you would want to formalize the "lot" calibration code either once in the DeviceMetric - across all the observations that the transducer's report, or in the Observation itself.
John Rhoads (Oct 17 2018 at 03:56):
@Lauri Karppinen @Todd Cooper Sounds like an attribute that could be important in other cases as well. Similar to the code on a batch of glucose meter test strips that calibrates the meter to batch characteristics. Is it best considered as the attribute of a flow meter set, which is in turn a separately modeled component of a multicomponent device system, or is the calibration code of the current flow meter set best considered more simply as a changeable temporary attribute value of the principal device, which you could consider using the 'properties' name-value tuple in its Device resource to hold? Depends on the kinds of things your use case needs to be able to do with them.
Last updated: Apr 12 2022 at 19:14 UTC
