US Healthcare
Healthcare software, built as an extension of your team.
A regulated space we already know, with SOC 2 and HIPAA controls baked into the process, within the technology environment you already trust.
“They immersed themselves in our goals, asked the right questions, and ensured that every deliverable aligned with the outcomes we needed.”
Domain depth
We build healthcare software with you
We’re fortunate to work across the range — from writing the first lines of code for healthcare startups to building complex systems alongside established healthcare companies. One of those startups has since been acquired; another is backed by private-equity growth funding.
Revenue cycle management
Software across the revenue cycle’s hardest processes — appeals, denials and prior authorization.
Payer policy and eligibility, at scale
Automated systems that turn constantly changing policies and coverage into machine-readable libraries — across UnitedHealthcare and Aetna, EviCore, regional Blues plans and state Medicaid — a foundation to build solutions on.
Accelerated releases when it matters
Time-critical builds when the deadline can’t move — like the customer-facing app and support systems we shipped when Covid hit.
AI, used and verified
We use AI, but validate every output against a human-curated gold standard, built with custom tools. Because healthcare needs to be correct, not almost correct.
Data & access
How we work with your team
We work as part of your team, inside your own environment — by your rules, on your systems. Your data stays where it is, and everything we do stays on the record.
No PHI in our hands
We work on de-identified and synthetic data, never the real thing. There’s no PHI to leak and no BAA to sign — the exposure isn’t managed, it’s designed out.
Inside your environment
You and we work in the same place, as one team — your systems, your virtual desktops, nothing copied out. What’s yours never leaves your walls.
Access is granted, not held
No standing privilege. Access is requested when it’s needed and expires after, scoped to the least a role requires, with every action logged where it can’t be edited.
Compliance, the technical half
The settings an auditor actually checks
We build for what an auditor actually tests — not just that a system is secure, but that it can prove it, in records no one can quietly change.
We cover the technical side — the cloud infrastructure, the access model, and the evidence an auditor checks. The written program — policies, risk analysis, training — stays with you or your compliance partner. The settings that pass the audit are ours.
- Public access closed; databases off the public internet, behind private endpoints
- Secrets in a managed vault, out of config files and pipelines
- MFA everywhere, and privileged access that expires instead of sitting on an account
- Least-privilege roles — the people who read logs can’t change them
- Centralized audit logs, protected against edits and deletion
- Alerts on permission changes, incident response, backup and DR, penetration testing
Field notes
The detail behind the claims
Written up by the people who built it — not a brochure.
Where Could Epic Connectors Lead? A Thought Experiment
When Epic announced Connectors at Open@Epic in October, most of the coverage focused on the next twelve months. It’s a change in the right direction,…
What Epic’s Latest Moves Mean for Health Tech Products
In our last post, we looked at what Epic Connectors mean for Revenue Cycle products. But Connectors are only one piece of the larger picture based on…
What Epic Connectors Mean for Your Revenue Cycle Product
Open@Epic, held on 21st–22nd October, came with much-awaited announcements. The most impactful of all is “Connectors”-: the ability for Epic’s AI agen…
Taking Epic/Cerner Integration from Sandbox to Production
Almost every enterprise integration begins with a sandbox. Epic and Cerner (Oracle Health) also provide sandboxes for integration and testing prior to…
Your Appeals Are Only as Good as Your Policy Library
Every appeals, denials and prior-auth workflow eventually needs the same thing: the payer’s current medical policy, in a form a machine can read. A la…
Building healthcare software in the US?
Tell us what you’re working on. You’ll talk to a founder, not a sales rep.
Talk to us