FREQUENTLY ASKED QUESTIONS (AND EZ ANSWERS)
Click on the questions below to get EZ answers to common questions about ezEpi’s system, security, support, and other specifications to learn why ezEpi is the right tool for your health organization’s outbreak management needs.
What is ezEpi?
ezEpi is a web-based relational database Outbreak Management System (OMS) used to help detect and reduce health events such as influenza-like illnesses, foodborne illnesses, and bioterrorism events.
Who uses ezEpi?
ezEpi is used by Local Health Departments (LHD), state health agencies, and other public health organizations as a health event surveillance, investigation, analysis, and reporting tool.
Why should I use ezEpi?
ezEpi makes the data collection, investigation, monitoring, management, analysis, and reporting of health and bioterrorism events easier to help reduce morbidity and mortality, and improve public health.
Where is ezEpi accessed from?
ezEpi is accessed from the “cloud” or internet, and the system resides either on local health organization-owned and managed servers or secure servers remotely hosted and managed by Vitasys.
Can I import and export existing system case data?
Yes. ezEpi has a convenient import/export tool to help make data field mapping, importing and exporting data easy.
Does ezEpi integrate with the National Electronic Disease Surveillance System (NEDSS)?
Yes. ezEpi has a convenient import/export tool to help make data field mapping, importing and exporting data easy, including with NEDSS.
Does ezEpi support CDC’s Public Health Information Network (PHIN) initiative?
Yes. ezEpi uses and actively encourages Health Information Exchange (HIE) standards for easier data transfers and common naming protocols.
Is ezEpi data secure?
Yes. ezEpi uses Active Directory (AD) service created by Microsoft. Active Directory assists with network administration and security, and is responsible for authenticating and authorizing users and computers within a network, as well as assigning and enforcing security policies.
Does ezEpi provide technical support?
Yes, ezEpi was developed by, and is sold and serviced by Vitasys. Vitasys provides system installation guarantees and technical Help Desk support.
What kind of reports does ezEpi provide?
ezEpi provides a number convenient reports, including epi curves, spreadsheets, tables, graphs, and more.
How much does ezEpi cost?
ezEpi is priced according to the population served by a Local Health Department (LHD) based on 2010 US Census Bureau data. LHD’s serving < 50,000 = $9,000 (USD); LHD’s serving 50,000 – 500,000 = $19,000; and LHD’s serving 500,000+ = $29,000. Vitasys also provides an optional 12 month service agreement for nominal additional fees when requested.
What are the system requirements?
ezEpi is a Microsoft IIS-based system with SQL Server. We work closely with department system administrators to ensure successful system installations.
What are the IT costs associated with having this software?
Obviously, every organization is different in the way that it manages its IT infrastructure. Vitasys will work with you in order to determine the path of least resistance when it comes to ezEpi installation, configuration and testing. Here's some information about what your IT people will need to know:
SQL Server 2008 or 2012 is available under three licensing models:
Server plus device client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device.
Server plus user client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each user.
Processor license. Requires a single license for each CPU in the operating system environment running SQL Server. This license includes unlimited client device access.
Which version is suitable for your organization depends on number of users for the system. For a Device or User CAL based License, there will be a nominal server and user number cost. The cost will be higher for a Processor based License. For 30 users or less, we generally recommend a Device/User CAL based License.