Part 2 discontinued-program ISDEAA exception

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Current rule checkpoint

Live 42 CFR 2.19(a)(3) recognizes an exception when a Part 2 program is transferred, retroceded, or reassumed under the Indian Self-Determination and Education Assistance Act, 25 U.S.C. 5301 et seq., and its implementing 25 CFR part 900. The exception is tied to that specific legal framework and transaction. Section 2.16 security duties and other applicable Part 2 requirements still need to be applied to the handoff.

Match the actual transaction

Current 42 CFR 2.19(a)(3) names transfer, retrocession, and reassumption under ISDEAA. Counsel with relevant tribal and federal experience should identify the parties, authority, agreement, effective date, program, records, successor, and implementing provisions.

Avoid treating every tribal transition alike

Tribal ownership, contracting, compact status, affiliation, funding, or service to tribal members does not by itself prove that this exception applies. Preserve the source-supported legal determination and any conditions for record transfer, retention, access, or disposal.

Build a controlled handoff

Apply § 2.16 safeguards to inventory, custody, encryption, access, vendors, paper, devices, backups, keys, incidents, patient access, active care, complaints, legal holds, final copies, and acceptance by the authorized successor.

Establish the transaction with specialized authority

Identify the Tribe, Tribal organization, Indian Health Service or other federal component, program, contract or compact context, transfer, retrocession or reassumption action, effective date, governing documents, approvals, parties, successor, and record scope. Preserve the operative statutes, regulations, agreements, notices, and legal conclusion.

Use counsel experienced in Part 2, ISDEAA, federal Indian law, and the specific tribal and federal governance involved. Engage authorized tribal leadership and records, privacy, security, clinical, and legal roles according to the applicable decision structure.

Avoid using tribal affiliation as a shortcut

Service to tribal members, tribal ownership, a referral relationship, funding, affiliation, location on tribal land, or a general asset transaction does not by itself prove a section 2.19(a)(3) transfer, retrocession, or reassumption. Classify each affected program and legal entity from the actual transaction documents.

If the exception does not cover a record set, use patient-consented transfer, legally required retention, destruction, de-identification, or another supported path. Record mixed-scope and unresolved items separately.

Build a jointly governed record inventory

Map active and historical patients, paper, electronic systems, portals, messages, email, devices, backups, archives, billing, payer records, research, vendors, subcontractors, legal holds, complaints, incidents, and off-site storage. For each, document owner, custodian, authority, destination, retention, access, key, format, status, and acceptance criteria.

Respect tribal data governance, sovereignty, applicable tribal law and policy, federal requirements, contracts, and patient rights. Resolve record ownership, stewardship, access, return, retention, and secondary use explicitly rather than assuming the technical recipient controls every decision.

Protect care and confidentiality during handoff

Maintain urgent care, medications, appointment continuity, patient access, privacy contacts, safe communications, interpreter and disability access, referrals, billing, complaints, and correction processes. Explain material patient-facing changes accurately without exposing SUD status through broad outreach.

Apply section 2.16 controls to paper transfer, electronic transmission, encryption, keys, accounts, role access, vendors, logging, backup, incident response, and media sanitization. Test destination security and accessibility before the effective date.

Reconcile custody and prove acceptance

Use secure transfer, inventories, counts, checksums, container and media identifiers, chain of custody, authorized signers, exception logs, rejected items, correction, receipt, and formal acceptance. Verify that the successor can read and govern the records and has the equipment, keys, agreements, staff, and procedures needed.

After acceptance, close source access, accounts, integrations, vendors, devices, paper, backups, and residual copies according to the supported legal plan. Preserve evidence and resolve any record outside the exception.

Example

Eight program-transition record sets reach review. Six have ISDEAA authority, covered-program mapping, successor, inventory, custody, access, security, continuity, and receipt; two involve unrelated asset transfers. Exception readiness is 6 of 8 sets.

ISDEAA exception checklist

• identify the covered transfer, retrocession, or reassumption and governing documents;
• involve authorized tribal and federal roles and specialized Part 2 and ISDEAA counsel;
• map each program and record set without relying on ownership or affiliation alone;
• reconcile tribal governance, federal law, contracts, patient rights, and record stewardship;
• protect clinical continuity, privacy, security, access, vendors, keys, and incidents; and
• inventory, transfer, verify, accept, close source copies, and resolve uncovered records.

This is a transaction-specific federal Indian law exception. It should be applied with respect for tribal sovereignty and the actual legal and governance instruments, not as a generic tribal-program label.