The EMMa system is intended for diagnostic evaluation of patients who experience transient symptomatic events that may suggest non-lethal cardiac arthythmia to support and possibly improve an ongoing treatment by the patient's physician. Data received from battery powered ambulatory monitoring devices, triggered by an arrhythmia detection algorithm or manually by the patient, are stored and forwarded to licensed physician for review.
Device Story
EMMa (Electronic Monitoring Management) is a server-side software medical device for telemedical cardiac monitoring. It receives physiological ECG data transmitted via GSM from ambulatory monitors (Kate Loop/Kate MCT). The server stores data, enables configuration of remote devices, and facilitates report generation by technicians in a Telemonitoring Service Centre (TSC). Technicians review ECG strips and trend data to create Daily and End-of-Session reports for physicians. The system supports detection of arrhythmias including pause, Afib, VES, VES couplet/triplet, bigeminy, SVES, bradycardia, and tachycardia. EMMa does not perform automated data interpretation; it serves as a management platform for data review and physician communication. It is not intended for real-time monitoring or emergency alerting. By centralizing data and reporting, it assists physicians in diagnostic evaluation and therapy adaptation for patients with suspected non-lethal arrhythmias.
Clinical Evidence
No clinical data were required to support the safety and effectiveness of the device. Substantial equivalence was established through bench testing and software verification/validation.
Technological Characteristics
Standalone software medical device; web-based application. Functions as a data server for ambulatory ECG monitors. Supports up to 3-channel ECG. Connectivity via GSM for data transmission and over-the-air device configuration. Software lifecycle follows IEC 62304; usability engineering follows IEC 62366-1. Software level of concern: moderate.
Indications for Use
Indicated for patients experiencing transient symptomatic or asymptomatic events suggesting non-lethal cardiac arrhythmia. Contraindicated for patients with potentially life-threatening arrhythmias requiring inpatient monitoring or patients requiring hospitalization.
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.
Predicate Devices
DSI/DRG Telesentry, Model TS01, Scottcare Corporation (K092947)
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo features a stylized caduceus symbol, which is a staff with two snakes entwined around it. The caduceus is positioned to the right of the text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA", which is arranged in a circular fashion around the left side of the logo.
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
May 25, 2016
Vitasystems Gmbh Michael Rothhaar Director Corporate Quality Markircher Str. 22 Mannheim, 68229 DE
Re: K153477
Trade/Device Name: Emma 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: April 11, 2016 Received: April 15, 2016
Dear Michael Rothhaar:
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. 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 (reporting of medical device
{1}------------------------------------------------
related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. 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
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours.
for Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K153477
Device Name EMMa - Electronic Monitoring Management
#### Indications for Use (Describe)
The EMMa system is intended for diagnostic evaluation of patients who experience transient symptomatic events that may suggest non-lethal cardiac arthythmia to support and possibly improve an ongoing treatment by the patient's physician. Data received from battery powered ambulatory monitoring devices, triggered by an arrhythmia detection algorithm or manually by the patient, are stored and forwarded to licensed physician for review.
Contraindications of Use:
- Patients with potentially life-threatening arrhythmias who require inpatient monitoring. -
- -Patients who the attending physician thinks should be hospitalized.
The software is not intended to be used to trigger emergency treatment or alert chains.
Type of Use (Select one or both, as applicable)
2 Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
### PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON A SEPARATE PAGE IF NEEDED.
#### FOR FDA USE ONLY
Concurrence of Center for Devices and Radiological Health (CDRH) (Signature)
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 Druq 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}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the logo for Vitasystems. The word "vita" is in a teal color, and the word "systems" is in black. There are three curved lines above the "a" in "vita".
# EMMa
Electronic Monitoring Management
K153477
| Submitter: | Vitasystems GmbH<br>Markircher Str. 22<br>D-68229 Mannheim, Germany<br>Phone: +49 621 178918 100<br>Fax: +49 621 178918 101 |
|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Contact Person:<br>Michael Rothhaar, Director Corporate Quality<br>Phone: +49 621 178918 174<br>Fax: +49 621 178918 101<br>Mail: michael.rothhaar@vitaphone.de |
| Establishment<br>Registration Number:<br>Trade Name: | 3005191294<br>EMMa |
| Common Name:<br>Classification Name: | Cardiac Event Recorder Data Server<br>Detector and alarm, arrhythmia (per 21 CFR Section 870.1025, Product<br>Code: DSI, DRG) |
| Date Prepared: | May 24, 2016 |
{4}------------------------------------------------
Image /page/4/Picture/1 description: The image shows the logo for Vitasystems. The word "vita" is in teal, and the word "systems" is in black. There are three curved lines above the "a" in "vita".
### 1. Legally Marketed Predicate Devices
K092947 DSI/DRG Telesentry, Model TS01, Scottcare Corporation
### 2. Indications & Intended Use
The EMMa (Electronic Monitoring Management) is a standalone software medical device. Connected with battery powered ambulatory ECG monitor devices, it acts as an arrhythmia detector and alarm device. EMMa is designed to receive data, to send configuration parameters to the devices and to enable qualified persons to assess and forward the received data.
The EMMa system is intended for diagnostic evaluation of patients who experience transient symptoms or asymptomatic events that may suggest non-lethal cardiac arrhythmia to support and possibly improve an ongoing treatment by the patient's physician. Data received from battery powered ambulatory monitoring devices, triggered by an arrhythmia detection algorithm or manually by the patient, are stored and forwarded to licensed physicians for review.
#### Contraindications of Use
- Patients with potentially life-threatening arrhythmias who require inpatient monitoring. -
done on the ECG monitoring device, not on the EMMA, and is not scope of this 510k.
- Patients who the attending physician thinks should be hospitalized. -
### 3. Product Description
EMMa (Electronic Monitoring Management) is the server part of a telemedical system to receive data from the ambulatory ECG monitors Kate Loop (Event Monitor) and Kate MCT (Mobile Cardiac Telemetry; similar to Loop but with additional functions like trend data and streaming). Physiological data recorded by the ECG monitors are transmitted via their GSM module (cellular telephon network) to the server EMMa. The detection of arrhythmias and other cardiac conditions is
EMMa is provided to be installed in a Telemonitoring Service Centre (TSC). ECG-technicians / Agents working there generate patient reports from physiological data with the aim to send the reports to the patients' physicians. No interpretation of data is performed by the server software. The generated reports support physicians in adapting the therapy. EMMa is not designed for and compatible with iOS and Android.
Data mapping is implemented by assignment of patient, physician and mobile ECG device in EMMa. The report technicians review ECG-strips and trend data and generate Daily Reports and End of Session Reports. These reports are sent to the assigned physician. A real time monitoring of patients is not feasible with this system.
Data transmissions are triggered by the mobile ECG monitors when abnormal events are detected. Declaration of remarkable events can be configured individually for each device via EMMa based on the patient's physician's recommendations.
Transmissions can also be triggered by a configured timer or manually by patients or agents. The system supports the following events:
- Pause: short Sinoatrial arrest ●
- . Afib: atrial fibrillation
- VES: ventricular extrasystoles ●
{5}------------------------------------------------
Image /page/5/Picture/1 description: The image shows the logo for "vitāsystems". The word "vita" is in a teal color, and the word "systems" is in black. There are three curved lines above the "a" in "vita", which appear to be a design element.
- VES Couplet: pairs or VES ●
- VES Triplet: three VES in a row .
- Bigenimy: heart arrhythmia in which there is a continuous alternation of long and short heart . beats
- SVES Single: single supraventricular extrasystoles
- Bradycardia: slow heart rate (under 60 bpm) ●
- . Tachycardia: heart rate that exceeds the normal resting rate (over 100bpm):
### 4. Substantial Equivalence Discussion
| | EMMa (subject device) | TeleSentry Model TS01 | Comments |
|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
| Premarket<br>Notification<br>Number | K153477 | K092947 | N/A |
| Classification | Arrhythmia detector and<br>alarm | Arrhythmia detector and<br>alarm | same |
| Product Code | DSI<br>DRG | DSI<br>DRG | same |
| Requlation<br>Number | 870.1025 | 870.1025 | same |
| Class | II | II | same |
| Indication for<br>Use | For diagnostic evaluation of<br>patients who experience<br>transient symptoms or<br>asymptomatic events that<br>may suggest cardiac<br>arrhythmia. The device<br>continuously monitors and<br>records the data,<br>automatically records<br>events triggered by an<br>arrhythmia detection<br>algorithm or manually by<br>the patient, and<br>automatically transmits the<br>recorded event activity<br>associated with these<br>symptoms for review by a<br>licensed physician. | For diagnostic evaluation of<br>patients who experience<br>transient symptoms or<br>asymptomatic events that<br>may suggest cardiac<br>arrhythmia. The device<br>continuously monitors and<br>records the data,<br>automatically records<br>events triggered by an<br>arrhythmia detection<br>algorithm or manually by<br>the patient, and<br>automatically transmits the<br>recorded event activity<br>associated with these<br>symptoms for review by a<br>licensed physician. | Same |
| Supported<br>ECG devices | kate Loop + kate MCT | TeleSentry TS01 | Similar, difference<br>does not affect safety<br>or performance |
| Supported<br>ECG modes | Loop (Event Monitor)<br>MCT (Mobile Cardiac<br>Telemetry) | MCT | Difference does not<br>affect safety or<br>performance |
| Transmission<br>method | GSM | Bluetooth/GSM/USB | Similar, difference<br>does not affect safety<br>or performance |
| | EMMa (subject device) | TeleSentry Model TS01 | Comments |
| Device<br>configuration<br>via | GSM | Bluetooth + GSM | Similar, difference<br>does not affect safety<br>or performance |
| Device<br>compatible to<br>IOS or<br>Android | NO | NO | same |
| WIFI | NO | NO | same |
| monitoring in<br>real time /<br>near real time | NO | NO | same |
| Patient<br>management | Yes | Yes | same |
| Device<br>management | Yes | Yes | same |
| Physician<br>Management | Yes | Yes | same |
| ECG Viewer | Yes | Yes | same |
| ECG Live<br>streaming | Yes | Yes | same |
| Trend-data<br>analysis | Yes | Yes | same |
| Reports | End of Session, Daily<br>Report, Event Report | End of Session, Daily<br>Report, Event Report | same |
| Device<br>configuration<br>over the air | Yes | Yes | same |
| Display device<br>status<br>(Battery,GSM) | Yes | Yes | same |
| Leads-<br>On/Leads-Off<br>Event | Yes | Yes | same |
| Events | Pause, Afib, VES, VES<br>Couplet, VES Triplet,<br>Bigenimy, SVES Single,<br>Bradycardia, Tachycardia<br>up to 3 | Tachycardia, Bradycardia,<br>Pause, Afip | same |
| ECG<br>Channels | up to 3 | 3 | same |
| Report<br>Management | Creation and Management<br>of reports inside the<br>software | Creation of reports, no<br>management | Similar, difference<br>does not affect safety<br>or performance |
| User Interface | Web Application | Windows Client | Similar, difference<br>does not affect safety<br>or performance |
| Audit trail | Yes | Yes | same |
{6}------------------------------------------------
Image /page/6/Picture/1 description: The image shows the logo for Vitasystems. The logo is in a sans-serif font, with the "vita" portion in teal and the "systems" portion in black. Above the "vita" portion of the logo are three curved lines, also in teal, that appear to represent sound waves or a similar concept.
{7}------------------------------------------------
Image /page/7/Picture/1 description: The image shows the logo for Vitasystems. The word "vita" is in teal, and the word "systems" is in black. There are three curved lines above the "a" in "vita", which appear to be a design element.
### 5. Non-Clinical Performance Data
Verification and validation activities established the safety and performance characteristics of the subject device with respect to the predicate device. The following performance data have been provided in support of the substantial equivalence determination.
Software Verification and Validation Testing
- IEC 62304;2006, Medical Device Software-Software life cycle processes ●
- Software verification and validation testing was conducted and documentation provided . as recommended by the FDA Guidance for Industry and FDA Staff. Guidance for the Content of Software Contained in Medical Devices. The software is determined as a "moderate" level of concern because a failure or latent flaw could lead to a minor injury to the patient through incorrect information or through the action of the care provider.
#### Other testing
- IEC 62366-1;2015. Medical Devices Part 1—Application of usability engineering to med-● ical devices
EMMa Electronic Monitoring Management meets all the stated requirements and passed all the testing noted above.
### 6. Clinical Performance Data
Clinical data were not required to support the safety and effectiveness of the device EMMa.
#### 7. Statement of Substantial Equivalence
Through the data and information presented, Vitasystems GmbH considers EMMa as substantially equivalent to the previously mentioned predicate device. Any differences between the subject and predicate device have no significant influence on safety or effectiveness as established through performance testing. Therefore, EMMa raises no new issues of safety or effectiveness when compared to the predicate device.
Vitasvstems GmbH Michael Rothhaar Director Corporate Quality
Signature: ...................................................................................................................................................................
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.