Part 2 criminal-justice-referral consent

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

The referral and recipient must fit

42 CFR 2.35 covers specified criminal-justice referrals and monitoring recipients, such as a court or responsible probation or parole official. Verify the actual condition, official role, need, records, purpose, and consent before disclosure.

Collect the order, agreement, referral, disposition, supervision condition, or other authoritative record showing that treatment participation is tied to the criminal-justice action. Record the matter, jurisdiction, patient, program, monitoring requirement, official, agency, duty, contact, effective dates, and source. A referral from a lawyer, family member, employer, or general social-service program does not automatically fit this pathway.

Limit recipients to people within the criminal justice system who need the information for monitoring the patient's progress under the conditional release or other covered action. Verify current role and assignment immediately before disclosure. A broad agency mailbox, administrative roster, unrelated investigator, or former officer should not inherit access from the name of the agency.

Duration and revocability are specialized

The consent states a reasonable effective period considering treatment, the proceeding, final disposition, and other pertinent factors. Revocability begins by a specified time or ascertainable event no later than final disposition. These terms differ from the ordinary revocation element in 42 CFR 2.31.

Define the dates and events in language the patient and monitoring official can understand. Examples might refer to completion of the treatment condition, a named review event, end of supervision, or final disposition when supported by qualified analysis. Connect each event to an authoritative source and an owner who updates consent state when it occurs.

Do not set an indefinite period merely because the disposition date is unknown. Review extended treatment, continuances, transfer, early termination, revocation of release, completion, and a changed supervising official. Preserve the original period and every supported extension or replacement consent.

Keep disclosure tied to official duty

Map each report element to the monitoring duty and consent. Attendance, participation, progress, test results, clinical narrative, diagnosis, medications, counseling notes, incidents, discharge information, and other records may have different relevance and sensitivity. Send only the supported information to the verified recipient through the approved route.

Recipients may use and redisclose the information only to carry out official duties connected with the conditional release or other covered action. Communicate this limit through current required materials and recipient instructions. A monitoring disclosure does not authorize unrelated prosecution, employment, publicity, research, or general agency sharing.

Build an event-level release gate

Before every report, confirm referral status, patient, consent, recipient role, monitoring need, record scope, purpose, effective period, revocability state, proceeding status, and secure destination. Preserve the exact sent set, time, sender, recipient, authority, and delivery evidence. Scheduled reports should stop automatically when the triggering period ends or a required fact becomes unknown.

Use qualified privacy and legal review for conflicting orders, ambiguous final disposition, changed jurisdiction, new charges, requested testimony, counseling notes, or a recipient seeking information beyond monitoring. Keep a preservation hold separate from disclosure authority.

Handle transfer, completion, and error

When supervision moves, verify the new official and whether current consent supports the destination. At completion or final disposition, update revocability and scheduled-release controls promptly. Notify operational owners without exposing Part 2 status through broad task names or messages.

If information reached an unsupported recipient or exceeded official-duty scope, contain access where feasible, preserve evidence, identify downstream copies, and route privacy, security, legal, clinical, and patient communication decisions. Review other reports using the same recipient mapping.

Example with monitoring recipients

Ten proposed recipients are reviewed. Eight have a documented monitoring duty; two administrative recipients lack a need tied to conditional release. Recipient fit is 8 of 10 officials.

The program removes both administrative recipients, confirms the assigned monitoring officials, and narrows the distribution list. It reviews prior reports for the same routing rule and records one approved recipient for each case rather than treating an agency-wide mailbox as sufficient.

Justice-referral checklist

• Preserve the qualifying criminal-justice condition and authoritative source.
• Verify recipient role, assignment, need, and secure destination.
• Define a reasonable period and ascertainable revocability event.
• Limit every report to consent, monitoring need, and official duty.
• Recheck proceeding status, recipient, and consent before each release.
• Stop scheduled exchange on transfer, completion, or uncertain facts.
• Contain wrong-recipient or overbroad disclosure and review related events.

Owner controls

The 2024 final rule preserves this specialized pathway. Use matter and referral evidence, recipient-role checks, tailored duration, revocation event, official-duty limits, disclosure logs, change triggers, and counsel review.

Monitor active referrals, recipient verification, report frequency, consent periods, revocability events, transfers, final dispositions, stopped feeds, overbroad requests, and corrections. Audit from each report back to one qualifying condition and verified duty, then from active cases into current consent and scheduling state.