MEDAPPS 2.0 REMOTE PATIENT MONITORING SYSTEM, HEALTHPAL, HEALTHCOM, MOBILE LINK
Applicant
Medapps Inc., Dba Alere Connect
Product Code
DRG · Cardiovascular
Decision Date
Dec 12, 2013
Decision
SESE
Submission Type
Special
Regulation
21 CFR 870.2910
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The MedApps (Alere Connect) 2.0 - Remote Patient Monitoring System consists of 1) a cellular communication hub (MedApps' HealthPAL, Alere™ MobileLink or Alere™ HomeLink) an over-the-counter device that resides with the end-user (patient), which connects to commercially available FDA cleared accessory devices, specifically glucose meters, scales, blood pressure monitors, pulse oximeters, and PT/INR monitors (excluding HomeLink) and 2) web-based health data management application (MedApps' HealthCOM), that provides access to collected data stored on a secure host server system. MedApps / Alere Connect Remote Patient Monitoring devices receive and store measurements collected from the described accessory devices, either wirelessly using short-range radio protocols (e.g. Bluetooth, Zigbee, WiFi, Bluetooth Low Energy (BLE), Fitlinxx Radios) or tethered via cable (e.g. USB, serial, etc.). Regardless of connectivity mode, the MedApps / Alere Connect monitoring devices do not alter the indications for use of the described peripheral accessory health devices. MedApps / Alere Connect devices indicate successful or failed data reception and transmission with visual and audio feedback using a combination of any of the following: Display, LED Lights, verbal messages, and / or audio tones / chimes. MedApps / Alere Connect devices store collected data and forward / transmit to server for access in HealthCOM via commercially available, FCC compliant, wireless telecommunication protocols (including but not limited to cellular GSM, CDMA and WiMax). Healthcare professionals, clinicians and other authorized personnel can review the transmitted information within the MedApps HealthCOM system, where they can review collected readings, establish parameters to indicate readings exceptions to set thresholds, or trigger Interactive Voice Response (IVR) messages to the patient remotely to issue information such as reminders (e.g. "We haven't received readings from you today, please take and send your readings") or possibly educational information for conditions such as diabetes, hypertension, CHF, etc. Additionally, HealthCOM can port collected data to the healthcare providers' clinical back-end system(s) of choice. The MedApps /Alere Connect 2.0 Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, nor is it intended to provide realtime / time-critical data. The device is contraindicated for patients requiring direct medical supervision or emergency intervention.
Device Story
System acts as conduit for biometric data from FDA-cleared accessory devices (glucose meters, scales, BP monitors, pulse oximeters, PT/INR monitors) to secure cloud server (HealthCOM). Hubs (HealthPAL, MobileLink, HomeLink) collect data via Bluetooth, BLE, Zigbee, WiFi, or wired (USB/serial) connections. Hubs transmit data via cellular (GSM/CDMA) to HealthCOM. Clinicians review data, set thresholds for alerts, and trigger IVR reminders/educational content. HomeLink device includes touch screen for patient interaction with IVR questions. Used in home/remote settings by patients; clinicians access data via web portal. System provides no real-time/time-critical data; not for diagnosis. Benefits include improved patient adherence and remote data access for chronic condition management (diabetes, hypertension, CHF).
Clinical Evidence
Bench testing only. No clinical data provided. Verification and validation testing confirmed system functionality, integration with accessory devices, and software performance against design specifications.
Technological Characteristics
Hubs (HealthPAL, MobileLink, HomeLink) in plastic enclosures with OLED/touch screens. Connectivity: Bluetooth, BLE, Zigbee, WiFi, USB, serial. Cellular: GSM/CDMA. Power: AC adapter/rechargeable battery. Safety: IEC 60601-1 3rd Ed, IEC 60601-1-2 (EMC). Firmware: C language, RTOS (MobileLink/HomeLink).
Indications for Use
Indicated for patients requiring remote monitoring of biometric data (glucose, weight, blood pressure, oxygen saturation, PT/INR) via OTC hubs. 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.
{0}------------------------------------------------
#### EXHIBIT 02
#### PREMARKET NOTIFICATION 510(k) SUMMARY As required by 21 CFR §807.92(c)
#### Submitter
DEC 12 2013
| 510(k) Owner: | MedApps, Inc., DBA Alere Connect |
|-----------------------|---------------------------------------------------------|
| Owner / Operator: | 10027842 |
| Registration: | 3005916763 |
| Address: | 8767 E. Via De Ventura, Suite 300, Scottsdale, AZ 85258 |
| Telephone: | 480-305-6323 |
| Fax Number: | 480-305-6328 |
| Contact Person: | Kent Dicks |
| Contact Person Title: | CEO |
| Date Prepared: | September 3, 2013 |
#### 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 devices are:
| K040966 | Carematix Modified System |
|---------|------------------------------------------------------------------------|
| K083862 | MedApps 2.0 - Remote Patient Monitoring System |
| K124000 | MedApps 2.0 - Remote Patient Monitoring System (with MobileLink added) |
#### 3. INDICATIONS FOR USE
The MedApps (Alere Connect) 2.0 - Remote Patient Monitoring System consists of 1) a cellular communication hub (MedApps' HealthPAL, Alere™ MobileLink or Alere™ HomeLink) an over-the-counter device that resides with the end-user (patient), which connects to commercially available FDA cleared accessory devices, specifically glucose meters, scales, blood pressure monitors, pulse oximeters, and PT/INR monitors (excluding HomeLink) and 2) web-based health data management application (MedApps' HealthCOM), that provides access to collected data stored on a secure host server system.
MedApps / Alere Connect Remote Patient Monitoring devices receive and store measurements collected from the described accessory devices, either wirelessly using short-range radio protocols (e.g. Bluetooth, Zigbee, WiFi, Bluetooth Low Energy (BLE), Fitlinxx Radios) or tethered via cable (e.g. USB, serial, etc.). Regardless of connectivity mode, the MedApps / Alere Connect monitoring devices do not alter the indications for use of the described peripheral accessory health devices.
MedApps / Alere Connect devices indicate successful or failed data reception and transmission with visual and audio feedback using a combination of any of the
{1}------------------------------------------------
EXHIBIT 02
K132803 pg 2 of 12
following: Display, LED Lights, verbal messages, and / or audio tones / chimes. MedApps / Alere Connect devices store collected data and forward / transmit to server for access in HealthCOM via commercially available, FCC compliant, wireless telecommunication protocols (including but not limited to cellular GSM, CDMA and WiMax).
Healthcare professionals, clinicians and other authorized personnel can review the transmitted information within the MedApps HealthCOM system, where they can review collected readings, establish parameters to indicate readings exceptions to set thresholds, or trigger Interactive Voice Response (IVR) messages to the patient remotely to issue information such as reminders (e.g. "We haven't received readings from you today, please take and send your readings") or possibly educational information for conditions such as diabetes, hypertension, CHF, etc. Additionally, HealthCOM can port collected data to the healthcare providers' clinical back-end system(s) of choice.
The MedApps /Alere Connect 2.0 Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, nor is it intended to provide realtime / time-critical data. The device is contraindicated for patients requiring direct medical supervision or emergency intervention.
#### C. MedApps 2.0 SYSTEM DESCRITPION
The MedApps 2.0 - Remote Patient Monitoring System consists of:
- HealthPAL hardware: (1)
The physical component of the 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 module. LED lights to indicate activity, timer button to assist patients with their reading schedule (i.e. remind them to take their reading in X minutes), last reading button, volume up and down buttons. The HealthPAL Model 105 contains a GSM cellular module while the HealthPAL Model 106 contains a CDMA cellular module.
- HealthHUB hardware / software: (2)
The HealthHUB hardware is an extension of the HealthPAL functionality. HealthHUB acts as a "docking" station for the HealthPAL in order to act as a conduit for the AC power adaptor connecting the electrical wall outlet to the HealthPAL providing power and battery charging capability. The Hubs also provide additional connections to off the shelf Glucose Meters, Scales, Blood Pressure Monitors and Pulse Oximeters, via smart cables (per validated in HealthPAL software). The HealthHUB model MA200 allows for multiple wired connections for accessory devices. HealthHUB Model 205 is specific for the HealthPAL MA105, and the HealthHUB 206 is specific for the HealthPAL MA 106 with both Hubs having one wired connector.
(3) HealthPAL firmware / software:
The firmware captures data from commercially available health monitors, and stores and transmits the information to the HealthCOM server, via the embedded communication chip / platform.
{2}------------------------------------------------
The firmware allows HealthPAL to receive information via wire or via embedded wireless module from accessory medical devices that are compatibly wireless enabled, which have been paired to the MedApps HealthPAL.
The firmware has many additional functions including:
- Download of user profiles from the server to configure HealthPAL remotely. �
- . HealthPAL has audio capability to deliver verbal announcement of readings and acknowledgment of data transmission from all connected accessory medical devices, time settings, volume control, educational content and reminders, in any language that is loaded to the device.
- . Timer capability, activated by the user to provide assistance with adhering to a reading schedule (reminders to take readings within a set timeframe).
- . OLED screen displays information regarding the HealthPAL's status including battery level, volume level, data transmission status, transmission pending indicator, activity icons / messages and other information to provide ease of use and promote patient adherence; as well as information received from accessory medical devices, such as the type of device, measurement, date and time of the last reading collected.
- . Battery charging, isolation circuits, and interfaces to individual accessory medical devices / protocols via the smart cable.
- (4) MobileLink hardware / software:
AC020 MobileLink is a modified MA105 HealthPAL device. The physical component of the MobileLink is an electronic device contained in a plastic enclosure with built-in M2M cellular chip, speaker, standard USB cable and USB Smart Cable connection, OLED screen to review the reading, and LED lights to indicate activity regarding the receiving and transmitting of collected data.
Like the HealthPAL, MobileLink's firmware / software captures, data from commercially available retail health monitors, and transmits information. to the HealthCOM server, via the embedded communication chip / platform.
The firmware allows MobileLink to receive information via wire, either standard USB or with a customized USB Smart Cable, from accessory medical devices.
The firmware has many additional functions including:
- . Download of user profiles from the server to configure MobileLink remotely.
- . MobileLink's Audio feature uses audio tones to indicate acknowledgment of collected readings from all connected accessory medical devices as well as reading transmission via the cellular network.
- . MobileLink's visual user interface utilizes an OLED display to display collected readings from attached accessory medical devices as well as reading transmission acknowledgements. MobileLink's visual interface also contains a LED light to show power and provide reading request indication capability.
- (日) HomeLink hardware / software:
AC200 HomeLink is a modified MA105 HealthPAL device. The physical component of the HomeLink is an electronic device contained in a plastic enclosure with built-in M2M cellular chip, speaker, standard USB cable and USB Smart Cable connection, touch screen to review the reading and allow patients with ability to have "IVR"
{3}------------------------------------------------
#### EXHIBIT 02
K132803 pg 4 of 12
(questions and answers) functionality that was formally part of the HealthCOM IVR section, and wireless module.
Like the HealthPAL or MobileLink, HomeLink's firmware / software captures biometric data from FDA cleared commercially available accessory devices, and stores and transmits information to the HealthCOM server, via the embedded communication chip / piatform.
The firmware allows HomeLink to receive information via wire or via embedded wireless module from accessory medical devices that are compatibly wireless enabled, which have been paired to the HomeLink device.
The firmware has many additional functions including:
- Download of user profiles from the server to configure HomeLink remotely. .
- . HomeLink's has audio capability to deliver verbal announcement of readings and acknowledgment of data transmission from all connected accessory medical devices, volume control, user feedback, in any language that is loaded to the device.
- . HomeLink's visual user interface utilizes a touch screen display to display collected readings from attached accessory medical devices as well as other user interactions. One such patient HomeLink user interface includes the MedApps 2.0 System IVR functionality, which originally was executed from the HealthCOM webportal by professionals to patient's phones. The updated version allows end users (patients) to provide answers on the HomeLink device based on professional predefined questions that are reviewed in HealthCOM. This allows an improved user interaction of the previous IVR procedure. HomeLink screen also displays information regarding the device's status including volume level, data transmission status, preferred language, transmission pending indicator, activity icons / messages and other information to provide ease of use and promote patient adherence; as well as information received from accessory medical devices, such as the type of device, measurement, date and time of the last reading collected.
- (6) MedApps HealthCOM software application:
The HealthCOM software application allows caregivers access to review patient data collected from accessory medical devices using MedApps hardware on the secure HealthCOM website. HealthCOM software allows professional caregivers to set patient readings.
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 or Medical Record (EHR or EMR),
- (7) MedApps IVR software application from HealthCOM:
The IVR (Interactive Voice Response) software application provides the ability to contact the patient remotely, by phone (designated in the user profile), and executes an pre-approved ("canned") scripts to deliver pre-approved ("canned") 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"), educational content and gather survey information.
{4}------------------------------------------------
In addition, the MedApps IVR application will send out Email, SMS / Text Messages, Paging, IM and other forms of communications in order to contact patients or caregivers. This will include reminders and alerts, based on clinically defined parameters / thresholds established in HealthCOM by the professional care provider.
The original IVR system has moved to the HomeLink device for easier interaction with the patient compared to the need for the patient to receive an IVR phone call on their personal phone, which includes professionally defined questions that the patient can answer and both the questions and answers will be recorded in the HealthCOM system for professional review.
| OEM<br>Accessory<br>Device | Description | Integrated OEM FDA cleared accessory devices | | | FDA<br>Clearance<br>number |
|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|---------------------------|----------------------------------------|------------------------------|
| | | Manufacturer | Model | Alere Connect Hub Device | |
| Blood<br>Pressure<br>Monitor | Off the shelf device that<br>measures blood pressure,<br>pulse of an individual | A&D Medical | UA-767PBT | HealthPAL &<br>HomeLink | K012472 |
| | | A&D Medical | UA-767PC | MobileLink | |
| Scale | Off the shelf device that<br>measures weight of an<br>individual | A&D Medical | UC-321PBT | HealthPAL &<br>HomeLink | Class 1 no<br>510k<br>number |
| | | A&D Medical | UC-321PL | MobileLink | |
| Glucose<br>Meters | Off the shelf devices that<br>measure glucose level of<br>blood for an individual. | LifeScan (J&J)<br>OneTouch | Ultra and<br>Ultra2 | HealthPAL,<br>MobileLink &<br>HomeLink | K053529 |
| | | Abbott | Freestyle Lite | HomeLink | K070850 |
| | | Abbott | Freestyle<br>Freedom Lite | | K051839 |
| | | Bayer | Contour | | K091820 |
| | | Nipro | TrueBalance | | K090495 |
| | | Nipro | TrueResult | | K080641 |
| Pulse<br>Oximeter | Prescription Use Device<br>that measures oxygen<br>concentration of an<br>individual | Nonin | 9560 | HealthPAL &<br>HomeLink | K081285 |
| | | Oxypulse | OxiPro-6 | MobileLink | K100815 |
| PT/INR | Prescription Use Device<br>that measures<br>prothrombin time of<br>whole blood for<br>monitoring of oral<br>anticoagulation therapy. | Alere (formally<br>Hemosense) | InRatio2 | HealthPAL &<br>MobileLink | K021923 |
- Accessory Device Descriptions: (8)
{5}------------------------------------------------
## EXHIBIT 02
| K132803 pg 6 of 12 | | | | |
|--------------------|--|--|--|--|
|--------------------|--|--|--|--|
| Feature | Carematix<br>Modified System<br>K040966 | MedApps<br>Submission<br>K083862 | MedApps 2.0<br>Submission<br>K124000 | MedApps 2.0<br>Submission (This<br>submission) |
|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications of<br>Use | Physiological<br>monitoring system<br>that collects,<br>accumulates and<br>transmits patient<br>vital signs and other<br>data from a patient<br>who may be remote<br>form the healthcare<br>practitioner to the<br>practitioner. | The MedApps 2.0 -<br>Remote Patient<br>Monitoring System<br>consists of a patient<br>device, MedApps<br>HealthPAL and<br>HealthCOM software<br>monitoring<br>application. | Same as MedApps<br>2.0 with the<br>exception of<br>updates to Include<br>MobileLink device<br>and PT/INR monitor<br>as an accessory<br>device | Same as MedApps<br>2.0 System with the<br>addition of the<br>HomeLink device<br>(similar to<br>HealthPAL and<br>MobileLink Hub<br>devices) |
| Intended Use | Telemedicine<br>System | Telemedicine System | Same as Carematix<br>and MedApps 2.0 | Same as Carematix<br>and MedApps 2.0 |
| Intended Users | Home users and<br>Healthcare providers | Same | Same | Same |
| Site of Use | Home & Clinic | Same | Same | Same |
| | | Home (HealthPAL)<br>Clinic (HealthCOM) | Home (HealthPAL/<br>MobileLink);<br>Clinic (HealthCOM) | Home (HealthPAL/<br>MobileLink/<br>HomeLink);<br>Clinic (HealthCOM) |
| Data Collection<br>Software | Proprietary Software | MedApps Proprietary<br>Software | MedApps<br>Proprietary<br>Software | MedApps<br>Proprietary<br>Software |
| Data Collection<br>Software<br>Functionality | Transmit data from<br>Sensor devices to<br>Central Database | Same | Same | Same |
| Communication<br>method of hub<br>with Central<br>Server | Via modem over<br>telephone line | Via Embedded<br>Cellular Technology | Via Embedded<br>Cellular Technology | Via Embedded<br>Cellular Technology |
| Types of<br>sensors which<br>can be<br>Interfaced<br>(wired or<br>wirelessly) to<br>receiver hub | Medical Devices<br>designed for Home<br>use:<br>Glucose, Scale<br>Blood Pressure<br>Pulse Ox,<br>FEX/PEF,PT/INR<br>Temperature | Medical Devices<br>designed for Home<br>use:<br>Glucose, Scale<br>Blood Pressure<br>Pulse Ox | Same as MedApps<br>(Glucose, Scale, BP,<br>Pulse Ox with<br>PT/INR)<br>Same as CareMatix<br>(PT/INR) | Same as MedApps<br>(Glucose, Scale, BP,<br>Pulse Ox with<br>PT/INR)<br>HomeLink does not<br>interface with<br>PT/INR |
| Maximum<br>number and<br>type of<br>measurement<br>devices that can<br>be connected to<br>the devices | Determined by vital<br>sign devices that<br>are designed for<br>Home use, and have<br>a data port.<br>(Wireless or Wired) | Same | Same | Same |
| Maximum data<br>throughput<br>under worst<br>case conditions | Multiple readings<br>are stored on the<br>medical devices and<br>act as a backup if<br>data needs to be re-<br>sent to the server | Same | Same | Same |
| Feature | Carematix<br>Modified System | MedApps 2.0<br>Submission | MedApps 2.0<br>Submission | MedApps 2.0<br>Submission |
| | K040966 | K083862 | K124000 | (This Submission) |
| Time Delay in<br>the processing<br>of data collected<br>and transmitted | Readings stored in<br>the medical devices<br>can be sent up to<br>the server when the<br>connection is<br>restored. | Same | Same | Same |
| Implementation<br>method of<br>collecting data<br>from sensors | Modify OTS sensors<br>with previous 510k<br>approval by adding<br>communications<br>interface without<br>altering sensors | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired (tethered)<br>cables. | Short range radio<br>system using Wired<br>(tethered) | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired<br>(tethered) cables. |
| Sensor Software | Sensor Software<br>unchanged | Same | Same | Same |
| Connectivity | Wired or wireless to<br>hub | Short range radio<br>system using<br>Bluetooth and Wired<br>(tethered) cables. | Short range radio<br>system using Wired<br>(tethered) | Short range radio<br>system using<br>Bluetooth and Wired<br>(tethered) cables. |
| Communication<br>method of hub<br>with devices | Wireless RF protocol | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired (tethered)<br>cables. | Short range radio<br>system using Wired<br>(tethered) | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired<br>(tethered) cables. |
| Communication<br>s Protocol | Proprietary | Wireless (Bluetooth)<br>V2.0 and Wired<br>(Tethered) | Wired (Tethered) | Wireless (Bluetooth)<br>V2.0 and Wired<br>(Tethered) |
| Communication<br>Frequency | 915 MHz FCC<br>assigned channel | (HealthPAL)<br>Bluetooth : 2.402 to<br>2.480<br>GHz GSM: 850 / 900<br>/ 1800 / 1950 Mhz | (HealthPAL or<br>MobileLink)<br>GSM: 850 / 900 /<br>1800 / 1950 Mhz | (HomeLink)<br>Bluetooth : 2.402<br>to 2.480<br>GHz GSM: 850 /<br>900 / 1800 / 1950<br>Mhz |
| Power Source | Wall power plug<br>(120 VAC/50-60)<br>and Batteries in<br>Device | Wall power plug<br>(120 VAC/50-60) or<br>Rechargeable Battery<br>(HealthPAL) | Wall power plug<br>(120 VAC/50-60) or<br>Rechargeable<br>Battery (HealthPAL<br>or MobileLink) | Wall power plug<br>(120 VAC/50-60)<br>(HomeLink) |
| Display | On devices and hub,<br>and monitors<br>connected to central<br>server | Same | Same | Same |
| Communication<br>with Patients | On screen display | On screen display of<br>Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) | On screen display<br>with audio tones<br>instead of voice. | On screen display of<br>Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR)<br>through HomeLink |
| Use of<br>Thresholds /<br>Algorithms for<br>determining<br>how Thresholds<br>are set and<br>changed | Thresholds are set<br>by Healthcare<br>professionals in<br>Server Software | Same | 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 | Audio/visual reading<br>feedback on screen<br>and by speaker; and<br>Interactive Voice<br>Response (IVR)<br>System for patient<br>contact | Visual reading<br>feedback on screen<br>and audio tone by<br>speaker; and<br>Interactive Voice<br>Response (IVR)<br>System for patient<br>contact | Audio/visual reading<br>feedback on screen<br>and by speaker; and<br>Interactive Voice<br>Response (IVR)<br>System for patient<br>contact is through<br>HomeLink device |
| Messages and<br>Instructions<br>that can be sent<br>to the User. | On screen display | On screen display of<br>Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) | On screen display of<br>Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR) | On screen display of<br>Readings, Voice<br>Output and<br>Interactive Voice<br>Response (IVR)<br>functionality uses<br>HomeLink device |
#### TECHNOLOGICAL CHARACTERISTICS SUMMARY – as required by 807.92(a)(6) D.
{6}------------------------------------------------
## EXHIBIT 02
## K132803 pg 7 of 12
: .
{7}------------------------------------------------
### EXHIBIT 02
### K132803 pg 8 of 12
### Below is a Technological Characteristics Summary Comparison between MA105 HealthPAL, AC020 MobileLink, and AC200 HomeLink MedApps 2.0 System devices:
| Feature | MA105 HealthPAL | AC020 MobileLink | AC200 HomeLink |
|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
| Indications of Use | Enables healthcare providers to<br>monitor and manage blometirc<br>patient data collected remotely | Same | Same |
| Intended Use | Telemedicine System | Same | Same |
| Intended Users | Home users and patients outside<br>of the clinical setting, as well as<br>Healthcare providers for<br>HealthCOM | Same | Same |
| Site of Use | Remote setting (e.g. Home /<br>Work), Clinic | Same | Same |
| Data Collection<br>Software (firmware) | MedApps Proprietary Software | Same | Same |
| Data Collection<br>Software Functionality | Transmit data from Sensor devices<br>to Central Database | Same | Same |
| Communication method<br>of device hub with<br>Central Server | Via Embedded Cellular Technology<br>(GSM or CDMA) | Same | Same |
| Types of sensors which<br>can be interfaced (wired<br>or wirelessly) to<br>receiver hub | Medical Devices designed for<br>Home use:<br>Glucose, Scale, Blood Pressure,<br>Pulse Ox, PT/INR | Medical Devices<br>designed for Home<br>use:<br>Glucose, Scale,<br>Blood Pressure,<br>Pulse Ox, PT/INR | Medical Devices<br>designed for Home<br>use:<br>Glucose, Scale, Blood<br>Pressure, Pulse Ox |
| Transmission | Transmits information to the<br>MedApps secure host server called<br>"HealthCOM" | Same | Same |
| Implementation method<br>of collecting data from<br>sensors and general<br>Connectivity | Short range radio system using<br>Wireless (Bluetooth) and Wired /<br>tethered (Smart Cables). | MobileLink uses<br>wired / tethered<br>connection (USB,<br>Smart Cables) | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired / tethered<br>(Smart Cables). |
| Communication method<br>of hub with devices | Short range radio system using<br>Wireless (Bluetooth) and Wired /<br>tethered (Smart Cables). | MobileLink uses<br>wired / tethered<br>connection (USB,<br>Smart Cables) | Short range radio<br>system using<br>Wireless (Bluetooth)<br>and Wired / tethered<br>(Smart Cables). |
.
{8}------------------------------------------------
### EXHIBIT 02
K132803 pg 9 of 12
| Communication<br>Frequency | Bluetooth : 2.402 to 2.480 GHz<br>GSM: 850 / 900 / 1800 / 1900<br>Mhz | No Bluetooth<br>capability<br>GSM: 850 / 900 /<br>1800 / 1900 Mhz | Bluetooth : 2.402 to<br>2.480 GHz<br>GSM: 850 / 900 /<br>1800 / 1900 Mhz |
|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
| Power Source | AC adaptor Wall power plug (120<br>VAC/50-60) and Rechargeable<br>Batteries in Device | AC Adaptor that is<br>60601-1 3rd Edition<br>compatible with<br>Lithium battery only<br>used for soft shut<br>down functionality<br>and not powering<br>device. | AC Adaptor that is<br>60601-1 3rd Edition<br>compatible for<br>powering device. |
| Device Communication<br>with Patients | On screen display and audio volce<br>feedback | On screen display<br>with audio tones<br>instead of voice. | Touch screen display<br>with audio voice<br>feedback. |
| Applicable Certification<br>Testing | Safety 60601-1, EMC/EMI/FCC<br>(60601-1-2), ESD & Radiated<br>Immunity, FCC Bluetooth,<br>(PTCRB), CTIA (battery), ETSI | Safety 60601-1 3rd<br>Edition,<br>EMC/EMI/FCC<br>(60601-1-2), ESD &<br>Radiated Immunity,<br>PTCRB, ETSI<br>(Declaration of<br>Conformity) | Safety 60601-1 3rd<br>Edition,<br>EMC/EMI/FCC<br>(60601-1-2), ESD &<br>Radiated Immunity,<br>PTCRB ETSI (See<br>Declaration of<br>Conformity) |
Technological Characteristics Summary Comparison between MA105 HealthPAL, AC020 MobileLink, and AC200 HomeLink devices as part of the MedApps 2.0 System focusing on the HomeLink modification to other two devices:
| Feature | MA105 HealthPAL | AC020 MobileLink | AC200 HomeLink | Modification<br>Description |
|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
| Device<br>Dimensions | 4.2"x 2.1" x 0.9",<br>weighs 3 oz. | 4.5" x 1.9" x 0.75",<br>weighs 2.8 oz. | 5.1" x 7.9" x 0.7",<br>welghs 17 oz. | Modified to increase the<br>size of the device |
| User<br>Interface | 1.8" Full Color<br>Passive Matrix OLED<br>and buttons | 1.54" single color<br>OLED and buttons | 7" Full Color Touch<br>Screen | Modified to a touch<br>screen instead of<br>buttons |
| Voice<br>Interface | Voice and tones | Tones only | Voice and tones | Same as HealthPAL |
| Microprocess<br>ors | C8051F344 (Silicon<br>Labs); 8051<br>architecture | PIC32MX975F512L<br>(Microchip); MIPS<br>architecture | PIC32MX975F512L<br>(Microchip); MIPS<br>architecture | Same as MobileLink |
| Memory<br>Devices | 4GB MicroSD Card;<br>SDHC | 4GB or 8GB MicroSD<br>Card; SDHC | 4GB or 8GB MicroSD;<br>SDHC | Same as MobileLink |
| Energy<br>Sources | Main Power<br>Supply:SHWA12A-<br>S022(MEPOS)6061-1<br>3" Ed.[external]<br>Switching Power<br>Supplies:<br>TPS61080, BQ24014,<br>TPS63001(TI);<br>LTC3525(Linear)[inte<br>rnal] | Main Power<br>Supply: 18ur-09-<br>2000(Group West)<br>Power Supply<br>components:<br>BQ24014 (TI),<br>TPS61080(TI);<br>LTC3122(Liner);<br>A4490 (Allegro)<br>[Internal] | Main Power<br>Supply: 18ur-09-2000<br>(Group West)<br>Power Supply<br>components:<br>BQ24014(TI);<br>LTC2427,LT1617,<br>LT1930(Linear);<br>XC9119(Torex);<br>A4490(Allegro)[internal | Power Supply same as<br>MobileLink;<br>More Internal power<br>supply components<br>compared to other two<br>devices |
| Safety<br>Features | ESD Protection:<br>TPD6E001 (TI) | ESD Protection:<br>TPD6E001 (TI) | ESD Protection:<br>TPD6E001 (TI) | Same as both devices |
| Communicati<br>ons to Server | Cell Module:<br>GSM0308-<br>10(Enfora); | Cell Module:<br>SL8081 (Sierra<br>Wireless); | Celi Module:<br>SL8081 (Sierra<br>Wireless); . | Same as MobileLink |
{9}------------------------------------------------
#### EXHIBIT 02 K132803 pg 10 of 12
| Communicati<br>ons to<br>Accessory<br>Devices | Bluetooth:<br>WT11-A-<br>Ai4(BlueGiga);<br>Serial<br>Communication<br>though Smart Cable<br>(30 pin) | Serial<br>Communication<br>through Smart<br>Cable (USB) | Bluetooth: WT11-A-<br>Al4(BlueGiga); BR-<br>LE4.0-S2A(Blue<br>Radios); FitLinxx;<br>Serial Communication<br>through Smart Cable<br>(USB) | Bluetooth same as<br>HealthPAL;<br>Added Bluetooth low<br>energy and Fitlinxx |
|-----------------------------------------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
| Programmin<br>g Language | C Programming<br>Language | C Programming<br>Language | C Programming<br>Language | Same as HealthPAL and<br>MobileLink |
| Firmware<br>Architecture | Single threaded | Multi-threaded<br>(RTOS) | Multi-threaded (RTOS) | Same as MobileLink |
| IVR<br>functionality<br>communicați<br>on | Professional use<br>HealthCOM; End<br>Users use their phone | Professional use<br>HealthCOM: End<br>Users use their<br>phone | Professional use<br>HealthCOM; End Users<br>use HomeLink | HomeLink is used for<br>IVR functionality<br>instead of the End<br>User's phone |
### Data Collection:
The one predicate device and the MedApps 2.0 System solution connect to medical devices (designed for home use) by either wired (cable) connection or wireless (HealthPAL/HomeLink- Bluetooth). The data is collected from the devices and sent to a secure central server using various communication methods.
### Telecommunication Platform to Central Server:
Carematrix uses modem off telephone line; MedApps 2.0 System devices uses embedded Machine to Machine (M2M) module to transmit data via cellular connectivity.
### Patient Feedback Technology:
The predicate device and the MedApps solution allow data and messages to be displayed on a screen (for the HealthPAL/HomeLink) for the patient to read and acknowledge. MobileLink also uses audio and visual acknowledgement / feedback. The MedApps 2.0 System solution also uses an Interactive Voice Response (IVR) system in order to communicate with the patient and ask questions, gather survey information, or issue reminders. The HomeLink includes the user interface (IVR process) as part of the user interaction instead of using a patient's phone.
### Backend Data Storage:
All systems (predicate device and the MedApps 2.0 system solution), provide a backend system that allows data to be stored, and healthcare professionals to access and monitor collected patient data.
#### Types of sensors which can be interfaced (wired or wirelessly) to receiver hub:
CareMatix Modified System and the proposed MedApps 2.0 System both include PT/INR monitor as an FDA cleared accessory device to the receiver hub. The CareMatix uses wireless connectivity to the hub whereas the MedApps 2.0 System uses both wired and wireless connectivity to the hub. CareMatix System 510k (K040966) clearance summary letter includes the predicate Avid Care (K011779 and K010029) telemedicine system that connects to PT/INR monitor as an accessory device. The HomeLink includes all of the original MedApps 2.0 System (K083862) accessory devices without interfacing with the PT/INR monitor at this time.
{10}------------------------------------------------
#### NON-CLINICAL PERFORMANCE DATA TESTING AND REVIEW - as required by E. 807.92(b)(1)
### Non-Clinical Testing
The submitted 2.0 System has undergone MedApps' design control verification and validation testing. MedApps 2.0 validation testing include testing of all executable code and functionality and confirmation that all identified risks have been adequately addressed by software functionality, the user interface, documentation or user SOP.
MedApps 2.0 System verification and validation activities as part of the design control process include testing of all Design Specifications (Design Control Inputs) based on risk analysis, certification standards, and Verification plans. MedApps Product Verification and Release Plan execution on HealthPAL. MobileLink, and HomeLink devices ensures each medical device works with each applicable type of user accessory medical device (glucose, blood pressure monitor, scale, pulse oximeter and PT/INR (excluding HomeLink) as part of the MedApps 2.0 System including integration to HealthCOM backend software application. The output of these design control verification analysis documents MedApps 2.0 - Remote Patient Monitoring System shall meet its requirements and design specifications as intended. Additionally, the HomeLink question and answer functionality, which moved to the device instead of the patient's personal phone as part of the MedApps 2.0 System was included in the verification testing to ensure this user interface is verified.
Lastly, all relevant certification testing such as EMC (60601-1-2) and Safety (60601-1) are described in MedApps' Declaration of Conformity.
#### SUBSTANTIAL EQUIVALENT F.
The MedApps 2.0 Remote Patient Monitoring System 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 integrated to the patient medical device. implementation methods of collecting data from sensors, sensor software, connectivity, communication protocol, power source and general display method.
The HomeLink (this submission) is substantially equivalent to the HealthPAL (described in 510(k) K083862) and MobileLink (K124000) as all three devices, as part of the MedApps 2.0 System, connect to commercially available Glucose Meters, Scales, Blood Pressure Monitors, Pulse Oximeters, and PT/INR; data is collected, stored and transmitted using off-the-shelf FCC approved wireless / cellular connectivity. All devices provide audio and visual feedback / acknowledgement that readings have been collected and transmitted to MedApps' secure host server called "HealthCOM". The HomeLink (this submission) is substantially equivalent to the HealthPAL (described in 510(k) K083862) as both devices, as part of the MedApps 2.0 System, connect to commercially available Glucose Meters, Scales, Blood Pressure Monitors, Pulse Oximeters; data is collected, stored and transmitted using off-the-shelf FCC approved wireless / cellular connectivity. Both provide audio (voice) and visual feedback / acknowledgement that readings have been collected and transmitted to MedApps' secure host server called "HealthCOM". Both devices also use wireless connectivity (Bluetooth) for accessory devices that have this capability.
#### G. SAFETY AND EFFICACY ·
{11}------------------------------------------------
#### EXHIBIT 02
K132803 pg 12 of 12
The MedApps 2.0 Remote Patient Monitoring System 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 does not introduce any new questions concerning the safety or efficacy and is, therefore, substantially equivalent to the predicate devices.
{12}------------------------------------------------
Image /page/12/Picture/1 description: The image shows the logo for the U.S. Department of Health and Human Services. The logo consists of a stylized caduceus symbol, which features a staff with a snake winding around it, and three horizontal bars above it. The text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" is arranged in a circular fashion around the symbol.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
December 12, 2013
Medapps Inc., Dba Alere Connect Kent Dicks 8767 E. Via De Ventura, Ste 300 Scottsdale, AZ 85258 US
Re: K132803
> Trade/Device Name: Medapps 2.0 Remote Patient Monitoring System, Healthpal, Healthcom, Mobile Link Regulation Number: 21 CFR 870.2910 Regulation Name: Medapps Remote Patient Monitoring System Regulatory Class: Class II Product Code: DRG, NBW Dated: 11/12/2013 Received: 11/11/2013
Dear Kent 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. 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.
{13}------------------------------------------------
Page 2 - Kent Dicks
. . – •ı ••••
> 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 contact the Division of Small Manufacturers, International and Consumer Assistance at its tollfree number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. Also, please note the regulation entitled. "Misbranding by reference to premarket notification" (21 CFR 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.htm 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 (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default,htm.
Sincerely yours,
## Owen P. Faris -S
for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{14}------------------------------------------------
#### EXHIBIT 01
#### MedApps, Inc., DBA Alere Connect STATEMENT OF INDICATIONS FOR USE
K132803 510(k) Number: _
Preparation Date: September 3, 2013
Device Name: System
・ー (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2) -- (2
MedApps (Alere Connect) 2.0 - Remote Patient Monitoring
Indications For Use:
The MedApps (Alere Connect) 2.0 - Remote Patient Monitoring System consists of 1) a cellular communication hub (MedApps' HealthPAL, Alere™ MobileLink or Alere™ HomeLink) an over-the-counter device that resides with the end-user (patient), which connects to commercially available FDA cleared accessory devices, specifically glucose meters, scales, blood pressure monitors, pulse oximeters, and PT/INR monitors (excluding Homel.ink) and 2) web-based health data management application (MedApps' HealthCOM), that provides access to collected data stored on a secure host server system.
MedApps / Alere Connect Remote Patient Monitoring devices receive and store measurements collected from the described accessory devices, either wirelessly using short-range radio protocols (e.g. Bluetooth, Zigbee, WiFi, Bluetooth Low Energy (BLE), Fitlinxx Radios) or tethered via cable (e.g. USB, serial, etc). Regardless of connectivity mode, the MedApps / Alere Connect monitoring devices do not alter the Indications for use of the described peripheral accessory health devices.
MedApps / Alere Connect devices indicate successful or failed data reception and transmission with visual and audio feedback using a combination of any of the following: Display, LED Lights, verbal messages, and / or audio tones / chimes. MedApps / Alere Connect devices store collected data and forward / transmit to server for access in HealthCOM via commercially available, FCC compliant, wireless telecommunication protocols (including but not limited to cellular GSM, CDMA and WiMax).
Healthcare professionals, clinicians and other authorized personnel can review the transmitted information within the MedApps HealthCOM system, where they can review collected readings, establish parameters to Indicate readings exceptions to set thresholds, or trigger Interactive Voice Response (IVR) messages to the patient remotely to issue information such as reminders (e.g. "We haven't received readings from you today, please take and send your readings") or possibly educational information for conditions such as diabetes, hypertension, CHF, etc. Additionally, HealthCOM can port collected data to the healthcare providers' clinical back-end system(s) of choice.
The MedApps /Alere Connect 2.0 Remote Patient Monitoring System is not intended for diagnosis or as a substitute for medical care, nor is it intended to provide real-time / time-critical data. 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 | | |
| | Page Exhibit01-1 | | |
| | Digitally signed by Owen P. Faris -S Date: 2013.12.12 14:51:39 -05'00' | | |
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
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.