Implementing a telemedicine solution requires development of multiple patient and provider facing components that need to work in concert while maintaining simple and efficient workflow and strict privacy requirements. Typical features of such solution include
- Mobile app for patients
- HIPAA-compliant text/voice/video chat
- Integrations with multiple wearable devices and sensors
- Application for care providers for monitoring remote patient status and updating their care plans
- Backend integration with various EHRs
- Backend integration with billing systems
Remote Patient Monitoring (RPM), Chronic Care Management (CCM) and telemedicine in general, are attracting more and more attention from healthcare providers, patients and payers.
Adoption of CPT codes for RPM and CCM by CMS such as CPT 99091, enable healthcare providers to be reimbursed by Medicare for implementing telemedicine practices.
Instead of going along the “build-all-at-once” route, or adopting the 3rd party solution that only partially satisfy the requirements, we are proposing a 2-phase development of a telemedicine solution:
1. Development of a Proof of Concept solution. The PoC should be a fully functional system, rapidly developed, and limited to:
a. Single mobile platform - e.g. iOS.
b. Use off-the-shelf components: Apple CareKittm, ResearchKittm and similar
c. Gathering data only from devices that are already compatible with iOS - iWatch, FitBit, etc…
d. Backend integration with one EHR, or even just with non-production, test-only, anonymized health records
2. Once the PoC is finished, it can be used to evaluate user experience and gather requirements for implementation of the complete, production-ready solution.