append-only · scope · evaluation at disclosure

Charles Trinh — Consent Ledger | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading CONSENT LEDGER — append-only records consulted at every disclosure
Charles Trinh — Consent Ledger

A consent ledger is the record of who agreed to what, when, on what terms, and how that agreement was later changed. In healthcare it is the difference between a consent that exists and a consent that can be proven.

What this is

Consent in healthcare is not a single event. A patient agrees to treatment, to disclosure to a family member, to research use, to data sharing with an app, and to each of those under terms that can change. A ledger records each agreement as an immutable entry with a subject, a scope, a purpose, a timestamp and a provenance, and it records revocation as a new entry rather than as a deletion.

The first design decision is whether the ledger is the source of truth or a mirror of one. If consent lives in the EHR and the ledger mirrors it, the ledger is a reporting convenience and the EHR remains authoritative. If the ledger is authoritative, every system that acts on consent must query it, and the availability of the ledger becomes a clinical dependency. Both are legitimate; choosing by accident is not.

The second decision is granularity. A consent to disclose to a named family member is different from a consent to disclose to any family member, and both are different from a consent to share with a health information exchange. A ledger that stores only a boolean has thrown away the information that makes the consent meaningful, and no amount of downstream logic recovers it.

The third is revocation semantics. Revocation is not deletion. The record that consent existed, and that it was withdrawn on a date, is itself information that may be required. A ledger that deletes on revocation cannot answer the question of what was permitted at the time a disclosure occurred, which is precisely the question that gets asked.

Finally, a ledger is only useful if the systems that act on consent consult it at the moment of action. A consent check performed at onboarding and cached for a year is not a consent check. The integration pattern matters more than the data model, and it is where most consent programmes fail.

Consent also has a temporal dimension that most ledgers ignore. A consent granted for a research study has an end date. A consent granted to a family member may be time-limited. A consent granted under one privacy rule may not satisfy another. Storing an effective-from and an effective-until alongside the decision is what allows the ledger to answer the question of whether consent was in force at a specific moment, which is the only question that matters when a disclosure is challenged.

Interoperability adds a further constraint. Where consent is exchanged between organisations, the ledger has to express the decision in a form the receiving organisation can act on, which usually means a structured scope rather than free text. A consent recorded as a scanned PDF is a consent that cannot be enforced by software, and enforcement by software is the whole point.

The governance question is who may write to the ledger. A ledger that any system can append to is a ledger whose entries cannot be trusted. Write access should be restricted to the systems that are authoritative for each consent type, with the provenance recorded on every entry so the source is always visible.

Reporting is the last piece. An organisation needs to know how many consents are active, how many were revoked in a period, and which disclosures were made under which consent. A ledger that cannot answer those questions is a storage system rather than a governance tool, and the difference is a query layer designed at the start rather than bolted on later.

A final consideration is the relationship between the ledger and the patient. A patient who can see what they have consented to, and withdraw it, is a patient who trusts the system. A ledger that is invisible to its subject is a compliance artefact rather than a service. Exposing the subject view is a small piece of work and it changes the character of the whole programme.

How I do it

I start by enumerating the consent types the organisation actually relies on, with the scope and purpose of each, and the systems that act on them. That enumeration usually reveals that several systems hold their own consent state, and reconciling them is the first piece of work.

From there I design the ledger as an append-only structure with a subject, a scope, a purpose, a decision, a timestamp and a provenance reference. Revocation is a new entry that supersedes an earlier one, and the supersession chain is queryable.

The integration pattern is designed next: which systems query the ledger, at what moment, and what they do when the ledger is unavailable. A fail-closed default is appropriate for disclosure decisions and a fail-open default is appropriate for treatment, and stating that explicitly is part of the design.

Testing covers the awkward cases: a consent revoked between the decision to disclose and the disclosure itself, a consent that applies to one purpose and not another, a subject with two conflicting entries. Those cases are where a ledger earns its keep.

Finally, I leave an audit view that answers the question of what was permitted at a given moment, reconstructed from the entry chain rather than from a current-state table.

Where consent is exchanged with another organisation, I define the structured scope explicitly and test that the receiving system interprets it the same way. Ambiguity in scope is the most common cause of a disclosure that was technically permitted and practically wrong.

Write access is restricted per consent type, with the authoritative system named for each. The ledger records the source of every entry, so an audit can distinguish a consent recorded by the EHR from one recorded by a patient portal.

The reporting layer is designed alongside the schema rather than after it, because the questions the organisation needs to answer determine what has to be stored. Active consents, revocations in period and disclosures by consent are the three queries that drive the design.

The subject view is built alongside the ledger rather than after it, so the patient can see their own entries and withdraw consent through a path that produces a proper revocation entry rather than a support ticket.

Artifacts you keep

  • An enumeration of consent types with scope, purpose and consuming systems
  • An append-only ledger schema with supersession rather than deletion
  • A documented integration pattern naming which systems query at which moment
  • Explicit fail-open and fail-closed defaults per decision type
  • An audit view reconstructing permitted state at any past moment

Proof

  • Consent and revocation handling built alongside patient identity work
  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 104 clearinghouse enrolments across 53 jurisdictions
  • 67 public hostnames, 51 serving, one AWS account
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564

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

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 — consent ledger — 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