K212516 · Apple, Inc. · QDB · Oct 22, 2021 · Cardiovascular
Device Facts
Record ID
K212516
Device Name
IRNF App
Applicant
Apple, Inc.
Product Code
QDB · Cardiovascular
Decision Date
Oct 22, 2021
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2790
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Atrial Fibrillation Detection
Convolutional neural network
—
Sensitivity: 88.6%, Specificity: 99.3%
Over 2500 subjects and over 3 million pulse rate recordings; split into Training, Validation, Testing, and Sequestration sets.
—
Clinical study of 573 participants ages 22 and older.
—
Indications for Use
Photoplethysmograph analysis software for over-the-counter use. A photoplethysmograph analysis software device for over-the-counter use analyzes photoplethysmograph data and provides information for identifying irregular heart rhythms. This device is not intended to provide a diagnosis.
Device Story
Software-only mobile application (Apple Watch and iPhone) analyzing pulse rate data from Apple Watch PPG sensor. Operates as background screening tool; no user-initiated analysis. Algorithm processes pulse data to identify irregular rhythms suggestive of AFib; confirms findings via internal confirmation cycle. If AFib signs confirmed, Watch app notifies user and syncs data to iPhone Health app. iPhone app provides educational materials, notification history, and irregular rhythm timestamps. Used by consumers in non-clinical settings; encourages users to seek medical care upon notification. Benefits include opportunistic AFib screening for asymptomatic users.
Clinical Evidence
Clinical study of 573 participants (age 22+) with and without AFib history. Subjects wore Apple Watch and reference ECG patch for up to 13 days. Primary endpoint analysis (n=432) showed 88.6% sensitivity (124/140 AFib-positive subjects correctly identified) and 99.3% specificity (290/292 AFib-negative subjects correctly identified).
Technological Characteristics
Software-only mobile application. Uses PPG sensor data from Apple Watch (Series 3, 4, 5, SE). Rhythm classification algorithm utilizes a convolutional neural network (CNN) architecture. Data processed via background screening; syncs via HealthKit. No hardware materials; software-based sensing.
Indications for Use
Indicated for adults 22 years and older without a prior diagnosis of atrial fibrillation (AFib). Intended for OTC use with Apple Watch to analyze pulse rate data for irregular rhythms suggestive of AFib. Not intended for use on every episode of irregular rhythm; provides opportunistic notifications when sufficient data are available during periods of user stillness. Supplements AFib screening; not a replacement for traditional diagnosis or treatment.
Regulatory Classification
Identification
A photoplethysmograph analysis software device for over-the-counter use analyzes photoplethysmograph data and provides information for identifying irregular heart rhythms. This device is not intended to provide a diagnosis.
Special Controls
In combination with the general controls of the FD&C Act, the photoplethysmograph analysis software for over-the-counter use is subject to the following special controls:
- 1. Clinical performance testing must demonstrate the performance characteristics of the detection algorithm under anticipated conditions of use.
- 2. Software verification, validation, and hazard analysis must be performed. Documentation must include a characterization of the technical specifications of the software, including the detection algorithm and its inputs and outputs.
- 3. Non-clinical performance testing must demonstrate the ability of the device to detect adequate PPG signal quality.
- 4. Human factors and usability testing must demonstrate the following:
- The user can correctly use the device based solely on reading the device labeling; a. and
- b. The user can correctly interpret the device output and understand when to seek medical care.
- 5. Labeling must include:
- a. Hardware platform and operating system requirements;
- b. Situations in which the device may not operate at an expected performance level;
- A summary of the clinical performance testing conducted with the device: C.
- d. A description of what the device measures and outputs to the user; and
- Guidance on interpretation of any results. e.
In combination with the general controls of the FD&C Act, the hardware and software for optical camera-based measurement of pulse rate, heart rate, breathing rate and/or respiratory rate is subject to the following special controls:
*Classification.* Class II (special controls). The special controls for this device are:(1) Clinical performance testing must demonstrate the performance characteristics of the detection algorithm under anticipated conditions of use.
(2) Software verification, validation, and hazard analysis must be performed. Documentation must include a characterization of the technical specifications of the software, including the detection algorithm and its inputs and outputs.
(3) Non-clinical performance testing must demonstrate the ability of the device to detect adequate photoplethysmograph signal quality.
(4) Human factors and usability testing must demonstrate the following:
(i) The user can correctly use the device based solely on reading the device labeling; and
(ii) The user can correctly interpret the device output and understand when to seek medical care.
(5) Labeling must include:
(i) Hardware platform and operating system requirements;
(ii) Situations in which the device may not operate at an expected performance level;
(iii) A summary of the clinical performance testing conducted with the device;
(iv) A description of what the device measures and outputs to the user; and
(v) Guidance on interpretation of any results.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
October 26, 2021
Apple Inc. Luke Olson Regulatory Affairs Associate 1 Apple Park Way Cupertino, California 95014
Re: K212516
Trade/Device Name: IRNF App Regulation Number: 21 CFR 870.2790 Regulation Name: Photoplethysmograph analysis software for over-the-counter use Regulatory Class: Class II Product Code: QDB
Dear Luke Olson:
The Food and Drug Administration (FDA) is sending this letter to notify you of an administrative change related to your previous substantial equivalence (SE) determination letter dated October 22, 2021. Specifically, FDA is updating this SE Letter due to a typo in the trade name as an administrative correction.
Please note that the 510(k) submission was not re-reviewed. For questions regarding this letter please contact Jennifer Shih Kozen, Office of Cardiovascular Devices, 301-796-5813, Jennifer.Shih(@fda.hhs.gov.
Sincerely,
# Jennifer W. Shih -S
Jennifer Shih Kozen 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
{1}------------------------------------------------
Image /page/1/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo in blue. Underneath the FDA logo is the word "ADMINISTRATION".
October 22, 2021
Apple Inc. Luke Olson Regulatory Affairs Associate 1 Apple Park Way Cupertino, California 95014
Re: K212516
Trade/Device Name: Irregular Ryhthm Notification Feature (IRNF) 2.0 App Regulation Number: 21 CFR 870.2790 Regulation Name: Photoplethysmograph analysis software for over-the-counter use Regulatory Class: Class II Product Code: QDB Dated: August 9, 2021 Received: August 10, 2021
Dear Luke Olson:
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 mav, 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 located 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.
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
{2}------------------------------------------------
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 803) for devices or postmarketing safety reporting (21 CFR 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 (OS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-
542 of the Act); 21 CFR 1000-1050.
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 https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-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-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE(@tda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
# Jennifer W. Shih -S
Jennifer Shih Kozen 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) K212516
Device Name Irregular Rhythm Notification Feature 2.0
#### Indications for Use (Describe)
The Irregular Rhythm Notification Feature is a software-only mobile medical application that is intended to be used with the Apple Watch. The feature analyzes pulse rate data to identify episodes of irregular heart rhythms suggestive of atrial fibrillation (AFib) and provides a notification to the user. The feature is intended for over-the-counter (OTC) use. It is not intended to provide a notification on every episode of irregular rhythm suggestive of AFib and the absence of a notification is not intended to indicate no disease process is present; rather is intended to opportunistically surface a notification of possible AFib when sufficient data are available for analysis. These data are only captured when the user is still. Along with the user's risk factors the feature can be used to supplement the decision for AFib screening. The feature is not intended to replace traditional methods of diagnosis or treatment.
The feature has not been tested for and is not in people under 22 years of age. It is also not intended for use in individuals previously diagnosed with AFib.
Type of Use (Select one or both, as applicable)
| Prescription Use (Part 21 CFR 801 Subpart D) | <span style="text-decoration: overline;"> </span> |
|----------------------------------------------|---------------------------------------------------|
| Over-The-Counter Use (21 CFR 801 Subpart C) | <span style="text-decoration: overline;">X</span> |
#### 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) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirements of 21 CFR §807.92:
### 5.1 Submitter
| Applicant | Apple Inc.<br>One Apple Park Way<br>Cupertino, CA 95014 |
|----------------------------|--------------------------------------------------------------------------------------------|
| Primary<br>Correspondent | Luke Olson<br>Regulatory Affairs<br>Phone: (408) 609-2001<br>Email: luke_olson@apple.com |
| Secondary<br>Correspondent | Dachan Kwon<br>Regulatory Affairs<br>Phone: (669) 268-5659<br>Email: dachan_kwon@apple.com |
| Date Prepared | August 09, 2021 |
## 5.2 Device Names and Classifications
#### Subject Device:
| Name of Device | Irregular Rhythm Notification Feature 2.0 |
|------------------------|------------------------------------------------------------------------------------|
| Classification Name | Photoplethysmograph Analysis Software For Over-The-Counter Use,<br>21 CFR 870.2790 |
| Regulatory Class | Class II |
| Product Code | QDB |
| 510(k) Review<br>Panel | Cardiovascular |
### Predicate Device:
| Predicate<br>Manufacturer | Apple Inc. |
|---------------------------|---------------------------------------|
| Predicate Trade<br>Name | Irregular Rhythm Notification Feature |
| Predicate 510(k) | DEN180042 |
{5}------------------------------------------------
## 5.3 Device Description
Irregular Rhythm Notification Feature 2.0 (IRNF 2.0) is comprised of a pair of mobile medical apps - One on Apple Watch and the other on the iPhone.
IRNF 2.0 is intended to analyze pulse rate data collected by the Apple Watch PPG sensor on Apple Watch Series 3. Series 4. Series 5. and SE to identify exisodes of irreqular heart rhythms consistent with AFib and provide a notification to the user. It is a background screening tool and there is no way for a user to initiate analysis of pulse rate data. IRNF 2.0 iPhone App is part of the Health App. which allows users to store, manage, and share health and fitness data, and comes pre-installed on every iPhone.
IRNF 2.0 Watch App refers to the rhythm classification algorithm, confirmation cvcle algorithm, and the AFib notification generation. If an irreqular heart rhythm consistent with Afib is identified and confirmed through the confirmation cycle, IRNF 2.0 Watch app will notify the user and transfer the AFib notification to the iPhone App through HealthKit sync. In addition to indicating the finding of signs of AFib, the notification will encourage the user to seek medical care.
IRNF 2.0 iPhone App contains the onboarding and educational materials that a user must review prior to use. IRNF 2.0 iPhone App is designed to work in combination with IRNF 2.0 Watch App and will display a history of all prior AFib notifications. The user is also able to view a list of times of the irreqular rhythms contributing to the notification.
## 5.4 Indications for Use
The Irreqular Rhythm Notification Feature is a software-only mobile medical application that is intended to be used with the Apple Watch. The feature analyzes pulse rate data to identify episodes of irregular heart rhythms suggestive of atrial fibrillation (AFib) and provides a notification to the user. The feature is intended for over-the-counter (OTC) use. It is not intended to provide a notification on every episode of irregular rhythm suggestive of AFib and the absence of a notification is not intended to indicate no disease process is present; rather the feature is intended to opportunistically surface a notification of possible AFib when sufficient data are available for analysis. These data are only captured when the user is still. Along with the user's risk factors the feature can be used to supplement the decision for AFib screening. The feature is not intended to replace traditional methods of diagnosis or treatment.
The feature has not been tested for and is not intended for use in people under 22 years of age. It is also not intended for use in individuals previously diagnosed with AFib.
{6}------------------------------------------------
## 5.5 Comparison with the Predicate Device
| Item | Subject Device | Predicate Device |
|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | IRNF 2.0 App (K212516) | IRNF App (DEN180042) |
| Manufacturer | Apple Inc. | Apple Inc. |
| Submission<br>Reference | K212516 | DEN180042 |
| Intended Use | Photoplethysmograph analysis<br>software for over-the-counter use. A<br>photoplethysmograph analysis<br>software device for over-the-counter<br>use analyzes photoplethysmograph<br>data and provides information for<br>identifying irregular heart rhythms.<br>This device is not intended to provide<br>a diagnosis. | Photoplethysmograph analysis<br>software for over-the-counter use. A<br>photoplethysmograph analysis<br>software device for over-the-counter<br>use analyzes photoplethysmograph<br>data and provides information for<br>identifying irregular heart rhythms.<br>This device is not intended to provide<br>a diagnosis. |
| | Subject Device | Predicate Device |
| ltem | IRNF 2.0 App (K212516) | IRNF App (DEN180042) |
| Indications for<br>Use | The Irregular Rhythm Notification<br>Feature is a software-only mobile<br>medical application that is intended to<br>be used with the Apple Watch. The<br>feature analyzes pulse rate data to<br>identify episodes of irregular heart<br>rhythms suggestive of atrial fibrillation<br>(AFib) and provides a notification to<br>the user. The feature is intended for<br>over-the-counter (OTC) use. It is not<br>intended to provide a notification on<br>every episode of irregular rhythm<br>suggestive of AFib and the absence of<br>a notification is not intended to<br>indicate no disease process is<br>present; rather the feature is intended<br>to opportunistically surface a<br>notification of possible AFib when<br>sufficient data are available for<br>analysis. These data are only captured<br>when the user is still. Along with the<br>user's risk factors the feature can be<br>used to supplement the decision for<br>AFib screening. The feature is not<br>intended to replace traditional<br>methods of diagnosis or treatment.<br>The feature has not been tested for<br>and is not intended for use in people<br>under 22 years of age. It is also not<br>intended for use in individuals<br>previously diagnosed with AFib | The Irregular Rhythm Notification<br>Feature is a software-only mobile<br>medical application that is intended to<br>be used with the Apple Watch. The<br>feature analyzes pulse rate data to<br>identify episodes of irregular heart<br>rhythms suggestive of atrial fibrillation<br>(AFib) and provides a notification to<br>the user. The feature is intended for<br>over-the-counter (OTC) use. It is not<br>intended to provide a notification on<br>every episode of irregular rhythm<br>suggestive of AFib and the absence of<br>a notification is not intended to<br>indicate no disease process is<br>present; rather the feature is intended<br>to opportunistically surface a<br>notification of possible AFib when<br>sufficient data are available for<br>analysis. These data are only captured<br>when the user is still. Along with the<br>user's risk factors the feature can be<br>used to supplement the decision for<br>AFib screening. The feature is not<br>intended to replace traditional<br>methods of diagnosis or treatment.<br>The feature has not been tested for<br>and is not intended for use in people<br>under 22 years of age. It is also not<br>intended for use in individuals<br>previously diagnosed with AFib |
| Principle of<br>Operation | The IRN 2.0 acquires platform sensor<br>data from Apple Watch. After<br>acquisition, the IRN 2.0 algorithms<br>analyze pulse rate data to identify<br>episodes of irregular heart rhythms<br>suggestive of atrial fibrillation (AFib)<br>and provides notification to the user. | The IRN app acquires platform sensor<br>data from Apple Watch. After<br>acquisition, the IRN app algorithms<br>analyze pulse rate data to identify<br>episodes of irregular heart rhythms<br>suggestive of atrial fibrillation (AFib)<br>and provides notification to the user. |
| Item | Subject Device | Predicate Device |
| | IRNF 2.0 App (K212516) | IRNF App (DEN180042) |
| Clinical<br>Performance | Apple conducted a clinical validation<br>study to assess the performance of<br>the subject IRNF 2.0 app relative to<br>that of the predicate device on a<br>common sensor dataset.<br><br>IRNF 2.0 person-level sensitivity<br>(88.6%) and specificity (99.3%) were<br>both demonstrated to be non-inferior<br>to those of the predicate device. | In a study of 226 participants aged 22<br>years or older wearing Apple Watch<br>and an electrocardiogram (ECG)<br>patch concurrently, 57 participants<br>received AFib notifications.<br><br>Of those, 78.9% (45/57) showed<br>concordant AFib on the ECG patch,<br>while 98.2 % (56/57) showed AFib<br>and other clinically relevant<br>arrhythmias. |
| Compatibility<br>with Intended<br>Platforms | iOS version 15.5 or later<br>watchOS version 8.5 or later<br><br>Apple Watch Series 3, 4, 5, SE<br>iPhone 6s and later | iOS 12.1.1 and later<br>watchOS 5.1.2 and later<br><br>Apple Watch Series 1 and later<br>iPhone 5s and later |
{7}------------------------------------------------
{8}------------------------------------------------
## 5.6 Performance Testing
IRNF 2.0 was verified and validated according to Apple's internal design control processes and in accordance with the special controls for Photoplethysmograph Analysis software for over-the-counter use (21 CFR 870.2790). The testing demonstrated that the device performed according to its specifications and that the technological and performance criteria are comparable to the predicate device.
IRNF 2.0 includes a new rhythm classification algorithm that leverages machine learning techniques to differentiate between AFib and non-AFib rhythms. The new rhythm classification algorithm uses a convolutional neural network based architecture and was trained extensively using data collected in a number of development studies. In total, the studies included over 2500 subjects and collected over 3 million pulse rate recordings on a variety of rhythms including: atrial fibrillation, normal sinus rhythm, sinus arrhythmia, and other ectopic beats (PVCs, PACs).
{9}------------------------------------------------
The studies used to train the convolutional network recruited demographically diverse populations with broad representation of age, sex, BMI, race, and skin tones. Table 2 below summarizes approximate development study demographic characteristics:
| Age Group (years) | |
|---------------------------|-------|
| <55 | 39.5% |
| >=55 to <65 | 25.4% |
| >=65 | 35.1% |
| Sex | |
| Male | 49.6% |
| Female | 50.4% |
| BMI (kg/m2) | |
| <18.5 | 2.2% |
| >=18.5 to <25.0 | 32.7% |
| >=25.0 to <30.0 | 32.2% |
| >=30.0 | 32.9% |
| Race | |
| White | 71.5% |
| Black or African American | 18.0% |
| Other | 10.5% |
## Table 2. Development Study Subject Demographics
For the purpose of developing the algorithm, the data was split into four sets with matching distributions of rhythms and demographics: Traininq, Validation, Testing, and Sequestration sets. The model was trained on the Training set, with the Validation set used for early stopping and threshold selection. The model was then evaluated on the Testing set at reqular intervals during model development. When development was complete the model was locked, and then evaluated on the Sequestration set as a last test to ensure it had not been over-fit to the development data.
{10}------------------------------------------------
## 5.7 Clinical Performance
The performance of the Irreqular Rhythm Notification Feature (IRNF) was extensively tested in a clinical study of 573 participants ages 22 and older with a mix of diagnosed AFib and no known history of AFib. Study demographic characteristics are summarized in Table 3 below:
| | N=573 |
|---------------------------|-------------|
| Age Group (years) | |
| <55 | 123 (21.5%) |
| >=55 to <65 | 140 (24.4%) |
| >=65 | 310 (54.1%) |
| Sex | |
| Male | 286 (49.9%) |
| Female | 287 (50.1%) |
| Ethnicity | |
| Hispanic or Latino | 38 (6.6%) |
| Non-Hispanic or Latino | 535 (93.4%) |
| Race | |
| White | 502 (87.6%) |
| Black or African American | 57 (9.9%) |
| Other | 14 (2.4%) |
## Table 3. IRNF 2.0 Clinical Study Subject Demographics
Enrolled subjects wore an Apple Watch and a reference electrocardiogram (ECG) patch concurrently for up to 13 days. For those subjects contributing data to the primary endpoint analysis, 32.4% (n=140/432) presented with AFib as identified on the reference ECG patch and were included in determining the device sensitivity. Of those, 124 received an IRNF irregular rhythm notification with concordant AFib on the ECG patch, and the sensitivity was 88.6%. Of the 292 subjects who did not present with AFib on the ECG patch and contributed data to the analysis of device specificity, 290 did not receive a notification. The AF detection specificity was 99.3%. The remaining subjects (n=141/573) either contributed data to only secondary endpoint analyses and/or did not complete the study. These results support the device's effectiveness in detecting AFib.
{11}------------------------------------------------
## 5.8 Human Factors Testing
Compared to the predicate device, there is no change to the indications for use, intended user populations, intended part of body applied to, use environment, operating principle, user interactions, use related hazards, use scenarios and critical tasks for IRNF 2.0. As such, Apple leveraged the Usability Engineering Report generated during development of the predicate device.
## 5.9 Conclusion
IRNF 2.0 is substantially equivalent to IRNF as they are identical with respect to intended use and there are no differences in technological or performance characteristics that raise new questions of safety and effectiveness.
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.