INTEGRATION
Charles Trinh — Patient Portal Architecture | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A patient portal is the patient's view of the record, and the architecture behind it is the architecture of every consent, every access and every identity in the organisation. I design the portal as a single surface, backed by the customer's record, with no second chart.
The portal is a view, not a chart
A patient portal shows the patient the record the organisation already holds. It is a view, not a second chart and not a new source of clinical truth. A portal that reads the record is always current; a portal that stores its own copy has to be reconciled with the record, and usually is not.
The second consequence is access control. The portal does not invent its own access rules; those rules are the customer's rules, applied to the patient's own record. The portal sits on top of the customer's authorisation layer and inherits its decisions. Building a separate rule set inside the portal is how organisations end up with two answers to the question of who may see a chart, and the weaker answer is the one a patient finds.
The third consequence is audit. The patient's access is an audited event, written to the same trail as any other access. A portal that bypasses the customer's audit trail is a portal that cannot prove the patient's access was the patient's.
Identity binding: the hardest problem in the portal
The hardest problem in a patient portal is not the screen design. It is confirming that the person logging in is the patient whose record will be shown. An email address is not proof, because it can be shared, forwarded or mistyped. Date of birth is not proof, because it sits on every insurance card. The proof is a combination of factors that the customer's identity policy defines and the customer's identity provider enforces.
The usual pattern is account creation followed by verification, where the patient proves something only they would know or hold. The strongest factor is a code sent to a phone number held in the customer's registration record, because it ties the login to a number the front desk already verified. I check the phone record's quality first; a stale number locks the patient out and the support desk, not the patient, decides whether to reset it.
The second pattern is identity proofing through a third-party provider, where the patient's verified identity is matched to the customer's record by the customer's own matching rules. The portal never decides that two identities belong to the same patient; it asserts that the customer's process confirmed it. The match result travels with the session and the audit trail records which method was used, because the two paths carry different evidentiary weight.
The customer's release policy decides what is shown
The release policy is the customer's, not the portal's. The customer chooses which resources the patient may see, when the patient may see them and which resources the patient may change. The portal implements that policy and nothing beyond it. When a patient calls because a result is missing, the honest answer is the policy behind the gap, stated on screen, .
Laboratory results are the contested case. Some customers release them the moment the laboratory verifies, and others hold them until the ordering clinician has spoken with the patient. Both are legitimate. I implement the hold as configuration the customer's operations team can change, with the change approved by the customer's compliance officer.
The write path has the same shape. Patients can correct contact details, preferred language and communication preferences, and they generally cannot change clinical resources. The portal sends writes back through the customer's own interface, where the authorisation layer decides. A portal that updates the customer's database directly has quietly replaced the customer's authorisation model, .
Proxy and guardian access
Access is rarely a single patient. A spouse may need to see a shared household's medication list, a parent may need a minor's record, and a guardian may have legal authority over an adult's care. Each case has rules the customer's legal team defines and the portal enforces. I write those rules into the customer's identity policy and implement them; the portal does not invent proxy rules, because proxy authority is a legal question, not an interface one.
The proxy access record is the artefact that makes proxy access legitimate. The patient grants a named proxy a scope: which resources, for how long, and whether the proxy may update contact details. That grant lives in the customer's record and audit trail. When the patient withdraws it, the withdrawal is enforced at the customer's authorisation layer on the next request, not merely hidden from the portal's menu, so a proxy holding a cached page is refused.
Guardian access for minors turns on state law and the patient's age, and the portal is where the transition is visible. The customer's policy defines the age at which the minor's own account becomes authoritative, and the portal re-labels the guardian's view on that date. The change is audited with its timestamp, so the record shows exactly when guardian access became the child's own access, which is the fact a complaint turns on.
The interfaces that keep the portal honest
The portal is a client of the customer's interfaces, not a privileged insider. It calls the customer's FHIR surface through the customer's API gateway, and its requests appear in the customer's audit trail like any other client's. The SMART on FHIR patient launch is the same authorisation path the customer's other patient-facing applications use, so there is one launch contract to certify and one scope map to maintain.
The most important integration is the customer's Master Patient Index. The portal's patient is the customer's patient, so a merge or a split in the MPI flows through to the portal's view without a separate portal-side identity table. When two records merge, the portal shows the merged chart and the patient does not have to explain which account is theirs. When a record is split after a mis-match, the portal follows the split rather than holding a stale link.
The conformance evidence for the interface is the same test suite the customer runs for patient access. The portal's read and write operations are exercised by that suite, and I quote its result in the portal's release note: ONC (g)(10) 317 of 317 subtests passed on the interface the portal calls. A portal built over an interface that has not passed that suite is a portal whose patient access claim has no evidence behind it.
Operations, support load and ownership
The portal's running cost is the customer's infrastructure, the customer's identity provider and the customer's support load. Support load is the largest variable, and the biggest lever is self-service: what the patient can see, explain and correct without calling.
The portal's uptime matters more than most applications because patients use it outside office hours, and a portal that is down on a Saturday morning is a portal whose outage nobody notices until Monday's call queue. The health check I install probes the patient login path and a sample chart read, not a bare 200 on the home page, because a home page that loads while login is broken is the most common false green I have found.
Ownership is the customer's. The portal's code, configuration and runbook belong to the customer's engineering team, and every change goes through the customer's change control. The portal is a customer-owned front end over the customer's own interfaces, and the design goal is a portal the customer can re-skin, extend or rebuild without me. That is what I hand over, and it is what I test.
Cost, risk and the portal I would ship
The cost of a portal is dominated by identity binding and integration, not by the clinical screens. The screens take weeks; the identity proofing and the conformance testing take months. I quote the two as separate lines so the customer budgets honestly, and I start the identity work first, because a portal without a trustworthy binding is a security incident waiting for its first complaint.
The main risk is the second chart. It appears when the portal caches clinical data for speed, when an identity table grows beside the MPI, and when a write path bypasses the gateway. I test for all three on every release: the cache is a read-through with a short lifetime, the identity table is a reference and not a copy, and every write appears in the gateway's audit. If any test fails, the release does not ship.
The portal I would ship is the one where a patient can log in on a Sunday, see an accurate chart, understand what is held back and change their contact details without calling. It draws from the record through the customer's own interfaces, writes to the customer's own audit trail, and is owned by the customer. See the master patient index work and the telehealth platform architecture for the adjacent designs.
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 — patient portal 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
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
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.