Healthcare software and EHR integrations
HIPAA- and PHIPA-aware architecture, HL7 and FHIR integrations, and connections to labs, pharmacies, and e-prescribing networks.
The problem
Healthcare integrations are where timelines go to die
Every health product eventually has to talk to an EHR, a lab, a pharmacy, or a payer. Each one has its own interpretation of the standards, its own certification process, and its own pace.
Add privacy legislation on both sides of the border, and teams without healthcare experience find out late that their data model, hosting, or audit logging won't pass review.
What I do
Architect for privacy from the start
I design data flows, hosting, access control, encryption, and audit logging with HIPAA in the US and PHIPA in Ontario in mind, so compliance reviews confirm decisions instead of reversing them.
Plan and lead integrations
HL7 v2 messaging, FHIR APIs, and EHR vendor programs: I map what each integration really requires, sequence the work, and manage the vendor relationship.
Connect labs and e-prescribing
I've worked through lab ordering and results, pharmacy, and e-prescribing integrations, including the certification steps that come with them.
Model clinical data properly
Clinical data has edge cases that generic data models miss. I help your team model patients, encounters, orders, and results so the product holds up as it grows.
What you get
- Privacy-aware reference architecture and data-flow diagrams
- Integration roadmap with vendor requirements and sequencing
- HL7 and FHIR interface specifications
- Security controls and audit logging design
- Documentation to support privacy impact assessments
- Oversight of integration builds and certification
How we'd work together
Integration work is usually project-based, scoped per integration or per phase. Companies building a health product over the long term often keep me on retainer as their healthcare technology lead.
Monthly retainer
Ongoing technical leadership with a set amount of time each month.
Project-based
A defined outcome, a fixed scope, and a fixed fee.
Questions
Can you make our product HIPAA or PHIPA compliant?
Compliance is an organizational responsibility, not just a technical one, so no consultant can hand it to you. What I do is design and review the technology so it supports compliance, and work with your privacy officer and legal counsel on the rest.
Do you work with both Canadian and US healthcare systems?
Yes. I design for both markets, including the differences in privacy law, data residency expectations, and how integrations work in each.
HL7 v2 or FHIR?
Usually both. FHIR is the direction the industry is moving, but many labs, hospitals, and older systems still run on HL7 v2. The right answer depends on who you're connecting to.
We're not a healthcare company yet. Is it too early?
The best time is before you build. A few early decisions about data, hosting, and logging save months of rework when your first health system customer sends their security questionnaire.
Other services
- Fractional CTO and technical leadership
A senior technical leader in your company a few days a month: owning architecture, the roadmap, hiring, and the conversations with your board.
- AI and LLM integration
Production AI that earns its place: ambient AI, retrieval-augmented generation, agents, and clinical or enterprise AI with the guardrails your domain requires.
- Software architecture and cloud
Architecture that fits your stage and scales with you: system design reviews, cloud strategy, reliability, security, and cost control.
Plan your next healthcare integration
Bring the integration you're dreading. We'll map what it really involves on the first call.