Stream: implementers
Topic: Wearable device support in FHIR
Sheldon Hall (Jun 24 2019 at 16:15):
I am looking at developing a machine readable standard for recording wearable device data for health care in a useable form. I figure I am not the first and wondered if anyone in the FHIR community were aware of any efforts in this direction? It seems that the use of this type of data in healthcare provision will be increasing and thought it would be good to get ahead of the game a little.
Jose Costa Teixeira (Jun 24 2019 at 16:34):
Are you looking for a specific wearable device type with a specific type of data (e.g. heart rate , temperature...)? AFAIK we do support "wearable device data" because it does not matter whether the device is wearable or not as long as it gives a heart rate.
Or something else? Any specific requirements?
Eric Haas (Jun 24 2019 at 17:23):
I know of FHIR, Open mHealth and Continua/IEEE standard 137
Sheldon Hall (Jun 24 2019 at 18:19):
@Jose Costa Teixeira Right now I am just scoping out what is there. I am looking for a device agnostic representation (if possible) which I guessed could be created by combining FHIR resources. The main reason is to share healthcare data for research. For that reason I was thinking about whether the device definition should include maybe some kind of uncertainty and register the types of vital signs they can log. Further, whether there should be a way to encode the raw data and if heart rates from different devices could be used seamlessly or whether there are practical reasons this is not a good idea.
Sheldon Hall (Jun 24 2019 at 18:20):
@Eric Haas thanks I will check them out
Jose Costa Teixeira (Jun 24 2019 at 18:44):
whether the device definition should include maybe some kind of uncertainty and register the types of vital signs they can log.
I read this as "a catalog of DeviceDefinitions and the corresponding ObservationDefinitions". Could be.
Jose Costa Teixeira (Jun 24 2019 at 18:45):
"the raw data" sounds like observation.value. Not sure what you mean by encoding. perhaps a higher-level encoding..?
Sheldon Hall (Jun 24 2019 at 20:52):
Yes re-use of existing fields will cover a lot of use cases I suspect. Next I will probably aim to approach some vendors and users of the data to see if the fields provided cover everything they need. Thanks for the interest.
Last updated: Apr 12 2022 at 19:14 UTC
