EMR Implementation – The Expert Advice (Part 1)

With the government’s initiative to take healthcare into the new era of technology, practices of all sizes are vying to make the transition from paper to electronic documentation. For any practice seeking to make this conversion, a thorough analysis of their operations is required in order to assess how the implementation of an EMR solution should begin. Various operational aspects of the physician’s office have to be factored in prior to the beginning of the EMR implementation phase. Ray Parker, an EMR implementation specialist at a major health IT organization, gives us his take on the subject matter explaining the approach that practitioners should take in order to ensure a smooth execution of the system within their offices.

First and foremost, general practitioners and specialists alike have to identify the specific needs of their practices, while fully comprehending the reasons for conversion from paper to electronic medical records or a switch to a different EMR vendor. They have to ask whether they are looking to expedite documentation and reporting, and whether their existing solution inadequately equipped to handle these needs. Regardless of the motives driving physicians towards adoption, their eventual goal may well be common i.e. complying with Meaningful Use measures. If they are conforming to the standards set by CMS, the practice efficiency and expedition of operational processes is expected to improve by leaps and bounds. A significant determinant while finalizing your selection of the vendor should be the qualifications of the vendor organization (with special emphasis on the quality certifications) and subsequently judging the capability of the vendor in terms of meeting your practice requisites.

During the process of ascertaining the clinical and administrative requirements of the practice, some fundamental questions need to be answered and communicated with your vendor. For instance, how many clinicians are based within the practice, the workflows they follow, how many staff members need access to the system and what will be the corresponding training requirements etc? The practice has to be prepared beforehand to convey the entirety of its needs to their chosen service provider preceding a demo of the vendor system. For example a practice might want to stop getting paper faxes and want to receive their faxes electronically instead, or a practice may want to opt for an electronic lab interface with a local lab company. To help the vendor understand specific practice requirements, it’s very helpful to ensure that providers share their existing clinical data templates and specialty specific workflows before scheduling a demo with the vendor.

With respect to implementation, it’s of utmost significance that communication between physicians and vendors is crystal clear regarding data preservation requirements of the practice. Keeping into mind the legal ramifications of maintaining historical data (which varies from state to state), a provider has to aptly determine how much data has to kept and migrated. The vendor must be able to meet these necessities or propose appropriate alternatives to avoid unwarranted outcomes. Size and nature of their data plays a huge role at this stage, as clinical and billing data from older/outdated EMRs is very tedious to extract and even more complex to migrate. Apart from the data requisites of the practice, the clinician should also communicate any specific hardware requirements with their vendor. This provides an opportunity to the vendor to deal with any hardware compatibility problems that may arise at a later stage.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s