HIPAA Build and Integration
$60,000 - $300,000
Per initiative. 6 to 20 weeks.Every build is delivered under a signed business associate agreement with encryption in transit and at rest, least-privilege access, and audit logging designed to answer the questions an OCR investigator asks rather than the questions a developer finds interesting.
We work in one to three week increments with something demonstrable at the end of each. There is no six-month engagement where you see the first working version in month five.
What you receive
Working automation in production
The workflow, running against your real systems, with the failure modes handled rather than ignored.
Integration layer
FHIR, HL7 v2, X12, vendor APIs, or supervised database and browser automation where nothing better exists. Chosen on capability, not preference.
Technical runbooks
How it works, how it fails, how to restart it, and who to call. Written for your operations team, not for us.
Architecture and data flow documentation
Diagrams and written descriptions at the level a security reviewer or auditor expects to receive.
Monitoring and alerting
The automation tells you when it stops working. Silent failure is the single most expensive outcome in this category of system.
Knowledge transfer
Working sessions with your technical staff so the system is maintainable by people who did not build it.
How the engagement runs
In order, with what happens at each point stated plainly.
Define the workflow contract
Exact inputs, outputs, failure behavior, escalation rules, and success criteria, written down and agreed before code exists.
Prove the integration
We verify integration capability against a real non-production environment before committing to a design that depends on it.
Build in increments
One to three week increments, each ending in something you can see working against real data.
Test against real failure
Interface outages, malformed messages, payer portal changes, duplicate events. We test the failures, because they are what determines whether the system is trusted.
Deploy and monitor
Production deployment with monitoring, alerting, and a defined rollback path.
Hand over
Runbooks, architecture documentation, and working sessions until your team can operate it independently.
This is a good fit when
- A specific workflow with a defined owner and measurable current cost
- Organizations with the operational capacity to own a system after handover
- Integrations where off-the-shelf products genuinely do not fit the workflow
- Digital health companies that need an integration layer they control
This is the wrong engagement when
- Workflows nobody has mapped yet, which should start with the assessment
- Problems a well-configured commercial product already solves
- Organizations wanting an unowned system that runs indefinitely without maintenance
If any of these describe you, say so on the call. We would rather scope a smaller engagement correctly than a larger one badly. (307) 454-0600
Common Questions
Who owns the code?
You do. Source code, infrastructure definitions, and documentation are yours, in your repositories, from the first commit. We do not build businesses on client lock-in.
Do you work in our cloud or yours?
Yours, in the large majority of engagements. Running inside your tenant means PHI never leaves infrastructure you control, and it makes the compliance story materially simpler for both of us.
What happens if the payer portal or interface changes?
The automation detects the change and stops rather than proceeding on a wrong assumption, and it alerts a named owner. Handling that change is either your team’s work using the runbook, or ours under a managed agreement.
Request this engagement.
Tell us about the organization and the workflow. We will come back with a scope, a timeline, and an honest read on whether this is the right starting point.
Or browse the workflows we automate first.
Start with a conversation, not a proposal.
A 45-minute call with a senior engineer. We will tell you honestly whether automation is the right answer for the workflow you have in mind.