Integration of healthcare and patient information for doctors
One of the 5 challenges for the Hacknosis was the integration of healthcare and patient information for doctors.
Why does this matter?
As smart devices become more accessible to the public and with the rise of fitness and wellness apps available, patients are owning and tracking their own health data in ways that were not accessible to doctors before. Therefore, the need to create secure ways to share data with healthcare providers and connect to their health networks and systems is becoming increasingly important.
Patients are collecting data on their eating habits, fitness regimes, and if they have smart medical devices (such as Continuous Glucose Monitoring devices), this data can be shared with their healthcare providers. Enabling patients to share this information with their doctors could facilitate fewer visits, customized treatment plans, and reduce the need for testing in some cases, while giving doctors a better picture to diagnose and customize treatment based on lifestyle.
The ask:
We asked participants to develop a connector or solution that allows patients to seamlessly share their health information with healthcare providers securely.
A lot of wearable technology have health kits included as part of their software package. These health kits are making it easier for developers to create connectors for patients to access their records from providers but it does not allow users to share a lot of the data they're collecting back to their practitioner. Another core problem with data transmission to patients is they are receiving raw reports with no real value to the patient. A blood test with no descriptors for what is being tested and some results are now highlighted with red and green values in the results doesn't help the patient understand their results, still requiring a doctor to discuss and translate the findings.
Wearables are not created equally and some devices do auto-tracking better than others, developers could build solutions to auto-track activities therefore removing another barrier for accurate data collection from the patient.
The OpenText Difference
For this Hackathon, we provided participants access to our developer solutions which included use of the Information Management Services API's and allowed participants to utilize other teach stacks and API's to aid the build of their solution. The Information Management Services API's includes a set of API's that are meant to digitally transform data so it can be utilized in more meaningful ways. For this particular challenge, we wanted to see how participants could leverage the OpenText API's and Google Health API's to create solutions that make it easier to consume, ingest or share data with their providers and vice versa. Head over to the winners page to read about the winner's solution.
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 150 General Questions
- 148 Thrust Services
- 57 OpenText Hackathon
- 37 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 186 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 8 XM Fax
- Follow Categories