K192732 · Preventice Technologies, Inc. · DSI · Mar 26, 2020 · Cardiovascular
Device Facts
Record ID
K192732
Device Name
BodyGuardian Remote Monitoring System
Applicant
Preventice Technologies, Inc.
Product Code
DSI · Cardiovascular
Decision Date
Mar 26, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1025
Device Class
Class 2
Attributes
AI/ML, Pediatric
Indications for Use
The BodyGuardian System detects and monitors cardiac arrhythmias in ambulatory patients, when prescribed by a physician or other qualified healthcare professional. Not for use with patients requiring attended, in-hospital monitoring for life threatening arrhythmias. The Preventice BodyGuardian Remote Monitoring System is intended for use with adult and pediatric patients in clinical and non-clinical settings to collect and transmit health parameters to healthcare professionals for monitoring and evaluation. Health parameters are collected from a variety of commercially available, external plug in devices such as ECG sensors, weight scales, blood pressure meters and pulse oximeters, and parameters such as ECG, heart rate, body weight, temperature, respiration rate, blood pressure, and SpO2. The Preventice BodyGuardian Remote Monitoring System does not provide any diagnosis.
Device Story
System collects health parameters (ECG, heart rate, weight, temperature, respiration, blood pressure, SpO2) via external plug-in sensors; transmits data to remote server for healthcare professional review. Used in clinical/non-clinical settings; operated by patients and monitored by clinicians. Provides data visualization for clinical evaluation; does not provide automated diagnosis. Benefits include remote monitoring of ambulatory patients.
Clinical Evidence
No clinical testing performed. Substantial equivalence supported by non-clinical bench testing, including EMC, electrical safety, system safety, software verification/validation, and biocompatibility. Pediatric usability study conducted to assess risks.
Technological Characteristics
Ambulatory cardiac monitor and data hub. Connects to external sensors (ECG, scales, BP, pulse oximeters). Transmits data to remote server. Complies with ISO 60601 (Edition 3.1) for electrical safety. Biocompatible materials used for patient contact.
Indications for Use
Indicated for adult and pediatric patients in clinical and non-clinical settings for detection and monitoring of cardiac arrhythmias. Not for patients requiring attended, in-hospital monitoring for life-threatening arrhythmias.
Regulatory Classification
Identification
The arrhythmia detector and alarm device monitors an electrocardiogram and is designed to produce a visible or audible signal or alarm when atrial or ventricular arrhythmia, such as premature contraction or ventricular fibrillation, occurs.
Special Controls
*Classification.* Class II (special controls). The guidance document entitled “Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm” will serve as the special control. See § 870.1 for the availability of this guidance document.
{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 is in blue and includes the letters "FDA" followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in a stacked format.
March 26, 2020
Preventice Technologies, Inc. Charles Rector VP of Quality, Regulatory & Logistics 3052 Hwy52 N, Building 003-2 Rochester, Minnesota 55901
Re: K192732
Trade/Device Name: BodyGuardian Remote Monitoring System Regulation Number: 21 CFR 870.1025 Regulation Name: Arrhythmia Detector And Alarm (Including ST-Segment Measurement And Alarm) Regulatory Class: Class II Product Code: DSI Dated: February 20, 2020 Received: February 24, 2020
Dear Charles Rector:
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. 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 requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part
{1}------------------------------------------------
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 (QS) 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 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-regulatoryassistance/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,
Jennifer Shih Assistant Director (Acting) 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
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K192732
Device Name BodyGuardian Remote Monitoring System
#### Indications for Use (Describe)
The BodyGuardian System detects and monitors cardiac arrhythmias in ambulatory patients, when prescribed by a physician or other qualified healthcare professional. Not for use with patients requiring attended, in-hospital monitoring for life threatening arrhythmias.
The Preventice BodyGuardian Remote Monitoring System is intended for use with adult and pediatric patients in clinical and non-clinical settings to collect and transmit health parameters to healthcare professionals for monitoring and evaluation. Health parameters are collected from a variety of commercially available, external plug in devices such as ECG sensors, weight scales, blood pressure meters and pulse oximeters, and parameters such as ECG, heart rate, body weight, temperature, respiration rate, blood pressure, and SpO2.
The Preventice BodyGuardian Remote Monitoring System does not provide any diagnosis.
| 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."
{3}------------------------------------------------
| 510(k) Summary (As required by section 21 CFR 807.92(c)) | |
|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Submitter: | Preventice Technologies, Inc.<br>3605 Hwy 52N, Building 003-2<br>Rochester, MN 55122 |
| Contact Person: | Charles Rector<br>Vice-President, Quality/Regulatory<br>Telephone: 763-225-4977<br>Email: crector@preventice.com |
| | Preventice Technologies, Inc.<br>3605 Hwy 52N, Building 003-2<br>Rochester, MN 55122 |
| Date Prepared: | September 25, 2019 |
| Trade Name: | BodyGuardian Remote Monitoring System |
| Common/Usual Name: | Remote Monitoring System |
| Classification: | 21 CFR 870.1025<br>Patient Physiological Monitor (with arrhythmia detection) |
| Product Code: | DSI |
| Manufacturer: | Preventice Technologies, Inc.<br>3605 Hwy 52N, Building 003-2<br>Rochester, MN 55122 |
| Establishment Registration: | 3009883402 |
| Predicate Device: | BodyGuardian Remote Monitoring System, K151188 |
| Device Description: | Arrhythmia Detector and Alarm;<br>Patient Physiological Monitor (with arrhythmia detection) |
| 510(k) Summary (As required by section 21 CFR 807.92(c)) | |
| Intended Use | The BodyGuardian System detects and monitors cardiac<br>arrhythmias in ambulatory patients, when prescribed by a physician<br>or other qualified healthcare professional. Not for use with patients<br>requiring attended, in-hospital monitoring for life threatening<br>arrhythmias.<br><br>The Preventice BodyGuardian Remote Monitoring System is<br>intended for use with adult and pediatric patients in clinical and<br>non-clinical settings to collect and transmit health parameters to<br>healthcare professionals for monitoring and evaluation. Health<br>parameters are collected from a variety of commercially available,<br>external plug in devices such as ECG sensors, weight scales, blood<br>pressure meters and pulse oximeters, and parameters such as ECG,<br>heart rate, body weight, temperature, respiration rate, blood<br>pressure, and SpO2.<br><br>The Preventice BodyGuardian Remote Monitoring System does not<br>provide any diagnosis. |
| Comparison of<br>Technological<br>Characteristics: | The predicate device's ECG Unit is a small, ambulatory cardiac<br>monitor that records and transmits ECG data. The subject device's<br>ECG Unit is also a small, ambulatory cardiac monitor that records<br>and transmits ECG data.<br><br>Both products, the predicate and subject devices, provide a data hub function that connects to commercially available devices such as weight scales, blood pressure monitors, pulse oximeters, ECG<br>Units and other plug-in devices.<br><br>For both devices, the predicate and subject devices, data is transmitted to an external device or server, depending model. If not a server, this device sends the data to a remote computer server that allows healthcare professionals to access and review the data.<br><br>There are no fundamental differences between their technological characteristics. |
| 510(k) Summary (As required by section 21 CFR 807.92(c)) | |
| Non-Clinical Testing: | The following bench testing was conducted on the Preventice<br>BG RMS:<br>EMC and electrical safety testing Electrical and mechanical safety testing System safety testing Software verification and validation Performance testing Predicate device comparison tests Usability Testing The following testing has been performed to support<br>substantial equivalence:<br>Biocompatibility for patient contact materials. The following quality assurance measures were applied during development of this device:<br>Failure Mode Effects Analysis/Hazard Analysis (FMEA) Design FMEAs for mechanical and RF designs Performance Requirements Testing including Final System Verification and Validation Testing, ISO 60601 Testing, Edition 3.1. |
| Clinical Testing: | This technology is not new, therefore a clinical study was not considered necessary prior to release. Additionally, there was no clinical testing required to support the medical device as the indications for use is equivalent to the predicate device. The substantial equivalence of the device is supported by the non-clinical testing. |
## 510(k) Summary
{4}------------------------------------------------
{5}------------------------------------------------
{6}------------------------------------------------
| 510(k) Summary (As required by section 21 CFR 807.92(c)) | |
|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Conclusion: | We conclude that the results of testing show the Preventice BG<br>RMS to be substantially equivalent to the predicate device. |
| | The Preventice BG RMS has the same technological characteristics<br>as the predicate device in that all devices are intended to detect,<br>transmit, and report digital data using similar computerized<br>technology. The Preventice BG RMS has the same intended uses as<br>the predicate device in that all devices are intended for ambulatory<br>monitoring. A pediatric usability study has shown no new hazards<br>or risk associated with pediatric use. |
| | It has been shown in this 510(k) submission that the differences<br>between the Preventice BG RMS and the predicate do not raise any<br>questions regarding safety and effectiveness. The Preventice BG<br>RMS, as designed and manufactured, is substantially equivalent to,<br>and as safe and effective as, the referenced predicate device. |
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.