Technical developer responses
| EMR system | OpenMRS | DREAM–Sant Egidio | GHIS | iSanté | WorldVista | OSCAR |
| Servers | ||||||
| Type of servers which can run the EMR back end? | ||||||
| Brands compatible | Dell Power Edge 1950 | Any | Not available | HP/Dell/others | Not available | Any |
| Type of processors compatible | Intel Xeon Processors 5400 series at up to 3.33 GHz | PC | Not available | Intel/others | Not available | Any |
| Minimum number of processors required | 4 | 1 | Not available | 1 | Not available | 1 |
| Minimum hard drive capacity required | 4 GB | 1 GB | Not available | 1 GB | Not available | 200 MB |
| Operating systems compatible with the EMR server | Linux | Windows | Not available | Linux, Windows, Unix | Not available | Linux, Windows, Unix, OSX and Solaris |
| Web servers compatible with the EMR server | Apache, GLASSFISH V2 | Not applicable | Not available | Apache, IIS | Not available | Apache |
| Database systems compatible with the EMR system | MySQL | MS SQL Server | Not available | MySql, MS SQL Server | Not available | MySQL, ORACLE in older releases |
| Other software required for the EMR system functioning | Java JDK 1.6 +, PHP 5.3+ | No required | Not available | LDAP, Java, Perl, Cygwin (Windows only), JasperReports | Not available | Java |
| Approach price of a minimum capacity server to run the EMR system | $4000–$ 5000 | On small centre we use a $500 laptop. | Not available | $2000 | Not available | $329 |
| Workstations | ||||||
| Type of workstations that can run the EMR front end | ||||||
| Brands compatible | PC, NetBook, Tablet 1.5 Ghz any processors | ALL | Not available | Any windows server/notebook | Not available | Any machine that can load a web browser |
| Type of processors compatible | 1.5 Ghz any processors | PC | Not available | Intel/others | Not available | Any |
| Minimum hard drive capacity | 1 GB | 1 GB | Not available | 200 MB | Not available | 100 MB |
| Operating systems compatible with the EMR front end | Linux, Windows | Windows | Not available | Linux, Windows, Unix | Not available | Linux, Windows, Unix, Other, OSX, Android, IOS, blackberry |
| Minimum price of a workstation to run the EMR front end | $500–$1000 | $400 | Not available | $600 | Not available | $250 |
| Networking | ||||||
| Type of networks are compatibles with the EMR system | Ethernet, GPRS, 3G | Ethernet | Not available | Ethernet, Fast Ethernet | Not available | Ethernet, 3G |
| Network bandwidth required to run the system | 10 MB/s, Fast Ethernet | 10 MB/s | Not available | Ethernet | Not available | Ethernet |
| EMR system scalability capabilities | The interfaces can to be developed in any language as flex, gwt or rap. The interface can to be installed in any CMS and can manipulate information using service web with openMRS. We can develop any systems and store the information in openMRS | Actually, the system scalability capabilities are guarantee by the using of a client server architecture with Microsoft SQL Server that provides growing databases with the tools and features necessary to optimise performance, scale-up individual servers and scale-out for very large databases | System is completely scalable, designed for use in small clinics and hospitals | EMR typically needs to support only a few users at a time. No scaling tests have been done | Scales from one user to thousands | The base systems (Java, MySQL etc) are very scalable. Oscar itself has some bottlenecks that will become a problem when getting to hundreds of concurrent users. There are fixes for those but have not been committed back to the trunk. The other approach is to run a distributed strategy with servers linked through the ‘Oscar Integrator’ |
| Interoperability: capabilities to provide standard clinical information to external systems | Yes |
|
| NO | Yes | Yes |
| Interoperability standards supported | HL7, DICOM, LOINC | Not available | Not available | Not available | HL7, DICOM | HL7 |
| Questions regarding the EMR system software development and environment | ||||||
| Licensing requirements of the EMR software | Open source | Free software (Closed Code) | Open source | Free software | Open source | Open source, free software, GPS |
| System architecture | Web based, service oriented, architecture | Client/server | Client/server | Web based | Web based and client/server | Web based and client/server |
| EMR technical documentation availability | Yes | No | Yes, included in source and documentation | Yes | Yes | Yes |
| Software platform used to develop the software | Java Clients, Web Services, PHP Extension CMS Typo3 | NET, Access VBA | MS VB.Net | LAMP | Java Clients, Web Services | Java/Tomcat jsp/MySQL |
| Development environment used to develop the EMR system | Eclipse | VBA, Visual Studio | Visual Studio 2005 | Developers chose favourite IDE | M | Eclipse |
| Language | Java, PHP5 | C#, VB | MS VB.Net | PHP/Ext JavaScript Library | M | Java |
| Type of license of the development environment used to develop the EMR system | Open source | Proprietary | Proprietary | Open source | Open source | Open source |
| Security and privacy | ||||||
| Security characteristics: | User and login.Card, as cards bank Santander. Codification message between provider and client service web | Access only with login and password, user access levels, data exchange between centres or labs encrypted | System access via user name and password, record access based on user ID and type | Uses LDAP for authentication and application proprietary scheme for authorisation and roles | Meets all security requirements for operation in VA Hospitals and CCHIT | A granular security policy exists so access can be restricted |
| HIPAA compliance | Yes | No | No | Yes | Yes | No |
| Community | ||||||
| Is the EMR system supported by a community? | Yes | No | No | No | Yes | Yes |
| Services provided by the community | Documentation, bug reporting, update, module plugin, forum | – | – | – | – | Answering surveys, documentation, translations, some code |
EMR, electronic medical record.