Stream: implementers
Topic: MedicalDeviceTrack
Melanie Yeung (Nov 09 2016 at 18:44):
hi all, hope you're all excited to learn a bit more about medical device connectivity at the FHIR DevDays. I'll be leading the PersonalConnectedHealthAlliance/Continua track to discuss medical device data and data standards such as IEEE and Bluetooth.
Melanie Yeung (Nov 09 2016 at 18:48):
Medical devices are instrumental to everyday management of patients inside and outside the hospitals. Devices range from activity monitors, glucose meters, blood pressure monitors, and weight scales as well as why this data is so important to both the patient user as well as healthcare providers. Hope you are able to come learn more about the tech, the underlying data standards, it's clinical use cases and how we're going to be able to map it to FHIR
Melanie Yeung (Nov 16 2016 at 14:07):
How do we add a unit code to the SimpleQuantity? for Periodic measurements
Lloyd McKenzie (Nov 16 2016 at 14:12):
Not sure what you mean. Just use SimpleQuantity.code or .unit
Melanie Yeung (Nov 16 2016 at 14:19):
how do we see that in http://www.hl7.org/fhir/datatypes.html#SimpleQuantity
Melanie Yeung (Nov 16 2016 at 14:20):
unless you go into the JSON / XML examples http://www.hl7.org/fhir/simplequantity.profile.json.html
Melanie Yeung (Jul 06 2017 at 16:04):
Hello FHIR community! Personal Connected Health Alliance / Continua is back for another showing at the FHIR Dev Days this coming November. There are many different medical devices that can be extremely useful to patient management. Glucose meters for diabetes patients, blood pressure to track hypertension, weight scales and activity monitors for health and wellness just to name a few. We're interested to know if anyone out there is playing with device data - what type of data are you trying to use? how are you using it? how can we help? #devdays2017
Michael J. Kirwan (Jul 07 2017 at 02:52):
Melanie, PCHAlliance|Continua have several recently certified devices that could be used and Dev Days. Additionally, there are more planned devices in the certification pipeline that we can reach-out to ahead of Dev days. We would also be interested in helping any organizations interested in developing devices and apps ahead of Dev days (whic could also be used during Dev days).
Melanie Yeung (Aug 03 2017 at 14:46):
hey all, is anyone working on device data these days? what kind of data are you using? how are you using it? what are some of the issues that you are experiencing?
Melanie Yeung (Aug 03 2017 at 15:02):
@Jayashree Surnar are you currently working on integrating device data?
Mikael Rinnetmäki (Aug 03 2017 at 15:02):
We (Sensotrend) are using all sorts of data from medical devices as well as from wellness trackers, in our apps for people with type 1 diabetes. We know of Continua specs for glucose meters, for instance. Having standards is good, would be even better to see wide-spread adoption. Insulin pumps tend to be even more difficult and diverse, although there are only a handful of manufacturers on the market.
Brian Reinhold (Aug 03 2017 at 15:06):
@Mikael Rinnetmäki We at PCHA (Remote Patient Monitoring) are defining standards for the upload of medical device data from personal health devices using FHIR. Will you be participating in the FHir Dev days? We are interested in consumers of this data. We would love to have your applications to be able to consume the data.
Melanie Yeung (Aug 03 2017 at 15:09):
@Mikael Rinnetmäki we are also working on diabetes apps. Insulin pump devices are definitely more complicated and have a lot of important data that would be interesting to capture. In addition, CGMs!
Melanie Yeung (Aug 03 2017 at 15:09):
have you already used any of the FHIR resources for the diabetes data?
Melanie Yeung (Aug 03 2017 at 15:23):
also, is your app collecting the data directly from the device?
Erik Moll (Aug 03 2017 at 15:23):
We (Sensotrend) are using all sorts of data from medical devices as well as from wellness trackers, in our apps for people with type 1 diabetes. We know of Continua specs for glucose meters, for instance. Having standards is good, would be even better to see wide-spread adoption. Insulin pumps tend to be even more difficult and diverse, although there are only a handful of manufacturers on the market.
Are you consuming data from a back end / server or data coming directly from devices over Bluetooth or other transport?
Mikael Rinnetmäki (Aug 03 2017 at 15:45):
We have uploader apps that integrate with devices (both their cloud services and hardware, including bluetooth and usb), and also apps that visualize and help make sense of that data.
Mikael Rinnetmäki (Aug 03 2017 at 15:47):
Not sure yet whether we can make it to DevDays. Nov 14th is the World Diabetes Day, and fully packed with activities...
Mikael Rinnetmäki (Aug 03 2017 at 15:51):
We've mapped some of the data to FHIR resources, and are planning to do more of that quite soon (there's a new national PHR opening in Finland, based on FHIR). We're integrated with Epic and Cerner already, but currently mainly for the Smart on Fhir part (launching the app), not writing data to their EHR's. We do read HbA1c lab results etc. from the EHR though.
Mikael Rinnetmäki (Aug 03 2017 at 15:54):
Blood glucose observations seem trivial, but for instance for CGM we haven't found a LOINC code. A SNOMED code does exist, though. I've been following the discussion on food intake (we get the estimated carbs from bolus calculators), but there does not seem to be a FHIR resource for that yet.
Mikael Rinnetmäki (Aug 03 2017 at 15:55):
Insulin doses seem to be catered for in MedicationAdministration.
Melanie Yeung (Sep 01 2017 at 13:08):
We're excited to announce the theme for our track this year's hackathon in Nov. This track will explore device data generated from Continua compliant devices, consumed by FHIR information systems and then used by applications and clinical decision support systems in the context of hospital to home scenarios. Participants will work with device data through a pregnancy disorder use case and learn about Continua interoperability framework for bringing data from medical devices to services and systems used by patients and caregivers in a meaningful way.
Melanie Yeung (Nov 15 2017 at 13:10):
References:
http://www.pchalliance.org/continua-design-guidelines
http://www.itu.int/itu-t/recommendations/index.aspx?ser=H
H.810: Interoperability design guidelines for personal health systems
H.811: Interoperability design guidelines for personal health systems: Personal health devices interface
H.812: Interoperability design guidelines for personal health systems: Services interface: Common certified capability class
H.812.1: Interoperability design guidelines for personal health systems: Services interface: Observation upload certified capability class
H.812.2: Interoperability design guidelines for personal health systems: Services interface: Questionnaires
H.812.3: Interoperability design guidelines for personal health systems: Services interface: Capability exchange certified capability class
H.812.4: Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session capability
H.813: Interoperability design guidelines for personal health systems: Healthcare information system (HIS) interface
https://www.bluetooth.com/specifications/gatt
http://standards.ieee.org/findstds/standard/11073-10101a-2015.html
https://rtmms.nist.gov/rtmms/index.htm#!rosetta
Last updated: Apr 12 2022 at 19:14 UTC
