K210999 · Airs Medical, Inc. · LLZ · Oct 14, 2021 · Radiology
Device Facts
Record ID
K210999
Device Name
SwiftMR
Applicant
Airs Medical, Inc.
Product Code
LLZ · Radiology
Decision Date
Oct 14, 2021
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K210999 · Oct 14, 2021
SwiftMR
Airs Medical, Inc.
Retrospective clinical MRI images
Retrospective clinical images were used to validate the performance of the device's noise reduction and sharpness increase algorithms against predetermined acceptance criteria (SNR increase and FWHM decrease).
Performance test using retrospective clinical images; Retrospective performance validation
Brain MRI images
Not applicable for this study
Signal-to-noise ratio (SNR) increase; Full Width at Half Maximum (FWHM) decrease in ROI
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Noise reduction
CNN with cascaded filter banks
Average signal-to-noise ratio (SNR) increase >= 40%
Passed
—
—
Retrospective clinical images
—
Image sharpness
CNN with cascaded filter banks
FWHM of ROI decreased by >= 0.13% in >= 90% of datasets
Passed
—
—
Retrospective clinical images
—
Indications for Use
SwiftMR is a stand-alone software solution intended to be used for acceptance, enhancement and transfer of brain MRI images in DICOM format. It can be used for noise reduction and increasing image sharpness for non-contrast enhanced MRI images. SwiftMR is not intended for use on mobile devices.
Device Story
SwiftMR is a stand-alone software (SaMD) that enhances brain MRI images. It integrates with hospital PACS to automatically process DICOM images in the background. The device uses deep learning algorithms to simultaneously perform noise reduction and sharpness enhancement. Users (radiology technologists) can monitor the automated workflow, check image quality, and adjust settings via a client application. The enhanced images are returned to the PACS for clinical review. By improving image quality, the device assists in diagnostic workflows; it is intended for professional use in clinics, imaging centers, or hospitals.
Clinical Evidence
Bench testing only. Validation used retrospective clinical images. Noise reduction performance: average SNR increased by ≥40% compared to original images. Sharpness increase performance: FWHM of selected ROI decreased by ≥0.13% in ≥90% of test datasets. All verification and validation activities passed.
Technological Characteristics
Software-based image processing system (SaMD). Operates on PC hardware. Inputs/outputs: DICOM format MRI images. Algorithm: Convolutional neural network-based filtering. Functions: Simultaneous noise reduction and sharpness increase. Connectivity: Networked integration with PACS. Deployment: Client-server/background processing.
Indications for Use
Indicated for patients undergoing brain MRI. Used for noise reduction and sharpness enhancement of non-contrast enhanced brain MRI images. Not for use on mobile devices.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{0}------------------------------------------------
October 14, 2021
Image /page/0/Picture/1 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services seal on the left and the FDA acronym and name on the right. The FDA acronym and name are in blue, with the acronym in a square and the name in a sans-serif font.
AIRS Medical Inc. % Jihyeon Seo RA Manager 8-9F, CS Tower, 1838, Nambusunhwan-ro, Gwanak-gu Seoul. Seoul 08788 SOUTH KOREA
Re: K210999
Trade/Device Name: SwiftMR Regulation Number: 21 CFR 892.2050 Regulation Name: Medical image management and processing system Regulatory Class: Class II Product Code: LLZ Dated: August 31, 2021 Received: September 2, 2021
Dear Jihyeon Seo:
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 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for
{1}------------------------------------------------
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 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.
For
Thalia T. Mills, Ph.D. Director Division of Radiological Health OHT7: Office of In Vitro Diagnostics and Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K210999
Device Name SwiftMR
Indications for Use (Describe)
SwiftMR is a stand-alone software solution intended to be used for acceptance, enhancement and transfer of brain MRI images in DICOM format. It can be used for noise reduction and increasing image sharpness for non-contrast enhanced MRI images.
SwiftMR is not intended for use on mobile devices.
| Type of Use (Select one or both, as applicable) | |
|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
| <div> <span> X Prescription Use (Part 21 CFR 801 Subpart D) </span> </div> | <div> <span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> </div> |
## 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}------------------------------------------------
## K210999
Image /page/3/Picture/1 description: The image shows the logo for AIRS Medical. The logo consists of the word "AIRS" in large, bold, black letters. Below the word "AIRS" is the word "MEDICAL" in smaller, gray letters. The font is sans-serif and modern.
## 510(k) Summary
This 510(k) Summary of safety and effectiveness information is being submitted in accordance with the requirements of 21 CFR 807.92.
## I. SUBMITTER
Ms. Jihyeon Seo RA Manager AIRS Medical Inc. 8-9F, CS Tower, 1838, Nambusunhwan-ro Gwanak-gu, Seoul, 08788, Republic of Korea Phone: +82-70-777-5061 FAX: +82-2-6280-3185 Email: seo.kate@airsmed.com
Date Prepared: March 29, 2021
#### II. DEVICE
Name of Device: SwiftMR Common or Usual Name: Medical Image Management and Processing System Classification Name: system, image processing, radiological (21 CFR 892.2050) Requlatory Class: II Product Code: LLZ
#### III. PREDICATE DEVICE
Primary Predicate Device: SubtleMR – K191688 by Subtle Medical, Inc., Class II, CFR 892.2050, classification with product code LLZ.
## IV. DEVICE DESCRIPTION
SwiftMR, is software used as a Medical Device (SaMD) consisting of a software algorithm that enhances images taken by MRI scanners. The device only processes DICOM images for the end User and is intended to be used by radiology technologists in an imaging center, clinic, or hospital.
The device's inputs are standard of care MRI images in DICOM format. The deep learning algorithm produces enhanced images as outputs with reduced noise and increased sharpness in DICOM format. The device applies both denoising and sharpness increase functions simultaneously.
SwiftMR provides an automatic image quality enhancement function for MR images acquired in various environments. SwiftMR can only be used for professional purposes and is not intended for use on mobile devices.
SwiftMR 's automation procedure is as follows:
- . Upload MR images that have been taken or converted to the DICOM format
- . Image quality enhancement using Deep Learning model
- . Download enhanced MR image as DICOM format
There are two deep learning algorithms that should be selected by users according to the pulse sequences. One is for the general pulse sequences and the other is for the TOF pulse sequences. The two deep learning algorithms share network architecture, input data generation method, training procedures. The only difference between the two deep learning algorithms is the input / label dataset used for training.
{4}------------------------------------------------
Image /page/4/Picture/0 description: The image shows the logo for AIRS Medical. The logo consists of the word "AIRS" in bold, black letters on the top line, and the word "MEDICAL" in gray letters on the bottom line. The "A" in AIRS is stylized to look like a triangle.
## 510(k) Summary
After integration with the facilities PACS, SwiftMR performs image processing in the background automatically. At the same time, SwiftMR allows logged-in users to use its functions and change product settings through the client application. When logged in as the System Admin, the function is available to the control automation procedure and system change settings. On the User side, the User can retrieve the results of image processing in the form of a worklist by login to the user account.
The software provides three main functions, which are image processing, quality check and progress monitoring.
The software is intended to run automatically in the background so that it does not interrupt the workflow of users. When the user executes MR scans and saves the images in PACS as he/she usually does, the newly acquired images are automatically uploaded to the server and registered in the database (DB) for image processing. Once image processing is complete, the images are sent back to PACS.
If the user wishes to monitor this automated workflow to check on the status of image processing, he/she can log in to the Client App, and notifications will be received upon each task completion. Detailed information is also available when the main worklist is opened, and MR Study and/or Series in concern is selected.
A settings menu is provided in the form of a user interface to enable users and system admin to modify software settings as required by the institution or respective user.
## V. INDICATIONS FOR USE
SwiftMR is a stand-alone software solution intended to be used for acceptance, enhancement and transfer of brain MRI images in DICOM format. It can be used for noise reduction and increasing image sharpness for non-contrast enhanced MRI images.
SwiftMR is not intended for use on mobile devices.
#### VI. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE PREDICATE DEVICES
The subject device and predicate are both software applications that are loaded into PACS. Both systems have been developed for image enhancement on DICOM images generated by an MRI. The subject device and the predicate device are substantially equivalent in the areas of general function, application, and intended use.
Any differences between the predicate and the subject device have no negative impact on the device safety or efficacy and does not raise any new potential or increased safety risks and is equivalent in performance to existing legally marketed devices.
| Item | Predicate Device<br>(K191688) | Subject Device<br>(SwiftMR) | Differences |
|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Physical<br>Characteristics | Software device that<br>operates on off-the-<br>shelf computer<br>hardware | Same as predicate | No Difference |
| Computer | Linux Compatible | PC Compatible | Differences are basically in the<br>computer operating system but also<br>may have some differences in the<br>processor speeds, amount of RAM<br>memory, monitors, and hard drive<br>space requirements. However, the<br>subject device and the predicate<br>device are substantially equivalent |
| | | | |
| | | | in the areas of technical<br>characteristics, general function,<br>application, and intended use and<br>the computer platform differences<br>do not raise any new potential<br>safety risks. Therefore, it is our<br>determination that there is "No<br>impact on safety or efficacy" and<br>there are no new potential or<br>increased safety risks. |
| DICOM<br>Standard | The software processes | Same as predicate | No Difference |
| Compliance | compliant image data | | |
| Modalities | MRI | Same as predicate | No Difference |
| Image<br>Enhancement<br>Algorithm<br>Description | The predicate software<br>implements an image<br>enhancement algorithm<br>using convolutional<br>neural network-based<br>filtering. Original<br>images are enhanced<br>by running through a<br>cascade of<br>filter banks, where<br>thresholding and<br>scaling operations are<br>applied. Separate<br>neural network-based<br>filters are obtained for<br>noise reduction and<br>sharpness increase.<br>The parameters of the<br>filters were obtained<br>through an image<br>guided optimization<br>process. | SwiftMR implements an<br>image enhancement<br>algorithm using<br>convolutional<br>neural network-based<br>filtering. Original<br>images are enhanced<br>by running through a<br>cascade of<br>filter banks, where<br>thresholding and<br>scaling operations are<br>applied. Neural<br>network-based filters<br>that simultaneously<br>perform noise reduction<br>and sharpness<br>increase functions are<br>obtained. The<br>parameters of the filters<br>were obtained through<br>an image guided<br>optimization process. | The only difference is in how the<br>neural network-based filter exists.<br>As for the predicate device, there<br>are separate filters for noise<br>reduction and sharpness increase.<br>On the other hand, there are neural<br>network-based filters that<br>simultaneously perform both<br>functions for the subject device.<br>However, the same functions, which<br>are noise reduction and sharpness<br>increase, are applied by the filters.<br>Therefore, the difference does not<br>raise new questions of safety or<br>effectiveness. |
| Workflow | The predicate software<br>operates on DICOM<br>files on the file system,<br>enhances the images,<br>and stores the<br>enhanced images on<br>the file system. The<br>receipt of original<br>DICOM image files and<br>delivery of enhanced<br>images as DICOM files<br>depends on other<br>software systems.<br>Enhanced images co-<br>exist with the original<br>images. | Same as predicate | No Difference |
{5}------------------------------------------------
# MEDICA
# 510(k) Summary
{6}------------------------------------------------
## 510(k) Summary
## VII. PERFORMANCE DATA
SwiftMR, has been assessed and has passed all predetermined testing criteria. The Validation Test Plan was designed to evaluate output functions.
Validation testing indicated that as required by the risk analysis, designated individuals performed all verification and validation activities and that the results demonstrated that the predetermined acceptance criteria were met.
The following tests were conducted for SwiftMR:
- 1) Verification testing: Unit test, Intearation/system test conducted. These tests passed.
- 2) Validation testing: Performance test was conducted using retrospective clinical images for both noise reduction and sharpness increase functions.
- For the noise reduction performance, acceptance criteria were defined that the A. average signal-to-noise ratio (SNR) of the SwiftMR-processed image series is increased by 40% or more compared to the value of the original image series. This test passed.
- B. For the sharpness increase performance, acceptance criteria were defined that the FWHM of a selected region of interest (ROI) is decreased by 0.13% or more after applying SwiftMR for at least 90% of the test datasets. This test passed.
Therefore, it was demonstrated that SwiftMR performance was shown to be substantially equivalent to the predicate device.
## VIII. CONCLUSION
The information presented in the 510(k) for SwiftMR contains adequate information, data, and nonclinical test results to demonstrate substantial equivalence to the predicate device. SwiftMR was shown to be substantially equivalent to the predicate device in the areas of technical characteristics, general function, application, and does not raise different 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.