Integration and software for healthcare
We work with the standards hospitals use, FHIR and HL7, and with Epic’s own process for approving apps. Our engineers have been through Epic registration, interface go-lives and BAA reviews before.
Integration
- FHIRPatient data read and written over FHIR R4, with SMART on FHIR sign-in.
- HL7 v2 feedsAdmissions, orders, results and scheduling between hospital systems, with patients matched across them.
- EpicApp registration through Epic on FHIR, and launch from Hyperspace or MyChart where the health system allows it.
- Labs and pharmacyLab orders and results, and prescriptions exchanged with pharmacy systems.
Software on top
- Patient appsBooking, forms, reminders and messages on the patient’s phone.
- Staff dashboardsTools for clinical and admin staff, built on live record data.
- TelehealthVideo visits linked to the appointment and the patient record.
- ReportingReports on data with identifying details removed, for example in BigQuery.
Where AI helps in healthcare
We use AI for administrative work, such as reading documents and handling appointment requests. Clinical decisions stay with clinicians.
Document reading
Results and referrals that arrive as scanned PDFs are read, coded and routed, then checked against the structured data where it exists.
Patient assistant
Answers admin questions and books or moves appointments at any hour, within the same limits your staff work under.
Answers for staff
Staff ask about policies and procedures in plain language and get an answer with a link to the source document.
What AI does not do: give medical advice, read results to patients or make clinical decisions. Those go to a clinician, with the conversation attached.
Works with the systems you already use
Using something else? If it supports FHIR or HL7 v2, or has an API, we can usually connect to it.
Patient record systems
- Epic
- Other EHRs (FHIR or HL7 v2)
Other systems
- Laboratory systems
- Pharmacy and e-prescribing
- Billing and clearinghouses
- Health information exchanges
Questions we get on the first call
Have a question that is not here? Send it with the form below and an engineer will reply within one business day.
Will you sign a BAA?
Yes. Wherever we handle patient data, we work under a Business Associate Agreement, and each integration only sees the data its workflow needs.
How is patient data protected?
It is encrypted in transit and at rest in your own cloud account, it is kept out of logs, and only named service accounts can reach it. Test environments use made-up or de-identified data.
What happens if the record system is down or a message is rejected?
Outgoing messages wait in a queue and are retried. Rejected incoming messages are stored with the reason, and someone is alerted. Nothing is dropped without a trace.
How much message volume can it handle?
Integrations run as queued services that can scale out, so volume is a hosting decision. We size for your busiest hour, not your daily average.
Can you get us access to Epic?
We can take an app through Epic on FHIR registration and work with a health system’s Epic team, but the health system decides what an app can access. There is no shortcut around that.
Who owns the integration after go-live?
You do. The code, the infrastructure setup and the test messages are handed over with written instructions. We can stay on for support, or step away.
See how this works in practice
Four ways to work with us
A defined project
A defined integration or product, priced and scheduled up front, delivered with the test suite and infrastructure code you keep.
Engineers on your team
Engineers who join your team, your code and your daily meetings for as long as the roadmap needs them.
Ongoing support
We keep the integrations you run working: monitoring, vendor updates, new connections and month-end support.
Taking over existing systems
A system or integration nobody wants to touch: we review it, make it stable, then build on it.
