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?
We contract with consultants to identify system vulnerabilities. Those vulnerabilities that can be patched are released for the current version. Vulnerabilities that cannot be patched are addressed in the next release. This is an ongoing process to keep up with the evolving security threats.
Does Cardio Server support large IDNs (independent 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 multiple time zones.
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 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 with the previous ECGs on iOS smart devices.
What are Epiphany's Mobile Capabilities?
Epiphany Healthcare offers Cardio Server Mobile a responsive web technology that enables providers to access and edit ECG data from anywhere with iOS 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 home or office.
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?
Does Cardio Server support Active Directory for single sign on and authentication?
Is LDAP based authentication compatible with Cardio Server?
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 23 different modality types into your EHR with one bidirectional 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 to all major EMRs: Affinity, Allscripts, Athena, Centricity, Cerner, Clinview, CPSI, eClinical, Eclipsys, Epic, HMS, Iatric, Keane, McKesson, Medhost, NextGen, Opus, Prognosis, Pulse, Quadramed, Vista, Siemens, Meditech, Heartland, ChartMaxx.
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 server required to interface to cardiographs?
Yes. Two manufacturers’ devices that Cardio Server integrates with do require ELI Link or GE DICOM Gateway Pro.
Can Epiphany migrate ECG data from other ECG Management systems?
Yes. We have migrated millions of ECGs from MUSE, TraceMaster/IntelliSpace, Cerner, and Pyramis. For more information on this subject, view the second paragraph of this article.
How many companies are involved in producing, delivering, and supporting Epiphany products?
One. Epiphany is responsible for the development, implementation, and support of our products.
Does Epiphany provide 24/7 support?
Are upgrades, updates, new versions etc. included in the support agreement?
Yes, all upgrades are included with an active support agreement. Professional service fees are applied for project management and implementation services. Third-party license upgrades, such as Microsoft Operating systems, and hardware are the user's responsibility.
Do you have local support for our installation?
You provide your own server hardware, your IT department is the front line of hardware support, and Epiphany provides secure, remote software support. Our entire application can be remotely installed and entirely rebuilt in the event of a catastrophic failure. We support over 900 systems worldwide from our service facility in Durham, NC.
Does Cardio Server have 510(k) FDA registration?
Yes, Cardio Server received its 510(k) registration as a Class ll device in November, 2005. A copy of the registration is available upon request.
Can a software-only application for ECG management receive a 510(k) from the FDA?
Yes, the first sentence of Cardio Server's 510(k) registration states that it is available as a software-only application.
How long has Cardio Server been in clinical use?
Cardio Server was first deployed for use in 2001.
How many employees does Epiphany have?
Our staff numbers over 70 and growing.
Does Epiphany own the license to Cardio Server?
Is it true that one company's resting-ECG algorithm is somehow superior to another company's algorithm?
We discuss computerized-ECG findings with physicians every day. The one question that we always ask is, “How often do you agree with the interpretative statements coming from the cardiographs?” We, of course, hear the occasional extremes “never” or “95% of the time.” The most common answer, however, regardless of the cart manufacturer is, “60 to 75% of the time we agree with the computerized interpretation.”
When you transfer ECGs with interpretations from a cardiograph to Cardio Server, the original statements and measurements pass through to Cardio Server without modification. If you like your current algorithm you will still see the same data.
Is it true that transferring from carts to an ECG management system other than that of the cart manufacturer will void your cart warranty?
No. Epiphany has many sites with carts transferring to Cardio Server without voiding the warranty.
Can Cardio Server accept wireless transfer from MAC 5000/5500 cardiographs?
Yes. We have hundreds of GE carts transmitting ECGs wirelessly to Cardio Server.
Can I purchase Silex, wireless modems for my MAC carts from Epiphany?
Yes. The modems come with instructions for installation by Biomed, telephone support, and the original Silex warranty.
Why do the competitors say that Epiphany is either going out of business or going to get acquired?
We have heard a variety of rumors and misinformation over the last 15 years. This can happen when you displace older, staid companies in a monopolized market niche. We believe that robust competition benefits the end users with more features at better prices. We are growing, business is strong, and our customers are benefiting.
How does Epiphany import device data?
Most of our modality imports have both alpha/numeric feeds and waveform-PDFs. Supported formats include DICOM, XML, HL7, and PDF. When we receive the alpha/numeric data, we post it into editable fields. This is so much more than simply taking a PDF in for storage.
When we get only a PDF, we are doing much more to support our customers. Our PDF Import Tool allows the importation of any PDF to Cardio Server where we create a new modality in the database and populate all demographics with an ADT or orders feed. Our tool provides you flexible workflow including a cover page for physician interpretation, forms, acronyms, electronic signature, HL7 messaging into the EMR, automated messenger functions, and administrative reporting.
Have a question not answered by our FAQs? Contact us. We will respond to your inquiry as soon as possible.