GECHO is a software package intended to visually assess contrast-enhanced echocardiography for left ventricular function and myocardial blood flow by displaying enhanced images of the heart and Time-To-Replenish images. GECHO is intended for use by a cardiologist. GECHO is for use on images of adult patients who underwent contrast-enhanced echocardiography.
Device Story
GECHO is a software-only image review and analysis platform for cardiologists in echocardiography reading rooms. It processes DICOM R-wave tagged image sequences from contrast-enhanced echocardiograms. The device performs automated image stabilization, ECG gating, and myocardial segmentation (with manual override options). It utilizes a Time-To-Replenish (TTR) algorithm—based on a (1-exp) function—to quantify myocardial blood flow. Key features include image averaging for noise reduction and digital subtraction for contrast enhancement. The device outputs DICOM Secondary capture and DICOM SR files. By providing enhanced visualization and parametric TTR maps, the software assists cardiologists in interpreting left ventricular function and myocardial perfusion, supporting clinical decision-making regarding cardiac health.
Clinical Evidence
No clinical performance data was required. Substantial equivalence is supported by software verification and validation testing and a technical performance assessment of the TTR algorithm using synthetic and representative clinical data. The TTR algorithm demonstrated an RMSE of 0.98 seconds, minimal bias (0.0025 seconds), and robustness to noise (NMSE up to 0.05). An expert survey confirmed the clinical utility and intuitive representation of TTR images.
Technological Characteristics
Software-only radiological image processing system. Inputs: DICOM R-wave tagged image sequences. Processing: Automated image stabilization, ECG gating, manual/automated myocardial segmentation, image averaging, digital subtraction, and parametric imaging using a (1-exp) function. Outputs: DICOM Secondary capture and DICOM SR. Connectivity: Standalone software platform. Regulatory: Class II, Product Code LLZ.
Indications for Use
Indicated for adult patients who have undergone contrast-enhanced echocardiography for the assessment of left ventricular function and myocardial blood flow. Contraindicated for pediatric patients and for use on organs other than the heart.
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}
FDA U.S. FOOD & DRUG ADMINISTRATION
July 14, 2025
Narnar, LLC
% Meri Martinez
Regulatory Affairs Project Manager
Innolctics, LLC
1101 West 34th St. #550
Austin, Texas 78705
Re: K250120
Trade/Device Name: GECHO
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management and Processing System
Regulatory Class: Class II
Product Code: LLZ
Dated: June 27, 2025
Received: June 27, 2025
Dear Meri Martinez:
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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K250120 - Meri Martinez
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (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-reporting-combination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-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/medical-devices/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
{2}
K250120 - Meri Martinez
Page 3
the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,

Jessica Lamb, PhD.
Assistant Director
Imaging Software Team
DHT8B: Division of Radiological Imaging Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
K250120
Device Name
GECHO
Indications for Use (Describe)
GECHO is a software package intended to visually assess contrast-enhanced echocardiography for left ventricular function and myocardial blood flow by displaying enhanced images of the heart and Time-To-Replenish images. GECHO is intended for use by a cardiologist.
GECHO is for use on images of adult patients who underwent contrast-enhanced echocardiography.
Type of Use (Select one or both, as applicable)
☑ 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 displays a currently valid OMB number."
{4}
K250120
| narnar | 510(k) Summary |
| --- | --- |
| | Page 1 of 6 |
# 1. CONTACT INFORMATION
| Company Name | narnar, LLC |
| --- | --- |
| Address | 525 3rd St, Suite 231 Lake Oswego, OR 97034 |
| Phone Number | 503-442-9273 |
| Company Representative | Jiri Sklenar, CEO |
| Email | jiri@narnarhealth.com |
| Primary Correspondent | Jiri Sklenar, CEO |
| Primary Correspondent Email | jiri@narnarhealth.com |
| Date Summary Prepared | January 16th, 2025 |
# 2. DEVICE INFORMATION
| Trade Name | GECHO |
| --- | --- |
| Common Name | Radiological Image Processing System |
| Product Code | LLZ |
| Regulation Number | 892.2050 |
| Class | Class II |
| Panel | Radiology |
# 3. PREDICATE DEVICE INFORMATION
| Predicate Device Name | QLAB Advanced Quantification Software |
| --- | --- |
| Predicate Device K Number | K181264 |
| Product Code | LLZ |
| Regulation Number | 892.2050 |
| Class | Class II |
| Panel | Radiology |
510(k) Summary
{5}
narnar
510(k) Summary
Page 2 of 6
# 4. DEVICE DESCRIPTION
GECHO is an image review platform and analysis software that assists cardiologists in the interpretation of left ventricular function and myocardial blood replenishment from two-dimensional, contrast-enhanced echocardiograms.
# 5. INTENDED USE/INDICATIONS FOR USE
GECHO is a software package intended to visually assess contrast-enhanced echocardiography for left ventricular function and myocardial blood flow by displaying enhanced images of the heart and Time-To-Replenish images. GECHO is intended for use by a cardiologist.
GECHO is for use on images of adult patients who underwent contrast-enhanced echocardiography.
# 5.1. Contraindications for Use
GECHO is not for use for pediatric patients. GECHO is not for use on organs other than the heart.
# 6. SUBSTANTIAL EQUIVALENCE DISCUSSION
Table 1. Comparison of the Intended Use and Technological Characteristics of GECHO and the Predicate Device.
| Row # | Characteristic | Subject Device | Predicate Device | Differences |
| --- | --- | --- | --- | --- |
| 1 | Trade Name | GECHO | QLAB Advanced Quantification Software | N/A |
| 2 | Manufacturer | narnar, LLC | Philips Ultrasound Inc. | N/A |
| 3 | K# | K250120 | K181264 | N/A |
| 4 | Device classification | Class II | Class II | None. |
| 5 | Indications for Use / Intended Use Statement | GECHO is a software package intended to visually assess contrast-enhanced echocardiography for left ventricular function and myocardial blood flow by displaying enhanced images of the heart and Time-To-Replenish images. GECHO is intended for | QLAB Advanced Quantification Software is a software application package. It is designed to view and quantify image data acquired on Philips ultrasound systems. | Both devices have similar indications for use. The main difference is that the predicate is indicated for use on Philips ultrasound systems, while the subject device is compatible with multiple manufacturers. |
510(k) Summary
{6}
narnar
510(k) Summary
Page 3 of 6
| Row # | Characteristic | Subject Device | Predicate Device | Differences |
| --- | --- | --- | --- | --- |
| | | use by a cardiologist.
GECHO is for use on images of adult patients who underwent contrast-enhanced echocardiography. | | |
| 6 | Device Type | Radiological Image Processing System | Radiological Image Processing System | None. |
| 7 | Classification Regulation | 21 C.F.R. § 892.2050 | 21 C.F.R. § 892.2050 | None. |
| 8 | Product Code | LLZ | LLZ | None. |
| 9 | 510(k) Exempt | No | No | None. |
| 10 | Rx/OTC | Rx only | Rx only | None. |
| 11 | Patient Population | Anyone eligible for contrast-enhanced echocardiography. | Unspecified. | None. Neither the subject nor predicate device is indicated for use by a limited patient population. |
| 12 | Intended Use Environments | Echocardiography reading rooms. | Clinics, hospitals, office-based practices, and clinical point-of-care settings. | The intended use environment of GECHO is within the scope of those of the predicate device, therefore this difference does not raise additional questions of safety or effectiveness. |
| 13 | Module of Interest | N/A | Cardiac Parametric Quantification (Cardiac PQ) Q-App. | GECHO has specialized functionality that is comparable to the function of the QLAB Cardiac PQ Q-App. Q-App modules of the predicate device function independently, so this does not raise questions of safety or effectiveness. |
| 14 | Anatomical Region | Heart | Heart | None. |
| 15 | Scan Type | Echocardiogram | Echocardiogram | None. |
| 16 | Software only device? | Yes | Yes | None. |
510(k) Summary
{7}
narnar
510(k) Summary
Page 4 of 6
| Row # | Characteristic | Subject Device | Predicate Device | Differences |
| --- | --- | --- | --- | --- |
| - | Key Functions and Features | - | - | - |
| 17 | Manual, editable segmentation of the myocardium | Yes | Yes | None. |
| 18 | Automated image stabilization | Yes | Yes | None. |
| 19 | Automatic detection of the first frame after flash images with optional manual overwrite | Yes | Yes | None. |
| 20 | Automatic ECG gating with optional manual overwrite | Yes | Yes | None. |
| 21 | Image averaging of stabilized, ECG-gated images | Yes | No | Image averaging is a common noise-reduction technique that does not represent a clinically meaningful risk to the safety or effectiveness of GECHO. |
| 22 | Baseline subtraction and color coding | Yes | No | Digital subtraction is an established technique in contrast radiology that does not represent a significant risk to the safety or effectiveness of GECHO. |
| 23 | Parametric Imaging using (1-exp) function | Yes | Yes | None. |
| 24 | Use of color palettes to display parametric images. | Yes | Yes | None. |
| - | Technical Specifications | - | - | - |
510(k) Summary
{8}
narnar
510(k) Summary
Page 5 of 6
| Row # | Characteristic | Subject Device | Predicate Device | Differences |
| --- | --- | --- | --- | --- |
| 25 | Input file type | DICOM file – R-wave tagged image sequences captured during an exam using a contrast agent. Power mode data is not supported. | DICOM files – R-wave tagged image sequences captured during an exam using a contrast agent. Including echo or power mode data. Minimum of 4 R-waves in each scan. | The input files accepted by GECHO are a subset of files supported by QLAB. |
| 26 | Output file type | DICOM Secondary capture, DICOM SR | DICOM Secondary capture, DICOM SR, AVI files | GECHO outputs are a subset of files outputted by QLAB. |
| - | Required Testing | - | - | - |
| 27 | Clinical testing required? | No | No | None. |
| 28 | Software verification & validation required? | Yes | Yes | None. |
# 7. PERFORMANCE DATA
## 7.1. Software Verification and Validation Testing
Software verification and validation testing were conducted, and documentation was provided as recommended by 2023 FDA Guidance “Content of Premarket Submissions for Device Software Functions”.
The software verification and validation testing verified that the design requirements were successfully met. The Intended use and user needs were successfully validated.
As the intended use, functionality and performance of the subject device and the predicate device are equivalent, the result of the performance testing is evidence that the GECHO performs in an equivalent manner to the QLAB Advanced Quantification Software.
## 7.2. Technical Performance Assessment
Technical performance assessment of the subject device involved evaluating the Time-to-Replenish Output (TTR) as recommended by 2022 FDA Guidance “Technical Performance Assessment of Quantitative Imaging in Radiological Device Premarket Submissions”.
510(k) Summary
{9}
narnar
510(k) Summary
Page 6 of 6
The TTR algorithm was tested on synthetic data across a wide range of representative clinical data parameters. Tested parameters included TTR, plateau videointensity (A), the number of selected frames (or heart cycles), heart rate and normalized mean square error (NMSE).
Additionally, an expert survey was conducted to ensure the TTR image correctly represents the information present in raw images and is intuitive and useful, in combination with raw images, for the interpretation of myocardial blood flow.
The TTR (Time-to-Replenish) algorithm demonstrated strong performance with these key metrics:
- RMSE of 0.98 seconds, showing high accuracy
- Minimal bias of 0.0025 seconds
- Can detect TTR values down to 0.5 seconds
- Performs well even with noise (NMSE up to 0.05)
These results validate that the algorithm is reliable for assessing myocardial blood flow in clinical settings.
## 7.3. Clinical Performance Testing
No clinical performance data was necessary to claim substantial equivalence.
## 8. CONCLUSION
The GECHO shares similar technological characteristics, intended use, and functionality with the predicate device. There are no differences between the devices that raise new questions of safety and effectiveness.
Furthermore, technical performance test data and software verification and validation demonstrate that GECHO performs comparably to the predicate device in terms of safety and effectiveness.
Based on the device comparisons and the acceptable testing results, it is determined that GECHO is substantially equivalent to the predicate device.
510(k) Summary
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.