Interoperability

FHIR patient access is not a portal — what the difference costs

9 November 2026Charles TrinhRemote
FHIR patient access is not a portal — what the difference costs — cover card
Interoperability · FHIR patient access is not a portal — what the difference costs

A portal is a destination, not an exchange

A patient portal shows what the organization already chose to show. A FHIR R4 patient-access integration returns the record the payer or agency actually holds, against a SMART/FHIR scope the patient granted, and it can be read by any client the patient authorizes. The distinction is control, not interface.

What Blue Button and Lighthouse actually give you

CMS Blue Button 2.0 returns Medicare claims through a FHIR API; VA Lighthouse does the same for veterans' records. Both are read APIs behind OAuth. The engineering question is not whether they respond, but whether the response lands in a record the patient owns, with consent recorded before the exchange.

The failure mode nobody logs

Most patient-access projects fail at consent, not at transport. If the authorization is implied by a login rather than recorded as an explicit grant, revocation cannot be honoured later. Recording grant, refusal and revocation as first-class events is what makes the integration defensible when it is audited.

FHIR R4CMS Blue ButtonVA LighthouseConsent
TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh