K141102 · Hospira, Inc. · FRN · Jul 8, 2014 · General Hospital
Device Facts
Record ID
K141102
Device Name
HOSPIRA MEDNET MEDICATION MANAGEMENT SUITE
Applicant
Hospira, Inc.
Product Code
FRN · General Hospital
Decision Date
Jul 8, 2014
Decision
SESE
Submission Type
Special
Regulation
21 CFR 880.5725
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The Hospira MedNet™ Medication Management Suite (MMS) is intended to facilitate networked communication between MMS compatible computer systems and Hospira Infusion pumps. The MMS provides trained healthcare professionals with the capability to send, receive, report, and store information from interfaced external systems, and to configure and edit infusion programming parameters. The MMS is intended to provide 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 a trained healthcare professional according to physician's orders.
Device Story
Hospira MedNet™ Medication Management Suite (MMS) is an optional software product for healthcare facilities; facilitates bi-directional networked communication (wired/wireless) between hospital information systems and compatible infusion pumps. Inputs include infusion parameters, pump configurations, location data, history, events, trending, alarms, and status. System enables sending, receiving, reporting, and storing pump data; automates infusion parameter programming to reduce manual data entry steps. Operated by trained healthcare professionals; cannot remotely start, modify, or terminate ongoing infusions. Healthcare providers use output to manage pump configurations and infusion data; supports clinical decision-making by ensuring accurate, physician-ordered infusion programming. Benefits include reduced manual entry errors and improved infusion management efficiency.
Clinical Evidence
No clinical trials performed. Substantial equivalence supported by non-clinical verification and validation testing, risk management activities, and human factors studies validating error mitigation effectiveness.
Technological Characteristics
Software-based infusion pump management system. Features include Drug Library Editor (DLE), server-based download/upload management, pump configuration, log management, multiple drug entries per Clinical Care Area (CCA), and bi-directional wireless/wired communication. Operates on networked PC/server infrastructure.
Indications for Use
Indicated for use by trained healthcare professionals in healthcare facilities to facilitate networked communication between hospital information systems and Hospira infusion pumps, including configuration, infusion parameter programming, and data management.
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.
Predicate Devices
Hospira MedNet™ Medication Management Suite (MMS) (K042609)
Submission Summary (Full Text)
{0}------------------------------------------------
# JUL 0882014
1
#### K141102 510(k) SUMMARY
## A summary of 510(k) safety and effectiveness information in accordance with the requirements ` of 21 CFR 807.92.
| Submitter Information | |
|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Name | Hospira, Inc |
| Address | 275 North Field Dr, Lake Forest, IL 60045 |
| Phone number | 858-391-1142 |
| Fax number | 224-212-5401 |
| Establishment<br>Registration<br>Number | 3005579246 |
| Name of contact<br>person | Tom Gutierrez |
| Date prepared | April 28, 2014 |
| Name of device | |
| Trade or<br>proprietary name | Hospira MedNet™ Medication Management Suite |
| Common or<br>usual name | Infusion Pump Accessory Software |
| Classification<br>name | Infusion Pump |
| Classification panel | General Hospital |
| Regulation | 880.5725 |
| Product Code(s) | FRN |
| Legally marketed<br>device(s) to which<br>equivalence is claimed | Hospira MedNet™ Medication Management Suite (MMS), cleared<br>under K042609. |
| Reason for 510(k)<br>submission | Software Changes |
| Device description | The Hospira MedNet™ Medication Management Suite (MMS) is<br>an optional software product intended for use in healthcare<br>facilities by trained healthcare professionals to facilitate<br>networked communications (wired or wireless) between MMS<br>compatible hospital information systems and compatible infusion<br>pumps.<br>The MMS provides healthcare professionals with the capability to<br>send, receive, and store information from infusion pumps. The bi-<br>directional communication includes infusion parameters, pump<br>default configurations, pump location, history, events, trending,<br>alarms and status. The MMS cannot remotely start, modify, or |
| | terminate ongoing infusions. |
| Intended use/<br>Indications for use of<br>the device | The Hospira MedNet™ Medication Management Suite (MMS) is<br>intended to facilitate networked communication between MMS<br>compatible computer systems and Hospira Infusion pumps. The<br>MMS provides trained healthcare professionals with the<br>capability to send, receive, report, and store information from<br>interfaced external systems, and to configure and edit infusion<br>programming parameters. |
| | The MMS is intended to provide a way to automate the<br>programming of infusion parameters, thereby decreasing the<br>amount of manual steps necessary to enter infusion data. All<br>data entry and validation of infusion parameters is performed by<br>a trained healthcare professional according to physician's<br>orders. |
{1}------------------------------------------------
Summary of the technological characteristics of the device compared to the predicate device ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Characteristic | Subject Device<br>Hospira MedNet™<br>Medication Management<br>Suite | Predicate Hospira MedNet™<br>Medication Management Suite<br>K042609 |
|---------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------------------|
| Drug Library Editor (DLE) | Yes | Yes |
| DLE on PC | | |
| Manage Download and<br>Uploading via server | Yes | Yes |
| Configure Pumps | Yes | Yes |
| Manage Pump Logs | Yes | Yes |
| Multiple Drug entries per<br>CCA | Yes | Yes |
| Multiple CCAs | Yes | Yes |
| Pre-populating pump | Yes | Yes |
| Wireless Communications | Yes | Yes |
| Bi-directional<br>Communications | Yes | Yes |
i
{2}------------------------------------------------
CN A THE SERVER A SPERFORMANCE DATA - CATAL - CATAL CARA - C
SUMMARY OF NON-CLINICAL TESTS CONDUCTED FOR DETERMINATION OF SUBSTANTIAL EQUIVALENCE*
#### Non-Clinical Performance Test Summary
Verfication and validation activities for Hospira MedNet™ software confirmed that the software meets user needs and design inputs.
Verification and validation testing was conducted and confirmed that the new feature design requirements were met. Additionally, pre-existing design requirements were re-tested. It was reconfirmed that Hospira MedNet™ continued to meet all pre-existing design requirements.
Risk management activities are incorporated in to the design and development process and a Safety Assurance Case has been generated to demonstrate the safety of the Hospira MedNet™ Medication Management Suite.
Human Factors studies have been conducted to validate the effectiveness of use related error mitigations.
## SUMMARY OF CLINICAL TESTS CONDUCTED FOR DETERMINATION OF SUBSTANTIAL EQUIVALENCE AND/OR OF CLINICAL INFORMATION
#### Clinical Performance Data/Information
No clinical trials have been performed. The modifications described in the submission do not meet the clinical testing criteria outlined in the FDA guidance "Total Product Life Cycle: infusion Pump –Premarket Notification {510(k)} Submissions (DRAFT GUIDANCE) issued in April 23, 2010, given:
- Hospira MedNet is not a new device
- there were no changed or modification in the intended use of the device
- the modifications were not intended to correct problems with the design of the user interface or usability of the product
A CONCLUSIONS DRAWNIFROM NON-CLINICAL AND CLINICAL DATA
The results of the verification and validation testing as well as the risk analysis applied, supported by the Human Factors studies, demonstrate that the modifications described in the submission met design specifications and the device as a whole continues to be safe and effective.
{3}------------------------------------------------
#### DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
July 8, 2014
Hospira, Incorporated Mr. Tom Gutierrez Associate Director Global Regulatory Affairs 275 North Field Drive Lake Forest, IL 60045
Re: K141102
Trade/Device Name: Hospira MedNet™ Medication Management Suite Regulation Number: 21 CFR 880.5725 Regulation Name: Infusion Pump Regulatory Class: II Product Code: FRN Dated: June 6, 2014 Received: June 9, 2014
Dear Mr. Gutierrez:
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.
{4}------------------------------------------------
Page 2 - Mr. Gutierrez
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 (OS) 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/Resourcesfor You/Industry/default.htm.
Sincerely yours,
Mary S. Runner -S
Erin I. Keith, M.S. Division Director Division of Anesthesiology, General Hospital, Respiratory, Infection Control and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
#### DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration
## Indications for Use
Form Approved: OMB No. 0910-0120 Expiration Date: January 31, 2017 See PRA Statement befow.
510(k) Number (if known)
## 241102
#### Device Name
Hospira MedNet™ Medication Management Suite
#### Indications for Use (Describe)
The Hospira MedNet™ Medication Management Suite (MMS) is intended to facilitate networked communication between MMS computer systems and Hospira Infusion pumps. The MMS provides trained healtheare professionals with the capability to send, receive, report, and store interfaced external systems, and to configure and edit infusion programming parameters.
The MMS is intended to provide a way to automate the programming of infusion parameters, thereby decreasing the arnount of manual steps necessary to enter infusion data. All data entry and validation of infusion parameters is performed by a trained healthcare professional according to physician's orders.
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) | |
| Digitally signed by<br>Richard C. Chapman -S<br>Date: 2014.07.08<br>10:04:40 -04'00' | |
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."
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.