Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

The Path to Meaningless Use:

As many of you know the ACE 2010 event just took place last week. As I was pouring through some of the handouts I couldn’t help but be drawn into the “Handy Trail Guide” which Allscripts has touted as “The Path to Meaningful Use” This is a great high level guide to reaching Stage 1 of Meaningful Use – Capture and Share Data.

The more I read through this the more I thought of how clients will be looking at this with an eye to the shortest path to receiving their stimulus check, and rightfully so – every group should be looking to take advantage of this, from the largest hospital to the smallest single-doc practice. However, I wanted to make sure we don’t lose sight of the forest from the trees here and bring this trail guide back to the true reason for the stimulus – improving patient care! Hence the genesis of this article, The Path to Meaningless Use.

There are a couple of main points I’d like to highlight before dissecting the step by step approach.

1. Sell benefits of the EHR – I feel like this process is woefully underappreciated. In order for your rollout to be a success you absolutely need buy-in from all end-users, including physicians, nurses, data-entry folks and really any person that will touch the EHR on any level. How is this product going to improve their productivity? Make their job easier? Make their work experience more enjoyable?
2. Change is a good thing – Change is the process by which innovation and improvement are instilled. I know that people are comfortable with the status-quo and yes, change for change sake is useless, but there’s a reason for change here, I promise! Challenge your co-workers to look at everything objectively and really question if the products and processes currently in place really make sense or if there could be a better way.
3. Make concessions, don’t over-customize – The product is designed to work best when used in an out of the box capacity, sans customizations. The reality is that you probably aren’t going to be able to sell the idea of changing every workflow to fit the product, but that doesn’t mean you shouldn’t try. Ultimately in the long term the stability of the system is most closely tied to how close you stay to it’s intended use, therefore fight for those process changes to model the system, there’s a reason the EHR was designed the way it was! This point goes back to selling the benefits, be able to show how using the new workflows will actually improve the end-user experience!

With those main points made here are a few comments on the step in the Path to Meaningless Use, enjoy!

1. Understand Stimulus – Don’t just aim for the stage 1 level of capturing and sharing data, yes this can improve productivity but don’t lose sight of the true end goal, improving patient care.
2. Assess Gaps – Be honest with yourself. Are the tools you are using as efficient as they could be? Don’t keep old processes and tools in use just because people are “comfortable” with them, if there is a better tool out there, use it! Sometimes taking people out of their comfort zone is exactly what is needed to promote healthy growth.
3. Design New Workflows – Don’t be unwilling to change workflows simply because that’s the way it’s always been done. Be prepared to pitch workflow re-design to physicians with benefits for them in mind.
4. Upgrade EHR & Stimulus Set – Don’t rush this upgrade. There are many factors that go into an upgrade (depending on how many versions you are jumping) and simply upgrading for the sake of getting the stimulus approved version may end up biting you if you haven’t correctly re-worked process flows to use the EHR in a meaningful way.
5. Rollout – During training stress benefits to end users, a 3 day crash course on the new EHR system is great but if you can’t prove to your end users why the new product and workflows make sense you aren’t going to receive full buy in and consequently won’t get the most out of the product.
6. Begin 90-day Meaningful Use – Metrics should be kept on an ongoing basis, not just for 90 days. It’s great to hit the 90 day plateau to receive the stimulus check but the true purpose of the EHR is to improve patient treatment, and you can’t improve what you don’t measure.
7. Report & Claim Stimulus – Nothing meaningless about this step, claim the money and move on to the next stage!

Tags: Allscripts, EHR, Meaningful Use, v11 upgrade

Recently, the Centers for Medicare and Medicaid Services issued the final rule concerning meaningful use of electronic health records looking to qualify for the government incentives intended to increase the implementation of EHRs in the American healthcare system. A collective sigh of relief could be heard in offices of organizations around the country who have been scrambling to try to develop a game plan to meet the requirements outlined in the interim final draft. The final rule was drafted with an eye towards concerns that the requirements in the interim final rule were unattainable. By breaking the requirements down into two sets, a “Core” set of 15 items that all must be implemented, and another “Menu” set of 10 additional items of which only 5 need to be implemented between 2011-2012, CMS has made the process of meeting the requirements appear attainable. The final rule presented by CMS provides a more manageable framework for implementation of the technologies and actually may provide an opportunity for the organizations implementing the electronic health records to get some meaningful use out of the this legislation.

Tags: Allscripts Enterprise EHR, EHR, Meaningful Use

We here at Galen have seen a greater influx of requests to be able to integrate client’s EHR environments with 3rd party applications and/or internet websites.

I’ve created a few examples that I’ve added to our Wiki page.

1. http://wiki.galenhealthcare.com/Patient_Portal_Integration

With this case study Galen had a client who has implemented a patient portal application whereby patients are able to send messages to their doctors regarding tests, results and general questions. The client was looking for a way to have the provider be able to integrate this application directly into the EHR. With RelayHealth’s help we have succesfully built a prototype whereby a provider can seamlessly communicate with a patient in the most efficient manner possible!

2. http://wiki.galenhealthcare.com/images/5/57/Add_new_Web_framework_documents_to_the_EHR.pdf

In this example a client was looking for a new link on their vertical toolbar which would allow them to display any website in their current workspace (the main viewing pane of the EHR). This one example integrates the website directly into the EHR window without having to navigate through a new tab or window, showing a FRAX calculator. The other tab actually has the ability to take in patient context (height, weight, blood pressure, etc.) and pass it into a form automatically populating fields to save physicians valuable time. This article goes through the steps involved in setting up new vertical toolbars, horizontal toolbars, and workspaces to set up these outside websites in the EHR. The actual code to populate patient context is fairly complex but definitely something Galen would love to help out with!

Tags: Allscripts, EHR, EHR Implementation, HL7, Integration, Successful EHR Implementation, Technical

According to an article in Health Data Management, e-prescribing providers will now be able to use e-prescribing for controlled substances (about 20% of all scripts sent). A key piece of the article says, “The rule will permit pharmacies to receive, dispense and archive electronic prescriptions for controlled substances.”

This is a long overdue ruling, and much necessary. It is crazy to think that a paper process was safer (and offered more security) than e-prescribing could. A link to the article is offered below.

http://www.healthdatamanagement.com/news/controlled_substances_e-prescribing_rule_dea-39995-1.html

Tags: E-prescribing, EHR, electronic RX

Business Need/Problem Statement

Some of our clients have recently expressed the desire for a limited, read-only view in to the AE-EHR to extend access to audit entities. For instance, the requirements of one organization included a limited patient-access read-only environment to be in compliance with FDA Research Part 11 restrictions for clinical trials. Another organization needed it for insurance audit purposes. And still again, others desired to provide an extended environment to allow hospitalists, ED physicians, and critical care physicians access to selective patient charts.

Approach

One of the more popular approaches has been to segment out a separate read-only organization in the Allscripts Enterprise Electronic Health Record (AE-EHR). The AE-EHR handles organizations quite nicely and facilitates an approach of segmenting out entities – the following Galen Wiki article covers a scripted means of deploying a new organization in v10 AE-EHR.

Once the organization has been created, patients can then be “bulk-loaded” to the organization via SQL scripts. New AE-EHR users can then be created and associated to this organization. Finally, to setup the read-only portion, security gates can be implemented.

Extendability

An additional requirement of one of our clients included an approach that offered the capability to dynamically add/remove patients to the “Audit” organization real-time. We facilitated this via creation of a file-based interface from ConnectR to the AE-EHR. The interface accepted its input from a well defined flat-file (comma-delimited, including MRN, Action – Add or Remove, and OrganizationID) and utilized that data to add/remove patients to the org via a custom stored procedures – the de facto application programming interface (API) to the AE-EHR clinical database.

And still further, another client requested that the audit/read-only entities (users of the system) be granted the ability to create tasks . For example, the client desired a specific, high priority task, identifiable as originating from the audit/read-only entity – in this case hospitalists which could be assigned to the patient’s PCP. In this case, the clients’ hospitalists could communicate high priority continuity of care tasks, which require prompt reaction, to the PCP at discharge. However, the PCPs should not be able to task back to the hospitalists, and this can be achieved by setting the EnableOrgFilterFlag preference in the AE-EHR.

If your organization needs assistance in setting up a audit environment to provide limited, read-only access to the AE-EHR, please contact sales@galenhealthcare.com and visit our website for more information regarding our technical and professional service offerings.

Tags: Allscripts Enterprise EHR, Audit, EHR, EHR Implementation, Extendability, Interfaces, Read-Only, Tasking