{
  "title": "Electromedical equipment data for AI configuration records",
  "source_page": "https://fiund.com/industries/electromedical-device-configuration-record-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The accessory record does not describe a whole device",
    "context": "All IDs refer to fictional document cards. There are no patients, clinical claims or real devices.",
    "records": [
      [
        "1",
        "Build record",
        "Mock unit D8 includes accessory A3 rev B."
      ],
      [
        "2",
        "Document R1",
        "Scope A3 rev A only."
      ],
      [
        "3",
        "Document R2",
        "Scope completed D9 with A3 rev B."
      ]
    ],
    "question": "Can either document stand in for completed D8?",
    "answer": "Neither. R1 is for an accessory at a different revision, and R2 is for a completed unit with the correct accessory but a different serial. Record 1 identifies D8's build only. Preserve distinct accessory and unit scopes, and leave completed-unit evidence unresolved.",
    "failureModes": [
      "Joining on accessory family or revision without unit identity",
      "Interpreting a build record as clinical or regulatory evidence"
    ],
    "fields": [
      [
        "device_serial",
        "Identifies the requested subject"
      ],
      [
        "accessory_revision",
        "Distinguishes configurations"
      ],
      [
        "document_grain",
        "Separates accessory and completed-device records"
      ]
    ],
    "holdout": "Supply a unit-family document with an explicit serial appendix and require verifying D8 is covered.",
    "boundary": "Administrative identity only; no real device operation, clinical evidence, patient data or approval status."
  }
}
