SECURITY

Charles Trinh — 42 CFR Part 2 and Substance Use Records | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading 42 CFR PART 2 — written consent, segmented records and a disclosure trail
Charles Trinh — 42 CFR Part 2 and Substance Use Records

42 CFR Part 2 protects substance use disorder records more strictly than the rest of HIPAA medical data. I design consent, segmentation and the disclosure trail so an organisation shares what it may, refuses the rest and keeps its clinical workflows intact.

Why Part 2 is stricter than HIPAA

A record is treated as a Part 2 record, and not simply a HIPAA record, when it relates to the treatment of a substance use disorder and the provider's identity itself would reveal that the person is in such treatment. The 2024 final rule aligned much of the rule with HIPAA's permission scheme but left the core intact: disclosure needs a written consent naming the recipient and the purpose, and that consent must be revocable by the patient at any time.

The stricter rules also block disclosure for payment and operations in many cases. A clinic cannot send the Part 2 record to an insurer to process a claim unless the patient has consented, even though HIPAA would allow it for payment without separate permission. That single distinction breaks workflows designed around HIPAA assumptions and produces the awkward calls that land in a legal or compliance inbox the morning after a claim is denied.

Most Part 2 failures come from not knowing which records are covered. Substance use treatment is embedded in behavioural health, primary care and care coordination notes. Unless the organisation can identify it at capture or shortly after, the stricter rule cannot be applied to the right data later. Identifying the data is the foundation of every other control in this area, and it is the control most often missing in the first assessment.

Consent that names the recipient and the purpose

I design a consent structure with named recipients, a disclosure purpose, an optional expiration and a revocation path. The form must tell the patient what is being disclosed, to whom, for what and for how long. A broad consent is permitted if the patient agrees to one, but the form must still be specific about the categories of information and the recipients, otherwise the consent is unwieldy to enforce and difficult to defend in front of a receiving provider.

The receiving side has to be able to parse the consent. I map the consent structure to the exchange standard in use so a receiving HIE or payer can evaluate it against the disclosure actually requested. Where a broad consent covers a purpose but not the exact records being sent, the workflow must still check that what is being transmitted fits the scope. Consent is the legal instrument; scope evaluation is the technical enforcement, and the two have to agree at the point of transmission.

I test revocation end to end. A revocation that stops the consent record but leaves the data pipeline running has not revoked anything. I simulate revocation during an active disclosure, verify the next message from the integration layer is blocked and check the log records the refusal. That end-to-end test usually surfaces a second system holding a cached permission nobody had mapped, and that cached permission is the failure mode that survives every policy update.

Segmentation, the part vendors underestimate

Part 2 records must remain identifiable so they can be protected when shared. In plain terms, the system has to know what is substance use data, and a free-text note or a diagnosis code buried in a claim is not enough. I start with a data model: structured flags, an encounter-level tag and a note-level classification that follows the record through export, analytics and reporting. Without a clean tag, the downstream controls cannot work and the export cannot be filtered.

The integration layer is harder. An HIE or clearinghouse that receives a full longitudinal record must either exclude segmented data or accept that it is now a Part 2 recipient. That is an interface and contract decision, not a database tweak. I design the interface to either strip the fields or apply the receiving-side obligations, and I document which path the organisation chose so nobody later assumes the other one was taken.

Analytics and population health are the leak points. A reporting table that aggregates by diagnosis can reveal SUD status without carrying the flag. I review every downstream dataset that consumes clinical data, drop the SUD indicator or apply an aggregation policy that prevents re-identification. That review often uncovers the same flag not applied to a partner-facing dashboard that everyone had forgotten shipped raw claims data to a customer-facing tool.

Redisclosure notices and downstream parties

Recipients of Part 2 data are told they may not redisclose it unless they hold another written consent or fall under a specific exception. The rule describes this as a notice of prohibition on redisclosure, and it must accompany the disclosure. I attach the notice to every transmitted message using the standard that carries it, then verify it arrives in the receiving system's log. A notice that sits in a PDF on a shared drive is not an accompanying notice.

Downstream vendors become recipients too. A transcription service, a fax vendor and a claims clearinghouse receiving a claim with an SUD diagnosis each need the prohibition notice and a contractual commitment to honour it. I review BAA language and separate services agreements, and where the vendor's standard contract omits the prohibition I name the gap rather than rely on the vendor's brand. Most contracts I see include a HIPAA BAA but say nothing specific about Part 2.

I also design a refusal path for requests that arrive without valid consent. The answer is not a polite no; it is a documented refusal with the reason, so the requesting party can cure the deficiency and the organisation can prove it did not release data without authority. Every refusal is logged with the date, the requester and the specific deficiency, so a pattern of non-compliant requests from one payer becomes visible to the compliance owner before it becomes a complaint.

A disclosure log an auditor can follow

The rule and good practice require an accounting of disclosures. I build the log at the layer that actually transmits rather than in a spreadsheet someone fills in weekly. Each entry records the patient identifier, the recipient, the purpose, the authorisation on file, the fields released and the timestamp. When an auditor asks for the account of one patient's disclosures, the log answers from its own table rather than from a fuzzy search across fax confirmations and email threads.

The log is queryable by patient, so an accounting request can be answered inside the required window without a recall exercise. I test that query against a sample of known disclosures and confirm the counts agree across the source system, the interface engine and the disclosure log. A mismatch between those three is where investigations usually begin, and reconciling early costs hours rather than the weeks that follow a subpoena.

Retention follows the organisation's HIPAA policy and the rule's own record requirements. I write the retention rule into the system so a database cleanup job does not delete entries the organisation still needs. That happens routinely when logs sit in a table partitioned by a default policy, and the damage is discovered during a request for disclosures from two years earlier, when the log has already been overwritten.

Operating it after the project

I define who may grant consent in the patient's name where the patient lacks capacity. The rule allows a personal representative, a guardian and, in some states, a parent in limited situations. The determination is not always simple, so I write it into a short decision tree and train the people who will actually make the call. That training is the difference between a compliant programme and one that depends on a single knowledgeable employee.

Urgent treatment disclosures without consent have their own procedures. I write down when a provider may release information during a medical emergency, what documentation is required afterwards and who audits the exception. The exception is easy to abuse, and a failure to document an emergency release properly is the fastest way to transform one difficult case into an organisation-wide finding when an examiner pulls a sample of emergency releases and finds three without a note.

The staff training piece is small but specific. Front-desk staff who take a release request, billing staff who see SUD diagnoses on claims and clinicians who write shared notes each need the rule explained in their own language. I provide a one-page decision tool and run it past the people who will use it rather than a committee. Pair this work with HIPAA privacy and security gap and the consent ledger.

Procurement and contract language for SUD data

The contracts governing vendor access to SUD data carry more weight than the ones covering general patient data. I add explicit Part 2 language to the BAA or a separate addendum: the prohibition on redisclosure, a commitment not to use SUD data for secondary purposes without a fresh consent and a notification obligation naming the responsible persons. A standard HIPAA BAA covers none of these points, and most vendors accept the addendum once it is presented in plain language.

The data-location clause deserves particular attention. A vendor that stores SUD data outside the United States needs a reason the organisation can defend, and a vendor whose sub-processors include a third party in an unclear jurisdiction needs that party named in the contract. I treat each subcontractor touching SUD data as a recipient, with the same prohibition notice and the same right to audit that applies to the primary vendor, because the chain is only as strong as its weakest link.

On exit, the contract must require destruction of SUD data and certification that it happened. A vendor that keeps a copy in its disaster-recovery backup after termination is still bound by Part 2, and the organisation's compliance depends on the vendor. I write the exit obligations and follow them up after the relationship ends, which is the moment most organisations stop thinking about the vendor entirely and the obligations quietly persist for years.

The evidence pack a Part 2 examiner asks for

An examiner inspecting a Part 2 programme starts with the consent forms and works backwards from a sample of disclosures. I assemble an evidence pack that answers the standard questions before they are asked: a sample of consents with recipients and purposes, the matching disclosure log entries, the interface configurations that applied the consent and the log of any refusals. That pack is compiled from the operating systems rather than a manual spreadsheet.

The harder questions concern segmentation. An examiner will ask how the organisation knows which records are SUD data, where that classification is stored and how it survives export. I document the data model, the classification rules and a worked example where a record enters the system, receives its flag and is excluded from an export to a partner without consent. That worked example is often the fastest way to show the control is real.

The pack is refreshed with every test cycle and every regulatory change. I keep it in a dated folder structure so the examiner can see what the organisation could prove on a given day, not only what it can prove today. That history is the difference between a programme that is operating and one that was assembled for the inspection, and it is visible from the file names alone when someone opens the folder.

Where the system and the law meet

The output is a control set the organisation can test annually: consent forms, a segmentation map, interface rules, a disclosure log with query capability and a refusal path. Each test is documented with the evidence it produced and the person who ran it. When the test fails, the result is a corrective finding rather than a shrug, and that closes the loop between the rule and the operation in a way an examiner can follow.

I also keep the programme aligned with the federal interoperability rules. The TEFCA framework and its exchange purposes interact with Part 2 through disclosure contexts, and where the organisation participates in a QHIN the consent must work through that flow without weakening the Part 2 restrictions. I review the exchange purpose codes against the consent structure as part of the project and check the QHIN framework against its own documentation.

The final deliverable is not a policy alone but a working system proven against real cases. I run consent, segmentation and log tests with a small set of sample patients before the organisation turns them on for the whole population. That pilot is quick, and it catches the interface and data-model issues that a policy document can never reveal and that a written procedure cannot anticipate in advance.

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 — 42 cfr part 2 and substance use records — 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

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