FHIR is easy to demonstrate and hard to conform to. The distance between a working demo and a certified endpoint is mostly profile discipline.
Charles Trinh builds FHIR R4 and US Core conformance from Las Vegas, Nevada: patient access and provider directory APIs, bulk export, SMART App Launch, and the conformance evidence an Inferno run or a customer review expects.

US Core is not a suggestion list. Each profile fixes the mandatory elements, the terminology bindings and the search parameters, and a resource that omits a must-support element is not conformant even if it parses.
The practical approach is to take the profiles the programme actually needs, generate the validation into the build, and treat a failed validation as a failed build rather than a warning.
A patient access API has four moving parts: identity and registration, the authorisation server, the resource endpoints and the audit trail. Each is tested separately and together.
The failure that surprises teams is registration: matching a real person to their record without creating a duplicate or exposing someone else's data. That is an identity problem wearing a FHIR costume.
Bulk export is a job, not a query. It needs an asynchronous pattern, a status endpoint, a signed file and a retention rule that does not leave protected data lying in a bucket.
The provider directory is the other half: practitioner and organisation resources that stay current when a clinician joins or leaves. Stale directory data is the most common complaint from the applications that consume it.
Certification and customer review both ask the same question: show it working on your data, with your profiles, under your authorisation. A test transcript from a reference server is not that.
The deliverable is a run book: the endpoints, the test patients, the expected responses and the failure modes, reproducible by someone who did not build it.
US Core covers the common ground, and the common ground is not every case. A specialty clinic, a device feed or a payer programme may need elements the profile does not carry.
The rule is to extend deliberately: a documented extension, a rationale, and a mapping back to the core profile so a consuming application can degrade gracefully. Extensions that are not documented become the reason a partner integration takes nine months instead of three.
It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.
If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.
Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.
Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.
Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.
Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.
If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.
Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.
The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.
Las Vegas health systems and the vendors that sell into them are held to the same national profiles, but the local testing time zone and the ability to sit with the integration team shorten the loop considerably.
Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.
Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.
The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.
Serving customers in Columbus, Ohio, United States and worldwide.
Teams searching for FHIR R4 help near Las Vegas usually need a conformance pass, not a tutorial. The work is profile-by-profile with the evidence attached.
R4, with US Core profiles, since that is what patient access and most payer programmes require.
Yes, and the result is documented as evidence rather than a screenshot.
Yes, for internal or partner use.
It can be designed and implemented, or reviewed if one already exists.
Four to eight weeks depending on the resource set.
trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489