{
  "title": "Multispecialty outpatient clinic task ownership data for AI",
  "source_page": "https://fiund.com/industries/multispecialty-clinic-visit-ownership-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An episode reference can contain several visits with different task owners",
    "context": "A fictional clinic-coordination fixture uses role labels and administrative tasks. No clinician schedule, patient chart, internal policy or clinical referral is included.",
    "records": [
      [
        "MV1",
        "Episode map",
        "Episode E contains visit V1 for Team A and visit V2 for Team B. Task T1 belongs to V1; T2 to V2."
      ],
      [
        "MV2",
        "Acknowledgments",
        "Team A acknowledges T1/V1. Team B acknowledges T2/V2. Handoff T3 under E has owner field unassigned."
      ],
      [
        "MV3",
        "Duplicate episode row",
        "Another row repeats E but names distinct visit V3 and Team C. No T3 assignment or relationship to V1/V2 supplied."
      ]
    ],
    "question": "Which teams have acknowledged T1 and T2, and can T3's owner be inferred from the episode or duplicate row?",
    "answer": "MV1 and MV2 support Team A's acknowledgment of T1/V1 and Team B's of T2/V2. T3 remains unassigned in MV2. MV3's repeated episode reference and distinct V3 do not assign T3 to Team C or transfer either earlier team's acknowledgment. Preserve episode, visit and task as separate keys and request explicit ownership confirmation rather than assume every action under one episode belongs to the same team.",
    "failureModes": [
      "Joining task ownership at episode level while ignoring visit and task IDs.",
      "Inferring an unassigned handoff owner from a nearby duplicate row."
    ],
    "fields": [
      [
        "Episode, visit and task",
        "Defines nested identity."
      ],
      [
        "Team acknowledgment and target",
        "Supports the assigned action."
      ],
      [
        "Unassigned state and duplicate-row scope",
        "Preserves ownership gaps."
      ]
    ],
    "holdout": "Add a proposed T3 assignment to Team A without acknowledgment. Require proposed ownership to be distinct from accepted responsibility.",
    "boundary": "Use original dummy roles and records. Exclude charts, schedules and patient identifiers; treatment and referral decisions remain outside the task."
  }
}