K083862 · Medapps, Inc. · DRG · Jun 5, 2009 · Cardiovascular
Device Facts
Record ID
K083862
Device Name
MEDAPPS 2.0 REMOTE PATIENT MONITORING SYSTEM
Applicant
Medapps, Inc.
Product Code
DRG · Cardiovascular
Decision Date
Jun 5, 2009
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2910
Device Class
Class 2
Indications for Use
The MedApps 2.0 - Remote Patient Monitoring System consists of a patient device, MedApps HealthPAL, which is a mobile Over-The-Counter wireless communication hub that connects to commercially available wireless and tethered Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters. The HealthPAL stores and displays the information on the OLED screen, and transmits the information to the MedApps secure host server called "HealthCOM" using off the shelf FCC approved wireless / cellular connectivity (including, but not limited to GSM, CDMA and WiMax). Healthcare professionals can review the transmitted information within the MedApps HealthCOM system, set thresholds to flag readings based on specific thresholds being exceeded. In addition, the MedApps Interactive Voice Response (IVR) has the ability to contact the patient remotely and use pre-approved ("canned") educational or reminder messages. ("Your nurse would like to talk to you, can I connect you now", "We haven't received a reading from you today, please send us your readings"). The MedApps 2.0 - Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, and it is not intended to provide real time data. The data is made available to the patients when time-critical care is not required. The device is contraindicated for patients requiring direct medical supervision or emergency intervention.
Device Story
MedApps 2.0 is a remote patient monitoring hub (HealthPAL) connecting to home-use medical devices (glucose meters, scales, BP monitors, pulse oximeters) via Bluetooth or wired cables. It collects, stores, and displays physiological data on an OLED screen and transmits it to a secure server (HealthCOM) via cellular/wireless networks. Healthcare professionals review data and set thresholds for alerts. An Interactive Voice Response (IVR) system provides automated patient reminders and educational messages. The system facilitates data transfer to PHR/EHR systems. Used in home settings by patients; monitored by clinicians in clinics. Benefits include improved patient adherence and remote oversight of chronic conditions without requiring real-time intervention.
Clinical Evidence
No clinical data. Bench testing only. Verification and validation included alpha testing of all executable code, functionality, and hazard mitigation. Operational performance data was generated by simulating a sophisticated user environment to confirm design specifications were met.
Technological Characteristics
System includes HealthPAL (OLED screen, M2M cellular chip, Bluetooth/wired interfaces), HealthLINK (docking), and HealthPOD (recharge/backup comms). Connectivity via GSM, CDMA, WiMax, Bluetooth, Zigbee, ANT, ULP. Power via wall plug or rechargeable batteries. Software manages data capture, transmission, and IVR scripts.
Indications for Use
Indicated for patients managing chronic conditions requiring remote monitoring of glucose, weight, blood pressure, or pulse oximetry. Contraindicated for patients requiring direct medical supervision or 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.
MedApps Remote Patient Monitoring System (D-PAL) (K062377)
Submission Summary (Full Text)
{0}------------------------------------------------
### MedApps, Inc. 510(k) SUMMARY
. K083862
P.1/7
PREMARKET NOTIFICATION 510(k) SUMMARY
As required by 21 CFR §807.92(c)
### Submitter
510(k) Owner: MedApps, Inc. Owner / Operator: 10027842 Registration : 3005916763 7975 North Hayden Road, Suite A-200, Scottsdale, AZ 85258 Address: Telephone: 480-305-6323 480-393-1892 Fax Number: Contact Person: Kent Dicks Contact Person Title: President / CEO December 23, 2008 Date Prepared:
### Device Information
| Trade Name: | MedApps 2.0 - Remote Patient Monitoring System |
|------------------------|------------------------------------------------------------------------------------------------------|
| Common Name: | Remote Patient Monitoring System |
| Classification Status: | Class II per regulations 870.2910 |
| Classification Name: | Transmitters and Receivers, Physiological Signal, Radiofrequency (21 CFR 870.2910. Product Code DRG) |
#### LEGALLY MARKETED PREDICATE DEVICE A.
Legally marketed predicate device are: Intel Health Guide PHS6000 K080798 K072698 Confidant 2.5 MedApps Remote Patient Monitoring System (D-PAL) K062377
#### B. DEVICE DESCRIPTION
The MedApps 2.0 - Remote Patient Monitoring System consists of a patient device, MedApps HealthPAL, which is a mobile Over-The-Counter wireless communication hub that connects to commercially available wireless and tethered Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters. The HealthPAL stores and displays the information on the OLED screen, and transmits the information to the MedApps secure host server called "HealthCOM" using off the shelf FCC approved wireless / cellular connectivity (including, but not limited to GSM, CDMA and WiMax). Healthcare professionals can review the transmitted information within the MedApps HealthCOM system, set thresholds to flag readings based on specific thresholds being exceeded. In addition, the MedApps Interactive Voice Response (IVR) has the ability to contact the patient remotely and use pre-approved ("canned") educational or reminder messages. ("Your nurse would like to talk to you, can I connect you now", "We haven't received a reading from you today, please send us your readings").
{1}------------------------------------------------
K083862 p. 2/7
The HealthCOM system allows the patient to login and create a personal account. The patient can specify / authorize which Personal Health Record (PHR) or Electronic Health Record (EHR / EMR) they would like to send / view their data within, outside of the HealthCOM system.
The MedApps 2.0 - Remote Patient Monitoring System uses MedApps Accessories that help the patient in usability of the product, including HealthLINK which docks the HealthPAL, and HealthPOD which connects to off the shelf medical devices via their data port to transmit data via wireless or RF technology (including, but not limited to bluetooth, zigbee, ANT, ULP, etc.).
The MedApps 2.0 - Remote Patient Monitoring System consists of:
(1) MedApps HealthPAL hardware:
The physical component of the MedApps HealthPAL is an electronic device contained in a plastic enclosure with an OLED screen, built-in M2M cellular chip, speaker, smart cable connection, smart cables, wireless, LED Lights to indicate activity, timer button to remind the patient to take their reading in X minutes, last reading button, volume up and down buttons.
- (2) MedApps HealthPAL software application:
The software application captures, stores and transmits information to the MedApps HealthCOM server, via the embedded communication chip / platform.
The software application takes in additional information via the embedded wireless module from other medical devices that are wireless enabled, and that have been paired to the MedApps HealthPAL.
The software application has many additional functions including:
- Download of the users profile from the server to configure the . HealthPAL remotely. .
- Ability to "talk" to the patient with verbal acknowledgments of . readings from all attached medical devices, time settings, volume control, educational content and reminders, in any language that is loaded to the device.
- Timer set that was activated by the user at a set timeframe to ● do whatever they wanted to be reminded to do.
- Control the OLED screen to show certain information including, . battery status, volume level, transmission status, message waiting indicator, medical device last reading, activity icons / messages and more as it pertains to provide ease of use and easier adoption for the patient.
- Battery charging, isolation circuits, and interfaces to individual . medical devices / protocols via the smart cables.
{2}------------------------------------------------
### MedApps, Inc. 510(k) SUMMARY
K083862 p.3/7
- . For complete comparison of predicate devices see paragraph D - TECHNOLOGICAL CHARACTERISTICS SUMMARY table below. please reference Exhibit 08 - System Additionally, Requirements Specifications (FDA-SRS-8009) document for complete software / system functionality.
- (3) MedApps HealthLINK hardware / software:
The HealthLINK hardware / software plugs into off the shelf Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters, and transmit the data via wireless to a receiver that it is already paired with. This functionality was cleared in the MedApps D-PAL submission K062377 in July 2007.
- (4) MedApps HealthPOD hardware / software:
The HealthPOD hardware / software is an extension of the HealthPAL functionality that is outlined in this submission. HealthPOD acts as a "docking" station for the HealthPAL in order to recharge batteries, take in additional connections to off the shelf Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters, via smart cables (per validated in HealthPAL software), add a backup communication method via phone line (POTS line), and communicate via wireless to HealthPAL or additional HealthPODs.
- (5) MedApps HealthCOM software application:
The software application allows caregivers to set thresholds and review patient data on the secure HealthCOM website.
The HealthCOM software also allows the patient to establish an account and to direct / authorize their data to be directed to an outside, validated Personal Health Record (PHR), Electronic Health Record (EHR or EMR).
- (6) MedApps IVR software application:
The software application calls the patient on any phone that is designated in their user profile, and executes an approved ("canned") script to gather information. ("Your nurse would like to talk to you, can I connect you now", "We haven't received a reading from you today, please send us your readings").
In addition, the MedApps IVR application will send out Email, SMS / Text Messages, Paging, IM and many other forms of communications in order to contact patients or caregivers. This will include reminders and alerts, based on parameters / thresholds set in the HealthCOM system.
{3}------------------------------------------------
K083862 p. 4/7
#### INDICATIONS FOR USE C.
The MedApps 2.0 - Remote Patient Monitoring System consists of a patient device, MedApps HealthPAL, which is a mobile Over-The-Counter wireless communication hub that connects to commercially available wireless and tethered Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters. The HealthPAL stores and displays the information on the OLED screen, and transmits the information to the MedApps secure host server called "HealthCOM" using off the shelf FCC approved wireless / cellular connectivity (including, but not limited to GSM, CDMA and WiMax). Healthcare professionals can review the transmitted information within the MedApps HealthCOM system, set thresholds to flag readings based on specific thresholds being exceeded. In addition, the MedApps Interactive Voice Response (IVR) has the ability to contact the patient remotely and use pre-approved ("canned") educational or reminder messages. ("Your nurse would like to talk to you, can I connect you now", "We haven't received a reading from you today, please send us your readings").
The MedApps 2.0 - Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, and it is not intended to provide real time data. The data is made available to the patients when time-critical care is not required. The device is contraindicated for patients requiring direct medical supervision or emergency intervention.
| Feature | Intel Health<br>Guide PHS6000<br>K080798 | Confidant 2.5<br>K072698 | MedApps<br>Submission<br>K083862 |
|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
| Indications of<br>Use | Enables healthcare<br>providers to<br>monitor and<br>manage chronic<br>conditions of<br>patients remotely | Same | Same |
| Intended Use | Telemedicine<br>System | Same | Same |
| Intended Users | Home users and<br>Healthcare<br>providers | Same | Same |
| Site of Use | Home (HealthPAL),<br>Clinic (HealthCOM) | Same | Same |
| Data Collection<br>Software | Intel Care<br>Management Suite<br>Software | The Hermes<br>Proprietary<br>Software | MedApps<br>Proprietary<br>Software |
| SUMMARY | | | K083862 |
| Feature | Intel Health<br>Guide PHS6000 | Confidant 2.5 | MedApps<br>Submission |
| | K080798 | K072698 | K083862 |
| Data Collection<br>Software<br>Functionality | Transmit data from<br>Sensor devices to<br>Central Database | Same | Same |
| Communication<br>method of hub<br>with Central<br>Server | Via DSL or Phone<br>Line Connection | Via Cellular Phone | Via Embedded<br>Cellular<br>Technology |
| Types of sensors<br>which can be<br>interfaced (wired<br>or wirelessly) to<br>receiver hub | Medical Devices<br>designed for<br>Home:<br>Glucose<br>Scale<br>Blood Pressure<br>Pulse Ox<br>Peak Flow | Medical Devices<br>designed for<br>Home:<br>Glucose<br>Scale<br>Blood Pressure | Medical Devices<br>designed for<br>Home:<br>Glucose<br>Scale<br>Blood Pressure<br>Pulse Ox |
| Maximum<br>number and type<br>of measurement<br>devices that can<br>be connected to<br>the devices | Determined by<br>vital sign devices<br>that are designed<br>for Home use, and<br>have a data port.<br>(Wireless or Wired) | Same | Same |
| Maximum data<br>throughput<br>under worst case<br>conditions | Multiple readings<br>are stored on the<br>medical devices<br>and act as a<br>backup if data<br>needs to be re-sent<br>to the server | Same | Same |
| Time Delay in the<br>processing of<br>data collected<br>and transmitted | Readings stored in<br>the medical<br>devices can be sent<br>up to the server<br>when the<br>connection is<br>restored. | Same | Same |
| Implementation<br>method of<br>collecting data<br>from sensors | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. | Short range radio<br>system using<br>Bluetooth | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. |
| Sensor Software | Sensor Software<br>unchanged | Same | Same |
| Connectivity | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. | Short range radio<br>system using<br>Bluetooth | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. |
| Communication<br>method of hub<br>with devices | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. | Short range radio<br>system using<br>Bluetooth | Short range radio<br>system using<br>Bluetooth and<br>Wired (tethered)<br>cables. |
| SUMMARY | | | |
| Feature | Intel Health<br>Guide PHS6000<br>K080798 | Confidant 2.5<br>K072698 | MedApps<br>Submission<br>K083862 |
| Communications<br>Protocol | Bluetooth V2.0 and<br>Wired (Tethered) | Bluetooth V2.0 | Bluetooth V2.0 and<br>Wired (Tethered) |
| Communication<br>Frequency | Bluetooth : 2.402<br>to 2.480 GHz | Bluetooth : 2.402<br>to 2.480 GHz<br>GSM: 850 / 900 /<br>1800 / 1950 Mhz | Bluetooth : 2.402<br>to 2.480 GHz<br>GSM: 850 / 900 /<br>1800 / 1950 Mhz |
| Power Source | Wall power plug<br>(120 VAC/50-60) | Wall power plug<br>(120 VAC/50-60)<br>and Rechargeable<br>Batteries in Device | Wall power plug<br>(120 VAC/50-60)<br>and Rechargeable<br>Batteries in Device |
| Display | On devices and<br>hub, and monitors<br>connected to<br>central server | Same | Same |
| Communication<br>with Patients | On screen display | Same | On screen display<br>of Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) |
| Use of<br>Thresholds /<br>Algorithms for<br>determining how<br>Thresholds are<br>set and changed | Thresholds are set<br>by Healthcare<br>professionals in<br>Server Software | Same | Same |
| Information<br>presented to the<br>user, if it is<br>different from<br>that presented<br>by the<br>measurement<br>devices | On screen display | Same | On screen display<br>of Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) |
| Messages and<br>Instructions that<br>can be sent to<br>the User. | On screen display | Same | On screen display<br>of Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) |
#### TECHNOLOGICAL CHARACTERISTICS SUMMARY - as required by D. 807.92(a)(6)
{4}------------------------------------------------
:
:
、
:
.
:
.
・
、
. . . . . . .
:
# EXHIBIT 02
:
{5}------------------------------------------------
## Data Collection:
The 2 predicates and the MedApps solution connect to medical devices (designed for home use) via either through wired (cable) or wireless (bluetooth). The data is collected from the devices and sent up to the central server via various communication methods.
# Telecommunication Platform to Central Server:
Intel Health uses DSL connectivity (wired point of care), Confidant uses an off the shelf Cell Phone (Cellular), and MedApps uses an embedded Machine to Machine (M2M) module that transmits the data via cellular connectivity.
{6}------------------------------------------------
**EXHIBIT 02**
K083862 p.7/7
## Patient Feedback Technology:
On the 2 predicates and MedApps, data and messages are displayed on a screen for the patient to read and acknowledge. The MedApps solution also uses an Interactive Voice Response (IVR) system in order to call up the patient and ask them a question, or remind them to take their readings.
#### Backend Data Storage:
All systems (2 predicates and MedApps), have a backend system that allows data to be stored, and for Healthcare professionals to have the ability to monitor the patients data.
#### NON-CLINICAL PERFORMANCE DATA TESTING AND REVIEW - as E. required by 807.92(b)(1)
#### Non-Clinical Testing
The submitted device has undergone significant verification and validation testing, Alpha validation testing included testing of all executable code and functionality and confirmation that all identified hazards have been adequately addressed by software functionality, the user interface, documentation or user SOP.
Alpha validation activities included exhaustive validation scripts of all Detail Design Specifications (DDS), which was summarized and discussed to provide a preliminary record of performance data. Additionally, the submitter duplicated the operational environment of a sophisticated user and provided the complete record of those executed scripts as operational performance data. The output of these two performance data records documents that MedApps 2.0 - Remote Patient Monitoring System met its required requirements and design specifications as intended.
#### F. SUBSTANTIAL EQUIVALENT
The MedApps Remote Patient Monitoring System 2.0 is substantially equivalent to the predicate devices in terms of data collection software functionality, operating system for the patient device, communication method of patient device with central server, types of sensors which can be interfaced to the patient device, implementation method of collecting data from sensors, sensor software, connectivity, communication protocol, power source and display method.
#### G. SAFETY AND EFFICACY
The MedApps Remote Patient Monitoring System 2.0 does not rely on an assessment of clinical performance data. The device conforms to FDA's recognized consensus standards and relies on its conformity to demonstrate its safety and efficacy. The device introduces no new questions concerning the safety or efficacy and is, therefore, substantially equivalent to the predicate devices.
{7}------------------------------------------------
## DEPARTMENT OF HEALTH & HUMAN SERVICES
Image /page/7/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo features a stylized eagle with its wings spread, and the words "DEPARTMENT OF HEALTH & HUMAN SERVICES. USA" are arranged in a circular pattern around the eagle. The eagle is black, and the text is also black. The background is white.
#### Public Health Service
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850 ..
JUN ~ 5 2009
MedApps, Inc. c/o Mr. Kent Dicks President & CEO 7975 North Hayden Road, Suite A-200 Scottsdale, AZ 85258
Re: K083862
Trade/Device Name: MedApps 2.0 Remote Patient Monitoring System Regulation Number: 21 CFR 870.2910 Regulation Name: Radiofrequency physiological signal transmitter and receiver Regulatory Class: Class II Product Code: DRG Dated: March 31, 2009 Received: April 1, 2009
Dear Mr. Dicks:
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 additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical
{8}------------------------------------------------
## Page 2 - Mr. Kent Dicks
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/cdrh/mdr/ for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of 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,
Dina R. Rohner
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{9}------------------------------------------------
| MedApps, Inc. |
|----------------------------------|
| STATEMENT OF INDICATIONS FOR USE |
510(k) Number: _K083862
Preparation Date:
December 23, 2008
Device Name:
### MedApps 2.0 - Remote Patient Monitoring System
Indications For Use:
The MedApps 2.0 - Remote Patient Monitoring System consists of a patient device, MedApps HealthPAL, which is a mobile Over-The-Counter wireless communication hub that connects to commercially available wireless and tethered Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters. The HealthPAL stores and displays the information on the OLED screen, and transmits the information to the MedApps secure host server called "HealthCOM" using off the shelf FCC approved wireless / cellular connectivity (including, but not limited to GSM, CDMA and WiMax). Healthcare professionals can review the transmitted information within the MedApps HealthCOM system, set thresholds to flag readings based on specific thresholds being exceeded. In addition, the MedApps Interactive Voice Response (IVR) has the ability to contact the patient remotely and use pre-approved ("canned") educational or reminder messages. ("Your nurse would like to talk to you, can I connect you now", "We haven't received a reading from you today, please send us your readings").
The MedApps 2.0 - Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, and it is not intended to provide real time data. The data is made available to the patients when time-critical care is not required. . The device is contraindicated for patients requiring direct medical supervision or emergency intervention.
(PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Prescription Use (Per 21 CFR 801.109) OR Over-The-Counter Use
X
Dunia R. James
Division of Cardiovascular Devices
510(k) Number K083862
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.