Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

Organizations exploring Computerized Physician Order Entry (CPOE) might first pursue low-hanging fruit and implement an electronic workflow for results and keep a paper workflow for orders. Often times, electronic order entry can be cumbersome for end users and cause longer workflows.  As alluded to in a previous blog article, the benefits of implementing a solicited result interface are compelling – reducing paper and scanning, and offers the capability for automated result tasking.

In the Allscripts Enterprise EHR (AE-EHR), results can tie back to existing orders, facilitating completion of the order. This functionality is enabled and configured within the results interface deployed at a particular group and can be achieved in one of two ways:

• Order Number: the Order Number EXT generated from Allscripts is sent back with the results. The Order Number is tied directly to a specific order – a specific CBC order in a patient’s chart.
• Requisition Number: the Req Number EXT generated from Allscripts is sent back with the results. The Requisition Number is tied one or more orders – all orders on a single requisition. A requisition is defined by the Patient, Encounter, Performing Location and Ordering Provider.

For some organizations, a paper order work flow may be utilized, in which a paper requisition is presented to the lab instead of an electronic order. However, the Laboratory Information System (LIS) may not allow for discrete capture of the Allscripts-generated order number or requisition number. For that matter, the LIS also may not have the capability to send back this number in the result interface (typically a HL7 ORU result message).

Additionally, most organizations encounter a percentage of solicited results that do not complete the order. In the latter scenario, a lab may manually enter the order introducing the possibility for human error and can cause issue with not only reconciliation of the order, but potentially patient or provider matching.

Furthermore, if a lab has to change an order for any reason (for instance, changing the orderable item), the corresponding result will likely not reconcile the order (with the AE-EHR, the correct protocol would be to cancel the order and place a new order with the desired changes).

This situation can cause nightmares for organizations that are trying to gain semblance as to where lab vendors stand in terms of order fulfillment.  Additionally, order reconciliation reporting will likely be inaccurate.

This is especially pronounced in v11 AE-EHR, in which solicited results that are unable to reconcile to the original order create a “reported order.’ The original order is left unreconciled and a “duplicate” order renders in the patient chart:

We have resources available on our wiki to guide an organization through interfaced result-driven order reconciliation and can assist those organizations looking to gain control of order fulfillment and reconciliation. Please contact sales@galenhealthcare.com for more information.

Tags: Allscripts Enterprise EHR, CPOE, Crystal Reports, Custom Reports, Integration, Interfaces, Interoperability, Meaningful Use, Order Interface, Reconciliation, Reporting, Requisition, Results Interface

Tags: Allscripts Consultants, Allscripts Demo, Allscripts Enterprise EHR, Data Conversion, EHR Implementation, Enterprise EHR, Extensibility, Integration, Meaningful Use, ScanMD

Last Wednesday I attended the VITL Summit ’10 in Burlington Vermont.  VITL is non-profit “public charity” that operates as a partnership between the public and private sectors; VITL receives funding from the federal and state governments, as well as the Vermont Health IT Fund.

As part of the HITECH Act (Health Information Technology Extension Program) VITL became a Regional Extension Center (REC) and received $6,762,080 in Round 1 funding from the ONC.  RECs provide: training and support services to assist doctors and other providers in adopting EHRs, information and guidance to help with EHR implementation and technical assistance as needed.

The Summit Key Note speaker was Dr. David Blumenthal, the national coordinator for health IT.  Vermont Governor Jim Douglas was also there to emphasize how important the topic is to the state.  Dr. Blumenthal’s speech touched on a variety of topics and as expected, stressed how important the adoption and use of EHRs is to the future of how doctors practice medicine.  An interesting personal note Dr. Blumenthal shared was about his daughter who is currently in Residency.  Her current rotation had her moving from a practice that used an EHR to a practice that did not.  Her immediate response… ‘how could someone possibly be affective without an electronic system in place?’; an opinion father and daughter obviously share.  Along those lines, he suggested that new doctors, fresh out of medical school, would know nothing other than an electronic practice.

Additional notes from Dr. Blumenthal’s remarks;

• Dr. Blumenthal is an self-proclaimed “non-geek”, with a house in South Pomfret, VT.  He believes Vermont serves as a model for how EHR/HIE programs could be designed and thinks VT has a unique, competitive edge because of its collaborative spirit and natural desire to exchange information.
• Some reasons he thinks EHRs develop better doctors;
  • 24/7 Information access – problems, meds, history, etc
  • “See” what’s been done – even if you weren’t around when it happened
  • Knowing/receiving result more quickly
  • Decision support
  • Interaction checking – allergies, meds
• The big benefits of adoption – (most, if not all are oft repeated by those in our industry)
  • Reduce costs – an important point for many of the individuals participating in the conference.  Short term improvements in terms of reducing operational costs of a practice (efficiencies), longer term.. see next bullet.
  • Increase the quality of care – this was a point he expressed a number of times.  He pointed out that perhaps not in phase 1 of MU, but long term (phases 2 and 3), this was the ultimate goal.  I.e. EHRs would improve patient outcomes, remove redundancies and ultimately affect overall patient health.
• 3 Barriers of EHR adoption (+1 more)
  1. Financial
  2. Logistical/technical – especially for smaller practices.. there is a tendency to think it’s too difficult or time consuming
  3. Sharing – Will sharing patient data be accepted?  Will it actually hurt my practice?
  4. Trained workforce – Dr. Blumenthal mentioned that many more colleges and universities are now developing disciplines in Healthcare IT (including some in Vermont!)
• Meaningful Use will be here before you know it…
  • Practices will have 2 years, from Oct 1^st , to pick an EHR and meet MU requirements for reimbursement.  DO NOT wait.  Time will pass quickly and inevitably a bottleneck will develop.

In a separate presentation, VITL’s HIE offering was discussed.  Connection to an Exchange like this one will eventually be a requirement for all those participating in the MU program.  VITL’s exchange is run by GE and like other HIE’s, employs a hub and spoke model to connect practices and make the exchange of patient data possible.  Besides the physical network making the connections and the software platform running the exchange, HIE policy will play a large part in how information is shared.  Whether individual patients choose to participate, what privacy rules are in place and how security is managed will all play a central role in an HIE.

An interesting part of the Summit was the presence of all the big vendors; GE, McKesson, Greenway, NextGen, Athena, Cerner, Medent, eClincalWorks and of course Allscripts.  The interesting part came from being able to go from both to both and see one application after the next.  Seeing and feeling the dramatic differences in how they each work, look and perform.

This year’s event was sold out and overall seemed like a big hit with everyone in attendance.  Great job VITL!

Tags: EHR, EMR, HIE, HITECH, REC, VITL

Currently, exchange of clinical data in and out of the Allscripts Enterprise EHR is facilitated via stored procedures. This  application programming interface (API) approach certainly comes with its downsides. In this article, we propose a re-design of the API to segment out the data and the configuration components of clinical data exchange.

At the outset of an interface project where there has been precedent set (existing Quest or LabCorp <-> AE-EHR order/result data exchange deployments), we almost always get the following questions from the vendor:

• Shouldn’t the interface be the same from client-to-client?
• Why do we need to pay Galen (vendors will often times subsidize the cost of interfaces) to design a known interface deployed across hundreds of clients?
• Why do we need to reinvent the wheel?

Now these are very valid questions. And the response is as follows: Due to the approach utilized with the Allscripts interface API, an interface designer must take care in translating data extracted from outbound stored procedures into a valid, compliant HL7 message the vendor can accept (ORM for orders) and also take care in translating an HL7 message from a vendor (ORU) into a stored procedure call which sets both data elements and configuration options. To help guide the client and vendor through design decisions, Galen provides interface-specific (document, result, immunization) questionnaires.

Back to our proposed re-design: segmentation of the data elements (patient first name, provider ID, order item code) and configuration settings (enable tasking, utilize NPI for provider matching, utilize EntryCode for item matching – setting the traditional form parameters of the inbound stored procedures). With this approach, the vendor is responsible for providing the data elements as they normally do in the HL7 message (ORU for results), and the client sets the configuration settings via a workplace within the TWAdmin context in the AE-EHR – much as they do to set application preferences:

We have covered AE-EHR inbound interfaces quite well, so let’s address proposed re-design for outbound interfaces. Instead of each client requiring a site-to-site VPN and individual interface deployment, what if Allscripts chose some of its top vendor partners (Quest, Labcorp) and offered the capability to exchange out of the box, without the need for one-off interfaces? This approach is somewhat analogous to that of Surescripts acting as the hub and router for electronic prescriptions. In the case of outbound interfaces (orders for our example), there would still be the need to segment data (patient, provider, item) from configuration settings (a setting to enable or disable sending insurance information – IN1 segment of an HL7 ORM order message).

In conclusion the Allscripts clinical data exchange API serves its purpose quite well, but it could do a better job. Much of the functionality is derived from legacy, antiquated methods. Our hunch tells us that in promoting themes of Community Exchange and Connecting, the “new” Allscripts will be addressing this in short order.

Tags: Allscripts Enterprise EHR, ConnectR, Database, Enterprise EHR, Enterprise Order, HIE, HL7, Integration, Interfaces, Interoperability, Meaningful Use, Results Interface, Technical

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

As many of our loyal blog followers know, the Allscripts Client Experience (ACE) is Allscripts annual user conference, and a huge event for Galen. It’s a time for us to reconnect with clients, Allscripts contacts, and build new relationships. The theme of this year’s conference was “GO” – the time is now to implement an EHR, and ensure groups are setup to exhibit Meaningful Use.

Some of my own key highlights and takeaways from ACE:

• “The Path to Meaningful Use”
  • Allscripts offered a handy trail guide for ACE:

• The theme of “Community”
  • Our CEO, Steve McQueen, exhibited some pre-conference foresight in lending his own insight into Galen’s community
  • MyAllscripts - client portal for all Allscripts products facilitating collaboration via discussion forums, enhancement idea exchanges and blogs.

• Analytics
  • Dan Mingle, Chief Physician Execute from Maine MSO and Dan Reber, Lead Product Architect at Precision BI led an informative session on the Analytics product, touching on the correct process to implement Analytics as well as using the cross-tab analysis and linked group analysis.
  • I was unaware of its existence, but a user group community has been established for analytics
  • Precision BI has a roadmap for several improvements

• Aternity – an Allscripts performance monitoring solution
  • The ideal tool is non-invasive, comprehensive, accurate and provides an aggregated analysis
  • Facilitates user-centric proactive IT management
  • Yields performance by location, variation by site, and performance over time

• Allscripts Product Portfolio Roadmap – Jon Zimmerman, Allscripts Senior VP Solutions Management
  • Revenue Mix Changes:
    • Today: Fee for Service and Bonus Payments
    • Tomorrow: Fee for Service, Bonus Payments for Savings, Contract per Patient per Month, and Other P4P
  • Systems Evolution
    • Paper Health Records -> Electronic Health Records -> Electronic Health Systems -> Intelligent Networks
  • Connectivity Blueprint:
    • Allscripts HUB: Connecting commercial lab, hospital, pharmacy, payer, HIE, government registries, and sate RHIO
    • Services Framework: EntEHR, PM, ProEHR, MyWay

For more information regarding the topics touched on above, be sure to visit MyAllscripts to view presentations from ACE.

Thanks again for everyone who stopped by our booth to say hello. It was both great to see old friends and establish new relationships. And a special congrats goes out to Melissa Singh, Analyst at NSLIJ, for winning the grand prize – an Apple IPAD – in our “Spin and Win” drawing.

Tags: Allscripts, Allscripts Enterprise EHR, EHR Implementation, Enterprise EHR, Meaningful Use

Issue:

A recent issue came up with one of our clients in that interfaced patient appointments from their Practice Management system were not making it in a timely manner to the EHR. The client witnessed that appointment messages built up in the interface queue and there was a delay in processing the messages. The client desired a resolution that would assist in speed up of the processing of the messages such that appointments booked in PM would render in the EHR quickly without a disruption to workflow.

Investigation:

Enter the ConnectR Toolbelt “Transaction Processing Time” report:

This report extracts transaction count, minimum, average, and maximum ConnectR processing time per hour. Using the report, the following analysis was conducted.

Findings:

Based on the aforementioned analysis, it was determined that in the clients Live Reg/Sched system target, blocked messages were being logged. Having blocked messages logged can be invaluable when first designing and developing interfaces. However, as evidenced in the analysis, it can lead to performance degradation as the system requires much less processing time when messages are not logged.

Outcome:

Logging of blocked messages in the Live Reg/Sched target was disabled on 6/30/2010 and as witnessed in the analysis spreadsheet the number of transactions decreased by roughly 70% and peak transaction processing time decreased by roughly 90%.

Tags: Allscripts Enterprise EHR, Business Intelligence, ConnectR, ConnectR Toolbelt, Integration, Interfaces, Meaningful Use, SQL Server Reporting Services

Galen Healthcare Solutions is proud to announce that we will be continuing our popular series of free webcasts this fall related to Allscripts Enterprise EHR.   These Webcasts will cover topics including Analytics, Allscripts Enterprise EHR Note, Interfaces, Reports, Allscripts Enterprise EHR Orders, Tech System maintenance.

Learn more »

Tags: Allscripts, Enterprise Order, Galen Webcast Series, Integration, Interfaces, Meaningful Use, Technical

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

Last night, my colleagues and I attended a New England HIMSS event in Wellesley, MA covering Mobile Health. After battling through brutal traffic commuting from Boston to Wellesley during rush hour, we arrived and were all equally impressed with the night’s speaker -  Robert Havasy, Business Analyst at the Center for Connected Health in Massachusetts. I particularly liked the presentation technology used for his pitch – Prezi - a web-based presentation application and storytelling tool that uses a single canvas instead of traditional slides.

Some key takeaways from the presentation:

• Will the FDA regulate smart phones or mobile devices and treat them as medical devices?
• Patients are unencumbered by the regulatory process
• Two focus areas for mobile health technology
  • Capturing Data – vitals, blood sugar, etc
  • Coaching – guiding patients to make better choices
• Sunscreen adherence using mobile technology
  • Electronic monitor used to accurately measure usage of sunscreen
  • Reminder texts sent to mobile phone
  • After six weeks adherence rates for the reminder group were almost double that of the control group who did not receive reminder texts: 56 versus 30 percent.
• Utilizing text messaging to influence patient behavior -Center for Connected Health – project in Lynn, MA.
  • Two areas of focus: Opiate addiction and Teenage pregnancy
  • Localization is important – mention people by places and name
  • Who the message was from (especially doctor) meant more to patients that if it were personally addressed to them
  • Barrier to participation – cost – patients were afraid they would have to pay for the additional text messages
  • Unleash the nurses – nurse evangelist sells benefits to non-physician staff
  • Offset workflow changes in offices – take administration off of practice
  • Sustainable reimbursement structure – engage carriers – CMS – insurers – alternative quality contracts
• Northeastern University, working in collaboration with industry players, announced an incubator program for mobile health technologies. Contact Dan Feinberg, Director, Graduate Health Informatics Program at Northeastern University, President at New England Chapter of HIMSS, for more information

Tags: ehealth initiative, Extensibility, Integration, Interoperability, Meaningful Use, mHealth