REGULATORY
Charles Trinh — Healthcare Compliance Programme Design | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A compliance programme that exists only as a binder of policies will fail the first time it is tested. A programme that works is a set of controls someone can prove, owned by named people and measured on a schedule.
Start from what must be proved, not what must be written
Most compliance programmes are built from the outside in: a framework, a template, a set of policies. The result passes an initial review and fails the moment someone asks for evidence of an actual control. I build healthcare compliance programmes from the questions an auditor will ask: what data do you hold, where does it go, who can touch it, and how do you know. Each question is answered by a control, and the control produces evidence on a defined schedule.
The data map is the foundation. It identifies systems, categories of health information, flows to third parties and access paths. The map does not need to be perfect, but it must exist and be maintained. Every control is anchored to one or more elements of the map. The HIPAA Security Rule's administrative, physical and technical safeguards become controls, and each control is mapped to named systems and processes.
The artefact is a control register, one row per control: the obligation it meets, the owner, the evidence, the schedule and the date it was last proven. The register is the programme's structure. Frameworks are useful as classification when they describe the organisation's obligations, but they are not the programme.
Technical controls outlive technical oversight unless they are measured
The technical controls in a healthcare compliance programme concentrate in access management, encryption, logging and boundary protection. Each is a system or a set of systems. The failure pattern is that the controls exist as configuration but drift. A firewall rule opens to accommodate a project, an encryption standard lags a provider update, an access review is skipped in a busy quarter. The control's configuration is still present, but the evidence is missing and the risk has changed.
I build measurement into each technical control. Access review: a scheduled report that lists every account with access to systems holding health information, its owner and last review date. Encryption: an inventory that proves the algorithm and configuration at rest and in transit. Logging: a test that produces a log entry for every event class the control expects. The measurement produces a report with named recipients, and the recipient acknowledges it.
The reports are the evidence. When a control fails, the report's gap identifies the system and the failure is worked to closure. Without the report, the control's state is an opinion, and an opinion does not survive the first internal audit test.
Business associate agreements are a control, not a filing cabinet
A programme with many business associate agreements must manage the lifecycle of each: who signed, for what services, what rights it gives, and when it must be renewed or terminated. Agreements that are archived but never reviewed are a common gap. I build an agreement lifecycle register with fields for counterparty, services, data categories, retention and renewal date, and I attach the controls the agreement requires the counterparty to provide.
The agreement register connects to the onboarding workflow. Before a new vendor can receive health information, the register must contain a signed agreement with the relevant obligations, and the controls the agreement requires must have been evidenced. For existing vendors, the register runs a review cycle and the plan owner attests to continued suitability. Where a vendor is not yet ready to evidence the controls, the agreement's scope is narrowed until it is.
The register is a living document, refreshed at least annually and after any acquisition. In the first year, existing agreements are reviewed systematically. After that, the review is scheduled, and the schedule is published to the vendor relationship owners.
Policies must be actionable, not decorative
A policy that reads well but does not correspond to a workflow is worse than no policy because it creates false assurance. I audit each policy against the actual workflow in the relevant operational team. The question is simple: if a member of staff follows the policy on their next task, will it work and is it the process they use. If the answer is no, the policy or the workflow changes.
Policies about access control, incident response and workforce training are the highest-impact policies because they map to concrete controls. Each policy names the roles, the systems and the events that trigger it. It includes a short, dated change log. It is reviewed with the operational owners, not just the compliance team. The review cycle is annual, with a critical update process for changes to statutory obligations.
The policy set is the artefact, with the review owner named for each. Policies that have not been reviewed within their period are visible in the register and treated as a programme failure, because an out-of-date policy is a claim about the organisation that may no longer be true.
Incident response needs a rehearsed muscle, not a document
An incident response plan is only useful if the people executing it have practised it. The obligations for breach notification, risk analysis prompts, legal review and member communication are complex enough that the first execution is the wrong time to learn them. I run tabletop exercises with real roles and realistic scenarios, including a lost laptop, a compromised vendor, a ransomware event and a misdirected email.
Each exercise produces a timeline and a findings list. The findings are assigned to owners with due dates, and the next exercise repeats a variant of the scenario to verify that the findings were addressed. The exercise records go into the programme's evidence folder. They are the most convincing evidence a programme can produce of readiness, because they show the organisation performing rather than promising.
I integrate the exercise cycle with the access review cycle and the vendor review cycle so that the programme's calendar has a uniform rhythm rather than a set of independent deadlines.
Report to the board in numbers rather than prose
The programme's reporting to the board should be quantitative, specific and tied to the control register. A board that is told the compliance programme is on track has no way to challenge the statement. A board that is shown the controls proven, the controls behind schedule, and the exceptions that are open can question the programme and hold it accountable.
I design a one-page board report with sections for control health, open exceptions, incidents, vendor risk and training. Each section gives a number, a direction and an owner. The board's questions become inputs to the programme, and their answers are recorded in the next report. That exchange makes the programme acknowledge the board's oversight while keeping the technical detail at the working level.
The programme's calendar is a written artefact. Each cycle in the year has its own products: the control register, the access reports, the vendor reviews, the exercises and the board report. The programme's health is visible in the calendar's completion, and the calendar is reviewed and adjusted annually.
What the programme looks like when it is working
A working programme answers a regulator, an auditor or a customer's due-diligence questionnaire with a pointer to a file rather than a promise of a report. The evidence for each control is current, the owners are named and the exceptions are visible with dates. The programme is not invisible; it is quiet in the way that a well-run service is quiet, because the work happens before the question is asked.
I favour programmes that fit the organisation's size. A startup with a single cloud account needs fewer controls than a hospital group, and a programme scaled to the wrong size is either theatre or bureaucracy. The controls are those that the organisation can actually sustain. A control the team cannot run is not a control; it is an aspiration on a page.
That principle shapes everything I hand over: the register, the measurement routines, the vendor review, the exercises and the board report. Each one is sized to the organisation and run by its own people, so the programme survives the consultant leaving and the audit after that.
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 — healthcare compliance programme design — 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.