- Would EpiSoft replace my current health record system?
It depends what functions your current health record system offers. Generally speaking, EpiSoft should be considered supplementary to any practice management (front-office) system and may often also be
supplementary to your current clinical information system. EpiSoft has a standards-based approach to system integration and there is no reason why you cannot integrate locally stored datasets
with EpiSoft to avoid duplicate data entry. Unlike most inter-enterprise health data connectivity models, we aim for real-time interoperability wherever possible to achieve a seamless flow of data and
work process for users accessing multiple systems.
We would typically recommend interfacing your current application rather than replacing it if it is supporting routine clinical processes. If it is a locally built data entry and reporting
system that has substantial overlap with data items in EpiSoft, there may not be much point in maintaining both systems. So sometimes it will be more practical and cost-effective to decommission locally stored
applications and migrate historical datasets to EpiSoft. You can download and analyse any data in EpiSoft at any time so your access to the raw data does not change. Whether you prefer to supplement your
existing systems with the unique clinical and time saving benefits of EpiSoft or migrate your current data to EpiSoft and use it as your core clinical system is entirely your choice.
- What are the benefits of EpiSoft over a local database or spreadsheet?
Many of the time saving and workflow features of our system are unique to EpiSoft - as far as we know. Some of the more generic of these features are listed on our Features in focus page.
Others are specific to particular clinical communities and are not published on our website.
The many benefits of the cloud computing approach are listed on our Product introduction page and most certainly are not available from a local database
or spreadsheet.
- Can I run a local copy of EpiSoft in my own network?
Yes. EpiSoft is developed on standard architecture (the database is MS SQL 2005) and can be deployed on a server in your own network if that is your preference.
You may not realise all the benefits of the cloud computing approach listed on our Product introduction page if you do this but you may have other reasons to want to host the system
in your own infrastructure.
- Who owns the data?
This question is generally answered by health record and/or privacy legislation in your jurisdiction. Usually it is the party who created the data (that is, the clinician or the organisation
to which the clinician belongs) whos owns the data. In the case of sponsored clinical trials, it would be as determined by the Human Research Ethics Committee submission (typically the study sponsor).
In all cases, EpiSoft is just a service provider. The data ownership paradigm does not change because of the physical location of servers. Our End User Terms & Conditions make explicit these data ownership arrangements.
Our End User Terms & Conditions are available to registered users at any time and to prospective customers of EpiSoft on request.
- Who can access the data?
See our Privacy Statement for further information.
- Is an Ethics Committee submission necessary to use EpiSoft?
The question of whether an HREC submission is required is contingent on what you use the system for. We recommend you refer to relevant
guidelines and codes of practice in your country to determine whether your use of the system warrants an HREC submission.
Australian users, please refer to the following National Health and Medical Research Council publications for further information:
When does Quality Assurance in Health Care Require Independent Ethical Review? (NHRMC, 2003)
National Statement on Ethical Conduct in Human Research (NHRMC, 2007)
