INTEGRATION

Charles Trinh — EHR Vendor Selection | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Diagram of an EHR selection process with requirements, demos, contract review and evidence scoring
Charles Trinh — EHR Vendor Selection

An EHR vendor selection decides the next ten years of an organisation's integration work. I run the process as a series of structured evaluations, with the vendor's interfaces and contracts proven in writing before the signing, not after.

Selection is an integration decision, not a shopping decision

An EHR selection is usually run as a feature-comparison exercise and signed as a procurement event. The decision that lasts ten years is not the feature list; it is the integration burden the vendor leaves behind. The vendor's APIs, its interface engine, its upgrade cadence, its data exit terms and its support model determine the organisation's costs for the life of the contract. I run the selection as an integration evaluation, with the vendor's interfaces proven in writing and the customer's integration team's view weighted as heavily as the customer's clinical team's.

The decision's scope is also the organisation's data: a new EHR creates a migration, a set of interfaces, a portal and a set of analytics. The vendor selection is the moment to decide whether those will be the vendor's built-in capabilities or the organisation's own integrations. Vendors differ widely. Some vendors bundle a portal, an interface engine and an analytics platform; others expose APIs and expect the customer to build. The bundle's cost is the customer's dependency on the vendor for each of those functions. The API's cost is the customer's engineering burden. Both are legitimate; the customer should choose deliberately.

The third scope is the exit. Every EHR contract has an exit clause and a vendor's exit terms are the organisation's future negotiation position. The exit terms cover the data format the vendor exports, the time the vendor allows for the export, the support the vendor provides after termination and the fees the vendor charges for those services. I read the exit terms in the selection, not after the customer has committed. A vendor "with a good exit" in marketing's description may have an exit whose data format is proprietary and whose fees are unstated.

Requirements: from the clinical workflow and the integration estate

The requirements come from two sources: the clinical workflow the organisation actually runs and the integration estate the organisation already has. The clinical workflow is gathered through observation (the same observation I use for clinical automation) and through the customer's clinical leads. The integration estate is gathered from the customer's existing interfaces, APIs and data flows. The requirements are a merged list, weighted by the customer's leadership, and the vendor's capabilities are scored against it.

The integration requirements I write are specific and testable. "Must support FHIR R4 patient access" is too broad. "Must expose a FHIR R4 patient access API that passes the (g)(10) test suite without customisation" is a requirement the vendor can answer, and the vendor's answer is evidence. "Must support HL7v2 interfaces with the customer's existing code sets" is another requirement. "Must accept and deliver HL7v2 ADT and ORU messages through the vendor's interface engine" is a requirement that the customer's integration team can test.

The requirements' weighting is the customer's decision, but I recommend a few explicit weights. The integration experience's weight should reflect the customer's integration team's capacity. The clinical workflow's weight should reflect the customer's clinical leads' ranking. The migration's weight should reflect the customer's data volume and the vendor's migration track record. The cost's weight should reflect the customer's total cost of ownership over the contract, not the initial subscription price. A vendor with a lower subscription and a higher integration burden can be more expensive over ten years.

Scripted demos: the vendor's demonstration on the customer's scripts

The vendor's demo is the vendor's marketing, and an unscripted demo is the vendor's strongest material. The scripted demo is the customer's test of the vendor's capabilities with the customer's scenarios. I write a demo script for the top three or four vendors, with five or six scenarios drawn from the customer's observed workflows. Each scenario has a starting state, a sequence of actions the customer's clinician will ask the vendor's demo user to perform and an expected result. The vendor's demo user is not the vendor's salesperson; it is the vendor's product specialist who can show the system, even when the scenario does not match the system's default.

The demo's value is the vendor's response to a scenario the system does not do well. A vendor whose system does not support the scenario but offers a workaround is a vendor the customer can understand. A vendor whose system does the scenario by adding a feature request is a vendor the customer will find out about during implementation. I record the vendor's response to each scenario and score it against the customer's requirements. The customer's clinical leads attend the demo and their scoring is the most important input.

The demo's second value is the vendor's attitude to the customer's integration estate. I ask the vendor's integration specialist to show, in the demo, how a specific message (for example, an ADT A01 registration) would be delivered to the customer's existing system. The vendor's specialist who has a prepared integration demo is a vendor whose integration is real. The vendor's specialist who says "we will plan that during implementation" is a vendor the customer should price for a longer integration. The customer's integration staff see the difference immediately.

Contract review: the interface, the upgrade and the exit in writing

The contract review is the second most important step after the demos. The contract contains the vendor's interface commitments, the vendor's upgrade commitments and the vendor's exit terms. The interface commitments are the vendor's responsibility to expose the APIs and messages the customer needs. The upgrade commitments are the vendor's responsibility to provide advance notice of changes and regression testing for the customer's interfaces. The exit terms are the vendor's responsibility to provide the customer's data in a usable format.

The contract's interface section is often vague. The vendor's contract may say the vendor "will provide standard interfaces" without specifying the interfaces. I add an interface schedule to the contract: the specific interfaces, their versions, their conformance statements and the vendor's commitment to maintain them through the contract. The schedule is a negotiated document, and the vendor's willingness to sign it is itself evidence of the vendor's interface quality. Vendors whose interfaces are real sign the schedule; vendors whose interfaces are aspirational delay it.

The upgrade clauses are the second negotiation. The vendor's upgrade cadence is part of the customer's cost. A vendor that upgrades quarterly needs a quarterly interface regression; a vendor that upgrades annually needs an annual regression. The contract should specify the upgrade notice period and the vendor's commitment to test the customer's interfaces against the new version before the upgrade is applied to the customer's environment. The vendor that commits to the interface regression in the contract is a vendor with a real non-production environment; the vendor that commits to notice only is a vendor who will tell the customer about an interface break.

Evidence scoring and the decision the customer can defend

The evidence scoring is the decision's foundation. Each vendor's evidence is scored against the customer's requirements, with the evidence quoted and referenced. The evidence includes the vendor's response to the requirements, the demo's scoring, the contract's interface schedule and the customer's own test of the vendor's interfaces in the vendor's non-production environment. The last piece is the strongest: if the vendor will let the customer test the interface in the vendor's non-production environment, the customer can compare the vendor's claims against the real behaviour.

I recommend a fixed scoring model with explicit weights and no discretionary points. The customer's leadership assigns the weights before the demos; the scoring is done by the evaluation committee with the weights visible to every member. The vendor's own claims are quoted with their source. The customer's leadership receives the scores and the references and makes the decision. The scoring model is the decision's defence: the customer can show the vendor's evidence, the weights and the scoring and answer the question of why vendor A was chosen over vendor B.

The second piece of evidence is the reference customers. The reference customers should be similar in size and integration estate to the customer. The reference customers should be contacted independently, not through the vendor's reference programme. The vendor's reference programme provides the vendor's best case; the independent reference provides the real case. I ask the independent references the questions that matter: how long the implementation took, how many of the promised interfaces were delivered in the first year and how the vendor responded to the first upgrade's interface break. The answers are more valuable than any scoring model.

The implementation plan and what the contract's schedule must contain

The contract's schedule includes the implementation plan, not just the interface schedule. The implementation plan is the customer's and the vendor's joint commitment, with defined milestones, defined responsibilities and defined acceptance. The acceptance criteria for each milestone are testable: the interface is live in the vendor's non-production environment, the message is delivered to the customer's existing system and the customer's integration team signs the result. The acceptance criteria prevent the "implementation complete" milestone that the customer only discovers is incomplete at go-live.

The implementation plan's budget is part of the selection. The vendor's professional services quote is the vendor's estimate of the implementation's cost. The customer's own integration effort is separate and often the larger number. I estimate the customer's effort against the requirements (the interface count and the message count) and the vendor's quote. The customer's total implementation cost is the sum; the vendor's quote is not the customer's budget. The vendor's quote with a smaller professional services number and a larger integration number is a quote the customer should compare carefully.

The selection I would hand over has a requirements list, a demo script, a scoring model with evidence, a contract with an interface schedule and an implementation plan with testable milestones. The customer's leadership signs the decision with the evidence; the customer's integration team signs the interface schedule with the vendor's non-production environment. See the fractional architect service for the selection's integration advice, the EHR data migration work for the migration the selection creates and the ONC (g)(10) readiness work for the patient access requirement the vendor must meet.

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes charles trinh — ehr vendor selection — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io

Talk to Charles

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.

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