Epiphany Cardio Server Mobile is a software application used for accessing and displaying ECG data and related patient information previously stored, analyzed or received by the Cardio Server ECG Management System. The Epiphany Cardio Server Mobile software application is intended to be used from a mobile device to perform the following: View ECG test results, such as waveforms, measurements and diagnosis statements as well as other relevant current or historical patient information originally stored, analyzed or received by the Cardio Server ECG Management System. View the ECG lead traces using different display settings. Compare the results of current ECG tests with the patient's previous ECG test results stored on the Cardio Server ECG Management System. Perform manual ECG-related measurements using the electronic caliper tool. Communicate information with the Cardio Server ECG Management System such as login credentials and user settings. Epiphany Cardio Server Mobile application is intended to be used under the direct supervision of a licensed healthcare practitioner and by trained operators. Epiphany Cardio Server Mobile is not intended for real time monitoring.
Device Story
Software application for mobile devices (iPad/iPhone) providing remote access to ECG data stored on Cardio Server ECG Management System; requires Wi-Fi or cellular connection. Input: stored ECG waveforms, measurements, and patient data from server. Operation: displays ECG traces, allows manual measurements via electronic caliper tool, and enables comparison of current/historical tests. Output: visual representation of ECG data on mobile screen. Used by clinicians/trained operators in clinical or remote settings. Does not store data locally; does not perform automated analysis or pattern recognition; does not modify original waveforms. Benefits: enables remote clinical review of ECG results, facilitating timely decision-making by healthcare providers.
Clinical Evidence
Bench testing only. Software verification, validation, and security testing performed. Unit and system-level testing confirmed operability with the predicate system and user accuracy of ECG waveform representation in simulated environments. Testing verified display quality, zoom, navigation, and measurement accuracy compared to the source Cardio Server ECG Management System.
Technological Characteristics
Software-only application for iOS (Apple iPhone/iPad). Functions as an accessory to Cardio Server ECG Management System. Connectivity via Wi-Fi or cellular. No local data storage. Manual measurement tool (electronic caliper). No automated diagnostic or pattern recognition algorithms. Non-real-time system.
Indications for Use
Indicated for use by trained operators under direct supervision of a licensed healthcare practitioner to access and display previously stored ECG data, waveforms, measurements, and diagnostic statements from the Cardio Server ECG Management System on mobile devices. Not for real-time monitoring.
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains 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, followed by the words "U.S. FOOD & DRUG" in blue, and the word "ADMINISTRATION" in smaller blue letters below that.
July 30, 2018
Epiphany Healthcare, LLC % Mark Job Responsible Third Party Official Regulatory Technology Services, LLC 1394 25th Street, NW Buffalo, Minnesota 55313
Re: K181720
Trade/Device Name: Epiphany Cardio Server Mobile Regulation Number: 21 CFR 870.1425 Regulation Name: Programmable diagnostic computer Regulatory Class: Class II Product Code: DOK Dated: June 28, 2018 Received: June 29, 2018
Dear Mark Job:
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/CombinationProducts/GuidanceRegulatoryInformation/ucm597488.html; 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 http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/) and CDRH Learn (http://www.fda.gov/Training/CDRHLearn). 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 (http://www.fda.gov/DICE) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
M.A. Wilhelmsen
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) K181720
Device Name Epiphany Cardio Server Mobile
#### Indications for Use (Describe)
Epiphany Cardio Server Mobile is a software application used for accessing and displaying ECG data and related patient information previously stored, analyzed or received by the Cardio Server ECG Management System. The Epiphany Cardio Server Mobile software application is intended to be used from a mobile device to perform the following:
· View ECG test results, such as waveforms, measurements and diagnosis statements as well as other relevant current or historical patient information originally stored, analyzed or received by the Cardio Server ECG Management System.
· View the ECG lead traces using different display settings.
· Compare the results of current ECG tests with the patient's previous ECG test results stored on the Cardio Server ECG Management System.
· Perform manual ECG-related measurements using the electronic caliper tool.
· Communicate information with the Cardio Server ECG Management System such as login credentials and user settings.
Epiphany Cardio Server Mobile application is intended to be used under the direct supervision of a licensed healthcare practitioner and by trained operators. Epiphany Cardio Server Mobile is not intended for real time monitoring.
| Type of Use (Select one or both, as applicable) | |
|---------------------------------------------------------------------------|--------------------------------------------------------------------------|
| <div> <span>☑</span> Prescription Use (Part 21 CFR 801 Subpart D) </div> | <div> <span>☐</span> Over-The-Counter Use (21 CFR 801 Subpart C) </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}------------------------------------------------
# 510(k) SUMMARY Epiphany Cardio Server Mobile
Epiphany Healthcare, LLC
3000 E. Boundary Terrace, Suite 2
Midlothian, VA 23112
Contact Person: Pat White
Phone: 336-617-7923
Fax: 703-991-2501
Date Prepared: July 27,2018
| Name of the device: | Epiphany Cardio Server Mobile |
|-----------------------------|-----------------------------------------------|
| Common Name: | Cardio Server Mobile |
| Classification Name: | Programmable Diagnostic Computer/ 870.1425 |
| Classification Regulation: | 21 CFR 870.1425 |
| Product code: | DQK |
| Device Class: | Class II |
| Primary Predicate Device: | McKesson Cardiology ECG Mobile (K133534) |
| Reference Predicate Device: | Cardio Server ECG Management System (K052883) |
### Intended Use / Indications for Use
Epiphany Cardio Server Mobile is a software application used for accessing and displaying ECG data and related patient information previously stored, analyzed or received by the Cardio Server ECG Management System. The Epiphany Cardio Server Mobile software application is intended to be used from a mobile device to perform the following:
- . View ECG test results, such as waveforms, measurements and diagnosis statements as well as other relevant current or historical patient information originally stored, analyzed or received by the Cardio Server ECG Management System.
- View the ECG lead traces using different display settings. .
- Compare the results of current ECG tests with the patient's previous ECG . test results stored on the Cardio Server ECG Management System.
- . Perform manual ECG-related measurements using the electronic caliper tool.
{4}------------------------------------------------
- . Communicate information with the Cardio Server ECG Management System such as login credentials and user settings.
The Epiphany Cardio Server Mobile application is intended to be used under the direct supervision of a licensed healthcare practitioner and by trained operators. The Epiphany Cardio Server Mobile application is not intended for real-time monitoring.
# Technological Characteristics
The Epiphany Cardio Server Mobile provides secure access to ECG records and related information contained on the Cardio Server ECG Management System. The Epiphany Cardio Server Mobile software functions as an accessory to the Cardio Server ECG Management System, and requires a WIFI or cellular connection to a pre-installed and properly configured Cardio Server ECG Management System. Through providing remote access to the ECG data stored on the Cardio Server ECG Management System, the user is able to review current and previous ECG tests, results, and perform measurements on the ECG waveforms. Cardio Server Mobile does not store ECG or patient related information on the mobile device, does not directly communicate with cardiographs or other waveform acquisition devices, and does not use any automatic electronic data processing and pattern recognition methods to derive measurements (e.g. intervals and amplitudes) or provide diagnostic statements from the ECG data. The device does not allow modification of the original ECG traces (waveforms) stored on the Cardio Server ECG Management System.
The Epiphany Cardio Server Mobile application is not intended to replace the functionalities provided by the Cardio Server ECG Management System desktop client but to extend those to make selected functionalities described above available via mobile devices.
The Epiphany Cardio Server Mobile functions as a non-real time system and is not intended for real time monitoring.
The Epiphany Cardio Server Mobile can be used both inside and outside of medical facilities except in areas where cellular phone or wireless device use is prohibited.
The Epiphany Cardio Server Mobile is intended to operate on Apple iPad and iPhone running iOS mobile operating system from Apple Inc.
# Comparison of Technological Characteristics with the Predicate Device
(See table below.)
{5}------------------------------------------------
| Comparison of Technological Characteristics with the Predicate Device | | | | | | | |
|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------|----|----|----|----|
| Number | Description | Epiphany Cardio<br>Server Mobile | McKesson Cardiology ECG<br>Mobile (K133534) | | | | |
| 1 | Intended Use/Indications for Use<br>View ECG test results from a mobile<br>device, including waveforms,<br>measurements, and diagnosis statements. | Yes | Yes | | | | |
| 1.2 | View current or historical patient<br>information originally stored, analyzed, or<br>received by the device to which this device<br>is an accessory. | Yes | Yes | | | | |
| 1.3 | View ECG lead traces using optional<br>display settings. | Yes | Yes | | | | |
| 1.4 | Compare the results of current ECG tests<br>with any previous ECG test results stored<br>on the device to which this device is an<br>accessory. | Yes | Yes | | | | |
| 1.5 | Perform ECG related measurements using<br>electronic calipers. | Yes | Yes | | | | |
| 1.6 | Communicate information with the device<br>to which this device is an accessory, such<br>as login credentials and user settings. | Yes | Yes | | | | |
| 1.7 | Does not store patient information or test<br>results on the mobile device. | Yes | Yes | | | | |
| 1.8 | Does not provide real-time monitoring. | Yes | Yes | | | | |
| 2 | Target Population | | | | | | |
| 2.1 | To be used under direct supervision of a<br>licensed healthcare practitioner and by<br>trained operators. | Yes | Yes | | | | |
| 3 | Performance | | | | | | |
| 3.1 | Non-clinical testing included software<br>verification, validation, and security<br>testing. | Yes | Yes | | | | |
| 4 | Materials | | | | | | |
| 4.1 | Software only. | Yes | Yes | | | | |
| 5 | Compatibility with the environment and other devices | | | | | | |
| 5.1 | Requires WIFI or cellular connection to<br>access data. | Yes | Yes | | | | |
| 5.2 | Compatible with Apple iPhone and iPad. | Yes | Yes | | | | |
| 5.3 | Compatible with iOS 10 and later. | Yes | Yes | | | | |
| 5.4 | Compatible with iOS 7.x, 8.x, 9.x versions. | No | Yes | | | | |
| 6 | Where Used | | | | | | |
| 6.1 | To be used in hospital or any remote<br>location that allows mobile device use, cell<br>phone use, or WIFI use. | Yes | Yes | | | | |
| 6.2 | To be used under the direct supervision of<br>a licensed healthcare practioner and by<br>trained operators. | Yes | Yes | | | | |
| 7 | Not applicable to the above devices | | | | | | |
| 7.1 | Thermal Safety | No | No | | | | |
| 7.2 | Mechanical Safety | No | No | | | | |
| 7.3 | Sterility | No | No | | | | |
| 7.4 | Biocompatibility | No | No | | | | |
| 7.5 | Electrical Safety | No | No | | | | |
| 7.6 | Chemical Safety | No | No | | | | |
| 7.7 | Radiation Safety | No | No | | | | |
| 7.8 | 7.9 | Anatomical Site | Energy Used and/or Delivered | No | No | No | No |
| | Epiphany Cardio Server Mobile 510(k) Summary | | | | | | |
{6}------------------------------------------------
# Performance Data
Non-clinical testing performed included software verification, validation, and security testing to ensure that the Cardio Server Mobile met all design specifications and requirements. Unit and system level testing included assurance of operability with the predicate McKesson Cardiology ECG Mobile application and user accuracy qualification of ECG waveform and related information representation in a simulated user test environment.
Bench testing performed verified the Cardio Server Mobile display and measurements capabilities using sample cases based on technical characteristics and relevancy to the intended function of the Epiphany Cardio Server Mobile application. The testing considered different display manipulations (e.g., full-screen display, zoom, navigating between screens, device orientation), display quality, and display accuracy when compared to the original data as presented by Cardio Server ECG Management System. In particular, the testing was performed to ensure adequate user readability and imaqe quality on a small screen.
In all instances, the Epiphany Cardio Server Mobile functioned as intended by the design requirements and the observed results demonstrated substantial equivalence with the predicate device.
## Substantial Equivalence
The Epiphany Cardio Server Mobile has the same intended use, similar indications, technological characteristics and principles of operation as the predicate device. Both devices display ECG tracings and procedure data, and allow for manual waveform measurements.
Any differences between the predicate device and Epiphany Cardio Server Mobile do not raise any new questions related to safety and effectiveness. Based on the performance test results, the Epiphany Cardio Server Mobile is substantially equivalent to the McKesson Cardiology ECG Mobile (K133534).
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.