Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

A recent article in Health Management Technology – Poised to touch all things -  highlighted the importance of Picture Archiving and Communication System (PACs) and offered the opinions of where PACs is headed from various leaders within the industry.

Additionally, as presented in a recent article in Health Data Management -  Is a Picture Worth a Thousand Interfaces?: “integrating imaging workflows – and images – in EHRs can be costly. But the benefits keep many trying.”

Many organizations utilizing Allscripts Enterprise EHR are unaware that image integration capability exists, and those that do figure it is too costly to implement.

In this demo, we will present Allscripts Imagelink capability. Imagelink is an Allscripts add-on that can be used to integrate outside systems with Allscripts Enterprise EHR.

More specifically, Imagelink provides organizations access to images and other documents associated with a result from a variety of different systems that have a web-based image viewer - from within the EHR.

With this solution, users of the EHR are presented with the clinical data they need to interpret, comment on, review or validate a particular result – without leaving the EHR application.

Just a few of the vendors we have experience in integrating to the Enterprise EHR via Imagelink include (but not limited to):

• NovaRad
• Stryker
• SCImage
• GE

Be sure to look out for one of our upcoming free webcasts covering Imagelink configuration within the AE-EHR and implementation of corresponding result interface dependencies.

Contact us today to see if your organization can realize the compelling benefits of Enterprise EHR Imagelink integration.

Tags: Allscripts Enterprise EHR, Demonstration, Enterprise EHR, Extensibility, Imagelink, Integration, Interfaces, Interoperability, Meaningful Use, Results Interface

Integrating other web applications into the EHR is a dream for many.

Here, we take the risk calculator built based on the Framingham Heart Study, and integrate it into the Allscripts Enterprise EHR.  With the integration from Galen, the EHR sends the required fields into the Framingham Risk Calculator, like patient age, blood pressure and cholesterol, reducing the data entry and number of clicks for the clinician.  

Now’s it’s as simple to calculate the patient’s risk of heart attack, as it is to view their chart, all while in the EHR.

As we mention in the video, the Framingham Risk Calculator is just one example of integrating a website or web application into the EHR.

Galen has worked with groups on many types of EHR to web application integration – what would you add to the EHR, if you could?

Tags: Extensibility, Interfaces, Interoperability, Meaningful Use

One of the “Menu Set” CMS Final Rule Meaningful Use Stage 1 objective and measures specifies that “at least 40% of all clinical lab tests ordered whose results are in a positive/negative or numerical format are incorporated in certified EHR technology as structured data.” Additionally, the Certification Commission for Health Information Technology (CCHIT  - certifying body for EHRs) indicates via IO-AM 07.02 that “The system shall provide the ability to receive and store microbiology laboratory results with organisms recorded as free-text. (Not MU).” This brings to question the handling of interfacing microbiology results into the EHR.

Microbiology results are often longer, textual results including sensitivities. Additionally, microbiology results can have 3 levels of hierarchy:

1. Orderable item(s) (Urine Culture)
2. Culture(s)/Organism(s) (Light Growth Escherichia Coli)
3. Susceptibility(ies) (Amplicillin)

The problem is that most EHRs are not well-suited to rendering interfaced results with three-levels of hierarchy; rather, the EHR is suited for just two levels of hierarchy:

1. Orderable(s)
2. Resultable(s)

When the interfaced result is sent by the vendor as a “discrete” result, the result likely will not render in the EHR properly:

To accommodate for this, most vendors have the capability of sending the interfaced result as “non-discrete,” or in other words, sending a free-text version of the result.  However in an instance where the vendor is able to send “discrete” microbiology results only, the interface analyst is charge with developing a interface customization to translate the “discrete” result to file into the EHR as a “non-discrete”:

The disadvantages of filing the result as “non-discrete” include the likely lack of ability to aggregate or report on these types of results.

For reference the original printed report from the Laboratory Information System (LIS) for the example above (recall that if an interface is not setup, this is the report that is usually provided by the LIS via fax).

Please contact sales@galenhealthcare.com if you or your organization would like assistance in interfacing discrete/non-discrete results to your EHR.

Tags: Allscripts Enterprise EHR, CCHIT, Certification Commission for Health Information Technology, ConnectR, Database, Enterprise Order, HL7, Integration, Interfaces, Interoperability, Laboratory Information System, LIS, Meaningful Use, Microbiology Results

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

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

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

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

Galen Healthcare Solutions will be hosting a series of free webcasts covering Allscripts EHR Infrastructure. The purpose of these webcasts is to provide insight into the integration of server roles in your EHR environment. We will cover the Message Server role in our first instance.

Tech – The Message Server

This webcast provides insight into the flow of data for the processes handled by Allscripts’ Message Server role. Topics covered will include configuration and troubleshooting of the TW Spooler service, as well as the workspaces involved in printing administration.

July 20, 2010 – 2:00pm-3:30pm: To register and reserve a spot please click here.

July 22, 2010 – 10:00am-11:30am: To register and reserve a spot please click here.

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