80 likes | 311 Views
Mobile Health/HCD Joint Session. By Matthew Graham Mayo Clinic. What is Mobile Health?. Many things to many people Mobility is the common factor Mobile patients and service users Mobile health and care providers Mobile technologies Extending reach, enabling innovation
E N D
Mobile Health/HCD Joint Session By Matthew Graham Mayo Clinic
What is Mobile Health? • Many things to many people • Mobility is the common factor • Mobile patients and service users • Mobile health and care providers • Mobile technologies • Extending reach, enabling innovation • A new challenge for HL7 International • Mobile Health means mobile information • ...and greater dependence on standards
Interoperability between Healthcare and Mobile Devices • Healthcare Devices record Patient Generated Healthcare Data (PGHD) in the form of observations and event logging. • Mobile devices are used aggregate and propagate PGHD to other systems. • Mobile devices are used to facilitate journaling and validation of HCD observations.
Mobile Health WG Focus How do we facilitate Patient Healthcare Data Interoperability? Electronic Health Record 3G / 4G Mobile Internet WiFi Inputs Mobile Communication Device (phone / tablet / PC) Audio data Video Circuit Switched Network (PSTN) Personal Health Record Health Care Device data Data Health Care Device Health Care Device Health Care Device Health Care Device(s) Zero or More Devices As Needed
Examples of PGHD • Observations: weight, blood pressure, glucometer readings, heat rate etc. • Activity readings, walking, running, stairs and sleep patterns.
Uses of PGHD • What are some of the uses of PGHD? • Upload to patient’s PHR for future use. • Send data in message to Care Team. • Upload PGHD to Care Provider’s Patient Portal.
MH Projects (cont) • FHIR Project#1 (MH Project#4) • mFHIRframe • Develop a set of open source Libraries/APIs and Software Development Kits (SDKs) that would facilitate the implementation of mobile health applications based on FHIR (Fast Healthcare Interoperability Resources) standards. • These APIs will provide platform-independent, real-time, standardized means to access health information from/to mobile devices. • Class libraries will be created that support a variety of mobile/portable platforms, including iOS, Android, .NET, and Arduino. These class libraries will contain APIs that ease the incorporation of FHIR resources into their corresponding application interfaces; facilitate interaction with EHR systems; manage workflows and use cases set forth by IHE. • The work will be built upon existing FHIR artifacts