{
  "title": "Pharmacy receiving and package tracing data for AI",
  "source_page": "https://fiund.com/industries/pharmacy-package-tracing-exception-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A product-level receipt can still mismatch the individual package identifier",
    "context": "Original inert cartons use invalid product and package aliases. No actual drug, prescription, supplier transaction, person or release action is included.",
    "records": [
      [
        "PTX1",
        "Carton A",
        "Dummy product P1, package DEMO-A1. Receipt R1 explicitly lists P1/A1, exact fixture transaction T1."
      ],
      [
        "PTX2",
        "Carton B",
        "Dummy product P1, package DEMO-B1. Receipt R2 lists P1/DEMO-BI, final letter I instead of digit 1, transaction T2."
      ],
      [
        "PTX3",
        "Review packet",
        "No verified B1/BI equivalence or correction. Shared product class and visual carton design are not package identifiers."
      ]
    ],
    "question": "Which package-to-receipt match is supported, and what exact mismatch requires review for B?",
    "answer": "PTX1 exactly matches A's product P1 and package A1 to R1/T1. PTX2 matches product P1 but conflicts at package level between B1 and BI. PTX3 leaves that character difference unresolved, so route B's receipt association to authorized review rather than normalize it silently or clear the item because the product name matches. The fixture does not make a real release, medication-safety, dispensing or patient decision.",
    "failureModes": [
      "Matching product code while overlooking a distinct package-level identifier.",
      "Silently substituting letter I for digit 1 or treating a match as release authorization."
    ],
    "fields": [
      [
        "Dummy product and package identifiers",
        "Separates identification levels."
      ],
      [
        "Receipt and transaction reference",
        "Supports the link."
      ],
      [
        "Exact discrepancy and reviewed correction",
        "Preserves the exception."
      ]
    ],
    "holdout": "Add a B1 correction to the receipt but keep a conflicting transaction reference. Require package identity and transaction matching to be evaluated separately.",
    "boundary": "Use original inert props and invalid codes. Exclude drugs, prescriptions and actual supply-chain records; authorized staff retain release decisions."
  }
}