VIRIDIA INFORMATION CENTER SOFTWARE FOR M3154A OPT C22
K993907 · Agilent Technologies, Inc. · MHD · Dec 6, 1999 · General Hospital
Device Facts
Record ID
K993907
Device Name
VIRIDIA INFORMATION CENTER SOFTWARE FOR M3154A OPT C22
Applicant
Agilent Technologies, Inc.
Product Code
MHD · General Hospital
Decision Date
Dec 6, 1999
Decision
SESE
Submission Type
Special
Regulation
21 CFR 880.5725
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
For central monitoring of multiple adult, pediatric and neonatal patients; and where the clinician decides to monitor cardiac arrhythmia of adult, pediatric, and neonatal patients and/or ST segment of adult patients to gain information for treatment, to monitor adequacy of treatment, or to exclude causes of symptoms.
Device Story
Viridia Information Software for Model M3154A Database Server (Release B.02) provides read-only remote access to retrospective patient physiologic data; inputs include alarm, event, wave, trend, and ST segment data; enables clinicians to view data via hospital intra/internet (HIS LAN) rather than only at the central monitor in the care unit; supports treatment monitoring and symptom exclusion; intended for use by clinicians in hospital settings.
Clinical Evidence
Bench testing only. Verification and validation activities included system-level, integration, environmental, and safety testing based on hazard analysis. Pass/Fail criteria were derived from predicate device specifications; results demonstrated that the web software interface meets all reliability and performance requirements.
Technological Characteristics
Software-based database server access; provides read-only web interface for retrospective physiologic data review; operates over hospital intra/internet (HIS LAN); maintains same core technological characteristics as predicate HP CentralVue software.
Indications for Use
Indicated for central monitoring of adult, pediatric, and neonatal patients; includes cardiac arrhythmia monitoring for all populations and ST segment monitoring for adults to inform treatment decisions or exclude symptoms.
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}------------------------------------------------
DEC - 6 1999
9.0 510(k) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirements of the Safe Medical Devices Act of 1990 and 21 C.F.R. §807.92.
1. The submitter of this premarket notification is: Dave Osborn Regulatory Affairs Engineer Healthcare Solutions Group Agilent Technologies 3000 Minuteman Road Andover, MA 01810-1085
978 659 3178 Tel: Fax: 978 685 5624 Email:dosborn@agilent.com
This summary was prepared on 10 November, 1999
- 2. The name of this device is the Viridia Information Software for Model M3154A Database Server, Release B.02. Classification names are as follows:
870.2800, II 74 DSH Recorder, Magnetic Tape, Medical
- 3. The new device is substantially equivalent to the previously cleared HP CentralVue Software device marketed pursuant to K964832, and K993171.
- 4. The modification is a software-based change that provides database server access via the hospital intra/internet system.
- 5. The new device has the same intended use as the legally marketed predicate device. It is used for the read-only viewing of patient physiologic data, including retrospective review applications of Alarm, Event, Wave, Trend, and ST segment (adults) Review to gain information for treatment, to monitor adequacy of treatment, or to exclude causes of The difference is that the modified device extends symptoms. the review of retrospective patient data from the central monitor in the care unit to remote locations via the hospital's HIS LAN web access (hospital intra/internet).
- 6. The new device has the same technological characteristics as the legally marketed predicate device.
{1}------------------------------------------------
- 7. Verification, validation, and testing activities establish the performance, functionality, and reliability characteristics of the new device with respect to the predicate. Testing involved system level tests, integration tests, environmental tests, and safety testing from hazard analysis. Pass/Fail criteria were based on the specifications cleared for the predicate device and test results showed substantial equivalence. The results demonstrate that web software interface functionality meets all reliability requirements and performance claims.
{2}------------------------------------------------
Image /page/2/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a stylized eagle or bird-like symbol with three curved lines forming its body and wings. Encircling the symbol is the text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" in a circular arrangement. The text is in all capital letters and appears to be in a sans-serif font.
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
DEC - 6 1999
Mr. Dave Osborn Regulatory Affairs Aqilent Technologies, Inc. 3000 Minuteman Rd. Andover, MA 01810-1099
Re : K993907 Viridia Information Center (VIC) Software for Model M3154A Database Server (DBS), Release B.02 Requlatory Class: III (three) MHX, DSI, MLD Product Code: November 16, 1999 Dated: November 17, 1999 Received:
Dear Mr. Osborn:
We have reviewed your Section 510(k) notification of intent to market the device referenced above and we 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). 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.
If your device is classified (see above) into either class II (Special Controls) or class III (Premarket Approval), it may be subject to such additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 A substantially equivalent determination assumes compliance to 895. with the Current Good Manufacturing Practice requirements, as set forth in the Quality System Regulation (QS) for Medical Devices: General regulation (21 CFR Part 820) and that, through periodic QS inspections, the Food and Drug Administration (FDA) will verify such assumptions. Failure to comply with the GMP regulation may result in regulatory action. In addition, FDA may publish further announcements concerning your device in the Federal Register. Please note: this response to your premarket notification submission does not affect any obligation you might have under sections 531 through 542 of the Act for devices under the Electronic Product Radiation Control provisions, or other Federal laws or regulations.
{3}------------------------------------------------
Page 2 - Mr. Dave Osborn
This letter will allow you to begin marketing your device as described in your 510(k) premarket notification. The FDA finding of substantial equivalence of your device to a legally marketed predicate device results in a classification for your device and thus, permits your device to proceed to the market.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801 and additionally 809.10 for in vitro diagnostic devices), please contact the Office of Compliance at (301) 594-4648. Additionally, for questions on the promotion and advertising of your device, please contact the Office of Compliance at (301) 594-4639. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR 807.97). Other general information on your responsibilities under the Act may be obtained from the Division of Small Manufacturers Assistance at its toll-free number (800) 638-2041 or (301) 443-6597 or at its internet address "http://www.fda.gov/cdrh/dsma/dsmamain.html".
Sincerely yours,
Dan R. Teth
2n Celia M. Witten, Ph.D., M.D. Acting Director Division of Cardiovascular, Respiratory, and Neurological Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{4}------------------------------------------------
Page 1 of 1
510(k) Number (if known):
Device Name: Viridia Information Center (VIC) Software for Model M3154A Database Server (DBS), Release B.02
For central monitoring of multiple adult, pediatric and Indications For Use: neonatal patients; and where the clinician decides to monitor cardiac arrhythmia of adult, pediatric, and neonatal patients and/or ST segment of adult patients to gain information for treatment, to monitor adequacy of treatment, or to exclude causes of symptoms.
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
| (Division Sign-Off) | |
|-------------------------------------------------------------------|---------|
| Division of Cardiovascular, Respiratory, and Neurological Devices | |
| 510(k) Number | K993907 |
| Prescription Use X<br>(Per 21 CFR 801.109) | OR | Over-The-Counter Use ______ |
|--------------------------------------------|----|-----------------------------|
|--------------------------------------------|----|-----------------------------|
(Optional Format 1-2-96)
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.
