Does the software have the ability to interface with local laboratories and hospitals?
To decrease the amount of time spent duplicating order forms and other paperwork, practices should look for software that can interface with the labs and hospitals that they most often use. If an EHR cannot be found that interfaces with all, practices should consider purchasing separate interfaces to make the interconnectivity possible. • Does the software work with your technology infrastructure? Think about how the requirements of the EHR software fit with your current and future technological capabilities. For example, many practices with remote offices opt to use a “thin-client environment,” where the EHR is loaded onto a central server, which can be accessed from any computer by logging on to the server. Practices can then choose whether to install computers in every room, or use laptops or tablets. • Is the EHR an application service provider (ASP)? Unless you have very specific needs, choosing a vendor with an EHR as an ASP is easiest. The ASP vendor hosts the servers, maintains
Related Questions
- How is the interface with Microsoft SMS and the ability to take an inventory snapshot of the installed network hardware/software in a distributed environment?
- What is meant by online versus offline restores? How is this affected by the client software’s local storage feature?
- Does the software have the ability to interface with local laboratories and hospitals?
