Stream: implementers
Topic: DeviceSetting
ravi.kuchi (Sep 21 2017 at 16:49):
Hi, We are from Dialysis World and we want to capture the machine setting like Temperature, BloodFlow rate when we write the prescription. We checked DeviceMetric but it does not seem to be for this purpose. Can somebody help us and point us to use the right resource to be used when we want to record the dialysis parameters that are used while writing the prescriptions. Some of the dialysis parameters we have are: 1) Machine Temp 2) Blood Flow Rate 3) Dialysate Flow Rate 4) Estimated Dry Weight 5) Sodium Profiling - Start Level , End Level, Modeling Time. etc. Thanks
Lloyd McKenzie (Sep 21 2017 at 17:55):
So this is about ordering dialysis and specifying what the characteristics of what the settings on the machine should be when dialysis is performed?
Eric Haas (Sep 21 2017 at 17:57):
Good catch I thought was part of the report
Eric Haas (Sep 21 2017 at 17:59):
We have been looking at adding instructions to ProcedureRequest but never discussed machine settings in particular
ravi.kuchi (Sep 21 2017 at 18:09):
Yes, some of these are device settings although the order would also contain instructions about the sodium modeling and UFR profiling and Dialysate concentrations to be used in the Procedure. What we have noticed is that the value and reference range in observation resource actually capture the information that we currently have on the order form. We were wishing if these fields could be accommodated as a repeatable structures under instructions in ProcedureRequest.
Lloyd McKenzie (Sep 21 2017 at 18:14):
I suspect that device settings might also be part of orders for radiation therapy and certain other procedures as well. One of my questions is whether we'd ever need to deal with settings for different types of devices within a single order. Similarly, would there ever be a dynamic component to settings - e.g. make the setting X for 10 minutes, then change the setting to Y.
Eric Haas (Sep 21 2017 at 18:14):
Thinking this through... ProcedureRequest.supportingInfo with reference to the appropriate resource would be the way to go but I see your point that DeviceMetricdoesn't seem to handle your needs.
Lloyd McKenzie (Sep 21 2017 at 18:15):
For now, I'm afraid you'll need to use extensions. We're going to need to think carefully about how to handle this in a generalizable way (and figure out whether we want to handle it as core elements or standard extensions)
Todd Cooper (Sep 21 2017 at 18:16):
There is a project in OO w/ DEV WG support on dialysis devices and it is a regular topic of discussion - should sync up with the DoF team on your needs and proposal
Todd Cooper (Sep 21 2017 at 18:19):
One would hope that the approach taken would be analogous to what is needed for medication orders (e.g., using an infusion pump) or ventilator settings or other therapeutic devices
Todd Cooper (Sep 21 2017 at 18:21):
In terms of settings vs. reporting (observations) of settings, the terminology should be consistent
ravi.kuchi (Sep 21 2017 at 21:23):
@Todd Cooper , could you please provide the links to the support group you are referring to. Thanks
Todd Cooper (Sep 22 2017 at 23:10):
@ravi.kuchi For FMC you should probably give Teri Neal <Teri.Neal@fmc-na.com> a ping. She was the main person involved the last I checked. There is a terminology component and a (currently) V2 focused element, but from what I heard reported (indirectly) from the San Diego meetings last week, they will be moving toward FHIR sometime soon. So good timing to connect some dots ... sooner than later!
Last updated: Apr 12 2022 at 19:14 UTC
