Part 2 court-application fictitious name

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.64(a) requires a noncriminal Part 2 order application to refer to a patient with a fictitious name and bars patient-identifying information unless the patient is the applicant, has provided qualifying written consent, or the court has sealed the proceeding from public scrutiny. Identity protection applies to the application as filed, including information that identifies indirectly.

The pseudonym rule protects the application stage

42 CFR 2.64 requires a fictitious name and states the three identifying-information routes. Apply the protection to captions, facts, exhibits, declarations, proposed orders, metadata, docket descriptions, certificates of service, and attachments.

A pseudonym can still be identifying

Rare facts, clinic names, dates, locations, relationships, case numbers, employer details, or quoted communications may reveal the patient without a name. Counsel should review direct and indirect identifiers and seek sealing or further minimization when necessary.

Consent and sealing need exact evidence

If the patient is not the applicant, verify written consent under Part 2 or a court sealing order before including identifying information. Record the consent scope, expiration, revocation status, sealing terms, permitted viewers, filing method, and later public access.

Choose and control the fictitious identity

Assign a neutral pseudonym unrelated to patient attributes, program identifiers, record numbers, or facts that could reveal identity. Use it consistently across the application, declarations, exhibits, draft order, service materials, internal index, and hearing preparation. Store the linkage separately with restricted access and logging.

Avoid familiar initials, rare demographics, exact addresses, or descriptive labels. A fictitious name cannot protect a filing whose context identifies the patient.

Inspect every identification surface

Review narrative, quotations, dates, geography, providers, facilities, diagnoses, medications, events, case numbers, filenames, headers, footers, screenshots, images, signatures, email chains, comments, tracked changes, document properties, hidden layers, URLs, and docket fields. Consider combinations and publicly available information.

Use a second-person redaction review and inspect the final rendered filing. Do not rely only on a word search for the patient's name.

Verify any exception before using identity

If the patient is the applicant, document that fact and the exact identifying content still necessary. If written consent is relied upon, verify it meets current Part 2 requirements and covers the application, court, information, purpose, and timing. If sealing is relied upon, obtain and preserve the entered sealing order before filing identifying information.

Do not treat a motion to seal, proposed order, confidentiality agreement, or local restricted-access flag as an entered order without counsel confirmation.

Coordinate notice and hearing protection

Protect patient identity when giving required notice to the patient and holder and when filing responses. Arrange chambers or another method that prevents disclosure during argument, evidence review, or hearing unless the patient requests an open hearing through qualifying written consent. Restrict transcripts, exhibits, remote links, and attendance.

The 2024 final rule provides regulatory context, while current section 2.64 controls the procedure.

Respond to identity leakage

If a draft or filing exposes identifying information, stop further distribution, preserve evidence, notify privacy and counsel, seek sealing or removal through the court, replace files where permitted, assess recipients and access, and evaluate Part 2 and other incident duties. Do not overwrite the event without a record.

Audit applications, pseudonym maps, redactions, consents, sealing orders, docket access, hearing materials, transcripts, vendors, and corrections. Test filing systems with representative documents.

Example with filing packets

Twelve application packets are checked. Ten use a protected pseudonym and remove indirect identifiers; two reveal identity through unsealed exhibits. Filing readiness is 10 of 12 packets.

Owner controls

The 2024 final rule provides current context. Use pseudonym templates, metadata scrubbing, exhibit review, sealed-filing procedures, consent checks, restricted service, docket monitoring, and correction response.

Fictitious-name checklist

• assign a neutral pseudonym and protect the linkage separately;
• inspect text, exhibits, metadata, filenames, images, quotations, and context;
• verify patient-applicant, qualifying-consent, or entered-sealing-order exceptions;
• protect notice, responses, hearings, transcripts, remote links, and service;
• review the final rendered and filed versions through a second person; and
• contain, correct, and audit any identity leakage across court and vendor systems.

A pseudonym is one identity-control layer. The whole filing and proceeding must avoid revealing the patient through other facts.

Keep the pseudonym key outside the ordinary matter file, restrict its access, and record each authorized lookup. Destroy or retain that linkage under counsel-approved requirements after the proceeding closes.