Most likely, you are using a computerized billing and scheduling system, regardless of whether you are currently using electronic medical records (EMR). With more than one computer used in your practice, it is more than likely that you are on a network. When multi-user, multi-tasking EMI systems are integrated into practice, the complexity of capabilities and network designs becomes significant. Although many practitioners simply intend to hire an IT consultant or firm to solve these problems, this article will discuss some of the most common network design concepts that need to be considered.
Networking basics: WAN, LAN or MAN
Some EPM / EMR software may not be compatible with system software or network hardware. This needs to be determined before purchasing your system, and if you think that you are adding other users, it is often more economical to acquire licenses for several users rather than individual retail software packages. A local area network (LAN) can connect computers and printers in a limited space, such as an office. This LAN can connect to other LANs via wireless or network connection.
Unfortunately, some EPM / EMR applications may have compatibility issues between the network and the operating system software. This compatibility must be ensured before purchasing the EMR package. In addition, if you expect you to add new users, it is often more efficient to buy a license to use multiple users, rather than individual consumer licenses in a retail network.
A broadband network (WAN) connects small local area networks or metro networks (MAN). This can be done in a wider geographic area, as in a number of remote offices. These wans are often used by large companies. The most widely known WAN is today called the Internet. The Internet can allow access to the intranet of a company where employees communicate with each other no matter where they are. For an EPM / EMR system that operates between satellite offices, a stable high bandwidth connection is imperative for continuous and smooth operation.
Bandwidth and Topology
Network bandwidth is the capacity of the data that it can carry, usually expressed in bits per second or bps. Connection speeds range from 56 kilobits per second to millions of bits per second. However, the actual time to reach bandwidth may be limited by the hardware used, sometimes even the software used. In addition, the overall network speed can be significantly reduced as several users try to access information from the EMR system.
A fast connection means little if the network speed is slow due to poor scheduling or insufficient equipment. Network topology is also important. Topology is the physical form of a network, as in a chain of computers that minimizes the amount of wiring between them. However, if one part of this network goes down, it can pull out the entire network. A better topology requires more wiring, but is resistant to system failure than a single weak point. However, the total amount of machines in this type of network is limited. Large networks use a mesh topology that provides redundancy and provides better extensibility.
Wires
On average, the paperless technology office room, exam room contains computers connected to the server that runs the EMR software. However, some physicians who are technically savvy may want to enter information into a wireless device, passing it between areas in practice. The concept of a wireless network adds a new series of points to solve.
Signal strength - We found that wireless access devices collect less-promised ranges when working in a typical office setting with many walls.
Bandwidth - Even if your LAN has good bandwidth, the access speed may be limited by the speed of your wireless connection.
Security - Hackers can destroy your network if it is not properly protected. Even a basic wireless access point should have built-in protection that can be easily enabled.
Fat or thin clients - Will you use wireless laptops that run the software directly on a wireless connection (fat), or automatically launch the software over a remote connection (thin)? Disconnection is a simple fact for wireless networks; thin client allows the program to continue to work in this case, allowing you to pick up where you were interrupted. A fat client solution with a broken connection can lead to subsequent software failure.
