{
  "title": "Outpatient behavioral health record request and scope data for AI",
  "source_page": "https://fiund.com/industries/outpatient-behavioral-program-release-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An authorization's recipient and category limits must both match a request",
    "context": "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.",
    "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": "Which request elements match the supplied fictional scope, and which need authorized review before any separate disclosure decision?",
    "answer": "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.",
    "failureModes": [
      "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": [
      [
        "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."
      ]
    ],
    "holdout": "Move Q1 to day 12. Require even its earlier field matches to be qualified by the expired exercise interval.",
    "boundary": "Use original fictional cards without actual records or a disclosure action. Legal validity and release remain with qualified staff; no real data is included."
  }
}