Open a thread
Tell us about the workflow.
The first conversation is two senior engineers on a thirty minute call. No SDRs, no discovery deck. We read what you send, and we come prepared.
In your first message
Four things that
help us come prepared.
- 01
The workflow you're trying to move
Encounter cycle, prior auth, intake, RPM triage. The single thing that, if it worked better, would change your week.
- 02
The systems it touches
Epic, Oracle Cerner, Athenahealth, eClinicalWorks, NextGen, AdvancedMD, Healthie, Mirth, billing, monitoring, your data warehouse. A rough sketch is fine.
- 03
Who we'd work alongside
The clinician owner, the engineering lead, anyone who has to live with what we ship.
- 04
Timing
When you'd want this in production, and what's blocking that today.
Other ways in
- Response
- One business day
- Coverage
- US · EU · Asia
Written by an engineer, not a sales seat.
HQ in San Francisco. Engineers across the Americas, Europe, and Asia. Follow-the-sun coverage, embedded with you for the engagement.
Common questions
Things prospects
always ask.
01How do you engage, fixed bid, time and materials, or retainer?
How do you engage, fixed bid, time and materials, or retainer?
Most engagements run as a quarterly retainer for an embedded pod (one to three forward deployed engineers). For diligence and architecture reads we run a fixed two week sprint. Project rate cards are shared after a first call.
02Do you work with Epic, Oracle Cerner, and Athenahealth directly?
Do you work with Epic, Oracle Cerner, and Athenahealth directly?
Yes. We ship FHIR R4, HL7v2, and Bulk FHIR integrations against Epic, Oracle Cerner, Athenahealth, eClinicalWorks, NextGen, AdvancedMD, Healthie, and the practice systems the long tail of US clinics runs on.
03Who owns the code at the end of the engagement?
Who owns the code at the end of the engagement?
You do. Service as software modules ship to your repo under your license. We do not retain a perpetual license on engagement output.
04Are you HIPAA capable and willing to sign a BAA?
Are you HIPAA capable and willing to sign a BAA?
Yes. We work inside customer infrastructure under BAA, and we ship HIPAA aligned architectures (segregated PHI, audit logs, access controls, BAA covered vendors only).
05How fast can an FDE start?
How fast can an FDE start?
For most engagements, two to four weeks from signed SOW to first commit. Concierge availability varies by quarter, so earlier conversations help.