Charles Trinh · Nevada · FHIR R4 integration

FHIR R4 integration — consulting in Nevada

FHIR R4 is the specification most payer and patient-access work now targets, and almost none of the difficulty lives in the specification itself. It lives in what the other end actually returns.

Charles Trinh — T markCharles Trinh · Nevada · trinh.io
FHIR R4 integration — consulting in Nevada — Charles Trinh, Nevada

What this covers

The failures I see are consistent. An Implementation Guide is declared but the resource profiles inside it are not enforced, so a Patient resource arrives with a date of birth as a string in one system and an ISO instant in another. A $everything operation is implemented but paginated with a link that the client cannot follow without a bearer token it does not have. A Bundle contains a search.mode of include that points at a resource the responding server has already deleted. None of these break a demo. All of them break a production interface on the third week.

The work is therefore mostly conformance and evidence. I build against the patient-access and provider-directory requirements, capability statements first, then a mapping sheet that names every field, its cardinality, its terminology binding and the system that owns it. Where the remote FHIR endpoint cannot be trusted, the integration keeps a normalised internal model and reconciles, rather than passing unvalidated resources through to whatever consumes them.

Two things I insist on before any build starts: a sandbox with the exact version of the remote FHIR server that production will speak, and a written list of the resources the patient actually needs. Without the first, the interface is tested against a fiction. Without the second, the project integrates everything and satisfies nobody.

Fhir r4 integration work, as a consulting engagement

fixed-scope work with a written output. Assessment first, then a sequence of changes, with the criteria for each step agreed in advance so the outcome is measurable rather than asserted.

Where it usually goes wrong

The failure I meet most often is an interface that passes conformance and fails clinically: every resource validates, but the patient with two identifiers arrives as two patients, and the clinician sees half a history. Conformance is necessary and not sufficient.

Working in Nevada

Engagements run statewide from Las Vegas: Reno, Sparks, Carson City and the rural counties, where a critical-access hospital often has one IT director covering infrastructure, security and the EHR. Remote delivery is the default; travel is done when the work genuinely needs a room with the people in it. Statewide work usually involves the state Medicaid programme, which changes the interface requirements materially compared with commercial payers.

Scope

Scope is a sequence of work with a measurable acceptance criterion per step. Each step is signed off before the next begins.

What the engagement produces

How the work runs

Charles Trinh works from Las Vegas, Nevada and delivers remotely across the United States. Engagements are scoped in writing, fixed in fee where possible, and measured against the interface or control they were meant to produce. Where the work touches patient data, the data-handling terms are agreed before access is granted.

Questions

Which FHIR version should a new integration target? R4 for anything involving the patient-access and payer rules today; R4B or R5 only when the counterpart server states support in its CapabilityStatement and the consuming application is ready for it.

Do we need a FHIR facade over our existing database? Often yes, and it should be thin. A facade that models the whole clinical record is a second product. One that exposes the resources the counterpart asks for, validated against the IG, is a few weeks of work and can be replaced later.

How do you test without a live counterpart? An IG-derived fixture set plus a replay of real responses captured from the sandbox. The fixture proves conformance; the replay proves the interface survives what the counterpart actually sends.

What does this engagement produce? A written design or assessment tied to a specific interface, control or revenue workflow, with the evidence behind each finding.

How is it delivered? Remotely, with a scope call first and a fixed fee agreed before work begins.

Charles Trinh — T mark

Nevada near me

Working with organisations across Nevada and the surrounding area — on site, remote, or both.

Related services

Related

Charles Trinh · Nevada · charles@trinh.io · 702-559-3489 · trinh.io