Frequently Asked Questions

Information Technology 

Can we provide our own server hardware?
Yes, we utilize your preferred vendor for servers or virtualized servers such as VMware, Citrix XenServer and Windows Server Hyper-V. Epiphany will provide specifications based on your testing volume.

Is Cardio Server compatible with virtual environments? Yes, virtualized servers such as VMware, Citrix XenServer and Windows Server Hyper-V are supported.

How many concurrent users does Cardio Server support?
Cardio Server is scalable from 3 to 250 concurrent users. A concurrent user is not a seat license as with some systems. Concurrent users apply to anyone accessing the application simultaneously. 

How does Epiphany address security?
Epiphany is one of the few vendors whose software has received DIACAP Certification (DoD Information Assurance Certification and Accreditation Process). During the certification process, every line of code was audited by the Epiphany engineering team for IA (Information Assurance) compliance. All points of entry into the system are documented and tested. Cardio Server also provides comprehensive HIPAA logging for actions and changes in interpretations.

Does Cardio Server support large IDNs (integrated delivery networks)?
Yes, Epiphany offers broad flexibility to enterprise medical systems with multiple hospitals, clinics, and physician practices. Cardio Server supports different levels of complexity and workflow between various sized facilities within your IDN. 

Does Cardio Server support sites in multiple time zones?
Yes, Cardio Server does support sites in multiple time zones on a single platform.

Is Cardio Server compatible with Microsoft.Net architecture?
Yes, Cardio Server is compatible with Microsoft.Net but we do not require it.

Is Cardio Server a web-based, true thin client application?
Yes, Cardio Server is web-based, it is pure IIS. All functions such as reading, editing, and printing can be done from any PC on your network subject to user privileges. No downloadable applets are required and all terminals on the network have full functionality.

What does it mean to be "web-based?"
Web-based means Cardio Server runs in a standard web browser environment without ActiveX, Flash, or .Net. Web-based means interventionalists can view STEMI ECGs with the previous ECGs on smart devices.

Can we use our existing VPN technology for remote access to Cardio Server?
Yes; VPN is an excellent way to provide physicians and others access to their ECG data from their homes or offices.

Can we use our existing SAN, NAS, tape, etc. backup system with Cardio Server?
Yes; simply add Cardio Server to your regular backup procedures.

Can we use our existing SAN for the live database storage?
Yes.

Does Cardio Server support Active Directory for single sign on and authentication?
Yes.

Is LDAP based authentication compatible with Cardio Server?
Yes.

Is our preferred virus protection plan compatible with Cardio Server?
Yes, Cardio Server is a web application running on your infrastructure.

What database program does Cardio Server use?
Cardio Server utilizes MySQL.

How much system administrator support is required by Cardio Server?
Cardio Server requires little day-to-day maintenance. Chief maintenance tasks include patch management, backup oversight, virus protection maintenance, and periodic log review. Note that these recommended practices are generally no different than standard support for any other server – Cardio Server does not require specialized “care and feeding.”

Can Cardio Server take orders from and send results (including waveforms) to our EHR?
Yes, and Cardio Server can support 15 different modality types into your EHR with one bi-directional interface. Cardio Server has its own, internally developed HL7 tool that allows us to customize inbound and outbound HL7 messages to your specifications. Currently deployed interfaces include: Meditech Magic and Client Server, Cerner, McKesson, Siemens, GEMMS, EPIC, Opus, MedWinSys, etc. The interfaces continue to grow; our web site maintains an up-to-date listing.

Can I view ECG data within my cardiology PACS system?
Yes, in most cases. Cardio Server supports an API link and other technologies to receive requests from cardiology PACS to display 12-lead ECGs and other reports within the PACS viewer.

What is an API (application program interface)?
An API is the interface that an application provides in order to allow requests for services to be made of it by other computer programs and/or to allow data to be exchanged between them. In the case of Cardio Server, an API could be used to access ECGs from your PACS.

Is an extra computer required to interface to cardiographs?
No, all of Cardio Server's interface modules are fully integrated into our application.

Other Inquiries 

Have a question not answered by our FAQ? Contact us. We will respond to your inquiry as soon as possible.