Question #1 – Our practice is currently using:

1. EMR on a limited basis – 30%
2. EMR to a significant degree – 26%
3. ePrescribing only – 25%
4. No EMR, just practice management – 17%

Question #2 – My role in the practice is:

1. Administration – 32%
2. IT (information technology) – 28%
3. Clinical/Medical Tech – 22%
4. Physician/Partner – 18%

Question #3 – We anticipate the costs of EMR to our practice will be:

1. More than $10K per provider – 46%
2. Not sure, we have not made the transition yet – 24%
3. Between $5K and $10K per provider – 20%
4. Less than $5K per provider – 8%

Question #4 – Our biggest obstacle to EMR implementation is/was:

1. Physician resistance – 32%
2. Lack of useful information/not knowing where to start – 26%
3. Uncertainty about which system to get – 26%
4. Cost – 15%

Question #5 – Our practice size/situation is:

1. Solo practitioner – 50%
2. Small group, 2-5 physicians – 31%
3. Mid-size group, 6-12 physicians – 12%
4. Large group, less than 40 physicians – 3%
5. Mega-group or clinic, more than 40 physicians – 3%

The most interesting answers I think were to questions 3 and 4. A majority of respondents feel that the cost of EMR implementation will be at least $10K per provider and that physician resistance is the most common obstacle. I am actually not surprised about that last one as that was a major issue in our practice.

Questions or comments? Post them here….

Tweet This Post

EMR Update 6 – eRx and PQRI: Are Your Leaving Money on the Table?

This Issue:

• How can your practice qualify for ‘Stimulus Bill’ financial incentives?
• ePrescribing(eRx) & PQRI – what bonuses can you expect for each?
• How do you make a claim?
• Find out about PQRI Toolset, a tool that can help you claim bonus payments

(Note: MPT has a financial interest in Protodrone LLC, creator of PQRI Toolset)

Tweet This Post

Read more on EMRs and care coordination

Tweet This Post

Last week, one day shy of its Dec. 31 2009 deadline, the Dept. of Health and Human Services issued its long-awaited near-final rules defining the “meaningful use” requirements doctors and hospitals must meet to cash in on the government’s $20 billion-plus health IT incentive programs starting 2011.

Read more on Meaningful Use by Marianne Kolbasuk McGee

Tweet This Post

Stage 1 criteria (the first of 3 total) would cover 25 meaningful use objectives (and 23 for hospitals). These are listed under modules known as Health Outcomes Policy Priorities such as Improving quality and patient safety (use of drug-allergy interaction checks, use of ePrescribing, maintaining active medication list, etc.), Engaging patients and their families in their health care (e.g., provide patients with a copy of their health information), Improving care coordination (e.g., exchanging key clinical information among authorized entities), Improving population and public health (e.g., capability to submit data to immunization registries), and Ensuring adequate privacy and security for personal health information (through the use of appropriate EMR technology).

The implementation of Stage 1 meaningful use standards would begin in 2011. Stage 2 (which would essentially expand upon certain aspects of Stage 1) and Stage 3 (which would deal with achieving improvements in conditions of a national high-priority nature and population health outcomes) would follow later.

While this certainly doesn’t clear things up completely for the individual physician, every piece of information that trickles down from Washington is eventually analyzed and translated for all parties which have a vested interest in the process. Hopefully, resources such as this can help doctors stay informed and as up-to-date as possible.

If you have any comments or questions, please post them here. If we don’t know the answer we’ll certainly try to find someone who does.

Tweet This Post

Tweet This Post

Emailing Documents Instead of Printing

Any forms that have to be distributed throughout the practice are ‘printed’ as PDF files and emailed, instead of printing memos and physically handing them out. This also allows the sender to keep a record of what has been sent. I have also used this to scan and email important documents to myself, which can then be shredded, so I don’t have to drag paperwork home from the office.

Document Repository

The redundancy and security of our servers makes them ideal to store private (for an individual’s use only) and public (for use by all staff members) documents. Some of the doctors use these to backup important personal or financial information. Large documents that are frequently updated, like employee manuals, can be accessed electronically without the need for wasting massive amounts of paper at the slightest change. It can also be used for important timely documents such as a practice-wide Influenza Pandemic plan.

‘All Hands’ Alerts

Previously, someone would have to call the satellite offices to try to locate a missing chart or document. Now an alert is sent to everyone in the practice via the network. This has significantly cut down on hours spent on this process.

Security Issues

Prior to setting up our practice-wide network, we had a rag-tag collection of PCs which were unsupervised. Any employee could send email or access the Internet with impunity. Now that the amount of bandwidth needed for our EPM and EMR is critical, unauthorized use of this resource is a problem. Our administrator can access email or Internet usage and determine its appropriateness. It is important to note that employees should be instructed that use of practice computers is not considered personal and is subject to scrutiny.

Batch Scanning of Paper Documents

Temporary workers help handle the load of documents which need to be scanned into the EMR system – these include laboratory data, personal documents, or medical records from other physicians. The batches are then processed by clinical techs, from whatever location they may be at, and placed in the appropriate patient files.

Public Outlook Folders

Our executive secretary posts the doctors’ social schedule, meeting schedule, and on-call schedules. The clinical supervisor posts announcements, memos, and meeting minutes. The doctors have also posted any articles of interest to others for viewing. Our marketing director posts ad tracking data, as well as advertising proofs for review. Our EMR committee has a shared task-list folder for sharing progress on template changes or other projects.

Confidential Documents

Our bookkeeper and business office personnel can send certain critical documents electronically with password-protection.

Computerized HVAC Control

We installed this system at our ambulatory surgery center. It tracks temperature and humidity throughout the building and plots these on a graph. Our nurse administrator can optimize the system depending on the use of the facility, and can even remotely monitor the system from home if there is a problem at night or over the weekend. We have been able to run the building much more efficiently, recouping half of the system cost already from energy savings.

Networked Devices

Expensive peripheral devices such as color laser printers can be shared among employees, making them more cost-effective. Newer diagnostic equipment is frequently network-ready, so reports can be accessed from anywhere in the practice without having to print and fax, saving paper costs on both ends. Cameras are also networked so images can also be seen electronically instead of using expensive photo paper.

Employee Intranet Portal

This is basically an internal website for staff members only. What started out as a simple way of communicating within the practice has grown into a myriad of tools, from critical ones to fun ones:

• Practice Wiki – from the Hawaiian word wiki meaning ‘fast’, a wiki is a simple website that can be easily edited by many different users. We use this to post manuals and how-to’s for every kind of task or project.
• Employee blog – this is a website managed by our marketing director and keeps the staff up to date on practice news. Employees can also post news of interest to their colleagues which makes it a great morale booster.
• Security cameras – these networked cameras can be accessed by physicians and supervisors. Buildings can be checked on remotely during off-hours or during periods of bad weather. They can also be used for theft deterrence.
• Doctor scheduler tool – supervisors can check all the doctors’ schedules at a glance to determine optimal staff scheduling.
• Work order system – our staff utilizes an online work order system for department-specific issues. Examples include printer cartridges needed at a particular location, a leaky faucet at a satellite office, or a new employee who needs orientation, security codes, or time card access. These ‘orders’ would then be distributed to the appropriate department (physical plant, clinical supervisor, IT staff, HR staff, etc.). In the past, this required phone calls or paper messages which would invariably get lost.
• EMR Bug Tracker – this is a tool used to post problems or ‘bugs’ with the EMR system. These can range from misspelled words to a template that crashes to a wish list item. Our IT department can prioritize these on the fly.
• Various auditor tools – these are used by different supervisors to monitor things such as schedule changes, use of the EMR medication module, coding audits, or triage workflow, to name a few.

Tweet This Post

You see, with the advent of recent privacy regulations, there are increasing responsibilities being placed on the shoulders of medical practitioners to insure the protection of patient medical information. Before we get down to the details, let’s discuss some terminology:

Privacy vs. confidentiality. According to Gary Kurtz, in an article in the Journal of Healthcare Information Management, privacy is the right of an individual to control disclosure of his or her medical information. Confidentiality is the understanding that the information will only be disclosed to authorized personnel. This is what is known as a “need to know” basis.

Information Security. Since patient information will be increasingly common in a digital-only format, loss of electronic medical records could have an adverse impact on patient care. So it is up to the guardian of that information, typically the physician, to ensure that there are proper procedures for protecting both the safety and the integrity of that data.

The data safety relates to such issues as access to the information with minimal downtime, proper backup of the data with redundancy, and a disaster recovery plan which is regularly tested.

Integrity refers to processes which insure a true, uncorrupted and legal record. Most EMR systems maintain what is known as an audit trail, which tracks every change made to a record, when and by whom. Without an audit trail, it would be nearly impossible to tell if a patient’s record had been altered. Imagine a physical chart written on a dry-erase whiteboard – changes could be made at any time without discovery.

That said, the two main issues of information security relate to Who is controlling the information and Who has access to the information.

Who controls the information. Previously we discussed the two main types of EMR systems available: server-based and web-based. In server-based systems, the patient data is typically located on a computer or server in the doctor’s office. The upside: the doctor has ultimate control over the information. The downside: the practice is responsible for maintaining the security of the patient records, something which most medical practices have little experience with.

In a web-based system, the doctor accesses the EMR system via the internet, and the data is located off-site, usually on the server of the EMR vendor or a third party. The upside: these entities usually have a lot of experience with information technology security processes as well as the resources to implement them. The downside: the information may be stored on the same server as information from other medical practices; there is the potential for the information to be accessed by someone other than an authorized party. In addition, loss of the internet connection means loss of access to your patient files.

Who has access to the information. As stated above, access to patient information should be on a “need to know“ basis. There may also need to be additional provisions for restricted types of visits such as patients with HIV, mental health issues, or those undergoing drug treatment.

HIPAA (the Health Information Portability and Accountability Act) determines how patient health information may be shared electronically. So a medical practice would need, according to HIPAA language, to insure the confidentiality of the patient information not only within its domain, but would also need to take any steps necessary to make sure that third parties who have access to the same information (outside vendors, laboratories, consultants, etc.) maintain confidentiality as well. This could even be carried, in the extreme perhaps, to anyone who potentially has access to patient records, such as cleaning service companies or maintenance contractors. A practice would be well-advised to sign Business/Vendor Associate Agreements for HIPAA compliance with these companies. You can find many examples of these online that you can use.

Other potential gaps in information access include:

• computer monitors within sight of other patients (these should be locked if an employee leaves her station)
• printers or faxes located in ‘public’ locations
• lost or misplaced laptops or thumbdrives with critical information and without password protection
• passwords taped on monitors (you should have a strict password policy including passwords which expire periodically)
• doctor or staff smart-phones or PDAs which are not password-protected
• a wireless network in the office with inadequate security encryption
• unattended EMR workstations (these should automatically lock after a short period of inactivity)
• unauthorized software downloads which could allow breach of the network

So, going back to our story about GMail…for a medical practice to use GMail for its email service, it would need to enter into a Vendor Associate agreement with Google Inc. and require Google to adhere to the practice’s procedures and policies for privacy of patient information (and every medical practice that used GMail would have to do the same). Needless to say, Google is highly unlikely to agree to signing these types of agreements with possibly thousands of doctors, and be potentially exposed to significant liability.

Tweet This Post

Some of the specific issues with which you should be familiar include:

Wiring: Typical Cat5e network wires have either a T568A or T568B standard. Select either, and be sure everything is wired to the same standard. The Cat6 wire standard is newer and more expensive, possibly a bit much for most medical practices. Copper wires between telephone communications closets shouldn’t contain segments over one hundred meters. Consider using fiberoptic cable for wiring over longer distances, as these cables can move more information and aren’t as vulnerable to interference and lightning. Fiberoptic, however, is more expensive.

Wireless: Are you considering wireless networking, also known as WiFi? If so, you will have to select a standard: either 802.11a, 802.11b, 802.11g, or 802.11h. Some newer standards provide higher data transfer speeds, but cost significantly more. The wireless standard that you choose should depend on whether you’re running a thin or fat client ( see Designing the Office Network for more about thin vs fat clients. Also, beware of interference from such common devices as cordless phones and microwave ovens.

Overwire: Most existing buildings are wired above the ceiling. Wiring is then dropped down the walls. When wiring, I would recommend ‘double drops,’ as the largest cost of wire installation is the labor. You will thank yourself later when you want to add more network devices (scanners, printers, diagnostic equipment, etc.), as these additional network connections will already be there.

Cooling: Network and server equipment create heat, and tend to shut down when over-heated. Plan for this by being sure that you have adequate cooling – you may want to consider installing a small, dedicated air-conditioning unit.

Electrical connections: It’s a  standard IT practice to have a certified electrician install isolated circuits for your network and servers – usually the outlets are orange so you can tell them apart.

Security: Don’t forget about security! Make the wiring closet secure, and remember that anyone with access to this closet can dismantle your network at any time.

Multiple locations: You’ll have to create a WAN, or wide-area network, to make a connection between remote office locations, so do your research and check out all your options. Larger metropolitan areas will generally have more options available for wide-area networks.

Fiber Backbones: Local utilities commonly maintain a fiber backbone which they allow businesses to access. These fiber backbones allow for high bandwidth rates between office locations (10-100Mbps) at a reasonable cost.

Local Phone Service: Meet with your local telephone sales people and service technicians. They understand the offerings in your geographic area. Some of the key points to discuss are:

• T1 lines: would a Metropolitan Area Network (MAN) or a Point to Point (PTP) be better?
• Inquire about both burst and committed information rates. A fast T1 connection may not cut it if the maximum isn’t available when you need it most.
• Will the phone company supply you with and maintain your router hardware, or will you need to take on this task yourself?

The costs of network infrastructure are much lower in new buildings. Apart from easier (and less costly) installation, the ability to oversee the network wiring in a building under construction is an advantage for clear design. Unfortunately, the majority of practices are located within existing buildings, so sound design and forethought in planning will help save your practice excessive costs and headaches later.

Tweet This Post

Below are some basic principles of computer network design you should be familiar with:

Networking Basics (WAN, LAN, or MAN?)

Certain network hardware and system software may be incompatible with some EMR and EPM systems. Obviously, you should know this in advance. If you plan on adding users to your network at a later time, it’s often better to buy multi-user licenses rather than individual retail software packages. You can connect computers and printers in a practice on a Local-Area Network, or LAN. The LAN can link up with other local area networks via wireless connectivity. But be sure to check with the vendor of the EMR software to insure that it can operate on a wireless network.

A Wide-Area Network (WAN) can connect other smaller LANs, or Metro-Area Networks (MANs). Large practices can use these WANs to connect multiple satellite offices over a wide geographic area, for example.

The most recognized WAN is the Internet. The Internet can also create the possibility of an Intranet, or a private Internet, on which employees can communicate and collaborate with each other, regardless of where they are located. For such a system to function well between dispersed offices, a hi-bandwidth connection is a must in order to maintain smooth operations. We use an Intranet for such things as employee manuals, a practice Wiki, staff newsletters, photo sharing, and educational materials.

Bandwidth and Topology

Data capacity, or network Bandwidth, is often measured in bits-per-second (bps). In most cases connection rates range from 56kbps to millions of bits per second. Even so, the rates achievable may be limited by the hardware or sometimes even the software used. Overall speed on the network can be drastically reduced when many users are trying to use the system at the same time. If network speeds are slow because the hardware is underpowered or the network design is bad, ‘fast’ connection speed rates promised by the internet service provider won’t really mean much.

Network Topology is also important. Topology is the ’shape’ of the network, as in the wiring between a series of computers. This topology should have a clean, intelligent design and not simply daisy-chaining PCs in a random, haphazard way. Optimal topography may mean more wires, but this can contribute to overall system resilience from failure due to a weak spot. Otherwise, if one part of the network fails, the entire network could collapse as a result. Proper topography protects against this sort of situation with redundancies. A network consultant should recommend a good balance between expandability and redundancy.

Wiring

In most cases, a practice running an EMR system will employ hard-wired computers connected to a server. However,  some physicians may prefer to input data via a wireless device, as this can be carried throughout the areas in a practice. However, wireless networks present some new points to address:

Signal

Wireless devices have less-than-expected ranges when functioning in an office with many walls. Many consumer-level devices may be inadequate for the needs of a medical practice network. And they may suffer from interference due to common appliances such as microwave ovens or cordless telephones.

Bandwidth

The useful speed on your local network can be limited by the speed of your wireless connection, even if your LAN has good bandwidth rates.

Wireless Security

A hacker can destroy your network if it isn’t protected. Even simple wireless access points need to have built-in security. This is especially important in the age of HIPAA compliance.

Firewall

And speaking of security, you can protect yourself further by having what is know as a firewall. These are software programs, either stand-alone or as part of a hardware device, which protect private networks against intrusion from the outside world. These have become relatively inexpensive for the small business, especially compared to the cost of a successful network attack.

Fat or Thin Clients?

Should you employ laptops (fat clients) that directly run software and connect to your network via a wireless connection? Or, should you run the software virtually with a network appliance (thin client) via a remote connection? With wireless networks, disconnects are an unavoidable reality. In this case, the thin client lets the software continue to run, and you can later pick up where you left off. A broken connection on a fat client may cause a software crash. On the other hand, the latter has certain other capabilities such as running video programs.

Tweet This Post