identity · consent · disclosure

Charles Trinh — Patient Identity and Consent

Charles Trinh — Patient Identity and Consent
Charles Trinh — Patient Identity and Consent

The expensive error

A duplicate record costs a repeat workup. A wrong merge puts one patient's data into another patient's chart with full confidence behind it, and no downstream control repairs it because nothing was breached.

Match rate rewards the cheaper error, so thresholds must be set for the expensive one and the review queue must be funded for the middle band.

Consent as directive

A boolean cannot express share with treating clinicians, withhold from the exchange, exclude substance use records, expire in twelve months, revoke at any time. Since it cannot, organisations default to withholding and the exchange delivers less than the patient expected.

Enforcement belongs in the data path before serialisation, and the withholdings must be logged, because correct withholding and a silent failure look identical from outside.

Segments, not records

Substance use records sit inside the same chart as everything else, so enforcement must be segment-level, evaluated at read time per requester and per purpose.

That requires the data model to carry the designation, the query layer to honour it, and the log to record what was withheld.

What I build

I built identity and consent into a clinical platform I operate: a 337-table store behind a 51-hostname estate, with a Fabric and EVM ledger pair for consent and disclosure.

The first measurement is always the duplicate rate per source system, because aggregate numbers hide the interface that is producing it.

Thresholds and the two errors

A matching engine has two failure modes and they are not symmetric. A missed match produces a duplicate: a repeated workup, a split history, a patient who has to explain themselves again. A false match produces a merge: one patient's data in another patient's chart, confidently, with no alarm. The first is visible and annoying; the second is invisible and clinical. A threshold tuned to maximise the match rate optimises for the visible error, which is why so many estates have good match rates and occasional catastrophic merges.

Set the threshold for the expensive error, fund the review queue for the middle band, and measure duplicate rate per source system rather than in aggregate. The per-source view usually reveals one interface producing most of the duplicates, and that interface is a fixable defect rather than a data quality fact of life.

Consent that a boolean cannot hold

Real consent has a period, a purpose, a category and a revocation. A boolean cannot express any of those, so organisations store the boolean and express the rest in policy, and the gap between the two is where the exchange delivers less than the patient expected. Modelling consent as a directive with those four attributes changes what the system can enforce and what it can explain years later.

Enforcement belongs before serialisation, in the data path, evaluated per requester and per purpose. That placement is what makes the withholding real rather than nominal, and it is also what makes the log meaningful, because the log records the decision rather than the outcome.

Segments and the sensitive categories

Substance use records sit in the same chart as everything else, which means a rule at record level cannot enforce a rule that applies to a category inside the record. Segment-level enforcement, evaluated at read time, is the only placement that works for 42 CFR Part 2 and for the other sensitive categories that will follow it.

That requires the data model to carry the designation, the query layer to honour it, and the log to record what was withheld and why. Each of those is a small change that is expensive to retrofit after the records exist, which is why the designation belongs in the schema from the first row.

Logging that makes either defensible

The discharge of the obligation is not the decision; it is the evidence that the decision was made and that it was consistent. Every withholding should leave a record: the request, the exception or rule applied, the decision-maker, the timestamp and what was withheld. Without it, correct judgement and total failure are indistinguishable from outside, and the organisation asked to explain will find itself reconstructing a decision from memory.

Build the log as a first-class output of the data path rather than an afterthought in the application. The systems that do this can answer a review with a query; the ones that do not answer with a meeting, and the meeting produces a document that an examiner reads as a narrative rather than evidence.

What the platform proves

The consent and disclosure records in the platform I operate run on a Fabric and EVM ledger pair, with no PHI on chain. The design point is that the proof of what happened should outlive the database that recorded it, and a ledger is the mechanism for that when the parties do not share a database. The chain holds digests, types and times; the record holds the substance and the keys.

The interesting part was never the cryptography. It was deciding what belonged on chain, which is a question about what someone would need to prove to someone else years later, and answering it wrongly produces either an unusable ledger or a permanent record of something that should have been deletable. That judgement is the work, and it is transferable to any estate considering the same architecture.

Unmerge and the right to be wrong

Every matching decision will eventually be wrong, and the design that matters is the one that can be reversed. An unmerge path needs the merge history, the field-level provenance and an audit of who approved the original merge, and building it after the fact is an exercise in archaeology. Build it first, because a system that cannot unmerge will eventually merge something it should not and have no remedy.

The same discipline applies to consent. A revocation that propagates in a day is a grant that persists for a day, and the patient who revoked it will not experience the difference until it matters. Test the propagation with a real revocation and record the elapsed time, because a revocation path nobody has exercised is a policy rather than a control.

Identity across organisations

Two organisations can each have an excellent identity layer and still fail to match the same patient, because the demographic fields they hold diverge at the source. The exchange does not fix that; it exposes it. Where identity is being federated, the design needs a stated fallback for a failed match and a way for the patient to correct it, because a member-facing exchange that cannot resolve a person is a support queue rather than a service.

Add the correction path to the design before the exchange goes live. The patients who need it are the ones with the least tolerance for a call centre, and the fix is usually a documented escalation rather than a matching change.

Record the match confidence alongside the merge decision, because a merge made at the edge of the threshold is the one that will be challenged later, and the confidence is the evidence that the decision was considered.

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 identity and consent — 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