K133532 · Carefusion 303, Inc. · FRN · Aug 21, 2014 · General Hospital
Device Facts
Record ID
K133532
Device Name
ALARIS SYSTEM WITH GUARDRAILS SUITE MX
Applicant
Carefusion 303, Inc.
Product Code
FRN · General Hospital
Decision Date
Aug 21, 2014
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 880.5725
Device Class
Class 2
Attributes
Therapeutic, Pediatric
Indications for Use
The Alaris System with Guardrails Suite MX is intended for use in professional healthcare facilities that utilize infusion devices for the delivery of fluids, medications, blood and blood products. The Alaris System with Guardrails Suite MX is intended to provide trained healthcare caregivers a way to automate the programming of infusion parameters, thereby decreasing the amount of manual steps necessary to enter infusion data. All data entry and validation of infusion parameters is performed by the trained healthcare professional according to a physician's order. The Alaris System with Guardrails Suite MX is an interoperable of communicating and exchanging data accurately, effectively, securely, and consistently with different information technology systems, sooftware applications, and networks, in various settings; and exchanging data such that the clinical or operational purpose and meaning of the data are preserved and unaltered.
Device Story
Modular infusion pump and vital signs monitoring system; consists of PC Unit and up to four detachable infusion/monitoring modules (plus optional Auto-ID module). Used by healthcare professionals in clinical facilities. Automates infusion parameter programming to reduce manual entry errors; provides 'safety net' via Guardrails Suite MX software. Compares programmed settings against facility-defined drug administration guidelines (Data Set) to intercept potential errors. Integrates into hospital networks for bi-directional communication with external systems (PCs, PDAs, HMS) regarding infusion parameters, clinical history, alarms, and status. PC Unit provides common user interface, power, and communication interface for modules. Benefits patient by reducing medication administration errors.
Clinical Evidence
No clinical data. Bench testing only. Software verification and validation performed to ensure v10.5 enhancements meet design inputs and safety requirements, including closed secondary clamp detection, input/output functions, and user interface modifications.
Technological Characteristics
Modular infusion pump system; PC Unit core with detachable modules. Connectivity: Networked (bi-directional communication with hospital IT systems). Software: Guardrails Suite MX safety management software (v10.5). Features: Closed secondary clamp detection. Energy source: Electrical (PC Unit power supply).
Indications for Use
Indicated for adult, pediatric, and neonatal patients in professional healthcare facilities requiring delivery of fluids, medications, blood, and blood products via IV, IA, subcutaneous, epidural, enteral, or irrigation routes. No known contraindications.
Regulatory Classification
Identification
An infusion pump is a device used in a health care facility to pump fluids into a patient in a controlled manner. The device may use a piston pump, a roller pump, or a peristaltic pump and may be powered electrically or mechanically. The device may also operate using a constant force to propel the fluid through a narrow tube which determines the flow rate. The device may include means to detect a fault condition, such as air in, or blockage of, the infusion line and to activate an alarm.
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health and Human Services. The logo features a stylized image of an eagle with three human profiles incorporated into its design. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" is arranged in a circular pattern around the eagle.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
August 21, 2014
CareFusion 303,Inc. Christine Caton Advisor, Regulatory Management 10020 Pacific Mesa Blvd. SAN DIEGO, CA 92121
Re: K133532
Trade/Device Name: Alaris System with Guardrails Suite MX Regulation Number: 21 CFR 880.5725 Regulation Name: Infusion Pump Regulatory Class: II Product Code: FRN, PHC Dated: July 22, 2014 Received: July 23, 2014
#### Dear Ms. Caton
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{1}------------------------------------------------
Page 2 - Ms. Caton
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default.htm. Also, please note the regulation entitled. "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely vours.
# Mary S. Runner -S
Erin I. Keith, M.S. Acting Director Division of Anesthesiology, General Hospital, Respiratory, Infection Control, and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K133532
Device Name Alaris System with Guardrails Suite MX
#### Indications for Use (Describe)
The Alaris System with Guardrails Suite MX is intended for use in professional healthcare facilities that utilize infusion devices for the delivery of fluids, medications, blood and blood products.
The Alaris System with Guardrails Suite MX is intended to provide trained healthcare caregivers a way to automate the programming of infusion parameters, thereby decreasing the amount of manual steps necessary to enter infusion data. All data entry and validation of infusion parameters is performed by the trained healthcare professional according to a physician's order.
The Alaris System with Guardrails Suite MX is an interoperable of communicating and exchanging data accurately, effectively, securely, and consistently with different information technology systems, sooftware applications, and networks, in various settings; and exchanging data such that the clinical or operational purpose and meaning of the data are preserved and unaltered.
Type of Use (Select one or both, as applicable)
2 Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
## PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON A SEPARATE PAGE IF NEEDED.
#### FOR FDA USE ONLY
Concurrence of Center for Devices and Radiological Health (CDRH) (Signature)
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
Image /page/3/Picture/0 description: The image contains the logo for CareFusion. The logo consists of an orange circle with a white shield-like shape inside, and the text "CareFusion" in gray, sans-serif font to the right of the circle. The shield shape within the circle has a small orange arrow pointing to the upper right.
#### Section 4.6: 510(k) Summary
Alaris System with Guardrails Suite MX
510(k) Number K133532
#### 510(k) Owner's Name:
CareFusion 303, Inc. 10020 Pacific Mesa Blvd. San Diego, CA 92121 USA Establishment Registration Number: 2016493 Owner/Operator Number: 9068764
#### Contact Person:
Christine Caton Advisor, Regulatory Management Phone: 858-617-2990 Fax: 858-617-5982
Date Summary was Prepared: 14 July 2014
#### Device Trade / Proprietary Name:
Alaris System with Guardrails Suite MX
### Device Common / Classification Name:
Pump, Infusion
| Device Class | Classification Panel | Regulation Number | FDA Product Code |
|--------------|----------------------|-------------------|------------------|
| 2 | General Hospital | 21 CFR 880.5725 | 80F--RN |
| 2 | General Hospital | 21 CFR 880.5725 | 80P--HC |
#### Identification of the Legally Marketed Device to which the Submitter Claims Equivalence:
The proposed component device v10.5 software is similar to other devices of comparable type in commercial distribution as described in the most recently cleared 510(k)s, as listed below, and have the same intended use. Any differences in the technological characteristics do not raise different questions of safety and effectiveness.
| Component Name | Model<br>Number | FDA Product<br>Code, Regulation | 510(k) Number | |
|---------------------------------------------------|-----------------|---------------------------------|---------------|---------|
| <b>Alaris System Components</b> | | | | |
| Point-of-Care (PC) Unit Module | 8015 | 80F--RN | K051641* | K091308 |
| Large Volume Pump (LVP) Module | 8100 | 21 CFR 880.5725 | K950419* | K012383 |
| Syringe Pump (SYR) Module | 8110 | | K023264 | N/A |
| <b>Guardrails Suite MX Components</b> | | | | |
| Alaris Guardrails Editor (GRE)<br>safety software | 8961 | 80F--RN<br>21 CFR 880.5725 | K072105* | K030459 |
*Primary
{4}------------------------------------------------
#### Description of the Device that is the Subject of the Premarket Notification Submission:
#### ● Indications for Use
The Alaris System with Guardrails Suite MX is intended for use in professional healthcare facilities that utilize infusion devices for the delivery of fluids, medications, blood and blood products.
The Alaris System with Guardrails Suite MX is intended to provide trained healthcare caregivers a way to automate the programming of infusion parameters, thereby decreasing the amount of manual steps necessary to enter infusion data. All data entry and validation of infusion parameters is performed by the trained healthcare professional according to a physician's order.
The Alaris System with Guardrails Suite MX is an interoperable of communicating and exchanging data accurately, effectively, securely, and consistently with different information technology systems, software applications, and networks, in various settings; and exchanging data such that the clinical or operational purpose and meaning of the data are preserved and unaltered.
- O Intended Use
The Alaris System with Guardrails Suite MX is a modular infusion pump and vital signs monitoring system intended for adult, pediatric and neonatal care that includes safety management software to help reduce medication errors. The Alaris System consists of the PC Unit and up to four detachable infusion and/or monitoring modules (channels). The Auto-ID Module can be included as a fifth module.
The Alaris System with Guardrails Suite MX is intended for use by Healthcare Professionals in facilities that utilize infusion pumps for the delivery of fluids, medications, blood and blood products using continuous or intermittent delivery through clinically acceptable routes of administration such as intravenous (IV), intra-arterial (IA), subcutaneous, epidural, enteral or irrigation of fluid spaces.
- Contraindications O
There are no known contraindications for the Alaris System with Guardrails Suite MX.
This is the same Indications for Use and Intended Use as previously cleared for the respective 510(k)s provided below. There have been no modifications. The verbiage has only been made consistent across the system.
#### . Description of the Device as Found in the Labeling or Promotional Material / Intended Use
The Alaris System with Guardrails Suite MX is similar to other devices of comparable type in commercial distribution. The indications for use, principles of operation, fundamental scientific technology, method of manufacture, and application have not changed. The following description is the same for the existing cleared device as for the proposed modified device.
The Alaris System with Guardrails Suite MX is a modular infusion pump and vital signs monitoring system intended for adult, pediatric and neonatal care that includes safety management software to help reduce medication errors.
The Alaris System with Guardrails Suite MX is intended to provide trained Healthcare Professionals with a way to automate the programming of infusion parameters, thereby decreasing the number of manual steps necessary to enter infusion parameters and provide a "safety net" at the patient's bedside. This helps to reduce the number of programming errors at the point-of-care. All data entry and validation of infusion parameters is performed by the trained Healthcare Professional according to a Physician's order.
The Alaris System with Guardrails Suite MX can be integrated into an existing hospital network and allows communications to and from external devices including personal computers (PCs), Personal Digital
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the CareFusion logo. The logo consists of an orange circle with a white shield inside. The shield has an orange arrow pointing to the upper right. To the right of the circle is the word "CareFusion" in gray text.
Assistants (PDAs), hospital monitoring systems and Hospital Information Management Systems (HMS). Bi-directional communication of data can include infusion parameters, system configuration, clinical history, events, trending, alarms and status.
- Explanation of How the Device Functions ●
PC Unit remains the core of the Alaris System, providing a common user interface and power supply for associated system modules. The basic components of the PC Unit include:
- A mechanical interface which provides structural interconnection between the PC Unit and the modules. o
- A power interface which provides power from the PC Unit to the modules. O
- A communications interface which provides the ability to communicate bi-directionally between the PC O Unit and the modules.
- A communications interface which provides the ability to communicate bi-directionally between the PC O Unit and an external host.
- The Scientific Concepts that Form the Basis for the Device .
Smart infusion pump systems can help prevent medication errors by alerting the healthcare professional to a pump setting that doesn't match the Healthcare Facility's drug administration guidelines programmed into the Data Set. By checking the programmed settings against the Healthcare Facility's Data Set for specific drugs and care areas, smart infusion pump systems can help the Healthcare Professional intercept and correct potentially serious infusion mistakes before they happen.
- Significant Physical and Performance Characteristics of the Device such as Design, Material and Physical Properties
The significant physical and performance characteristics of the infusion pump system are provided in the User Manuals.
- o Summary of Technological Characteristics of the Proposed Device Compared to the Predicate Device
The proposed infusion pump system with the v10.5 software enhancements has the same technological characteristics as the predicate devices.
The affected component devices with the proposed v10.5 software enhancements have the following similarities as the predicate devices:
- Have the same indications for use and intended use. O
- Apply the same operational principles. O
- Have the same design. O
- Have the same materials. O
- O Have the same components.
- O Have similar operational flow.
- O Have the same performance specifications.
- O Have the same physical properties.
- O Have the same manufacturing process.
- Have the same energy source. O
- Have the same technological characteristics or have different technological characteristics (e.g., Detect O Closed Secondary Clamp feature) and do not raise different questions of safety and effectiveness. There are no significant changes in the materials, design, energy source, or other features of the device from those of the predicates. The device is as safe and effective as the legally marketed device. This claim is supported by the information and data provided in this 510(k). This includes the following information:
- Descriptions of the existing and proposed device systems.
- 트 Indications for Use and Intended Use of the existing and proposed device systems.
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the CareFusion logo. The logo consists of an orange circle with a white shield inside. The shield has a small orange triangle in the upper right corner. To the right of the circle is the word "CareFusion" in gray sans-serif font.
- 트 Labeling for the existing and proposed device systems.
- 트 Comparison tables of features of the existing and proposed device systems.
- 트 Comparison tables of specifications of the existing and proposed device systems.
- 트 Proposed device system and software hazard analysis.
- Proposed device system and software requirements.
- 트 Proposed device system and software test plans and reports.
- 트 Proposed device system and software traceability matrix.
- Discussion of Non-Clinical Tests Submitted, Referenced or Relied On in the 510(k) and the Conclusions ● Drawn
Software verification and validation was performed to ensure that the proposed v10.5 software enhancements meet design input and safety requirements. Software testing included verification and validation of the closed secondary clamp detection functions, input and output functions and user interface modifications. The proposed v10.5 software enhancements do not affect the indications for use/intended use or introduce any unacceptable risks. Verification and validation testing to support the v10.5 software enhancements has been completed and demonstrate that design verification testing including software verification is acceptable and design outputs conform to the design input requirements. This confirms that the Alaris System with Guardrails Suite MX with the v10.5 software enhancements meet these requirements.
The proposed v10.5 software modifications did not require animal studies.
- Discussion of Clinical Tests Submitted, Referenced or Relied On in the 510(k) and the Conclusions Drawn
This 510(k) does not include clinical data.
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.