INDUSTRY FIELD GUIDE
Outpatient behavioral health record request and scope data for AI
A request can name multiple records while a fictional authorization covers only one recipient and one category.
NAICS 621420 · Outpatient Mental Health and Substance Abuse Centers
A request can name multiple records while a fictional authorization covers only one recipient and one category. HHS publishes guidance on the confidentiality of substance use disorder patient records under 42 CFR Part 2. An original example can test whether software identifies evidence gaps and routes them for review. HHS Part 2 final rule fact sheet
Invent a request, two abstract record categories and an authorization limited to one category and recipient. Add a second request with a similar recipient name. Ask which elements match the supplied scope and which need an authorized reviewer. Keep the model in a sandbox without an action to disclose files.
Use independently written forms and no actual identities, encounter details, counseling notes or treatment records. Leave legal and release decisions to qualified staff.
Describe a fictional scope-matching exercise
Original Fiund exercise
An authorization's recipient and category limits must both match a request
A sandbox uses independently written fictional scope cards and abstract record categories. It has no files to disclose and contains no identities, counseling notes, treatment record or legal release action.
| Record | Source | What it records |
|---|---|---|
| OR1 | Practice authorization | Alias A permits category CAT-1 to recipient REC-A during days 1–10. CAT-2 excluded from the stated scope. |
| OR2 | Request Q1 | Day 5, REC-A requests CAT-1 and CAT-2. Same sender alias as OR1. |
| OR3 | Request Q2 | Day 5, similarly spelled REC-AA requests CAT-1. No recipient-equivalence evidence or separate authorization supplied. |
Question for the model
Which request elements match the supplied fictional scope, and which need authorized review before any separate disclosure decision?
Show the reference answer and checks
OR1 and OR2 match Q1's REC-A, day five and CAT-1 fields. Q1's CAT-2 falls outside the card's explicit scope. OR3 names REC-AA, not REC-A, and no equivalence evidence resolves that recipient difference. Return these field-level matches and gaps for qualified review. A match within this invented fixture is not a legal determination of consent validity or authorization to release actual records.
- Extending an authorization from one category to every category in a request.
- Treating similar recipient names as identical or turning a scope check into an automatic release.
Fields to preserve
- Authorization and recipient alias
- Defines the intended destination.
- Category and effective interval
- Limits the stated scope.
- Requested element and review finding
- Makes partial matches visible.
Test another case
Move Q1 to day 12. Require even its earlier field matches to be qualified by the expired exercise interval.
Use original fictional cards without actual records or a disclosure action. Legal validity and release remain with qualified staff; no real data is included.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.