information blocking · exceptions · record
Charles Trinh — Cures Act and Information Blocking Review, Las Vegas NV

An operational review against the information blocking rules: which exceptions you rely on, whether the conditions are actually met, and what the record shows.
The default inverted
Withholding now requires a documented ground, and comfort is not one of them.
The exceptions are enumerated and each has conditions; treating them as general permission is a misreading that turns a solvable problem into a finding.
The practical test: name the exception, the condition, the decision-maker and the date for any withheld exchange.
The privacy exception, applied properly
Privacy is conditioned on consent scope or a legal permission, not on an organisation's preference.
If the real reason is an unsigned agreement, that is a security or infeasibility argument and should be made as one.
Invoking an exception dishonestly is worse than invoking none, because it converts an operational problem into a credibility problem.
What the record must contain
For every withholding: the request, the exception, the condition, the decision-maker, the timestamp and the content withheld.
A response that says we sent nothing is indistinguishable from a bug, and the difference is the entire defence.
Without that record, correct judgement and total failure look identical from the outside.
Screen-level analytics
Break down by category, purpose and service to see where the withholding actually clusters.
Aggregate numbers hide the outlier that will be asked about.
Review the top five clusters quarterly and confirm each still meets its condition.
Fees and the API exception
Any fee must be reasonably related to cost, documented, and not a condition on access to the underlying content.
The API exception requires specific effort; it is not a blanket exemption for difficult requests.
Publish what you charge and why, because the list is itself a disclosure argument.
Content and manner
You may require a specific format or timetable, but not one that creates a barrier or delays access beyond stated limits.
Document the standard and its rationale, and apply it consistently across requesters.
Inconsistent application is the fastest route to a complaint.
Where organisations get caught
Not by malice, but by a vendor clause nobody read, a workflow nobody owns and an interface nobody built.
Those are fixable in a week once somebody looks, and most organisations have never looked.
The first review is usually uncomfortable and rarely changes anything except the record.
What I do
I audit the actual withholding behaviour against the exceptions, then instrument the decision log.
I do not provide legal advice; where the question is legal I say so and stop.
The output is a list of withholdings with the exception being relied on and whether it holds.
The tests worth running
Take three recent withheld exchanges and try to reconstruct the decision from the record alone.
If you cannot, the exception is being claimed rather than exercised.
Repeat until the reconstruction takes minutes rather than a meeting.
Where to start
Pull the last twenty withholding decisions and check whether an exception was named at the time.
Anything unnamed becomes a question you will have to answer later with less information.
That single exercise usually changes how the team records decisions within a week.
How I do it
- One trace of a real case, timestamps at every hop, before any document is written.
- A findings list naming the defect, the system, the owner and the date — reviewed monthly.
- No attestation I did not test, and no template sold as an assessment.
Detecting blocking you did not intend
Most information blocking is not a decision; it is a workflow that quietly returns nothing at a boundary nobody instrumented.
Instrument the boundaries: count requests, count responses, count empty responses and route the empty ones to a person.
A silent empty response is the shape of both a bug and a refusal, and only the record tells you which one you are looking at.
Training is not a control
A briefing changes what people know; it does not change what the software does when nobody is watching.
The control is the decision recorded at the moment of withholding, with the exception named and the date attached.
Measure how often the record contains an exception name, because that is the difference between a policy and a practice.
The complaint path
A complaint is the cheapest signal an organisation receives and the one most often routed to a queue nobody reads.
Log every complaint with its date, the exchange involved and the disposition, and review the log monthly.
The pattern in that log is the review you would otherwise commission from outside at a multiple of the cost.
The actors and the audience
The rules distinguish actors, and the obligations differ; a developer and a health information network do not carry the same duties.
Write down which actor you are for each surface, because the exception analysis depends on it and the assumption is often wrong.
Review the classification annually, since a new product line can change it without anyone noticing.
Responding to a request you cannot honour today
An honest, dated statement beats a silence, both legally and operationally, because silence is indistinguishable from a refusal.
Log the request, state the obstacle, name the exception if one applies, and give the date the answer will change.
Follow up on the date, because an unkept promise converts a defensible position into a documented failure.
The quarterly review agenda
Four questions: what was withheld, under which exception, who decided, and did the record show it.
Anything that cannot be answered becomes a finding with an owner rather than a discussion item.
The review is short when the record exists and impossible when it does not, which is itself the signal.
The exceptions are narrow by design
Each exception describes a specific circumstance with conditions attached, and the conditions are the part that gets skipped under time pressure.
Write the conditions next to the exception name on a single page and keep it where the decision is taken.
An exception invoked without its conditions is a claim to a permission that does not exist, and the record will show it.
The record is the only defence
When the question is asked, months later, about why a particular exchange returned nothing, the answer lives in the record or it does not exist. Correct judgement exercised and undocumented is indistinguishable from a workflow that failed, and the organisation asked to explain will find itself reconstructing a decision from memory during a review it did not choose. The record needs to be created at the moment of the decision and it needs to name the exception, the condition, the decision-maker and the date, in that order.
The practical way to create it is to make the decision point a step in the interface rather than a note in a document. A person withholding an exchange selects a reason from a list that mirrors the exceptions, and the system writes the entry. That design has two effects: the record exists without anybody remembering, and the distribution of reasons becomes a reviewable number rather than an anecdote, which is how an organisation discovers that one workflow accounts for most of its withholding.
The third consequence is that the review becomes cheap. Instead of sampling exchanges and interviewing the people involved, the team reads the distribution, checks the largest categories against their conditions and asks whether each still holds. That exercise takes an afternoon a quarter, produces a short list of decisions to revisit, and leaves behind the artefact that answers the question when it eventually arrives, which is the point of building it before anyone asks.
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 — cures act and information blocking review, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance 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.