Direction 1 · Integrations

Healthcare and enterprise integrations that hold up in production.

HL7, FHIR, Firebase, SharePoint and external public APIs — designed to be reliable, auditable, and easy for your team to maintain after handover.

What I build

Capabilities

Practical integration work across the standards and platforms healthcare organisations and operations teams actually use.

HL7 & FHIR interfaces

v2 messaging, FHIR R4 APIs, interface engines, message validation and remapping — including ADT, ORM, ORU, SIU and custom workflows.

Firebase integrations

Real-time data pipelines, Firestore schemas, Cloud Functions, Auth and secure third-party API bridges from Firebase to your stack.

SharePoint & Microsoft 365

Custom connectors, Power Automate flows, document workflows, Teams integrations and structured data between SharePoint and external systems.

External public APIs

Connecting your product to third-party services — payments, identity, healthcare registries, lab platforms, you name it — with proper auth, retries and observability.

EHR / clinical systems

Working with Epic, Cerner, Athenahealth and others — through both standard interfaces and vendor-specific APIs.

Migration & modernisation

Replacing legacy interfaces, lifting data into modern formats, and decommissioning fragile point-to-point connections.

How it runs

From first conversation to handover

1. Discovery

Map your systems, message types and failure modes. Agree on a concrete scope before any code.

2. Design

Interface specs, data contracts and security boundaries documented up front — so nothing is a surprise later.

3. Build & test

Iterative development against your environments, with realistic test data and validation.

4. Handover

Full documentation, runbooks, and your code — owned by you, supported by me for an agreed window.

Start with discovery