Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

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

Galen Healthcare Solutions will be hosting a series of free webcasts covering the Allscripts EHR database and Allscripts Analytics application.

The purpose of the EHR webcasts is to give a detailed view into the underlying database schemas as well as useful queries for the Patient and Order/Results tables. For Analytics we will be covering a basic overview of the Analytics applications as well as detailed examples using Worksheets and Crosstabs. 

These will be structured in a similar format to university courses – the three classes will be at 100 (intro) levels.  The list of the webcasts and their times may be found below.

Allscripts EHR – Patient: Overview of the Patient tables as they relate to the Allscripts EHR Database. This course will cover basic concepts related to Patient tables, as well as useful queries, views and general best practice techniques. 

• Wednesday, June 2nd, 2010 at 2:00pm EST

Allscripts EHR – Order/Results: Overview of the Order/Results tables as they relate to the Allscripts EHR Database. This course will cover basic concepts related to Order/Results tables, as well as useful queries, views and general best practice techniques. 

• Wednesday July 7th, 2010 at 2:00pm EST

Allscripts Analytics: Overview of the Allscipts Analytics application. This course will cover basic concepts related to general functionality of the Allcripts Analytics applications, including example Worksheet and Crosstab problems as well as general best practice techniques. 

• Wednesday August 11th, 2010 at 2:00pm EST

To attend, please contact Dave Boerner, Dave.Boerner@galenhealthcare.com . You must be an existing Allscripts Enterprise EHR client to attend.

We also offer training courses and reporting services for the Allscripts Enterprise EHR database, ETL database, Analytics and the ConnectR  database.  Please contact sales@galenhealthcare.com for more information regarding these courses and our reporting services.

Tags: EHR Certification, Galen Webcast Series, Technical

Last Friday, I attended Governor Deval Patrick’s HIT conference in Boston and present my own musings and takeaways from day 2 of the conference. Be sure to check out Dr. John Halamka’s reactions from last Thursday morning’s CEO summit at the Govenor’s HIT Conference.

Keynote from the Surgeon General – Vice Admiral Regina M. Benjamin

• She covered how Hurricane Katrina affected her community in Alabama and the fact that due to the natural disaster, they were reliant on pharmacy chains to provide a record of what medicine the patients were taking.
• She also touched on a story of how members of her clinic were drying out the patients records after Hurricane Katrina and after they had them completely dried; a fire burned the entire clinic down. This brings to light the need for disaster recovery and collocation in some circumstances. Galen Healthcare Solutions proudly offer a downtime solution in its VitalCenter product.
• After the fire, Bentley college students came down to assist and one of those classes contacted the president of e-ClinicalWorks and convinced him to donate the EHR – integrated with both labs & referrals
• She stressed that prevention is the foundation to the National health System and as such we should be incentivizing prevention.
• She also mentioned how the EHR played a major role in prevention of errors

Getting Clarity – Developing Effective Health IT Policies and Standards

• Need to integrate claims and clinical data to provide total model for exchange
• 15 cents of every dollar in healthcare goes to administrative overhead
• Two key issues for data exchange – identity and consent
• Public Health entities currently receive data, however not every public health entity has the infrastructure to receive data
• How do we pull quality measures out of unstructured text?
  • Analogy of querying for alcoholics, but free text match is returned about using alcohol to swab skin before applying needle.
• The tough part of concerning clinical quality measures is the balance of structured and unstructured data
• Healthcare delivery is complex in that there is heavy fragmentation – 80% are solo or two physician practices
• Dr. John Halamka mentioned that we are the stewards of our own data and architecturally that is the design of the system

Jobs, Jobs, Jobs – Health IT, Business Opportunities, and Job Creation

• Healthcare workers do not have not enough IT in their educational curriculum
• Howard Messing, the President of Meditech mentioned that in Massachusetts in particular the cost of living is a barrier – Meditech actually has commuters from Atlanta.
• Girish Kumar Navani, CEO of e-ClinicalWorks indicated that they currently employ greater than 1000.
  • He anticipates hiring 500 new workers over the next 2 years for programming and business analyst positions
  • He also mentioned the analogy of the electrical socket – broadband network need to be as irreplaceable in physician office as the electrical socket.
  • He believes there is a need for a  new type of worker, the knowledge worker, who understands workflow and is able to analyze and make better decisions about population health
• Richard Reese, Executive Charmain of the Board, Iron Mountain, anticipates helping hospitals clean up paper mess.
  • He mentioned non-compliance in healthcare IT to storage and backup standards
  • Lesson in compliance can be drawn from Wall Street years ago and that healthcare organizations must design for workflow, but compliance as well
• Brad Waugh, President & CEO at Navinet, indicated that the network his company providers connects payers and providers, saving $800 million per year.
  • They currently require Microsoft .NET certified engineers and have over 30 openings
  • He indicated that the educational system must produce the folks needed in healthcare IT and currently it is just not doing so domestically
• This discussion brought to light a deeper seeded issue in American society in that as a society we are not pushing computer technology anymore as it is no longer the glamorized industry.
• There is a major need for qualified issues and it is a supply versus demand issue with the roots in education and society.
• One member of the audience mentioned that the goal of healthcare reform is to eliminate costs and the irony is that in a sense we are creating jobs to eliminate jobs
• Another member of the audience commented on the arrival of programs for night healthcare professional courses, much like it was the trendy thing to get a night MBA in the 90s
• Finally the point was made that by the middle of the current decade, we will be facing baby boomers hitting Medicaid and the amount of care they need is incredible. With less dollars, we will need to re-engineer the system and what could come as a result is care rationing

Panel: Successful HIEs – How They Did It and How It Helps

Fallon Clinic HIE

• Emergency care was the highest reason for HIE usage
• Some quotes from physicians on the value the HIE provided
  • “Importing the CCD expedited documentation”
  • “Reduced need to ask patients questions”
  • “Expedited verification of medication and allergy list”
  • “Saved time”
  • They estimate phone calls were avoided for 75% of hospitalist and were extremely beneficial for new patient visits
  • They estimate they spent 3 years and $3 million learning and developing “trust” and $1M in building and implementing in the final 2 years
  • Lesson learned:
    • They pre-registered all of their patients in the community (bulk-load) and this helped with performance as they didn’t have to query the state
    • They felt the key to sustainability was to reduce operating expenses
    • Each organization in the HIE was responsible for server maintenance – ends up being $2000/year/organization which represents rounding error in most healthcare IT budgets
    • Key points – earn trust – utilize real-world workflows – value of low cost

Indiana Health Information Exchange

• Federated data model – 62 hospitals – 3 billion structured results – doubling time of 4 months
• They meet the providers where they are whether it be delivery of data to the EHR or physicians receiving data as PDF or view into a portal
• They view sustainability in the sense of funding via offering services
  • work with public health services for syndrome surveillance and track immunizations
  • Their business model for sustainability is such that scale is needed and again they emphasized avoiding grants for operational costs.

NEHEN

• Their sustainability model is such that their organization provides governance – decide what has value – much as a board of directors would
• Federated model works better than centralized – more accepted in the marketplace
• Lessons learn include integrating processes across the enterprise
• The case of the transfer of information to public health is needed to sustain HIEs as well as the capability to sell other products within the network.

Tags: Adoption, Business Continuity, HIE, HL7, Immunizations, Integration, Interfaces, Interoperability, Meaningful Use

Galen Healthcare Solutions will be hosting a series of free webcasts covering ConnectR interfaces.  The purpose of these webcasts is to provide insight into advanced troubleshooting methods as well as advanced design and configuration options within your ConnectR environment.  We will cover various aspects of interface design, development and maintenance as well as best practice techniques.

These will be structured in a similar format to university courses – the initial three classes will be at 100, 300 and 500 levels.  The list of the webcasts and their times may be found below.

100 Series – Configuration and Deployment of Imagelink: Overview of Imagelink configuration within the AE-EHR and implementation of corresponding result interface dependencies.

• Wednesday, May 19th, 2010 at 2:00pm EST

300 Series – Advanced Troubleshooting: Error analysis and resolution as well as custom techniques for error remediation

• Wednesday, June 23rd, 2010 at 2:00pm EST

500 Series – Advanced Design: Interface filtering techniques and interface-driven tasking

• Wednesday, July 21st, 2010 at 2:00pm EST

To attend, please contact Justin Campbell, justin.campbell@galenhealthcare.com.You must be an existing Allscripts Enterprise EHR client to attend.

We also offer training courses and reporting services for the Allscripts Enterprise EHR database, ETL database, Analytics and the ConnectR  database.  Please contact sales@galenhealthcare.com for more information regarding these courses and our reporting services.

Tags: Allscripts, Allscripts Enterprise EHR, ConnectR, Database, Galen Webcast Series, HL7, Integration, Interfaces, Interoperability, Meaningful Use, SQL Server

Drawing on our past experience and expertise with data conversions, we recently assisted one of our clients with a conversion of administrative ICD9 diagnostic data extracted from their Practice Management system to clinical Medcin-based  problem data within the EHR. The project ultimately saved a tremendous amount of data entry time. Upon completion of the data-conversion, clinicians were then able to review the problem list in “Past Medical History” section of the patient chart within the EHR and categorize by either choosing to make the problem “active” or mark redundant or resolved problems as “Entered in Error”.

As with any data conversion, one must be cautious in terms of negative implications. For instance, administrative data has its limitations, and an example or where the process can go wrong is the highly-publicized case of e-Patient Dave.  Ultimately, problem conversions can be useful, but the data needs to be reviewed, and almost treated as suspect.  The value in the conversion is saving the entry of the problems that are accurate – say 80-90%.  Any that are incorrect, will be reviewed with the patient and can easily be marked EIE.

Statistics:

• 1,007,238 problems were loaded to the EHR for 205,831 patients via the interface engine, taking about 11 hours to process totally.
• PM Extract file statistics:
  • Total matchups of ICD9s to patients: 5,405,874
  • Total Unique ICD9s: 8346
  • ICD9s that only match up with 1 patient:1295
  • ICD9s that match up with 100 or more patients: 2027

Approach and Components:

• Master approved “ICD9” list provided by client
• Extract of ICD9 data from PM system provided by PM vendor
• Automated macro that attempts to match ICD9 to Medcin. Potential matches include the following:
  • 1 to 1
  • One to many (20 or less)
  • One to many (20 plus)
  • One to none
  • Each of the different flavors of matches were marked with an annotation (highlighted via an asterisk) to identify to clinicians the logic that was used in importing the problems:

• Once the translation was finalized, it was loaded into the interface engine and mapping logic loaded problems into the patient chart in the EHR via the API (existing stored procedure).

Known Issues Mitigated:

• Due to incorrect logic, some ICD9s were linked to patient profiles improperly. To mitigate this, a script was run to mark these problems as “entered in error”
• Problems were loaded to the “Past Medical History” section of the patient chart with a status of active. However, given this status, it didn’t facilitate providers to easily change the problem to be an active problem linked to a note.

Lessons Learned:

• Execute a proof-of-concept and as with any technical project, get clinician feedback. The client had a pilot group of 5 clinicians to vet out issues and bless the data before the live conversion was run.
• Do NOT use spreadsheets to track the cross-walk between administrative ICD9 diagnoses and clinical Medcin problems. Rather utilize a staging DB to serve as a single repository in developing ICD9 to Medcin translations. Also, the data from flat-file export from PM can be loaded into a staging environment via SSIS such that it can be analyzed and summarized while facilitating persistence.
• Make sure to tie the problem conversion load to a specific provider, that way if side effects or issues are identified after the fact, there is a clear way to identify which problems were loaded in the conversion via the provider they are tied to. The interface log should also have a record of this, but most organizations set the retention time to 90 days.
• Workflow validation – ensure that the workflow to move problems from PMH to Active will not be a barrier to use.

If your organization is looking for assistance in data conversion, please contact sales@galenhealthcare.com and visit our website for more information regarding our technical service offerings.

Tags: Allscripts, Allscripts Enterprise EHR, Data Conversion, ICD9, Interfaces, Medcin, Problem Conversion, TouchWorks Problem

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, EHR, EHR Implementation, Extendability, Interfaces, Read-Only, Tasking

Galen will be hosting another in Enterprise reporting workshop this coming March.  This has been a popular course, so please sign up early!

What: A three-day course for report writers, DBAs and those in healthcare informatics on the Allscripts Enterprise EHR database.
When: March 1 – 3, 2010
Where: Boston, MA
Price: $2,500

The Galen Database Architecture and Reporting Workshop has furthered our understanding of the Allscripts Enterprise EHR database.  The clear presentation and substantial hands-on time helped us to greatly accelerate our production of customized reports.  And, the data dictionary documentation alone is invaluable.
– Chris Hyde, DBA, Albuquerque Health Partners

The attached announcement includes additional information regarding the course and suggested audience (report writers, DBAs, etc).

Please contact Mike Dow to register, or if you have any questions – mike.dow@galenhealthcare.com

Tags: Allscripts Enterprise EHR, Crystal Reports, Custom Reports, Database, EHR, Reporting, SQL Server

There is quite a bit of buzz in the healthcare IT community surrounding the ONCHIT/CMS release of the Meaningful Use Interim Final Rule and the  and the EHR certification requirements. The author of HISTalk kindly spent his New Year’s Eve poring over the documents to provide an excel worksheet summary of the actual criteria and thresholds and the author of the Medical Software Advice blog did a great job of outlining definition, features and measurement with his blog entry.  I thought I would take it a step further and provide some meaningful information to CFOs and PMs by taking a stab at quantifying the effort involved with each measure. First some background information and disclaimers:

• This estimated effort is based on 50 physician multi-specialty organization.
• It is intended to give a ballpark of effort involved and the numbers serve as estimates only.
• It does not necessarily scale linearly with number of providers or specialties.
• The effort only addresses four categories of effort – implementation, technical, interface and training.
• Categories of effort not addressed include project management, systems configuration and deployment, networking configuration and deployment, hardware (including desktop) deployment, and helpdesk and on-going support.

The meaningful use matrix with effort broken-out can be found on the Galen Healthcare Solutions Wiki.

Now that we have presented the effort involved, let’s delve into how EHR deployments – specifically  AE-EHR deployements – are typically phased:

Phase I: Base, Document, Scan and Dictate

Description: Provide a baseline level of EHR functionality to all users. Real-time access to physician schedules, transcribed and scanned documents, facilitation of dictation.  Data conversions, Scanned charts and documents, Base Deployment. This approach typically appeals to all providers regardless of technical aptitude and would not require significant workflow changes

Advantages: Clinical information access internal and external to the clinic, reduced level of change for physicians through the use of dictate, realized benefits of decreased errors and re-work.

Interfaces:

• Registration & Scheduling
  • Real-time inbound registration and scheduling feed from practice management system.
  • Initial bulk-load of existing active patients and appointments
• Transcription
  • Real-time inbound transcription interface from transcription system.

*Phase II: Rx+, Note, Forms, Results

Description: Add medication management, structured note and results

Advantages: Ability to collect structured information facilitating use of panel queries. Additionally, formulary compliance, and prescription faxing/e-prescribing to pharmacies and ability to capture results as discrete data elements

Interfaces:

• Results
  • Real-time inbound results interface from lab system.

*Phase III: Order, Charge

Description: Facilitates charge capture and order transmission.

Advantages: Completes the access to centralized patient data and further enhances the quality of care and service to patients.

Interfaces:

• Orders
  • Real-time outbound order interface to lab system
• Charge
  • Real-time outbound charge interface to the practice management system.

*Phase II and III can be combined based upon the organization requirements

In conclusion, one of the biggest questions that lingers for me is how the data is to be relayed to the government such that organizations can be evaluated as to whether or not they meet the thresholds to receive the incentives. Custom reporting comes to mind as precedent has been set here, specifically with PQRI and Medicare HCC. Galen Healthcare Solutions certainly can provide custom reporting specific to organizations needs in order to communicate meaningful use. Another solution is Allscripts Clinical Quality Solution powered by TeamPraxis. In the meantime, we wait for the rule to be finalized and anticipate announcement of how the meaningful use data is to be relayed.

If your organization is looking for assistance in exhibiting meaningful use, please contact sales@galenhealthcare.com and visit our website for more information regarding our technical and professional service offerings.

Tags: Allscripts Consultants, Allscripts Enterprise EHR, Custom Reports, EHR, EHR Certification, EHR Implementation, Integration, Interfaces, Meaningful Use, Meaningful Use Matrix, Reporting, Successful EHR Implementation