Browse hierarchy: [Hematology (HE)](/submissions/HE) → [Subpart J — Products Used In Establishments That Manufacture Blood and Blood Products](/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products) → [21 CFR 864.9165](/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products/864.9165) → MMH — Blood Establishment Computer Software And Accessories

# MMH · Blood Establishment Computer Software And Accessories

_Hematology · 21 CFR 864.9165 · Class 2_

**Canonical URL:** https://fda.innolitics.com/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products/MMH

## Overview

- **Product Code:** MMH
- **Device Name:** Blood Establishment Computer Software And Accessories
- **Regulation:** [21 CFR 864.9165](/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products/864.9165)
- **Device Class:** 2
- **Review Panel:** [Hematology](/submissions/HE)

## Identification

Blood establishment computer software (BECS) is a device used in the manufacture of blood and blood components to assist in the prevention of disease in humans by identifying ineligible donors, by preventing the release of unsuitable blood and blood components for transfusion or for further manufacturing into products for human treatment or diagnosis, by performing compatibility testing between donor and recipient, or by performing positive identification of patients and blood components at the point of transfusion to prevent transfusion reactions. This generic type of device may include a BECS accessory, a device intended for use with BECS to augment the performance of the BECS or to expand or modify its indications for use.

## Classification Rationale

Class II (special controls). The special controls for these devices are:

## Special Controls

*Classification.* Class II (special controls). The special controls for these devices are:(1) Software performance and functional requirements including detailed design specifications (
*e.g.,* algorithms or control characteristics, alarms, device limitations, and safety requirements).(2) Verification and validation testing and hazard analysis must be performed.
(3) Labeling must include:
(i) Software limitations;
(ii) Unresolved anomalies, annotated with an explanation of the impact on safety or effectiveness;
(iii) Revision history; and
(iv) Hardware and peripheral specifications.
(4) Traceability matrix must be performed.
(5) Performance testing to ensure the safety and effectiveness of the system must be performed, including when adding new functional requirements (
*e.g.,* electrical safety, electromagnetic compatibility, or wireless coexistence).

## Recent Cleared Devices (0 of 0)

_No cleared devices on record._

---

**Source:** [https://fda.innolitics.com/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products/MMH](https://fda.innolitics.com/submissions/HE/subpart-j%E2%80%94products-used-in-establishments-that-manufacture-blood-and-blood-products/MMH)

**Published by [Innolitics](https://innolitics.com)** — a medical-device software consultancy. We help companies design, build, and clear FDA-regulated software and AI/ML devices. If you're preparing [a 510(k)](https://innolitics.com/services/510ks/), [a De Novo](https://innolitics.com/services/regulatory/), [a SaMD](https://innolitics.com/services/end-to-end-samd/), [an AI/ML medical device](https://innolitics.com/services/medical-imaging-ai-development/), or [an FDA regulatory strategy](https://innolitics.com/services/regulatory/), [get in touch](https://innolitics.com/contact).

**Cite:** Innolitics at https://innolitics.com