Integrations
We connect to what you already run. And we tell you what we haven't built.
Health-tech integration pages tend to be a wall of logos with no indication of what is real. Here is ours with the status marked honestly: in production, enabled per practice, or on the roadmap.
Status reflects what is deployed, not what is announced.
Reading your chart
We need your problem lists, medications, allergies, and visit history to know who qualifies. We take the least invasive route that gets us there.
- In production
FHIR / US Core export
Panel and problem-list ingest
Standard FHIR bundles, bulk $export NDJSON, and Epic EHI archives. Works on day one without waiting for anyone's API approval queue.
- On the roadmap
SMART-on-FHIR direct read
Continuous chart sync
A live authorized read against Epic FHIR R4 and equivalent endpoints, replacing periodic exports. Built behind the same internal interface, enabled per practice as access is granted.
- On the roadmap
Structured write-back
Notes and orders into the chart
Discrete write-back where the EHR supports it. Never a billing prerequisite — the fax path already satisfies the documentation requirement.
Getting data from the patient
For RPM, the device has to transmit on its own. That constraint eliminates most consumer hardware and all patient-typed numbers.
- In production
Cellular device fleet
FDA-cleared and auto-transmitting
FDA-cleared blood pressure cuffs, scales, glucometers, and pulse oximeters that transmit on their own cellular connection, with no dependency on the patient's home network. Ships preconfigured to the patient.
- In production
Patient messaging
SMS reminders and nudges
Enrollment reminders, transmission nudges, and scheduling. Engagement only — messaging never counts toward the interactive-communication requirement.
- Per practice
Consumer health app data
Engagement context
Patient-reported and phone-sourced readings can be displayed for clinical context. They are explicitly excluded from the transmission-day count.
Verifying and billing
Eligibility drives the APCM level and catches the single-biller problem before it becomes a duplicate claim.
- In production
Eligibility & claims
Coverage checks, MBI, and 837P
Coverage and beneficiary-tier verification at enrollment and monthly, plus claim preparation. Also how we detect that someone else is already billing the program.
- Per practice
Your billing system
Claim submission
Claims are prepared for your existing workflow and submitted by your practice under your own NPI. We do not bill Medicare and never take reassignment of benefits.
Getting documents back
Signed orders and monthly summaries have to land in the legal record. Fax is unglamorous and it is also universal.
- In production
Fax-to-chart
Signed orders, monthly summaries
HIPAA-compliant fax delivery through a vendor under a business associate agreement, with delivery confirmation retained as part of the evidence file.
- In production
Document export
Evidence files on demand
Any patient-month's complete evidence file, retrievable as a single document for audit response or internal review.
Every vendor that touches protected health information on our behalf operates under a downstream business associate agreement. We do not list a partner as in production until it is running in a real deployment path rather than a demo adapter.
Integration questions
What IT asks
Do we have to change or replace our EHR?
What if our EHR has no usable API?
Where do device readings actually live?
How long does onboarding take?
Tell us what you run and we'll tell you what's involved
Bring your EHR name and your billing setup to the panel scan. We will map the actual path rather than promising a generic one.
No EHR change. No commitment.