{
  "title": "Pharmacy benefit formulary version records for AI",
  "source_page": "https://fiund.com/industries/pharmacy-benefit-formulary-version-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Plan identity is required before selecting a dated product-list entry",
    "context": "Two imaginary plans list a wholly artificial product named DEMO-P. The task concerns document matching, with no medication, patient, prescription or treatment recommendation.",
    "records": [
      [
        "FV1",
        "Plan A list versions",
        "A-v1 lists DEMO-P in practice category C1. A-v2 changes it to C2, effective day 15; approval record links the change to Plan A only."
      ],
      [
        "FV2",
        "Plan B list",
        "B-v1 keeps DEMO-P in C1 throughout the practice period. No A-to-B equivalence rule supplied."
      ],
      [
        "FV3",
        "Questions",
        "Q1: Plan A, date day 12. Q2: DEMO-P, date day 20, plan identifier missing. No member determination records included."
      ]
    ],
    "question": "Which document supports Q1, and can Q2 be answered from the product name and date alone?",
    "answer": "FV1's A-v1 supports Q1 because day 12 precedes A-v2's day-15 change. Q2 lacks a plan identifier: FV1 and FV2 supply different day-20 categories for the same fictional product. Report the missing plan and route the incomplete question for review instead of selecting the most recent list across all plans. A list-category match does not constitute a member-specific coverage or benefit approval.",
    "failureModes": [
      "Applying a future list revision to an earlier question.",
      "Assuming that identical product names make two plans' lists interchangeable."
    ],
    "fields": [
      [
        "Plan and artificial product ID",
        "Defines the applicable list."
      ],
      [
        "Version and effective interval",
        "Supports date-specific retrieval."
      ],
      [
        "Question completeness and review state",
        "Marks missing scope before responding."
      ]
    ],
    "holdout": "Add Plan B to Q2. Require B-v1/C1 even though A-v2 is a newer document.",
    "boundary": "Use synthetic product codes and original lists. Exclude member, prescription, pricing and contract information; no drug-selection or coverage decision is requested."
  }
}