MEDFUSION 4000 PUMP DEVICE SPECIFIC REPORTS SOLFWARE FOR PHARMGUARD SERVER VERSION 2.0
K141193 · Smiths Medical Asd, Inc. · PHC · Jul 25, 2014 · General Hospital
Device Facts
Record ID
K141193
Device Name
MEDFUSION 4000 PUMP DEVICE SPECIFIC REPORTS SOLFWARE FOR PHARMGUARD SERVER VERSION 2.0
Applicant
Smiths Medical Asd, Inc.
Product Code
PHC · General Hospital
Decision Date
Jul 25, 2014
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 880.5725
Device Class
Class 2
Indications for Use
Device Specific Reports provide the user information compiled from data generated by networked devices and stored in the PharmGuard Server. This information may be used to support continuous quality improvement programs. Reports generated from the data can be used to analyze and trend various aspects of the designated infusion pump systems and therapies used.
Device Story
Accessory software for Medfusion 4000 Syringe Infusion Pump; integrates with PharmGuard Server. Extracts, transforms, and loads (ETL) historical infusion data (clinical/operational alarms, fault/power/maintenance events, therapy changes, telemetry) from networked pump databases. Provides near real-time monitoring and historical reporting. Outputs include graphical and tabular reports on drug compliance, safety events, alarm history, and pump status. Used by clinical staff/administrators to analyze infusion trends and support quality improvement programs. Facilitates data-driven clinical workflow decisions.
Clinical Evidence
Bench testing only; no clinical data. Software validation testing confirmed device met pre-established specifications.
Technological Characteristics
Software-based infusion data reporting tool. Operates as an accessory to PharmGuard Server. Utilizes SQL Server databases and a data mart for storage and processing. Employs ETL (Extract, Transform, Load) processes for data acquisition. Connectivity via networked infusion pump infrastructure.
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
Medfusion® Model 4000 Series Syringe Infusion Pump, PharmGuard® Toolbox 2.0 Medication Safety Software (K111386)
Submission Summary (Full Text)
{0}------------------------------------------------
# smiths medical
bringing technology to life
Smiths Medical 1265 Grey Fox Road St. Paul, MN 55112 T: 651 633 2556 F: 651 628 7459 www.smiths-medical.com
#### 510(k) Summary
#### 510(k) 141193
JUL 2 5 2014
#### DATE PREPARED: 16-JULY-2014
#### I. GENERAL INFORMATION
| Applicant's Name<br>and Address: | Smiths Medical ASD, Inc.<br>1265 Grey Fox Road<br>St. Paul, MN 55112 |
|----------------------------------|--------------------------------------------------------------------------------------------------------------------|
| Contact Person: | Tom Bliss<br>Sr. Specialist, Regulatory Affairs |
| Common/Usual<br>Name: | Infusion Safety Management Software |
| Product Code: | PHC |
| Proprietary Name: | Medfusion® 4000 Pump Device Specific Reports Software for<br>PharmGuard® Server, Version 2.0 |
| Predicate Device/<br>510(k): | K111386, Medfusion® Model 4000 Series Syringe Infusion Pump,<br>PharmGuard® Toolbox 2.0 Medication Safety Software |
#### II. DEVICE DESCRIPTION
The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 software is a medical device intended to be used in the analysis of infusion data, provide information used in forming clinical workflow decisions and improve infusion safety. The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 is an infusion pump accessory compatible with the PharmGuard® Server, which stores data exported from networked infusion pumps. The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 copies data from the PharmGuard® Server databases and uses it to create reports.
{1}------------------------------------------------
The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 can be used for transferring, displaying or storing and retrieving historical clinical data, clinical and operational alarm events, fault events, power events, maintenance events, therapy and therapy change events and telemetry events that are generated by the networked infusion pumps and stored in the PharmGuard® Server. It is also intended for near real-time monitoring of infusion pump history. For the purposes of this device "near real-time" is associated with time intervals typically measured in minutes rather than in seconds or in hours.
The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 manipulates and re-configures data to present information bevond the discrete data that is displayed on the pumps.
Reports include information on drug compliance, safety events, alarm history, drug program utilization, and pump technical status. Reports can summarize data and reveal trends in these areas by presenting results summarized by such parameters as time of day, facility, drug profile, alarm type and safety events. The information may be presented graphically, in table form and in some cases allows "drill through" to the underlying data used to produce the reports.
The Device Specific Reports Software comprises:
- . Instructions for Use and Help Files
- An executable file for launching the application .
- A Configuration Tool that provides a user interface to enter, update, and apply the . configuration parameters that operate the Data Mart associated with the Medfusion 4000® Device Specific Reports and associated SQL Server databases
- Metadata that is imported into the PharmGuard® Server System and that . determines what information within the PharmGuard® Server is available to be output via the Device Specific Report software
- Infrastructure files that interact to facilitate and coordinate the data acquisition, . storage, and processing between the PharmGuard® Repository and the Medfusion® 4000 Pump Device Specific Report data mart. The Reporting Infrastructure performs the following major tasks:
- o Extract, Transform, and Load (ETL) data from the PharmGuard Repository into the Reporting Infrastructure data mart.
- o Store device event data in the data mart
- Process requests for data retrieval for device specific reports 0
#### III. DEVICE INTENDED USE
Device Specific Reports provide the user information compiled from data generated by networked devices and stored in the PharmGuard Server. This information may be used to support continuous quality improvement programs. Reports generated from the data can be used to analyze and trend various aspects of the designated infusion pump systems and therapies used.
{2}------------------------------------------------
### IV. SUMMARY OF STUDIES
#### Performance Testing
Smiths Medical performed software validation testing on the Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0
#### Clinical Studies
Human clinical studies were deemed unnecessary to evaluate the safety or effectiveness of the Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0
#### Testing Conclusion
All testing met pre-established specifications, and successfully demonstrated that the device performed as intended. The testing results allowed for a conclusion to be made that the Medfusion® Model 4000 Series Syringe Infusion Pump with the Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 was as safe and effective as the predicate device.
#### VII. STATEMENT OF EQUIVALENCE
The Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 is an accessory to the Medfusion® Model 4000 Series Syringe Infusion Pump. The design and use of the Medfusion® 4000 Pump Device Specific Reports Software. Version 2.0 does not affect the device classification, intended use, technological characteristics, or risks associated with the pump. Validation tests confirmed the suitability of the Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 device for its intended use. The test results did not raise new safety or performance questions, and confirmed that the Medfusion® Model 4000 Series Syringe Infusion Pump with the Medfusion® 4000 Pump Device Specific Reports Software, Version 2.0 accessory is substantially equivalent to the predicate device.
{3}------------------------------------------------
Image /page/3/Picture/0 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a stylized eagle with three stripes extending from its wing. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES USA" is arranged in a circular fashion around the eagle.
Public I lealth Service
Food and Drue Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
#### July 25, 2014
Thomas Bliss Senior Regulatory Affairs Specialist Smiths Medical ASD. Inc. 1265 Grey Fox Road St. Paul, Minnesota 55112
Re: K141193
Trade/Device Name: Medfusion 4000 Pump Device Specific Reports Software for PharmGuard Server Version 2.0 Regulation Number: 21 CFR 880.5725 Regulation Name: Infusion Pump Regulatory Class: Class II Product Code: PHC Dated: May 7, 2014 Received: May 8, 2014
Dear Mr. Bliss:
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 10 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 cither 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.
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
{4}------------------------------------------------
Page 2 - Mr. Bliss
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/ResourcesforYou/Industry/default.htm. Also, please note the regulation entitled. "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding 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 yours,
## Mary S. Runner -S
Erin I. Keith, M.S. Director Division of Anesthesiology, General Hospital, Respiratory, Infection Control and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
# Indications for Use
K141193 510(k) Number (if known):
Device Name:
Medfusion® 4000 Pump Device Specific Reports Software for PharmGuard® Server, Version 2.0
Indications for Use:
Device Specific Reports provide the user information compiled from data generated by networked devices and stored in the PharmGuard Server. This information may be used to support continuous quality improvement programs. Reports generated from the data can be used to analyze and trend various aspects of the designated infusion pump systems and therapies used.
Prescription Use _____________________________________________________________________________________________________________________________________________________________
AND/OR
Over-The-Counter Use (21 CFR 801 Subpart C)
(Part 21 CFR 801 Subpart D)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Mary E. Brooks -A 2014.07.17 14:21:48 -04'00'
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.