Case study · Healthcare data platform · 2024–2025

Making a healthcare data platform fail small

Client and patients are withheld; every figure below was measured on the running system.

FHIR patient access — case study cover

Challenge

Build a patient-owned health record whose breach does not become a population breach, whose consent is evidence rather than an assumption, and whose interfaces are accepted by payers and federal agencies. Centralised record stores had already shown the failure mode at national scale: one clearinghouse, roughly 190 million people exposed.

What was built

LayerDecisionMeasured outcome
Data at restAES-256-GCM with a per-patient key derived through HKDF; ciphertext in the database1,047 FHIR resources and 63 patient rows encrypted in place; reads decrypt only for an authorised request
Key custodyShamir secret sharing, five shares, threshold threeAny three shares reconstruct the key; two reveal nothing; shares are not co-located
ConsentGrant, refusal and revocation recorded as eventsRevocation is provable with the file that granted access
InterfacesFHIR R4 patient access with SMART scopesValidated in CMS Blue Button and payer sandbox environments before promotion
OperationsSelf-hosted mail, storage, search, routing and monitoringNo critical function depends on a vendor that cannot be replaced

What changed

What I would do first, in a client environment

Read the contracts and the payer requirements; map the data flows; test what actually protects the record; then produce the decision set — build, buy or retire — in cost order. The first control or interface ships inside the first month.

Press and identity · Resume · Services · charles@trinh.io

Charles Trinh · Fractional Technology Architect / CTO / CIO · Las Vegas, Nevada · remote nationwide