Source: https://guthlabs.ai/docs/instruments/blood-type-transfusion-compatibility-reference/

instrument / verified-clean

# Blood Type / Transfusion Compatibility Reference

The current ledger marks this instrument verified clean within the source-bound verification corpus.

Status: **VERIFIED_CLEAN**Lifecycle: **verified-clean**

## Inspectable records

[01**Overview**Purpose and lifecycle](<https://guthlabs.ai/docs/instruments/blood-type-transfusion-compatibility-reference/>)[02**Mechanism**Method and assumptions](<https://guthlabs.ai/docs/instruments/blood-type-transfusion-compatibility-reference/mechanism/>)[03**Implementation**Binding and validation](<https://guthlabs.ai/docs/instruments/blood-type-transfusion-compatibility-reference/implementation/>)[04**Qualification**Evidence and errata](<https://guthlabs.ai/docs/instruments/blood-type-transfusion-compatibility-reference/qualification/>)

## Ledger state

The current ledger marks this instrument verified clean within the source-bound verification corpus.

**Area**: Biology, Medicine & Pharmacology (educational estimates only — every panel labeled not-medical-advice)

**Tranche**: tranche-7

**Evidence ID**: t7-122

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The lookup method is correct for an educational ABO/Rh compatibility reference when the RBC matrix and plasma antibody matrix are explicitly defined. Verdict is NEEDS_REVIEW because the specification does not state how RhD is handled for plasma, whether outputs list full ABO/Rh types or ABO groups, or how invalid and clinically exceptional blood types are handled. The honest-label warning is appropriate and should remain prominent.

### Formula and scope findings

No additional record

### Unit assumptions

- Blood types are interpreted as ABO group plus RhD status: O-, O+, A-, A+, B-, B+, AB-, or AB+.

- RBC compatibility is based on donor red-cell antigens versus recipient anti-A, anti-B, and RhD antibodies.

- Plasma compatibility is based on donor plasma antibodies; the standard convention used here treats RhD as generally irrelevant for plasma because plasma contains negligible red cells.

- The plasma RhD convention must be explicitly documented by the instrument because some institutional charts preferentially match RhD or display simplified ABO-only results.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

An empty recipient-type string produces an undefined lookup-domain input and must be rejected. A second hazard is directional ambiguity: reversing donor and recipient for O- changes the RBC result from 1 compatible donor type to 8 compatible recipient types.

## Errata and corrections

No applied erratum is attached to this unique-name record.

## Inspectable example

4 review vectors are recorded. One source-bound sample is shown below.

````
{
  "inputs": {
    "recipient_blood_type": "O-"
  },
  "expected_outputs": {
    "compatible_RBC_donor_types": [
      "O-"
    ],
    "compatible_plasma_donor_types": [
      "O-",
      "O+"
    ]
  },
  "reference_data": {
    "rbc_row": {
      "recipient": "O-",
      "compatible_donor_types": [
        "O-"
      ],
      "source_convention": "widely tabulated standard value (standard ABO/Rh RBC compatibility chart)"
    },
    "plasma_row": {
      "recipient_ABO": "O",
      "compatible_donor_ABO_groups": [
        "O"
      ],
      "rh_rule": "RhD ignored for plasma compatibility",
      "source_convention": "widely tabulated standard value (standard ABO plasma compatibility chart; RhD generally not relevant for plasma)"
    }
  },
  "working": "1. RBC check: an O recipient has anti-A and anti-B, and an RhD-negative recipient should not receive RhD-positive RBCs. Therefore allowable donor RBCs = O- only. 2. Plasma check: O plasma contains anti-A and anti-B, so it is compatible only with an O recipient. 3. Under the stated plasma convention, either RhD status is acceptable: O plasma donors = O- and O+. Result: RBC = [O-]; plasma = [O-, O+]."
}
````

## Related workflows

No source-defined multi-instrument workflow membership is recorded.

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json · VERIFIED_CLEAN`

- `evidence-tranche7/tranche7-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`