propagation · caches · downstream copies

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

A service card reading CONSENT REVOCATION — propagation proven, not assumed
Charles Trinh — Consent Revocation

Revocation is only real when every downstream copy stops being used. A revocation that stops at the database is a policy statement, not a control.

What this is

A patient withdraws consent, and the organisation updates a record. Whether anything changes depends entirely on how many other places that consent was copied to: a cache in the API layer, a denormalised column in an analytics warehouse, an extract sent to a vendor, a report that runs from a snapshot. Each is a place where the old decision keeps being applied.

The propagation problem is a data-lineage problem. To invalidate a decision you have to know where it was used, and most systems do not record that. Building the propagation therefore starts with building the map: every consumer of the consent decision, how it caches it and how quickly it refreshes.

The legal expectation is not deletion of everything ever disclosed; it is that future disclosures stop and that what was disclosed is known. Those are different requirements and they lead to different designs: a stop-list that every consumer checks, plus an audit record of what happened before the revocation.

I design revocation as an event with a fan-out and a verification step: the event is published, every consumer acknowledges, and a report shows which consumers have not. A revocation whose consumers are unknown is a revocation that will be found incomplete in an audit.

Timing expectations should be written down before the first revocation. Patients and regulators expect an effect; the organisation needs a stated window per consumer. A revocation that propagates within one refresh cycle is defensible if the cycle is disclosed, and indefensible if nobody knows what it is.Patients also need to see the effect. A revocation confirmation that says the request was received is not the same as one that says which services have stopped using the data. The confirmation should be generated from the consumer acknowledgements, so it states what is true rather than what was requested.

The report is the artefact regulators ask for, and it is also the one that improves behaviour internally: once each team can see its own propagation time, the slow consumer gets fixed without a policy memo.

Consumers are named in the design, not discovered during the incident: every service that reads consent has an owner, an acknowledgement path and a test that the revocation reaches it. The list is maintained as part of onboarding a new service, so a new consumer cannot appear without a propagation path.

How I do it

Map the consumers first: every service, cache, warehouse and vendor that reads the consent decision, with its refresh interval and its owner.

Then the event and the acknowledgement. Revocation publishes an event; each consumer records that it applied it; the report lists the ones that did not within the SLA.

Finally the tests: revoke and verify that a new disclosure is refused at the API, that a cached decision expires on schedule, and that the audit record still shows what was disclosed before the revocation.

Each revocation is opened as a case with a list of consumers, their acknowledgement times and a close-out when all have applied it. The case record is what makes propagation an auditable process rather than an intention.Revocation is also tested against the awkward case: a disclosure that was already in flight when the revocation landed. The expected behaviour is defined in writing, whether that is completion with an audit note or rejection, and the test asserts it rather than leaving the answer to whichever service wins the race.

Artifacts you keep

  • A consumer map with refresh intervals and owners
  • A revocation event with per-consumer acknowledgement
  • An incomplete-propagation report with an SLA
  • A stop-list every disclosure path checks
  • An audit record separating pre- and post-revocation disclosures

Revocation is a state transition, not a delete

Most systems record revocation by updating a grant row from active to revoked. That single choice destroys the audit trail, because the record of what was permitted before the revocation is overwritten by the record that it was revoked.

There was a state, an event occurred, and there is a new state. Both states are facts and both have to survive, because the question asked later is almost never whether it is revoked now — it is what was permitted in March, and who acted on it before the revocation in June.

The transitions worth modelling are proposed, active, suspended, expired and revoked. Expiry is not revocation and should not be recorded as one. Suspension is not revocation either, because it implies a return. Each transition carries an actor, a reason and a timestamp, and a change without those three is a data correction belonging in a different table with a different trail.

Propagation is the hard part

Revocation has to reach every cache, every derived authorisation decision, and every system that received data under the grant. The last cannot be undone — disclosing data under a valid grant is lawful even if the grant is later withdrawn — but the others must take effect immediately.

The mechanism that works is a grant-version stamp travelling with every authorisation decision. A decision made against version four fails when version five exists. It fails safe, it requires no cache invalidation fanout, and it is cheaper than the alternative in every dimension.

Shorter token lifetimes are not a substitute. A twenty-minute window still means twenty minutes of data flowing after a member withdrew consent, and from their side that is indistinguishable from being ignored.

The case nobody plans for

A member revokes consent while a bulk export is running. The export must terminate, not complete. That requires the export job to re-check the grant version at each batch boundary rather than validating once at kickoff, and it requires the job to be resumable so termination is not the same as failure.

Test it deliberately: start an export, revoke mid-run, and confirm the job stops and reports why. That single test separates an implementation with a revocation column from one with a revocation mechanism.

Log the withholdings, not just the disclosures

When a patient or an examiner asks why a record did not travel, sending nothing is indistinguishable from a bug. You need the elements withheld, the rule applied, the decision-maker and the timestamp. The withholding log is what turns a correct decision into a defensible one.

Report the withholding count monthly by rule and by requester class. A count that never moves is either a perfectly scoped population or a control that is not executing, and the log is the only way to tell which.

Where the model breaks under load

Revocation arrives at the worst possible moment in a batch process. A nightly reconciliation holding a long-lived token will complete against a stale grant unless every step re-checks, and retrofitting that check into a job that has already run for a year is a project rather than a change.

Design the batch boundaries first. Each boundary is a place where the grant version is re-read, which means each boundary is also a place where a revocation can take effect within the batch rather than after it. That is the only design where the answer to how quickly a revocation stops data is a number rather than a hope.

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 revocation — 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