3 ms·
We are planning on integrating with multiple EMR's to make sure we're able to offer a fully automated, fully integrated approach to practices. I love the steps
by Hydrick3232 7y ago
We are planning on integrating with multiple EMR's to make sure we're able to offer a fully automated, fully integrated approach to practices. I love the steps Epic is taking to open up API's. My hope is that more EMR's will follow suit. Healthcare is fun...and challenging :).
- technics256 7y agoGood luck! How long did mvp/integration take from idea? Us was long....over a year
- Hydrick3232 7y agoThanks! Idea to MVP/integration was 3 months. I feel your pain on the integrations. Would love any insight you have on streamlining that process.
- technics256 7y agoAs mentioned above, redox or other similar systems is your best bet! But redox is stubbornly expensive.
- aaron425 7y agoFHIR APIs are definitely becoming more and more broadly deployed, which is awesome! Scaling wise, it might be worth looking into the interoperability partners that specialize in standing up FHIR endpoints for providers like Datica & Redox.
- Hydrick3232 7y agoAwesome, thanks for the insight!
- kyloon 7y agoAgree on FHIR APIs are becoming ubiquitous especially with Apple Health pushing its adoption in consumer facing applications, not so much on the legacy enterprise side from what I've seen thus far (I work primarily in the clinical trials side of things) and we prototyped our own integration stack to help with wrangling with different standards (more like the lack thereof). It is worth actually building that ourselves in the early days as we have learned so much about the challenges to integrate with our partners and will at some point looking into interoperability partners as we scale.