The RTX3320 device is for use by patients at home. It is intended to be used in combination with a variety of patient monitors upon the prescription of a licensed physician or other authorized healthcare provider. RTX3320 serves as the remote communication link between compatible patient monitors, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center, or with the healthcare/wellness provider or other out-of-hospital caregivers. The purpose is to transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line. RTX3320 is a "black box" device – it is not connected to the patient and not operated by the patient. The installation must be performed by or under supervision of an authorized professional healthcare company. This device does not measure, interpret or make any decisions on the vital data that it conveys.
Device Story
RTX3320 Wireless Telehealth Gateway acts as a 'black box' communication hub; receives physiological data (weight, BP, glucose, ECG) from compatible wireless patient monitors via Bluetooth; transmits data over public switched telephone network to remote healthcare servers. Installed by authorized professionals; not operated by patients. Device performs no measurement, interpretation, or clinical decision-making. Healthcare providers receive transmitted data at remote facilities to support clinical management. Benefits include remote monitoring of chronic conditions without requiring patient interaction with the gateway.
Clinical Evidence
Bench testing only. No clinical investigation performed. Verification and validation activities established performance and reliability. Compliance with IEC 60601-1, IEC 60601-1-2, FCC Part 15, and FCC Part 68 demonstrated.
Technological Characteristics
Hub/gateway device; Bluetooth wireless connectivity to patient monitors; PSTN modem for data transmission. Designed for home use. Standards: IEC 60601-1 (safety), IEC 60601-1-2 (EMC), FCC Part 15 (radio), FCC Part 68 (telecom). Risk management per ISO 14971:2000.
Indications for Use
Indicated for home-based patients requiring remote transmission of physiological data (e.g., weight, BP, glucose, ECG) from compatible monitors to healthcare facilities. Not for emergency calls, real-time alarms, time-critical data, or patients requiring direct medical supervision/emergency intervention.
Regulatory Classification
Identification
A radiofrequency physiological signal transmitter and receiver is a device used to condition a physiological signal so that it can be transmitted via radiofrequency from one location to another, e.g., a central monitoring station. The received signal is reconditioned by the device into its original format so that it can be displayed.
Predicate Devices
M3810A Philips Telemonitoring System with M3812B TeleStation (K023749)
{0}------------------------------------------------
KC4816
page 1 of 4
JUL 1 9 2004
Image /page/0/Picture/2 description: The image shows the logo for RTX Healthcare. The logo consists of the letters "RTX" in a bold, sans-serif font. To the right of the letters, there is a stylized arrow pointing to the right. Below the logo, the words "RTX Healthcare" are printed in a smaller, sans-serif font.
### 510(k) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirement of 21 CFR 807.92
| Submitter: | Bjarne Flou |
|------------------|----------------------|
| | Managing Director |
| | RTX Healthcare |
| | Stroemmen 6 |
| | DK-9400 Noerresundby |
| | Denmark |
| | Tel: +45 96322300 |
| | Fax: +45 96322310 |
| | Email: bf@rtx.dk |
| Contact person: | Niels Ole Andersen |
| | Engineering Manager |
| | Email: noa@rtx.dk |
| Date of summary: | 04/15/2004 |
Physiological Transmitter and Receiver Common Name: Trade name: RTX3320 Wireless Telehealth Gateway
Classification name:21 CFR 870.2910 Physiological Signal Transmitter And Receiver. Classification no: DRG
#### Predicate Device:
The RTX3320 device is substantially equivalent to the following predicate device: 510(k) number: K023749 Device name: M3810A Philips Telemonitoring System with M3812B TeleStation. Applicant: Philips Medical Systems
#### Submission Device Description:
The RTX3320 telemedicine device perform transmission of physiological patient information to and from wireless patient monitors, and a remote data server healthcare facility using standard digital communication technologies and protocols.
The RTX3320, with its build-in modem, transmits data using the public switched telephone network. It is designed not to interfere with the normal use of phones on the same telephone line.
The RTX3320 device is not operated by, or used directly on a patient, and poses no significant risk to the patient or other people within the patient's home.
#### Intended use and indications for use:
The RTX3320 device is for use by patients at home. It is intended to be used in combination with a variety of patient monitors upon the prescription of a licensed physician or other authorized healthcare provider. RTX3320 serves as the remote communication link between compatible patient monitors, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center, or with the healthcare/wellness provider or other out-of-hospital caregivers.
{1}------------------------------------------------
The purpose is to transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line.
RTX3320 is a "black box" device – it is not connected to the patient and not operated by the patient. The installation must be performed by or under supervision of an authorized professional healthcare company.
This device does not measure, interpret or make any decisions on the vital data that it conveys.
#### Contraindications, precautions and warnings
This device is not intended for emergency calls, and may not be used for transmission or indication of any real-time alarms or time-critical data.
Clinical judgement and experience are required to check and interpret the measurements collected and transmitted.
This device is not for use in systems which substitute for medical care.
This device is not intended for patients requiring direct medical supervision or emergency intervention.
| Item | Predicate device | Submission device | |
|------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Intended use / Indication for use | See section 6. | See section 2. |
| 2 | Intended users | Home users and healthcare providers. | Home users and healthcare providers. |
| 3 | Site of use | Typically for use in patient's home, placed on a normal table. | Typically for use in patient's home, placed on a normal table. |
| 4 | Prescription | The device is intended to be used upon prescription of a licensed physician or authorized healthcare provider. | The device is intended to be used upon prescription of a licensed physician or authorized healthcare provider. |
| 5 | System description | Telemedicine system consisting of a device that is working as hub/gateway sending data measured by the system patient monitors to a system data server. | Telemedicine device that is working as hub/gateway sending measured data from compatible patient monitors to a compatible data server. |
| 6 | Wireless patient monitors | Wireless connection between the patient monitors and the hub/gateway. | Wireless connection between the patient monitors and the hub/gateway. |
| 7 | Transmission | Residential telephone lines | Residential telephone lines |
| 8 | Patient Interactions | Display and push buttons for collection of patient typed data | No patient interaction. ("Black box") |
| 9 | Measurements taken | Blood pressure, weight, ECG and Blood glucose | Blood pressure, weight, ECG, Blood glucose and other measurements provided from compatible monitor devices. |
| 10a | Contra indications and warnings | The device does not send any real time alarms. | The device is not for emergency calls, and may not be used to send any real-time alarms or time-critical data |
#### Substantial Equivalence Comparison table
{2}------------------------------------------------
KC41816
Page 3 of 4
| 10b | Contra indications<br>and warnings | Clinical judgment and<br>experience are required to<br>check and interpret the<br>information delivered. | Clinical judgment and<br>experience are required to<br>check and interpret the<br>measurements that are taken,<br>collected, and delivered by<br>systems using a RTX3320<br>device. |
|-----|-----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 10c | Contra indications<br>and warnings | The device is not intended as a<br>substitute for medical care. | The device is not for use in<br>systems which substitute for<br>medical care. |
| 10d | Contra indications<br>and warnings | The device is not for use in<br>systems set up for patients who<br>need direct medical supervision | The device is not for use in<br>systems set up for patients who<br>need direct medical supervision<br>or who might need emergency<br>intervention. |
| 11 | Wireless link<br>between patient<br>monitors and the<br>gateway | Short range radio system. | Short range radio system using<br>Bluetooth technology. |
| 12 | Environmental<br>specifications | Proprietary information | See section 5. |
| 11 | Wireless link<br>between patient<br>monitors and the<br>gateway | Short range radio system. | Short range radio system using<br>Bluetooth technology. |
| 12 | Environmental<br>specifications | Proprietary information | See section 5. |
#### Discussion on differences:
ltem 1: The intended use / Indications for use for the predicate device and submission device is generally the same. The exact use is for both devices to be decided and supervised by a licensed physician or an authorized healthcare provider, but limited to be within the intended use and with respect to the contra indications and warnings which are also generally the same for both devices.
ltem 5 The predicate device is a system consisting of patient monitor devices, a hub/gateway device and a system server software. The Submission device is a hub/gateway device with a specified generic protocol interface to any compatible patient monitor, and with a specified generic protocol interface to any compatible system server. The protocols are validated against existing compatible patient monitors and servers, and in the labeling it is stated that only compatible and system validated patient monitors and servers must be used with the hub/gateway.
Verfication and validation done on the compatible patient monitors ensure that no extra safety or performance risks are added when using the submission device compared with the predicate device.
The server side and database management must always be validated by the responsible system operator or provider, and using the generic and properly documented protocol adds no extra safety or performance risks to a system using the submission device compared to the predicate device.
{3}------------------------------------------------
Kc41816
page 4 of 4
It is very important to state that both the predicate and the submission device may only be n is very important to other that both the presence is used to check and interpret the measurements that are taken, collected and transmitted by the devices.
that are taken, bonoots and is fitted with a display and some push buttons for patient interaction. The purpose is to collect some additional information from the patient. The interaction device is not fitted with a display, and no user interaction is possible or necessary to perform the intended use.
hecossary to portom the internable assess physiological parameters as the predicate device r to oubmibolon as now over otheraction on the device. If additional information is needed this may be achieved by a normal voice phone call.
may be arrithe predicate device the measurements taken are defined by the patient momitors that are a part of the system. For the submission device the measurements taken mention and by the specific compatible patient monitors. Because of the similar intended use and indication for use for both the predicate device and the submission device, the measurements will typically be the same.
Inoded.omomonik thir typecifications about the wireless link between the patient monitors and the Gateway for the predicate device are proprietary and not available for RTX Healthcare. Based on the knowledge available as a leading company within wireless connectivity RTX Healthcare has evaluated that many different short range radio solutions are suitable for this type of devices without adding any additional risks to the patient. RTX Healthcare has chosen the Bluetooth wireless technology used in other medical devices like the Nonin Pulseoximeter (FDA-K041156 ) developed by RTX Healthcare. The general radio signal safety requirements and FCC Part 15 rules are regulatory requirements that are equal for both the predicate device and the submission device. Since the only purpose using a wireless radio link is to replace a cable, the wireless link in the submission device is evaluated not to add any additional risks within the intended use compared to the predicate device.
Item 12: Detailed environmental specifications for the predicate device are proprietary and not available for RTX Healthcare. This is evaluated not to add any additional risks to the patient since both the predicate device and the submission device, according to the intended use, are designed for use by patients at home. The environmental specifications for the submission device are defined according to IEC60601-1 and specifications available for other medical devices for home use.
#### Performance data:
The RTX3200 device has been tested to meet the requirements of the following standards and regulations used as acceptance criteria:
IEC 60601-1, IEC 60601-1-2, FCC part 15 and FCC Part 68.
Risk management is performed according to ISO14971:2000.
Based on the fact that the performance comparison of the predicate device and the submission device show that the differences are minor and causes no harm to the user, and the fact that the intended use and indication for use is the same, it was early in the project decided to focus on verification and internal validation instead of large scale validation in form of clinical investigation.
Verification and validation testing activities is conducted to establish performance and reliability characteristics of the device.
{4}------------------------------------------------
DEPARTMENT OF HEALTH & HUMAN SERVICES
Image /page/4/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo features a stylized caduceus, a symbol often associated with medicine and healthcare, consisting of a staff with two snakes coiled around it. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" is arranged in a circular fashion around the caduceus. The logo is presented in black and white.
Public Health Service
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
JUL 1 9 2004
RTX Healthcare A/S c/o Dr. J.A. van Vugt Certification Manager KEMA Quality B.V. Utrechtseweg 310, NL-6812 AR Arnhem P.O. Box 5185, 6802 ED Arnhem THE NETHERLANDS
Re: K041816
Trade Name: RTX3320 Wireless Telehealth Gateway Regulation Number: 21 CFR 870.2910 Regulation Name: Radiofrequency Physiological Signal Transmitter and Receiver Regulatory Class: II (two) Product Code: DRG Dated: July 2, 2004 Received: July 6, 2004
Dear Dr. van Vugt:
We have reviewed your Section 510(k) premarket notification of intent to market the device we nave reviewed your bocurity is the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate for use stated in the encrosuly to regars and ment date of the Medical Device Amendments, or to commence prior to May 20, 1978, the encordance with the provisions of the Federal Food, Drug, devices mat have occh recultion in assee approval of a premarket approval application (PMA). and Cosmetic Act (Act) that do not requent of the general controls provisions of the Act. The I ou may, merclore, maniel the Act include requirements for annual registration, listing of general controls provisions of the rees, 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 IT your device is classified (500 abs. 19) als. Existing major regulations affecting your device can
may be subject to such additional controls. Existing major regulations may be subject to suer additions, Title 21, Parts 800 to 898. In addition, FDA may be found in the Oode of Peachar Singerning your device in the Federal Register.
{5}------------------------------------------------
Page 2 - Dr. J.A. van Vugt
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 (301) 594-4648. 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 (301) 443-6597 or at its Internet address http://www.fda.gov/cdrh/dsma/dsmamain.html
Sincerely yours.
Neil McOglin
Bram D. Zuckerman, M. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{6}------------------------------------------------
#### 3. Indications for use statement
# Indication for Use Statement
#### 510(k) Number (if known):
Device name: RTX3320 Wireless Telehealth Gateway
#### Indications for Use:
The RTX3320 device is for use by patients at home. It is intended to be used in combination with a variety of patient monitors upon the prescription of a licensed physician or other authorized healthcare provider. RTX3320 serves as the remote communication link between compatible patient monitors, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center, or with the healthcare/wellness provider or other out-of-hospital caregivers.
The purpose is to transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line.
RTX3320 is a "black box" device – it is not connected to the patient and not operated by the patient. The installation must be performed by or under supervision of an authorized professional healthcare company.
This device does not measure, interpret or make any decisions on the vital data that it conveys.
## Contraindications, precautions and warnings
This device is not intended for emergency calls, and may not be used for transmission or indication of any real-time alarms or time-critical data.
Clinical judgement and experience are required to check and interpret the measurements collected and transmitted.
This device is not for use in systems which substitute for medical care.
This device is not intended for patients requiring direct medical supervision or emergency intervention.
Prescription Use X (Part 21 CFR 801 Subpart D) AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Nil R.P. Ogle
+N DDZ
(Division Sian-Off
**Division of Cardiovascular Devices**
510(k) 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.