The EXTENSION Clinical Alert Notification solution is a closed loop communications system that interfaces with health care information systems and medical devices to provide a secondary means of annunciating and displaying patient alarm text and other information to mobile health care workers that is important to patient care, nursing vigilance and overall hospital operations. The EXTENSION Clinical Alert Notification solution alerts and informs the clinician about critical patient alarms by drawing an identified individual's attention to a defined patient in a timely manner without requiring them to be at or near the bedside medical devices or central station displays. The EXTENSION Clinical Alert Notification solution is not intended to replace any part of the patient monitoring system or procedures already existing for the medical devices interfaced with the EXTENSION Clinical on solution. The EXTENSION Clinical Alert Notification solution is limited to use by qualified medical professionals who have been trained on the use of the device. It is intended for use in hospital type acute care environments and is not for home use.
Device Story
The EXTENSION Clinical Alert Notification solution is a middleware communications system that interfaces with hospital information systems and medical devices (patient monitors, infusion pumps, ventilators) to relay alarm text and patient data to mobile healthcare workers. It functions as a secondary notification system, alerting clinicians to critical alarms via mobile devices (VoIP handsets, pagers, PDAs) without requiring proximity to bedside monitors or central stations. The system utilizes standard IT infrastructure, including servers, routers, switches, and wireless access points (IEEE 802.11a/b/g/n, DECT). By providing timely remote alerts, the device supports nursing vigilance and hospital operations. It is intended for use by trained medical professionals in acute care settings. The system does not replace primary monitoring procedures; it serves as a supplementary communication layer to improve clinician response times to patient conditions.
Clinical Evidence
Bench testing only. No clinical data provided. The manufacturer performed risk analysis, design reviews, component-level testing, system-level testing, performance testing, safety testing, and usability/validation testing to demonstrate substantial equivalence.
Technological Characteristics
Middleware system utilizing standard IT/telecommunications hardware: servers, routers, switches, wireless access points (IEEE 802.11a/b/g/n, DECT), and mobile endpoints (VoIP handsets, pagers, PDAs). Software runs on a virtual machine. Connectivity via wired/wireless network infrastructure. No specific material standards or proprietary sensing hardware; device acts as a data relay/communications interface.
Indications for Use
Indicated for qualified medical professionals in hospital acute care environments to receive secondary notification of patient alarms from interfaced medical devices (e.g., patient monitors, infusion pumps, ventilators). Not for home use. Not intended to replace primary monitoring systems.
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.
{0}------------------------------------------------
### K130339 Page 1 of 3
## JUL 1 1 2013
| Submitted by: | EXTENSION, Inc.<br>7030 Pointe Inverness Way, Suite 230<br>Fort Wayne, IN 46804 |
|--------------------------------------|---------------------------------------------------------------------------------|
| Official Correspondent: | Todd Plesko, Chief Executive Officer, EXTENSION,<br>Inc. |
| Correspondent Address: | 7030 Pointe Inverness Way, Suite 230<br>Fort Wayne, IN 46804 |
| Correspondent Phone: | 260-797-0200 |
| Correspondent Email: | todd.plesko@ext-inc.com |
| Company Contact for this Submission: | Tim Gee, Principal, Medical Connectivity Consulting |
| Contact Address: | 7250 SW 154th Terrace<br>Beaverton, OR 97007 |
| Contact Phone: | 503-481-2370 |
| Contact Email: | tim@medicalconnectivity.com |
| Date Summary Prepared: | February 1, 2013 |
| Trade Name: | EXTENSION Clinical Alert Notification solution |
| Common Name: | Network and communications middleware |
| Device Class: | Class II |
| Product Code: | MSX |
| Classification Name: | System, Network and Communications, Physiologic<br>Monitors |
| Substantially Equivalent Devices: | Ascom Cardiomax, K103634 |
#### Description of Clinical Alert Notification
The EXTENSION Clinical Alert Notification solution is a closed loop communications system that interfaces with health care information systems and medical devices to provide a secondary means of annunciating and displaying patient alarm text and other information to mobile health care workers. The EXTENSION Clinicalion solution alerts and informs the clinician about patient alarms. The EXTENSION Inc. device is not intended to replace any part of the patient monitoring system or patient monitoring procedures already existing for the medical devices interfaced with the EXTENSION Clinical Alert Notification solution.
{1}------------------------------------------------
510(k) EXTENSION Clinical Alert Notification
K130339 Page 2 of 3
#### Intended Use/Indications for Use
The EXTENSION Clinical Alert Notification solution is a closed loop communications system that interfaces with health care information systems and medical devices to provide a secondary means of annunciating and displaying patient alarm text and other information to mobile health care workers that is important to patient care, nursing vigilance and overall hospital operations. The EXTENSION Clinical Alert Notification solution alerts and informs the clinician about critical patient alarms by drawing an identified individual's attention to a defined patient in a timely manner without requiring them to be at or near the bedside medical devices or central station displays. The EXTENSION Clinical Alert Notification solution is not intended to replace any part of the patient monitoring system or procedures already existing for the medical devices interfaced with the EXTENSION Clinical on solution.
The EXTENSION Clinical Alert Notification solution is limited to use by qualified medical professionals who have been trained on the use of the device. It is intended for use in hospital type acute care environments and is not for home use.
#### Technology
· The EXTENSION Clinical Alert Notification solution is made up of standard telecommunications and information technology. EXTENSION develops the application software that runs on a virtual machine and is accessed by client devices (PC computers running web browsers, wireless voice over IP phone handsets).
The EXTENSION Clinical Alert Notification solutions and transmits data similarly to the predicate devices. The EXTENSION Clinical Alert Notification solution and predicate devices use similar data transmission and communications technologies.
| Types of medical devices<br>supported | Patient monitors, infusion pumps,<br>ventilators, and similar devices | Designed for a variety of<br>therapeutic, diagnostic and<br>monitoring medical devices. Initial<br>interface for patient monitors. |
|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|
| Remote access to medical device<br>data via internet | Yes | Yes |
| Hardware wired connection | 1. Medical device connects to<br>radio.<br>2. Router switch connects to<br>access point<br>3. Router switch connects to<br>mobile device switch (phone or<br>other endpoint system)<br>4. Router switch connects to<br>server<br>5. Router switch connects to client<br>devices (PCs and displays) | Same |
| Hardware wireless connection | 1. Radio connects to access point<br>2. Phone or other endpoint device<br>transmitters connect to mobile<br>devices | Same |
{2}------------------------------------------------
# ENSION Clinical Alert Notification
| | | Page 3 of 3 | |
|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--|
| Wireless transmission<br>technology | 1. IEEE 802.11a/b/g/n<br>2. DECT/IEEE 802.11a/b/g/n for<br>handsets or PDAs | Same | |
| Hardware components | Standard telecommunications and<br>IT components:<br>1. Wireless VoIP handset or other<br>endpoint device<br>2. Access point<br>3. Switch/router<br>4. Server<br>5. Phone switch using access<br>point(s)<br>6. Pagers and/or handsets, PDAs | Same | |
#### Test Summary
The EXTENSION Clinical Alert Notification solution complies with the voluntary standards as detailed in Section 9 of this submission. The following quality assurance measures were applied to the development of the EXTENSION Clinical Alert Notification solution:
- · Risk analysis
- · Design reviews
- · Component level testing
- System level testing
- · Performance testing
- · Safety testing
- Usability and validation testing
#### Conclusions
The information in this 510(k) submission demonstrates that the EXTENSION Clinical Alert Notification solution is substantially equivalent to the predicate devices as a supplementary alarm system, with respect to safety, effectiveness, and performance.
{3}------------------------------------------------
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-002
July 11, 2013
Extension , Inc c/o Mr. Tim Gee 7250 SW 154th Terrace Beaverton, OR 97007
Re: K130339
> Trade/Device Name: Clinical Alert Notification System Regulation Number: 21 CFR 870.2300 Regulation Name: System, Network and Communication, Physiological Monitors Regulatory Class: Class II Product Code: MSX Dated: June 12, 2013 Received: June 13, 2013
Dear Mr. Tim Gee:
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. Tim Gee
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 go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHOffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. 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.htmfor 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 Small Manufacturers, International and Consumer Assistance 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,
Owen-Paris-S
for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
{5}------------------------------------------------
K130339 Page 1 of 1 510(k) Number (if known):
Device Name: EXTENSION Clinical Alert Notification
Indications for use:
The EXTENSION Clinical Alert Notification solution is a closed loop communications system that interfaces with health care information systems and medical devices to provide a secondary means of annunciating and displaying patient alarm text and other information to mobile health care workers that is important to patient care, nursing vigilance and overall hospital operations. The EXTENSION Clinical Alert Notification solution alerts and informs the clinician about citical patient alarms by drawing an identified individual's attention to a defined pattent condition in a timely manner without requiring them to be at or near the bedside medical devices or central station displays. The EXTENSION Clinical Alert Notification is not intended to replace any part of the patient monitoring system or procedures already existing for the medical devices interfaced with the EXTENSION Clinical on solution.
The EXTENSION Clinical Alert Notification is limited to use by qualified medical professionals who have been trained on the use of the device. It is intended for use in hospital type acute care environments and is not for home use.
Prescription Use __
And/Or
Over-the-Counter-Use: _
(Per 21 CFR 801 Subpart D)
(Per 21 CFR 801 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Digitally signed by Owen
Date: 2013.07.11 14:25:09
-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.