Archive for the 'ConnectR Toolbelt' Category

Does Your Interface Engine Perform Like a Clunker or a Ferrari?

Often times, clients take the approach that their interfaces are functioning as designed and don’t want to risk “breaking” the interfaces by making adjustments. However,  these interfaces may not be performing at maximum efficiency and/or may not be optimized to prevent errors. This issue is magnified for larger clients with a high volume of transactions.

Galen offers interface environment assessments  which leverage Galen’s ConnectR Toolbelt – a ConnectR Add-On – to provide interface engine health, findings and recommendations. Many of the reports offered in our assessment can be automated to email at a regular interval to appropriate stakeholders, yielding a view into the health of the interface engine, which is a critical component to the EHR as it files and extracts data real-time.

Two common opportunities for improvement, which are also incidentally inter-related, include auto-addition of dictionary dependencies (For example – type, status, scheduling location for appointments, order item, result item, and where performed for results) and interface database lookup scripts. In terms of auto-addition of dictionary dependencies, these interfaces are initiated before the main interface. For instance, an interface to check for the existence of orderable/resultable item, and auto-add if it doesn’t already exist can be initiated previous to the interface that actually files the result to the database.

With the aforementioned dictionary dependency interfaces, often times, dictionary lookup scripts are employed to “check” to determine if the particular dictionary item already exists in the database. In a high-volume interface, this can result in a tremendous number of “lookups” to the clinical Works DB only to result in a blocked message for the dictionary auto-add interface call in ConnectR (because the dictionary item already exists). These database lookup scripts are very “costly” in performance terms and can take tens or hundreds of times longer than an in-memory look-up. This adversely affects the systems required to do that look-up – the database and network specifically. We have developed a Cached ConnectR Lookup solution which provides an alternative to the costly traditional database lookup scripts.

In conclusion, we highly encourage clients to take time to evaluate the performance of their interface engine. As those who own a vehicle can attest, preventative maintenance is much more desirable than waiting until something breaks.

Galen offers interface assessments, on-site and on-line interface mentorship services, tier 2 interface maintenance and monitoring services (staff augmentation) and general interface consultation. Please contact sales@galenhealthcare.com  if you or your organization would like to learn more about how Galen Healthcare Solutions can help you.

A Great Day of Interface Training and Networking

Galen’s Interface Team had a full house in Boston yesterday, hosting twelve interface analysts from ten healthcare organizations throughout the country, for Galen’s first Results Interface Conference

The training covered the topic of building and maintaining results interfaces within the Allscripts Enteprise EHR. The group covered ImageLink, order reconciliation, Requested Performing Location identifiers, auto synching, troubleshooting errors and the underlying data model.

While I have great confidence in our Interface Team and the instruction provided given their expertise, the best part of the day was the interaction that occurred between the different healthcare organizations that attended the training. Throughout the day, I saw attendees pulling each other aside during breaks. They were discussing approaches to resolving errors they saw in their own environments, best practices for building new interfaces and trading ideas on working with microbiology results in Enterprise (a perennial issue).

The group continued conversations started on the Allscripts Interface Developers Network, which I’m sure will continue today and in coming months.

We look forward to offering similar conferences and trainings, and would love to get your thoughts on what type of training sessions and conferences we should host in the future.

Interface Transaction Processing Analysis

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%.