INTEGRATION

Charles Trinh — Telehealth Platform Architecture | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Diagram of a telehealth platform with patient and clinician video, an encounter record and a clinical record integration
Charles Trinh — Telehealth Platform Architecture

A telehealth platform is a clinical system with a video window in it. I design the clinical record, the video carrier, the consent and the audit as one system, so the encounter exists in the record whether or not the call connected.

What a telehealth encounter has to be

A telehealth encounter is a clinical encounter that happens to use video. The record of it is a clinical record: who was in the encounter, what was discussed, what was observed, what was decided and what was prescribed. The video is a carrier for the encounter's clinical content; it is not the encounter. The architecture that follows from this is that the clinical record is written whether or not the video call connects, and the video carrier is replaceable without losing the record. Platforms that treat video as the centre lose the record when the call drops.

The second piece is the encounter's evidence model. The platform has to prove the encounter happened, that the participants were who they said, that the encounter was within the customer's scope of practice and that the consent was captured before the encounter began. The evidence is a set of records: the video carrier's session log, the identity verification result for each participant, the consent record and the clinical note. The evidence model is the platform's job; the customer's compliance team reviews it before go-live.

The third piece is the encounter's identity. A patient in a telehealth encounter has a patient identity; the identity is the same identity the customer's EHR holds, and the encounter record is linked to it. The link is through the customer's master patient index (or, in smaller organisations, through the EHR's own patient identifier). The platform does not maintain its own patient identity. The platform's users are authenticated against the customer's identity provider. The platform's patients are linked to the customer's patient identity. Anything else is a second chart.

The video carrier: choices, trade-offs and the escape hatch

The video carrier is the platform's most visible component and the least architecturally interesting, once the carrier is treated as replaceable. I choose a carrier that supports end-to-end encryption, the participants' region, the customer's preferred recording policy and the carrier's own compliance posture. The major carriers differ mainly in the level of encryption control (WebRTC with E2EE vs WebRTC without E2EE), the carrier's recording capability, and the carrier's data-residency options. For most healthcare customers, the right carrier is the one the customer's CISO will approve and the one the customer's clinicians have used.

The carrier's recording capability is where the customer's choice has the biggest clinical consequence. Some states require a clinician's consent to record; others allow either party to record. The carrier's recording is separate from the platform's recording, and the patient may not know the platform is recording when the carrier's interface shows a "Record" button that the patient assumes is the only recording. I configure the platform's recording to be visible to both parties, with a banner and an audible notification, and I record the consent to record separately from the consent to treat.

The carrier's escape hatch is the fallback for connectivity failures. If the video fails, the encounter has to continue via voice or text, and the record has to capture the encounter's mode. The platform supports voice fallback (a phone call the platform places into the encounter) and messaging fallback (a secure message channel the platform maintains for the encounter). The fallback's use is recorded in the encounter and the customer's clinical operations team knows to expect the exception rate. A platform without a fallback is a platform where a bad connection is a cancelled appointment.

Consent and the ordering that compliance cares about

Consent for a telehealth encounter has three parts: consent to treat, consent to the platform's terms and consent to the recording. All three have to be captured before the encounter begins, and the order matters. A patient who has consented to treat but not to the platform's terms has a weaker record; a patient who has consented to record but not to treat has no encounter. I order the consent screens: platform terms, consent to treat, recording consent (if the encounter will be recorded) and the video test.

The consent's storage is in the customer's record, not the platform's. The platform captures the consent and writes it to the customer's EHR as a Consent resource or the customer's equivalent. The platform maintains a copy for its own evidence, but the customer's record is the authority. A platform that keeps the consent in its own database and only links to it from the record is a platform where the customer's data purge and the platform's data purge disagree.

The consent's withdrawal handling is the next piece. The patient can withdraw consent to record, and the withdrawal has to stop the recording from the moment it is captured. The platform's recording is the carrier's recording plus the platform's own metadata; both are stopped by the withdrawal. The withdrawal record is written into the encounter and the customer's record. The carrier receives a stop signal, and the platform's metadata capture is stopped by the same signal. The withdrawal is not an edit of the recording; it is an event that future readers can see.

Clinical record integration and the problem of the interim note

The platform writes the encounter's record to the customer's EHR. The record includes the encounter's start and end times, the participants, the encounter's mode (video, voice, text), the clinical note the clinician writes during or after the encounter and the encounter's evidence references. The write path is the customer's integration path, FHIR Encounter and FHIR DocumentReference or the customer's own message interface. The integration is not a one-way sync; the customer's EHR is the record of truth, and the platform's copy is a cache.

The interim note is the pattern I see most often. The clinician writes most of the note during the encounter and the note is written to the EHR before the encounter ends. The platform writes the partial note to the EHR as a draft the clinician can edit, and the EHR's own note editor is the interface the clinician uses to finish it. The platform's job is to give the clinician the right context and the right note to edit, not to be the clinician's documentation tool. I have seen platforms that tried to be the documentation tool and produced two charts.

The note's versioning is where the integration gets careful. The clinician may edit the note in the EHR after the encounter, and may add a late note. The platform's copy shows the EHR's version, not its own. The platform's role is to give the clinician the context to write the note (the encounter, the participant list, the carrier's session log) and to not become a second note store. The customer's note appending rules (who can add a note to an encounter and when) are the EHR's rules; the platform does not implement its own.

Identity, authentication and the patient's own device

The clinician authenticates against the customer's identity provider with SAML or OIDC, and the platform's session lifetime is set by the customer's policy. The clinician's session does not carry across patients; each encounter is a new authorisation check. The encounter's authorisation includes the customer's tenant and the clinician's role in the encounter. A clinician who has switched roles since their last encounter must re-authorize.

The patient's authentication is the harder side. The patient may be on a phone with an email link, a password, a one-time code, or a verified identity provider. The platform's choice is the customer's choice, and the FDA's practice-of-telemedicine rules and the state's telehealth rules may constrain it. I implement the strongest authentication the customer's workflow will support, and I record the authentication method in the encounter's evidence. An emailed link and a verified login are not the same evidence.

The patient's device is the platform's least controllable part. The platform tests the patient's camera and microphone before the encounter and reports the test result to both participants. The platform also tests the patient's bandwidth and recommends the call's mode (video, audio, text) based on the bandwidth. A patient on a slow connection who is forced into video will drop out; a patient who is offered audio will stay connected. The mode recommendation is part of the encounter's record and part of the clinician's expectation.

Evidence model and what the customer can prove afterwards

After the encounter, the customer can prove: who was present (the carrier's session log and the identity verification result), what the participants saw (the carrier's recording if consented, the platform's metadata), what the clinician documented (the EHR note), what was consented (the consent records), and how the encounter's mode was determined (the connectivity test result). The evidence set is the platform's output and the customer's compliance team reviews it against the state's telehealth documentation requirements.

The evidence's retention is governed by the customer's record retention policy and the state's telehealth rules. The platform's own retention is a copy; the primary record is the EHR. I configure the platform's retention to not exceed the customer's, and I delete the platform's copy when the customer's record is deleted. The customer's record is the source of truth; the platform's copy is a convenience for support and operations.

The evidence model's cost is the storage and the audit trail, and the benefit is the ability to answer a complaint. A patient who complains about a telehealth encounter requires the customer to produce the encounter's record within a short period. The customer's record and the platform's evidence set combine to answer the complaint. The platform without the evidence set cannot answer. See the patient portal architecture for the patient-side experience and the SMART app launch design for the clinician-side authorisation model.

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 — telehealth platform architecture — the scope, the failure modes it prevents and how the work is measured. It sits in the Identity and Consent 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