{
  "title": "Medical and dental supply wholesale package identification data for AI",
  "source_page": "https://fiund.com/industries/medtech-wholesale-udi-package-level-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An individual package code does not verify an outer case or its quantity",
    "context": "Original empty cartons use invalid mock device identifiers and abstract packaging levels. No device, patient, regulatory submission, hospital purchase or product release appears.",
    "records": [
      [
        "UDI1",
        "Practice product map",
        "Product P individual package code DEMO-E; outer case code DEMO-C. Original C card lists four individual units per sealed practice case."
      ],
      [
        "UDI2",
        "Carton A",
        "Observed outer tag DEMO-C with matched case card and intact original practice seal. Contents not independently opened or counted."
      ],
      [
        "UDI3",
        "Carton B",
        "Outer box carries DEMO-E code copied from individual package. No B case-level association or quantity record."
      ]
    ],
    "question": "Which code applies at each level, and can B's individual code or A's intact seal establish observed contents?",
    "answer": "UDI1 defines DEMO-E for the individual level and DEMO-C for the outer case. UDI2 matches A to the case card's stated four-unit configuration, but its sealed appearance is not a direct count of contents. UDI3 uses the individual code on an outer box, so B lacks an exact case or quantity source. Preserve label level and stated quantity separately from observed contents; no device release or safety decision is made.",
    "failureModes": [
      "Using an individual-package code as if it were a matched outer-case identifier.",
      "Treating a nominal case quantity and intact seal as directly observed contents or release evidence."
    ],
    "fields": [
      [
        "Invalid device and package-level code",
        "Defines hierarchy."
      ],
      [
        "Case configuration and stated count",
        "Supports expected quantity."
      ],
      [
        "Observed contents versus seal and mismatch",
        "Limits verification."
      ]
    ],
    "holdout": "Add a reviewed B case code for a different device alias. Require packaging level to match while product identity still conflicts.",
    "boundary": "Use original inert labels and props. Exclude real device, hospital and patient information; authorized staff retain release decisions."
  }
}
