Vios Monitoring System(TM) Model 2050; Vios Central Station Monitor/Vios Central Server Software
K232354 · Murata Vios, Inc. · DRT · Mar 22, 2024 · Cardiovascular
Device Facts
Record ID
K232354
Device Name
Vios Monitoring System(TM) Model 2050; Vios Central Station Monitor/Vios Central Server Software
Applicant
Murata Vios, Inc.
Product Code
DRT · Cardiovascular
Decision Date
Mar 22, 2024
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Indications for Use
The Vios Monitoring System (VMS) is intended for use by medically qualified personnel for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. It is indicated for use in monitoring of 7-lead ECG, heart rate, functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure and activity. VMS allows for the input of body temperature, and can display data from peripheral devices. VMS can generate alerts when the physiological vital signs fall outside of selected parameters. VMS can also generate alerts when cardiac arrhythmias (Tachycardia, Asystole, Ventricular Fibrillation and Atrial Fibrillation/ Atrial Flutter) are detected. The ECG rhythm analysis is intended for use by medically qualified professionals in the identification of arrhythmia events and to aid in clinical review of arrhythmias and medical interventions. The Vios CSM/CS Software is indicated for use by healthcare professionals for the purpose of centralized monitoring of patient data within a healthcare facility. The Vios CSM/CS SW receives, stores, and displays patient physiological and waveform data and alarms generated by Vios proprietary patient vitals monitoring software.
Device Story
Vios Monitoring System (VMS) Model 2050 is a wireless mobile platform for monitoring adult patient vitals in healthcare facilities. System components include a patient-worn Chest Sensor, Finger Adapter, Central Server, and Central Monitoring Station. The Chest Sensor collects physiological data (ECG, heart rate, SpO2, NIBP, activity) and transmits via Bluetooth to the VMS software. The software runs on commercial IT platforms, receiving, analyzing, and displaying waveform data and alarms. Arrhythmia detection algorithms identify events like Tachycardia, Asystole, and AFib/Flutter. Clinicians use the Central Station to review patient data and alarms to aid in clinical decision-making and medical interventions. The system provides centralized monitoring, allowing healthcare professionals to respond to out-of-parameter vital signs or detected arrhythmias, potentially improving patient safety through timely clinical response.
Clinical Evidence
Bench testing only. Performance of the arrhythmia detection algorithm was evaluated against the consensus standard ANSI/AAMI EC57:2012. Additional validation was performed using records from the LTAF, AAEL, and VFDB databases. No clinical trials were conducted for this submission.
Technological Characteristics
Wireless mobile monitoring platform. Components: Chest Sensor (CS2050), Finger Adapter, Central Server, Central Monitoring Station. Connectivity: Bluetooth. Standards: ANSI/AAMI EC57 (arrhythmia), IEC 60601-1 (electrical safety), IEC 60601-1-2 (EMC), IEC 60601-1-8 (alarms), IEC 60601-2-27 (ECG), IEC 60601-2-49 (multifunction), ISO 10993 (biocompatibility), ISO 80601-2-61 (pulse oximetry), ANSI C63.27 (wireless coexistence). Software development per EN 62304; Usability per EN 62366; Risk management per ISO 14971.
Indications for Use
Indicated for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. Monitors 7-lead ECG, heart rate, respiratory rate, pulse rate, SpO2, NIBP, posture, and activity. Detects cardiac arrhythmias including Tachycardia, Bradycardia, Asystole, Ventricular Tachycardia, Ventricular Fibrillation, Atrial Fibrillation, and Atrial Flutter.
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 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, with the letters "FDA" in a blue square. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
March 22, 2024
Murata Vios, Inc. John Lansdown General Manager, Quality, Regulatory, & Compliance 700 Commerce Drive. #190 Woodbury, Minnesota 55125
## Re: K232354
Trade/Device Name: Vios Monitoring System (Vios Monitoring System(TM) Model 2050; Vios Central Station Monitor/Vios Central Server Software 2050) Regulation Number: 21 CFR 870.2300 Regulation Name: Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms) Regulatory Class: Class II Product Code: QYW, DQA, DPZ, DRG, DXJ, OUG Dated: February 22, 2024 Received: February 22, 2024
Dear John Lansdown:
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.
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"
{1}------------------------------------------------
(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 OS 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.
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 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@fda.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
{2}------------------------------------------------
Enclosure
{3}------------------------------------------------
## Indications for Use
Form Approved: OMB No. 0910-0120 Expiration Date: 06/30/2023 See PRA Statement below.
510(k) Number (if known) K232354
#### Device Name
Vios Monitoring System(TM) Model 2050
Indications for Use (Describe)
The Vos Monitoring System (VMS) is intended for use by medically qualified personnel for physiological vital signs montoring of adult (18+) patients in healthcare facilities. It is indicated for use in monitoring of 7-lead ECG, heart rate, functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure and activity. VMS allows for the input of body temperature, and can display data from peripheral devices. VMS can generate alerts when the physiological vital signs fall outside of selected parameters.
VMS can also generate alerts when cardias arrhythmias (Tachycardia, Asystole, Ventricular Fibrillation and Atrial Fibrillation/ Atrial Flutter) are detected.
The ECG rhythm analysis is intended for use by medified professionals in the identification of arrhythmia events and to aid in clinical review of arrhythmias and medical interventions.
The Vos CSM/CS Software is indicated for use by healthcare professionals for the purpose of centralized monitoring of patient data within a healthcare facility. The Vios CSMCS SW receives, stores, and displays patient physiological and waveform data and alams generated by Vios proprietary patient vitals monitoring software.
Type of Use (Select one or both, as applicable)
X Prescription Use (Part 21 CFR 801 Subpart D) [ ] 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 displaysa currently valid OMB number."
{4}------------------------------------------------
# 510(k) Summary
### 510(k) Summary
| Submitter: | Murata Vios, Inc.<br>700 Commerce Drive, Suite 190<br>Woodbury, MN 55125 |
|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact Person: | John Lansdown<br>General Manager, Quality, Regulatory, & Compliance<br>john.lansdown@murata.com<br>Office: 651-888-8125 |
| Date Prepared: | 8/4/2023 |
| Trade Names: | Vios Monitoring System™ Model 2050<br>Vios Central Station Monitor/Central Server Software 2050 |
| Common Name: | Vital Signs monitor |
| Regulation: | 21 CFR § 870.1025 Arrhythmia detector and alarm (including ST-segment measurement<br>and alarm).<br>21 CFR § 870.2300 Cardiac Monitor (including cardiotachometer and rate alarm)<br>21 CFR § 870.2910 Radiofrequency physiological signal transmitter and receiver<br>21 CFR § 870.2700 Oximeter<br>21 CFR § 870.2710 Ear oximeter<br>21 CFR § 870.2450 Medical cathode-ray tube display<br>21 CFR § 880.6310 Medical device data system |
| Classification: | Class II |
| Review Panels: | Cardiovascular, Anesthesiology |
| Product Codes: | QYW, DQA, DPZ, DRG, DXJ, OUG |
| Predicate Devices: | Vios Monitoring System™ Model 2050 (K172586)<br>Vios Central Station Monitor/Central Server Software 2050 (K173107)<br>ViSi Mobile Monitoring System (K180472) |
| Device Description: | The Vios Monitoring System (VMS) Model 2050 is a wireless mobile medical device<br>platform that allows caregivers in healthcare settings to monitor patient vitals.<br>The VMS includes a proprietary monitoring software, Chest Sensor, Finger Adapter and<br>Central Server and Central Monitoring Station.<br>The VMS BSM SW Model B2050 is stand-alone software that can receive, analyze, and<br>display physiological vitals data from one or more patient-worn sensors via standard<br>communication protocols (Bluetooth™). It runs on a commercial IT platform and is<br>intended to be used in conjunction with the Vios Chest Sensor and Vios Lead Adapters<br>and can support peripheral, medical grade, Bluetooth™-enabled devices.<br>The VMS Chest Sensor Model CS2050 is a small, patient-worn, non-sterile multiple use, |
| Indications for Use: | The Vios Monitoring System (VMS) is intended for use by medically qualified personnel<br>for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. It is<br>indicated for use in monitoring of 7-lead ECG, heart rate, respiratory rate, pulse rate,<br>functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure, and<br>patient posture and activity. VMS allows for the input of body temperature, and can<br>display data from peripheral devices. VMS can generate alerts when the physiological<br>vital signs fall outside of selected parameters.<br>VMS can also generate alerts when cardiac arrhythmias (Tachycardia, Bradycardia,<br>Asystole, Ventricular Tachycardia/ Ventricular Fibrillation and Atrial Fibrillation/ Atrial<br>Flutter) are detected.<br>The ECG rhythm analysis is intended for use by medically qualified professionals in the<br>identification of arrhythmia events and to aid in clinical review of arrhythmias and<br>medical interventions.<br>The Vios CSM/CS Software is indicated for use by healthcare professionals for the<br>purpose of centralized monitoring of patient data within a healthcare facility. The Vios<br>CSM/CS SW receives, stores, manages, and displays patient physiological and waveform<br>data and alarms generated by Vios proprietary patient vitals monitoring software. |
| Summary of<br>Substantial<br>Equivalence | The Vios Monitoring System has the following similarities and differences with the<br>indicated predicate devices:<br>Intended use -The proposed device, Vios Monitoring System monitors the same vital<br>signs as the predicate, previously cleared Vios Monitoring System (K172586) except for<br>the addition of arrhythmia detection feature, which is included in the predicate, Visi<br>Monitoring System (K180472). Considered together, the intended use of the proposed<br>device is the same as the Vios Monitoring System the addition of arrhythmia detection<br>like the Visi System. The Vios Monitoring System, is similar to the predicate devices, is<br>intended to be used by licensed practitioners in a healthcare environment.<br>Device Performance – The modified Vios Monitoring System with the addition of<br>arrhythmia detection has been verified to meet the performance requirements as outlined<br>in the consensus standard ANSI/AAMI EC57:2012 - Testing and reporting performance<br>results of cardiac rhythm and ST-segment measurement algorithms. The subject device's<br>performance was also evaluated using additional records from LTAF, AAEL and VFDB<br>database. The predicate device (K180472) has also been tested for compliance to ANSI/<br>AAMI EC57 for the arrhythmia features.<br>Technology -The Vios Monitoring System is unchanged from its predicate submission<br>(K172586) except for the addition of arrhythmia detection measurement. The VMS<br>arrhythmia detection measurement feature are based on similar characteristic features to<br> |
| Summary of Non-<br>Clinical, Clinical, and<br>Conformance Testing | The non-clinical tests for evaluation of performance of Vios system with the addition of<br>arrhythmia alarms is based on ANSI/AAMI EC57, showing substantial equivalence to the<br>predicate (K180472). The subject device's performance was also evaluated using<br>additional records from LTAF, AAEL, and VFDB database, other than referred in the<br>standard. |
| | Other system performance remains unchanged from the predicate (K172586) except the<br>following standard: |
| | • AAMI/ANSI EC57 |
| | The safety and effectiveness of the VMS Model 2050 based on the following standards<br>remains unchanged: |
| | • Electrical safety, EMC, and vitals sign monitoring standards (IEC 60601-1, IEC<br>60601-1-2, IEC 60601-1-8, IEC 60601-2-27, IEC 60601-2-49, EC53)<br>• Biocompatibility standards (ISO 10993)<br>• Transportation Simulation testing (ASTM D4169-16)<br>• Software development life cycle (EN 62304)<br>• Usability and human factors standards (EN 62366)<br>• Risk Management (ISO 14971)<br>• Pulse oximetry clinical testing (ISO 80601-2-61)<br>• Respiratory Rate clinical testing<br>• Standard for evaluation of Wireless Coexistence (ANSI C63.27) |
| Conclusions: | Based on the results from the non-clinical tests performed, Murata Vios considers the<br>Vios Monitoring System to be as safe, as effective and substantially equivalent to the<br>legally marketed predicate devices. |
{5}------------------------------------------------
{6}------------------------------------------------
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.