After the MMDI project’s showing remarkable progress in building the wireless communication adapter and in processing and analyzing personal health data, it is the time to consider and plan the possible next steps for the project.
On one hand, extending or enriching the functionalities of the MMDI wireless communication adapter is an important task in the near future. The MMDI project was intended to build a universal adapter to connect multiple medical devices to cross-platform mobile devices with different wireless technologies. Medical devices can be classified into different categories and each category can have different products provided different venders. Similarly, mobile devices can be divided into various platforms, such as Android, iOS, Blackberry and etc. as well as mobile frameworks like Cordova/Phonegap. Meanwhile, the wireless technologies used in the device communication are also various, including Bluetooth, NFC and Wi-Fi. Therefore, different combinations of these factors make the MMDI project have a large number of aspects or areas that need to be researched or probed. Currently, the MMDI project has completed the implementations of using Android platform and Cordova on Android platform to connect to a certain number of medical devices based on Bluetooth technology. This means we have merely finished the first one or two step(s). The possible new research areas of the MMDI project could among the following list:
- Extending the MMDI project to support other mobile platforms or Cordova which are based on these platforms, such as iOS, Windows Mobile, webOS, Blackberry and etc.
- Adding NFC or Wi-Fi connectivity to the MMDI for supporting alternative wireless communication technologies.
- Implementing more Bluetooth enabled medical devices into the MMDI project to extend the current Bluetooth communication library for Android and Cordova/Phonegap on Android platform.
On the other hand, building up PHR data-process-adapter and common PHR data model would be the significant task or goal which will make the CDOT (NexJ) Health Research team be leading in the research of people-centered PHR system in healthcare industry. Actually, the Seneca Health Research team’s research and implementation of the applications based on the APIs of FitBit, Withings and MyOSCAR have made the team on the way toward this goal.
What is PHR data-process-adapter?
What is Common PHR Data Model?
Nowadays, there is no standard data model for building personal health record applications. The personal health data retrieved from different PHR servers may have different naming formats and data structures. The Common PHR (person health record) Data Model is the standard data model for retrieving, updating, analyzing personal health records (PHRs) used in mobile native or front-end web applications. Within these applications, all PHR data from different PHR servers will be converted into the common PHR data model by the PHR data-process-adapter. Thus, the end user (mobile native or front-end web) applications can process personal health records from different PHR servers seamlessly, supporting people-centered PHR analysis process.
Why we need the PHR data-process-adapter and the Common PHR Data Model?
The PHR data-process-adapter and the Common PHR Data Model will be used to deal with the mess or problems in today’s PHR software market and to realize the break-through of building people-centered personal health record analysis applications.
Today, there are a number of different PHR software/systems in the market. The interoperability among different PHRs is the issue to which no PHRs architecture wants to face. As results, people/patients may be forced to used certain PHR systems but none of these systems can provide comprehensive PHR data from different systems; doctors and health coaches are facing the same problems when accessing patient’s PHR.
Please view the following situations.
- People who use FitBit and Withings serial medical devices have to use vendor-provided mobile apps and servers for the collection and storage of personal health data.
- A patient who is suffering chronic illness may be asked to use MyOSCAR for his/her personal health records by his/her family doctor.
- A patient is probably asked to use TELUS PHR if the patient visits a specialist for his/her chronic illness.
- The health coaches for chronic illness may ask their patients to use the NexJ PHR systems created by the connected health and wellness project.
The above situations can mostly happen in particular for the patients who suffer multiple chronic diseases.
Building up PHR data-process-adapter and common PHR data model is to create a framework for building front end (mobile and Web) PHR applications which support people-centered PHR analysis or comprehensive PHR data analysis from multiple data sources.