SPACELABS MEDICAL CLINICAL EVENT INTERFACE, MODEL 91847
Applicant
Spacelabs Medical, Inc.
Product Code
MSX · Cardiovascular
Decision Date
Sep 19, 2006
Decision
SESE
Submission Type
Special
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The intended use of the Spacelabs Medical Clinical Event Interface is to interface with the Spacelabs monitoring network in order to provide a secondary means of annunciating and displaying patient alarm information to mobile healthcare providers. The device is indicated for use in real-time monitoring of routine patient status and alarm events. The pager is intended to serve as a parallel, redundant mechanism to inform the clinical staff of patient events The Waveform Pager System is intended for use as a secondary alarm in any hospital environment currently using or intending to use a Spacelabs patient monitoring network The Clinical Event Interface supplements the primary patient-monitoring system by providing a forwarding mechanism for annunciating and displaying patient alarm events and the critical information associated with the events - including parameter values and waveforms, typically within 4 - 8 seconds of an alarm event on the patient monitor The pager provides an audio or vibrating alert along with a series of displays showing patient identification, alarm parameters, and up to a 12-second waveform snapshot. The Spacelabs Medical Clinical Event Interface is a secondary alarm. It does not replace the primary alarm function on the monitor. -
Device Story
Software module (Model 91847) installed on OTS computer; interfaces with Spacelabs patient monitoring network. Inputs: patient alarm data and physiological data from monitoring network. Processing: Spacelabs software module detects new data, formats it, and passes to Emergin Integrated Messaging System (OTS). Output: formatted alarm data/waveforms sent to Motorola CP1250 pager via paging encoder. Used in hospital environments; operated by clinical staff. Provides secondary, redundant alarm notification via audio/vibrating alerts on pagers; displays patient ID, alarm parameters, and 12-second waveform snapshots. Benefits: enables nurse awareness of patient alarm conditions while away from bedside; supplements primary monitoring.
Clinical Evidence
No clinical data. Bench testing only. Validation included testing of all system components to verify data acquisition and forwarding from the monitoring network to the pager.
Technological Characteristics
Software module for OTS computer (Microsoft OS). Integrates with Emergin Integrated Messaging System and Motorola CP1250 paging hardware. Connectivity: Networked via Spacelabs patient monitoring network. Secondary alarm notification system.
Indications for Use
Indicated for real-time monitoring of routine patient status and alarm events in hospital environments using Spacelabs patient monitoring networks. Serves as a secondary, redundant alarm notification system for mobile healthcare providers. Not for use as a replacement for primary bedside monitor alarm functions.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
Predicate Devices
Spacelabs Medical Clinical Messenger, model 91841 (K992749)
Submission Summary (Full Text)
{0}------------------------------------------------
K062278
p1/3
SEP 1 9 2006
# 510(k) Premarket Notification Spacelabs Medical Clinical Event Interface (CEI), Model 91847 Summary of Safety and Effectiveness
System, Network and Communication, Physiological Monitors Classification Information: Specialty Cardiovascular Product Code MSX Regulation 21CFR \$870.2300 Class II Remote Alarm Notification System Common/Usual Name: Proprietary Name: Spacelabs Medical Clinical Event Interface (CEI), Model 91847 Est. Registration Number: 3023361 Performance Standard: No special controls have been identified for this product under 21CFR §870.2300
This 510(k) summary of safety and effectiveness information is submitted in accordance with the requirements of SMDA 1990 and 1992.
| Subject: | 510(k) Summary of Safety and Effectiveness Information for the Spacelabs Medical Clinical Event Interface (CEI), Model 91847 |
|---------------------------------|------------------------------------------------------------------------------------------------------------------------------|
| Submitter: | Spacelabs Medical, Inc.<br>PO Box 7018<br>Issaquah, WA 98029 |
| | David J. Geraghty |
| | Phone: 1 425 657 7200 |
| | Fax: 1 425 657 7207 |
| | david.geraghty@slmd.com |
| Proprietary Name: | Spacelabs Medical Clinical Event Interface (CEI), Model 91847 |
| Common Name and Classification: | Remote Alarm Notification System<br>(Cardiovascular, Product Code MSX, 21CFR §870.2300, Class II) |
Spacelabs Medical 510(k) CEI Summary of Safety and Effectiveness
030012
{1}------------------------------------------------
### Device Description:
The Spacelabs Medical Clinical Event Interface (CEI), model 91847, is a software module intended to be installed on an Off-The-Shelf (OTS) computer system utilizing a Microsoft operating system. The primarv purpose of the CEI is to forward patient monitor alarm event information, originating from a Spacelabs Patient Monitoring network, to a messaging and notification system for delivery to the healthcare provider via wireless pagers. The system is also capable of providing vital signs updates at regular intervals. CEI allows nurses to be aware of their patients' alarm conditions when they are away from the patient and the monitoring system.
CEI is an open design utilizing an OTS messaging system that is compatible with the Motorola CP1250 paging systems. The Clinical Event Interface includes a software module, created by Spacelabs Medical, that accesses patient data acquired from a Spacelabs Medical Patient Monitoring System. The monitoring system forwards the data to a database. The Spacelabs Medical software module recognizes when new information has become available. It accesses and formats that data for delivery to the Emergin Integrated Messaging System, an OTS software package. The Emergin software accepts input from the Spacelabs program, reformats it and passes it on to the paging encoder, an OTS component of the system. The paging encoder formats the data for the Motorola CP1250 pager and forwards it to the pager base station for transmission to the pager. The Spacelabs Medical CEI provides a complete, end-to-end solution for paging and incorporates all of these components in a single offering.
The CEI messaging system provides for the sending patient information in a text only or text and graphic format to the Motorola CP1250 pager. The CEI system is designed to forward alarm information as the alarms are recognized by the patient monitoring network. The system is also cable of being set up to periodically forward a patient's physiological data at predetermined intervals.
The Spacelabs Medical ICS Clinical Event Interface (CEI), model 91847, system is a secondary alarm notification system. It does not replace the primary alarm function of the bedside monitor.
Spacelabs Medical 510(k) Notification CEI - Executive Summary
## 000013
July 24, 2006 Page 2 of 3
{2}------------------------------------------------
K062278
P3/3
#### Intended Use:
The intended use of the Spacelabs Medical Clinical Event Interface is to interface with the Spacelabs monitoring network in order to provide a secondary means of annunciating and displaying patient alarm information to mobile healthcare providers. The device is indicated for use in real-time monitoring of routine patient status and alarm events. The pager is intended to serve as a parallel, redundant mechanism to inform the clinical staff of patient events The Waveform Pager System is intended for use as a secondary alarm in any hospital environment currently using or intending to use a Spacelabs patient monitoring network The Clinical Event Interface supplements the primary patient-monitoring system by providing a forwarding mechanism for annunciating and displaying patient alarm events and the critical information associated with the events - including parameter values and waveforms, typically within 4 - 8 seconds of an alarm event on the patient monitor The pager provides an audio or vibrating alert along with a series of displays showing patient identification, alarm parameters, and up to a 12-second waveform snapshot.
The Spacelabs Medical Clinical Event Interface is a secondary alarm. It does not replace the primary alarm function on the monitor. -
T`est Discussion:
The Spacelabs Medical Clinical Event Interface (CEI), Model 91847 and the Spacelabs Mcdical Clinical Messenger, model 91841, K992749 are substantially equivalent in design concepts, technologics and materials. CEI was validated through rigorous testing that, in part, support the compliance of the CEI software module and its OTS components to the Standards mentioned in Scction 6 of this submission. Additionally, the CEI software was developed following a robust software development process and was fully specified and validated. The test program included all of the components of the system and verified that as data became available to CEI it was acquired and forwarded through to the pager.
Test Conclusion:
The Spacelabs Medical Clinical Event Interface (CEI), Model 91847, is substantially equivalent to its predicate devices in design concepts, technologies and materials. Testing demonstrates that CEI is as safe and effective as Spacclabs Medical Clinical Messenger, model 91841, K992749.
Spacelabs Medical 510(k) Notification CEI - Executive Summary
{3}------------------------------------------------
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
SEP 1 9 2006
Spacelabs Medical Inc. c/o Mr. David J. Geraghty Manager, Regulatory and Quality 5150 220th Ave SE PO Box 7018 Issaquah, WA 98027-7018
Re: K062278
Trade Name: Spacelabs Medical Clinical Event Interface (CEI), Model 91847 Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (including cardiotachometer and rate alarm). Regulatory Class: Class II (two) Product Code: MSX Dated: August 22, 2006 Received: August 24, 2006
Dear Mr. Geraghty:
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.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), 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 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{4}------------------------------------------------
#### Page 2 – Mr. David J. Geraghty
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); 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. This letter will allow you to begin marketing your device as described in your Section 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), please contact the Office of Compliance at (240) 276-0120. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (240) 276-3150 or at its Internet address http://www.fda.gov/cdrh/industry/support/index.html.
Sincerely yours,
B.J. Arminio for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
## Indications for Use
510(k) Number (if known):
Spacelabs Medical Clinical Event Interface (CEI), Model 91847 Device Name: ___
Indications for Use:
The intended use of the Spacelabs Medical Clinical Event Interface with the Spacelabs monitoring network in order to provide a secondary means of annunciating and displaying patient alarm information to mobile healthcare providers. The device is indicated for use in real-time monitoring of routine patient status and alarm events. The pager is intended to serve as a parallel, redundant mechanism to inform the clinical staff of patient events. The Clinical Event Interface System is intended for use as a secondary alarm in any hospital environment currently using or intending to use a Spacelabs patient monitoring network. The Clinical Event Interface supplements the primary patient-monitoring system by providing a forwarding mechanism for annunciating and displaying patient alarm events and the critical information associated with the events - including parameter values and waveforms, typically within 4 - 8 seconds of an alarm event on the patient monitor. The pager provides an audio or vibrating alert along with a series of displays showing patient identification, alarm parameters, and up to a 12-second waveform snapshot.
The Spacelabs Medical Clinical Event Interface is a secondary alarm. It does not replace the primary alarm function on the monitor.
Prescription Use XX (Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use -------(21 CFR 801 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE OF NEEDED)
Concurrence of CDRH Office of Device Evaluation (ODE)
Blumermo
(Division Sign Off)
Page 1 of 1
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.