{
  "title": "Inpatient behavioral health follow-up evidence for AI",
  "source_page": "https://fiund.com/industries/inpatient-behavioral-followup-state-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A booked follow-up and another encounter's completion are different states",
    "context": "Two original fictional event timelines use inert encounter labels. They contain no stay, diagnosis, treatment narrative, person or clinical follow-up advice.",
    "records": [
      [
        "BF1",
        "Timeline A",
        "Encounter E-A: referral R-A sent, appointment booking B-A acknowledged for day 8. No visit-completion event supplied."
      ],
      [
        "BF2",
        "Timeline B",
        "Encounter E-B: follow-up completion C-B explicitly links to E-B and day 9. Its referral alias resembles R-A but differs."
      ],
      [
        "BF3",
        "Summary draft",
        "Draft says E-A follow-up completed because B-A was acknowledged and C-B appears in the same export."
      ]
    ],
    "question": "Which encounter has supported completion, and what is the most advanced documented state for E-A?",
    "answer": "BF2 explicitly documents completion for E-B. BF1 supports E-A's sent referral and acknowledged booking, without a completed visit. BF3 mixes a scheduling acknowledgment with another encounter's completion, so its E-A conclusion is unsupported. Preserve encounter-specific states and request an E-A-linked completion source before advancing it. The fixture establishes no clinical outcome, quality measure or real care status.",
    "failureModes": [
      "Treating an appointment booking as a completed follow-up.",
      "Joining a completion from another encounter because its referral alias looks similar."
    ],
    "fields": [
      [
        "Encounter and referral IDs",
        "Defines the timeline."
      ],
      [
        "Booking versus completion event",
        "Separates workflow states."
      ],
      [
        "Source link and unresolved evidence",
        "Limits the summary."
      ]
    ],
    "holdout": "Add an E-A cancellation after the booking. Require the timeline to record cancellation rather than infer completion from the original appointment date.",
    "boundary": "Use original abstract records only. Exclude actual stays, narratives and health data; privacy staff assess any separate real-data proposal."
  }
}