Part 2 criminal-justice monitoring recipient

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

The pathway starts with a qualifying condition

42 CFR 2.35 applies when the criminal justice system has made program participation a condition of disposition, parole, or another release. Confirm the order, agreement, or other authoritative record, the matter, the patient, and the monitoring purpose.

Record the jurisdiction, case or matter identifier, condition, source document, treatment requirement, effective period, disposition status, supervising organization, and change events. A treatment recommendation, voluntary referral, lawyer request, employer program, or family arrangement may need a different analysis. Do not select this route simply because a justice-system person appears in the correspondence.

Connect the condition to the specific Part 2 program and patient. Resolve identity, renamed matters, transferred supervision, multiple cases, and conflicting documents before release. Preserve the original source and qualified interpretation.

Need connects the recipient to the disclosure

Document the recipient's identity, agency, role, responsibility for the matter, information needed to monitor progress, secure destination, and current contact. Broad agency membership, curiosity, or a general law-enforcement request does not establish the rule's recipient condition.

Verify assignment through an authoritative roster, order, direct agency confirmation, or other approved source. Record start and end dates, substitute or supervisor roles, communication channel, and last verification. Avoid relying on an email signature, badge title, business card, caller ID, or stale directory entry.

Define the monitoring question before selecting records. Attendance, participation, compliance, progress, test results, discharge, clinical narrative, diagnosis, medications, counseling notes, and incidents may carry different relevance. The official's desire for a complete chart does not establish a case-specific need.

Manage recipient changes

When probation or parole transfers, a judge changes, an assigned prosecutor leaves, supervision ends, or an agency reorganizes, stop scheduled disclosure until the recipient and consent are revalidated. Do not forward records from an old official to a new contact on the assumption that the agency remains the same.

Maintain one active recipient record per supported role and preserve history. Remove shared mailboxes and distribution groups unless qualified review documents why every destination fits the monitoring need and official-duty limit.

Consent and disclosure limits still apply

The patient signs written consent that meets the applicable Part 2 requirements and the specialized duration and revocation terms. Release only the authorized information. Record each disclosure and remind the recipient of the official-duty restriction.

Before each event, confirm patient, qualifying condition, current recipient, monitoring need, consent, duration, revocability state, record scope, purpose, and secure route. Send required accompanying material and preserve the exact release set and delivery evidence. Scheduled reports should fail closed when an assignment or disposition fact is unknown.

Recipient qualification does not authorize use for a new investigation, prosecution, employment decision, publicity, research, or general agency intelligence. Route subpoenas, testimony, changed charges, and requests outside monitoring through the separate current legal process.

Respond to recipient or routing errors

If information reaches a former, unassigned, administrative, or overbroad recipient, contain access where feasible, preserve messages and logs, identify records and downstream copies, and route privacy, security, legal, clinical, and patient communication decisions. Review other reports using the same directory or workflow rule.

Example with recipient review

Twelve proposed recipients are reviewed. Nine have documented responsibility and need for monitoring; three administrative contacts lack a case-specific need. Recipient readiness is 9 of 12 people.

The program removes the three contacts, verifies one responsible official for each matter, and narrows the report scope to the documented monitoring need. It preserves the rejected requests and checks whether any earlier report used the same administrative distribution list.

Monitoring-recipient checklist

• Verify the qualifying condition, matter, program, and patient.
• Confirm current official assignment through an authoritative source.
• Document the monitoring question and information actually needed.
• Match consent, duration, revocability, scope, and secure destination.
• Stop scheduled reports on transfer, completion, or uncertain assignment.
• Keep official-duty use separate from investigation and other purposes.
• Contain wrong-recipient events and review related routing rules.

Owner controls

The 2024 final rule preserves this specialized pathway. Use matter identifiers, source orders, role verification, need statements, recipient confirmation, consent checks, disclosure logs, change triggers, and counsel escalation.

Monitor active recipients, verification age, reports sent, shared destinations, assignment changes, stopped feeds, rejected requests, and errors. Audit from each monitoring disclosure back to current need and consent, then from every active justice referral into recipient and scheduling evidence. Retest after directory, court, supervision, EHR, or interface changes.