Location: Remote. Must be able to collaborate with a globally distributed team across timezones.
Objective: We are developing a universal interoperability layer (“agnostic router”) that allows our backend platform and white-label health applications to instantly connect with multiple EMR/EHR systems. The goal is to enable seamless two-way data exchange — patient data, lab results, appointments, messages, consent, patient notes, patient plans, survey responses, lab ordering and notifications — between our AI-driven health apps and the clinical systems used by our clients (clinics, hospitals, insurers, and governments).
The agency will design and implement the foundational interoperability layer that integrates once and scales to many EMR/EHR vendors globally (e.g. Cerbo → Epic → Oracle Cerner → etc). All work must be HIPAA compliant.
Responsibilities:
- Architect and implement interoperability integration: Design and build a connection between our platform and an interoperability’s standardized API to connect data to the top the EMR/EHRs. Use data models to receive patient history, medications, lab results, vitals and scheduling information; write back patient‑generated data (lab results, survey responses, vitals) into the EHR, support PDF parsing for unsupported labs.
- Two‑way communication: Implement message queues or event subscriptions (e.g., FHIR Subscriptions) so that updates like new lab results, appointment confirmations and prescription changes trigger real‑time notifications to our app and EHR
- Design a multi-tenant, low-maintenance integration architecture that supports:
- On-prem, cloud, PAAS, IAAS, and SAAS deployments.
- HIPAA/GDPR/SOC-2 compliant security and consent logging.
- Minimal customization per clinic / white-label client.
- Minimum EHR/EMRs that must be compatible with the interoperability’s standardized API & within your team's expertise: Cerbo, Oracle Cerner, Epic. (Cerbo will be the project we develop as part of this project, but all 3 (and more) must be compatible with the approach and implementation).
- Implement patient consent and authorization flows, ensuring that only authorized data are shared and that the patient can select which data to share.
- Configure mapping for the EHR/EMRs FHIR/HL7/SMART APIs and map our backend’s data fields to theirs.
- Intake form and survey mapping: Design flexible data models that allow new questionnaire fields to sync automatically with EHR intake and consent forms.
- Security and compliance: Enforce HIPAA/HITRUST/SOC‑2 standards and encryption in transit and at rest. Implement consent and audit logging, role‑based access controls, and ensure data flows only with patient authorization. (Out of scope: HIPAA procedures or policies in addition to standard product documentation and handover materials)
- Testing, monitoring, alerting and fixing: Create automated testing protocols including data‑mapping verification and performance tests that can run, evaluate, self-heal and fix itself. Set up logging, error handling and monitoring to ensure reliability and capture data anomalies. All automatically resolved issues should generate a report for both technical and non-technical stakeholders
- Documentation & handoff: Produce technical documentation and knowledge transfer so our team can maintain the integration.
- **Develop in phases **
- This project does not involve frontend development.
- Proven delivery of ≥ 2 EMR/EHR integration projects that are relevant to this use case
- Strong knowledge of FHIR R4, HL7 v2, OAuth2 / SMART on FHIR.
- Completed and taken HIPAA projects to production with more than 2000 users
- Experience building API aggregators, event buses, or middleware platforms.
- Healthcare data-exchange compliance expertise.
- Ability to start immediately and complete Phase 1 within 4 weeks.
- Technical specification & integration plan detailing data flows, APIs and security measures.
- Fully functional Cerbo integration through the router launched to production & fully integrated with whitelabel apps. Demo + handover to internal engineering team (Phase 1).
Agnostic router design ready for other EMR/EHR extensions - e.g. Epic + Cerner. With remaining features; test reports, monitoring setup, and technical documentation. Demo + handover to internal engineering team (Phase 2).