K243146 · Ihealth Labs, Inc. · MWI · Feb 3, 2025 · Cardiovascular
Device Facts
Record ID
K243146
Device Name
iCare APP
Applicant
Ihealth Labs, Inc.
Product Code
MWI · Cardiovascular
Decision Date
Feb 3, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The iCare APP is intended for use in the home and clinical settings as an aid for users and their healthcare professionals to view test results which are measured by iHealth devices to better manage users' health and get feedback from their professional care team. The iCare APP can also connect to medical devices and/or non-medical devices and get data from devices during measurement or from the data stored in the memory of the device for enhanced data management. Data can be transmitted, displayed, and stored in the APP.
Device Story
iCare App is a mobile application (Android/iOS) for managing vital signs; inputs data from iHealth medical devices (blood pressure monitors, glucose meters, pulse oximeters, weight scales) via Bluetooth or manual entry; stores, displays, and transmits health data for user and healthcare professional review; features patient dashboard for tracking measurements, messaging care teams, viewing appointment history, medication instructions, and accessing health education; used in home and clinical settings by patients and healthcare providers; facilitates data management and professional feedback; does not provide medical diagnoses or treatment recommendations.
Clinical Evidence
No clinical data. Bench testing only, including software verification and validation, wireless coexistence testing, cybersecurity assessment, and usability testing.
Technological Characteristics
Software-only mobile application (iOS/Android). Connectivity via Bluetooth for data acquisition from iHealth medical devices. Functions as a Medical Device Data System (MDDS) and interface for cardiac monitoring, blood pressure, oximetry, and glucose systems. Software level of concern: moderate.
Indications for Use
Indicated for home and clinical users to view, manage, and store vital sign data (blood pressure, blood glucose, blood oxygen, weight) measured by iHealth devices, and to facilitate communication with professional care teams.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo features the letters 'FDA' in a blue square, followed by the words 'U.S. FOOD & DRUG ADMINISTRATION' in blue text.
February 3, 2025
iHealth Labs, Inc. Tianvang Liu Director of Medical Devices 880 W Maude Ave Sunnyvale, California 94085
Re: K243146
Trade/Device Name: iCare APP Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MWI, DXN, OCH, PUH, OUG Dated: September 30, 2024 Received: September 30, 2024
Dear Tianyang Liu:
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 (the 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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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.
{1}------------------------------------------------
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30. Design controls; 21 CFR 820.90. Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-device-advicecomprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatory
{2}------------------------------------------------
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
for
Robert T. Kazmierski -S
LCDR Stephen Browning Assistant Director Division of Cardiac Electrophysiology, Diagnostics, and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
# Indications for Use
510(k) Number (if known) K243146
Device Name iCare App
# Indications for Use (Describe)
The iCare App is intended for use in the home and clinical settings as and their healthcare professionals to view test results which are measured by iHealth devices to better manage user's health and get feedback from their professional care team.
The iCare App can also connect to medical devices and or non-medical devices and get data from devices during measurement or from the data stored in memory of the device for enhanced data managements. Data can be transmitted, displayed, and stored in the App.
| Type of Use (Select one or both, as applicable) |
|-------------------------------------------------|
|-------------------------------------------------|
| <span></span> Prescription Use (Part 21 CFR 801 Subpart D) |
|------------------------------------------------------------|
| <span></span> Over-The-Counter Use (21 CFR 801 Subpart C) |
# CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
# *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{4}------------------------------------------------
# 510(k) Summarv
### 1. Submitter Information
Name: iHealth Labs, Inc. Address: 880 W Maude Ave, Sunnyvale, CA 94085 Phone Number: 1-855-816-7705 Contact: Tianyang Liu Date of Preparation: September 30, 2024
### 2. Device Information
Trade name: iCare APP
# 3. Classification
Product Code and Regulation Number: MWI: Sec. 870.2300 Cardiac monitor (including cardiotachometer and rate alarm). DXN: Sec. 870.1130 Noninvasive blood pressure measurement system. OCH: Sec. 870.2700 Oximeter. PUH: Sec. 870.2770 Impedance plethysmograph. OUG: Sec. 880.6310 Medical device data system Class Classification: II Panel: 870 Cardiovascular
# 4. Predicate Device Information
Manufacturer: Andon Health Co., Ltd. Device: Connect App for iHealth Next 510(k) Number: K181541
# 5. Device Description
The iCare APP is a mobile application on both Android and iOS platforms.iCare allows users to better manage their own health by enabling them to measure their vital signs, access their results and relevant health information with just their smart device and internet connection, and receive feedback from their professional care team.
iCare includes a patient darshboard featuring the Home, Health, Plus, Education, and Profile tabs. Accessory devices can be connected to the system to allow for collection of blood sugar, blood pressure, blood oxygen, and/or weight measurements. The patient darshboard functionality includes the ability to start measuring, allows users to view and track measurements, and export testing schedules for blood
{5}------------------------------------------------
sugar, blood pressure, blood oxygen, and weight measurements; send messages to their professional care team; view previous appointment history information; view medication instructions; add entries to the food diary and review feedback from their registered dietician; set timers; and access articles and videos about health knowledge.
# 6. Intended Use
The iCare APP is intended for use in the home and clinical settings as an aid for users and their healthcare professionals to view test results which are measured by iHealth devices to better manage users' health and get feedback from their professional care team.
The iCare APP can also connect to medical devices and/or non-medical devices and get data from devices during measurement or from the data stored in the memory of the device for enhanced data management. Data can be transmitted, displayed, and stored in the APP.
# 7. Summary Comparing Technological Characteristics with Predicate Device iCare - Substantial Equivalence Comparison Tabular Format
| Feature | Subject Device<br>iCare | Predicate Device<br>Connect App for<br>iHealth Next | Comparison |
|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Regulatory and Intended Use Comparison | | |
| 510(k) Number | N/A | K181541 | N/A |
| Product Code<br>and<br>Classification<br>Name | MWI, DXN, OCH, PUH,<br>OUG, NBW | MWI, DXN, MNW,<br>DQA | Similar: the connected devices are the<br>same, OCH is product code for<br>sportoximeter, and PUH is new product<br>code for body analyzer exempt from<br>510(k).<br>DQA is product code for medical<br>oximeter needs 510(k), and MNW is<br>product code for body analyzer needs<br>510(k).<br>OUG and NBW is applicable to iCare<br>with glucose data transmission, display<br>and storage. |
| Class | Class II | Class II | Same |
| Regulation | MWI: Sec. 870.2300<br>Cardiac monitor (including<br>cardiotachometer and rate<br>alarm).<br>DXN: Sec. 870.1130<br>Noninvasive blood<br>pressure measurement<br>system.<br>OCH: Sec. 870.2700<br>Oximeter.<br>PUH: Sec. 870.2770 | MWI: Sec. 870.2300<br>Cardiac monitor<br>(including<br>cardiotachometer and<br>rate alarm).<br>DXN: Sec. 870.1130<br>Noninvasive blood<br>pressure<br>measurement system.<br>MNW: Sec. 870.2770<br>Impedance<br>plethysmograph.<br>DQA: Sec. 870.2700 | OUG and NBW is added for the glucose<br>meter data transmission, display and<br>storage. |
| | | | |
| | plethysmograph. | Physiological signal<br>amplifier. | |
| | OUG: 880.6310 Medical<br>device data system<br>NBW: 862.1345 Glucose<br>test system | | |
| Indications for<br>Use | The iCare APP is<br>intended for use in the<br>home and clinical settings<br>as an aid for users and<br>their healthcare<br>professionals to view test<br>results which are<br>measured by iHealth<br>devices to better manage<br>users' health and get<br>feedback from their<br>professional care team.<br>The iCare APP can also<br>connect to medical<br>devices and/or non-<br>medical devices and get<br>data from devices during<br>measurement or from the<br>data stored in the<br>memory of the device for<br>enhanced data<br>management. Data can<br>be transmitted, displayed,<br>and stored in the APP. | The Connect App for<br>iHealth Next is<br>intended for use in<br>home settings as an<br>aid for people to<br>view vital signs which<br>are measured by<br>iHealth devices<br>(noninvasive blood<br>pressure monitor and<br>pulse oximeter).<br>The Connect App for<br>iHealth Next should<br>not be used to either<br>self-diagnose a<br>disease state or<br>exclude it.<br>Please consult your<br>physician if you find<br>the reading is above<br>a normal threshold. | Similar: Both devices are used to<br>manage patient data. Both devices<br>make no interpretation, evaluation,<br>medical judgments, or<br>recommendations for treatment. Clinical<br>judgment and experience are required<br>to check and interpret the information<br>transmitted, and they are not intended<br>as a substitute for medical care. |
| Patient<br>Population | Home users | Home user | Same |
| Prescription<br>Use (Rx)/ Over<br>The Counter<br>(OTC) | OTC | OTC | Same |
| Technological and Performance Characteristics | | | |
| Fundamental<br>Technology | Software Only | Software Only | Same |
| Software<br>Platform | iOS and Android | iOS and Android | Same |
| User<br>Interfaces | Patient Portal | Patient Portal | Same |
| Biometric<br>Parameters | Blood Pressure, Weight,<br>Blood Glucose, and Pulse<br>Oximeter<br>Blood Glucose<br>concentration | Blood Pressure,<br>Weight, Pulse<br>Oximeter | Similar: Other biometric parameters are<br>either not medical devices or class I or II<br>510(k) exempt.<br>The subject device can also be<br>identified as MDDS, with function of<br>display and store blood glucose result<br>from glucose meter. |
| Data<br>Collection | Wireless Bluetooth and<br>manual entry | Wireless Bluetooth | Similar: Manual entry is not a medical<br>device functionality. |
| Educational Articles | Access to patient education articles | None | Similar: Educational article functionality is not a medical device functionality. |
{6}------------------------------------------------
{7}------------------------------------------------
Note: N/A indicates Not Applicable
# 8. Performance Summary Non-
# Non-Clinical Test
### Software Verification and Validation
Software verification and validation has been performed according to FDA guidance for the Content of Premarket Submissions for Software Contained in Medical Devices" . The iCare App software was considered a "moderate" level of concern since a failure or latent flaw in the software could result in minor injury to the patient or operator.
# Wireless Coexistence Test
Wireless coexistence test has been performed to verify that the subject device can be used in intended environments.
#### Cybersecurity
Cybersecurity activities were conducted in accordance with FDA Guidance for Industry and FDA Staff, "Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions." The iCare App underwent appropriate risk-based cybersecurity assessment and testing in accordance with referenced FDA guidance documents.
#### Usability Testing
Usability testing was conducted in accordance with FDA guidance, "Applying Human Factors and Usability Engineering to Medical Devices". The test result demonstrates that the iCare App can be used by lay users with only provided labeling, the device is safe and effective for the intended use.
# Clinical Test
This section is not applicable.
# 9. Comparison to the Predicate Device and the Conclusion
The iCare APP is similar to the predicate device Connect App for iHealth Next. The nonclinical tests all passed the test conditions and demonstrated the iCare APP is as safe and as effective compared to the predicate device.
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.