Stream: implementers
Topic: Error, warnings, messages generated by devices
Keerthi M (May 18 2020 at 14:19):
Hi All,
Could you please help me identify the best option to handle/store errors, warnings and messages generated by a device? For instance, a device generating an exception that "Battery is dead".
Similarly there could be many other warnings or messages.
Many thanks in advance!
Lloyd McKenzie (May 18 2020 at 15:20):
Probably Observation. @Todd Cooper @John Rhoads ?
John Rhoads (May 18 2020 at 17:07):
@Keerthi M @Lloyd McKenzie Great question. Certainly Observation is part of the answer, and I'd point you to the MDC code system and its underlying standard, IEEE 11073-10101 (2019), which has a lot of detailed nomenclature and codes for errors, warnings, and messages from numerous specialized acute-care and personal devices. There is an extension of this standard forthcoming this year with more event codes of these kinds. There are groups working on this area in both IHE (the Devices DEV domain) and HL7 Health Care Devices ("Devices on FHIR"), as well as IEEE 111073 Medical Device Communications, with particular focus on device events and alerts you might want to look into or, if you like, join. Real-time handling of device events and alerts with methods including FHIR is a hot topic. Contact me (john.rhoads "at" philips.com) or @Todd Cooper with questions
John Rhoads (May 18 2020 at 17:10):
Also, the US National Institute of Standards and Technology makes the MDC nomenclature available on the web at https://rtmms.nist.gov/rtmms/index.htm with royalty-free use by arrangement with IEEE.
John Rhoads (May 18 2020 at 17:12):
"Battery is dead" and other battery state messages are certainly in there...
John Moehrke (May 18 2020 at 18:28):
AuditEvent might be another good one to look at. This is certainly the kind of thing I would expect to find in AuditEvent.
Last updated: Apr 12 2022 at 19:14 UTC
