Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

The system is upgraded to Allscripts Enterprise EHR^TM (AE-EHR) version 11.2.x- now what to do? Evaluation of current workflows and deciding on the Meaningful Use measures the organization will be using are the next steps. This article will cover some basic key concepts of Meaningful Use as it related to the application and processes as well as examples to provide the foundation to move forward and build. Ideally, obtaining a baseline of the workflows currently used today in each site/clinic prior to the upgrade itself is the recommended approach. This article will highlight at the end the recommended timeline and priority items to provide the best success of not only the upgrade but more importantly capturing meaningful use.

Step 1- Evaluate current state workflows of each site and the role of the end user population

Even if the site recently went Live or had training- end users continuously find new ways to use the application. AE-EHR version 11 in general provides multiple ways to enter information and despite the best training and/or trainer, an end user may change their behavior over time.  Not only will a potential different workflow result in inaccurate testing of what is believed in the workflow; it may potentially allow for an area of missed training when moving to version 11.2. Here’s a great example, suppose clinical staff were not trained to enter problems, however over time the providers and office managers of a site have asked clinical staff to enter the problems for physicians. This would have an impact on training for meaningful use. Or, perhaps the staff is trained to enter smoking status on the social history but behavior has recently changed by the end users and they started capturing it in the comments field in vitals because the end user thought it would be quicker.

The best approach is to go to each site and evaluate each role on what they currently do in the application, as well as how they document in the application. This will allow the testing team to accurately test the role based workflows as well as train as appropriate on workflows. Once the current workflow is established then the foundation for configuration and re-training can begin.

Step 2- Decide which of the Meaningful Use Measures will be used by the organization.

The 15 Core measures will be required by all eligible providers, however only 5 of the 10 menu sets are required.   Additionally, of the 44 Clinical Quality Measures, three of the Core or Alternate Core will need to be used and three of the remaining Clinical Measures will need to be decided upon in order to have a total of six Clinical Quality Measures.

This step can be quite a task depending on your organization. Here are some sample questions to ask:

• Who will be the lead decision maker?
• What teams need to be informed of the Meaningful Use objectives- Business Admin, Executive, Physician Core team?
• Are there multiple teams that will make decisions on different aspects (clinical versus business versus administrative)?
• Do those key decision makers know about Meaningful Use and if so at what level – high-level or detailed?
• Will basic ARRA- Meaningful Use training be required?
• How will government incentives be paid out (to the organization, to the physician, to the site)? This will be asked at meetings and better to be prepared when instituting workflow change.
• What providers are eligible in the organization?
• Will the eligible providers report for Medicare or Medicaid?
• Who is responsible to enroll each provider with CMS?
• Does an analysis of potential eligible providers need to be assessed to make the decision of MU reporting?
• Does an analysis need to be done, and what patient population and/or diagnoses are seen by eligible providers to select the appropriate Clinical Quality Measures?
• Will eligible providers have a choice on whether to participate in MU reporting or will it be decided by the organization?
• Will each site, specialty, or provider select the measures (MENU and Clinical Quality Measures selections) or will it be directed from the organization?
• Will there be a team dedicated for Meaningful Use?
• Who will track the user’s behavior to ensure the necessary information is obtained?

These basic questions will allow the core Upgrade/Meaningful Use team to be prepared for configuration, workflow re-design, testing, and end user training. Each item can have a direct affect on one of the aspects of the upgrade/MU project. For example, if all eligible providers will be allowed to decide which measures they will select for reporting then the configuration team will need to configure to all CORE, MENU, and all 44 Clinical Quality Measures. In addition, if each provider selects their own measures ideally the training would be tailored around the measures for that eligible provider. Training all providers on all 44 Clinical Quality Measures or all 10 MENU items that may not pertain to that provider will not increase retention of the information and workflow change and likely decrease the MU reporting success.  Another example, from the above proposed questions is Medicaid provides a greater financial return if the measures are met however what if no one meets the necessary 30% of patients? Does it make sense as an organization to increase an eligible provider’s percentage of Medicaid patients to capture the higher value and if so who makes this decision and how does the front office staff know to direct more new patients of a certain insurance to a certain provider?

Step 3- Workflow Redesign for Meaningful Use

Once the system is configured and reviewed by the implementation consultant during the upgrade process, the workflows will need to be re-designed to meet the Meaningful Use Measures to guarantee success! A workflow is not just the use of the application but also the process in place for monitoring the Meaningful Use within the organization. At this point, the system has been configured by the organization configuration team (system analyst) based on Steps 1 and 2.  However, unless the users actually change behavior Meaningful Use will not count. Here are some examples below that will need to be considered based primarily on the CORE, MENU and Clinical Quality Measures.

• CORE EXAMPLE:  Suppose that currently the organization doesn’t allow clinical staff to enter and/or update problems or medications on patients, however the providers have not been keeping these lists up to date. Will the organization allow the clinical staff to begin to perform these tasks? Does configuration need to change to allow for retrospective/prospective authorization? Does enable verification of problems need to be added? Do clinical staff need to be trained how to do this item?

Remember there are many new alerts for Meaningful Use however everything doesn’t have an alert and likewise an end user can ignore an alert.

• MENU EXAMPLE:  Providing a Summary of Care Record to the patient and Patient Education. First, who will be responsible for providing the Summary of Care Record- clinical staff or providers? Will the Clinical Summary provided by Allscripts be used or will it print out from the v10 or v11 note? If the patient is a portal patient and you don’t want to provide a Clinical Summary or a non-portal patient how will the provider state if no Clinical Summary is to be provided? What/Who/How is the workflow to be defined, tested, and trained? Regarding Patient Education, will there be a standard developed if not already implemented such as every new medication prescribed by the provider the patient will receive the Drug Ed for that medication? How will the patient instructions be populated and printed?
• Clinical Quality Measure EXAMPLE:  Adult Weight Screening and Follow Up- many sites may already obtain the patient weight today and this may appear as an easy Clinical Quality Measure to capture. However, there are a couple of items to consider, by adding a free text box for comments to document if a patient denied obtaining their weight and if used would count for Meaningful Use. Is this configured already and/or do end users know to enter this information to count for Meaningful Use? In addition, to meet this measure the BMI of the patient needs to be evaluated and based on the patient’s age and BMI an additional workflow must be completed. Part of that measure states if the BMI is greater than 25kg/m2 a follow up plan must be in place. What will that plan be if not already used by an organization/site/provider? Will there be a dietary consultation or a BMI Management Follow Up Order? Will the end user be able to select from any of the potential recordable actions: Dietary consult with the appropriate SNOMED or the BMI Management Follow Up order with the appropriate CPT code? Will the clinical staff perform this action at the time the vital is taken or will the provider be responsible for adding this item on the patient.

These are some examples of Meaningful Use and all the decisions, configurations, and workflow changes that could be affected. This article is not all inclusive, rather, it is intended to begin the process for the team to meet the Meaningful Use objectives.  Please feel free to contact Cary Bresloff, Cary.Bresloff@GalenHealthcare.com, for further questions, guidance, or consultation on Meaningful Use and the impact to an organization.

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

In an effort to improve the way patient data is accurately maintained, the Health Care Industry is undergoing a historical transformation.  The initiative is fueled by the Health Information Technology for Economic and Clinical Health (HITECH) Act, enacted as part of the American Reinvestment and Recovery Act (ARRA) of 2009.  There are certainly a lot of preparations in the works to make this movement the next big shift in how medical care is provided.  With that comes advances in health technologies and the computer systems we incorporate to make it all happen.

The standard now has become an advanced network of cloud technologies, interfaced labs, pharmacies and networked providers all at your fingertips.  One would need a full team of dedicated professionals to navigate through the bests tools available to be ahead of the game, or a specialized group now called, the Upgrade Team.  A team of technically advanced, inquisitive and dedicated people to spend tireless hours scouring through new developments and documentation, who choose the proper tools and encourage you to set up your organization to succeed. 

The next best thing for an organization has now become Allscripts Enterprise EHR^TM version 11.2 (AE-EHR).  Because many clients have not yet participated in an upgrade process, but have instead experienced a net new implementation, service pack update or simple hot fix, we want you to be as prepared as possible. 

To begin, you will be assigned an Upgrade Team from the vendor which will include a Project Manager, an Upgrade Technician, an Upgrade Consultant and an Interface Analyst.  Your internal team should have representation for those same roles,  and in total your team should have at least 8 to 10 resources.  In addition to this core team, a group of Physician champions, super users, testers, trainers and help desk personnel is recommended to help run the command center and support each other during the actual Go Live week.

When the process begins, we hope that you take time to review all documentation available to you. Please refer to the Galen wiki and various Webcasts, Sales Force, and Client Connect.  You will be instructed to partake in the Allscripts eLearning courses, as well as an 8 hour instructional guide to the process by your Upgrade Consultant.  The Upgrade Team will introduce you to all the new functionalities in AE-EHR version 11.2, the Meaningful Use attestations, and will assist you in building your system to work seamlessly with your organization.  Part of the process will also incorporate the newly released Stimulus Set to the base AE-EHR version 11.2 application.  You will be responsible for attesting that your system is set up correctly to handle all the new requirements.  For this, you will need to allow various members of the Technical Team access to analyze and report how you have organized, mapped and set up your data.

To make sure the project stays on track, two weekly meetings will be held over the course of your 19 week upgrade.  The Project Manager will coordinate all resources for their action items and responsibilities, while the Upgrade Consultant meets to discuss the application, testing and build stages of the upgrade.  The Upgrade Tech and Interface Resource are invaluable pieces to the puzzle that will help you throughout the process, and will be available to you in addition to these meetings.  To start, a copy of environment is created to mirror your live system and is then upgraded to the new 11.2 version.  To personalize this base and to utilize the application, we need to configure the new parts to their full potential.  Many of the new functionalities in AE-EHR version 11.2 are in the areas of Security, Preferences, and new Tasks that all have been designed to help you meet the Meaningful Use criteria. 

As the go-live date approaches, testing has been as thorough as possible and all training has been passed along to your end users, we encourage you to prepare everyone for the new version.  It is recommended to provide reference materials for all users to avoid high traffic through your call center on go live Monday.  We also recommend an organized ticketing system to track the concerns that may arise, and a resource that may be available to uninstall and reinstall controls for various computers, tablets and devices that may not have been updated.  Your Upgrade Consultant will be with you throughout the entire go live process remotely, and host an open bridge screen share to walk you through the build process, testing concerns and later onto issue resolution.  You may request that the consultant be on site for this and an additional contract will have to be submitted.  Either way, the entire team will have constant contact with you throughout the first week of your live system.  Post upgrade, the one week transition period will help all team members decompress from the previous 19 weeks.  We will hold meetings to review our outstanding issues that came from the go live weekend as well as any outstanding Sales Force tickets that could be considered critical to your success.  Once we have transitioned past this first week, all outstanding minor concerns will be processed by the Allscripts post live queue and closed appropriately. 

For those of you who may be taking the Stimulus Set component after your go live with AE-EHR base version 11.2, you will once again be in contact with your Project Manager and Upgrade Consultant to repeat the process in building the set and moving forward successfully in attempts to use your Electronic Health records in a Meaningful Way.

Tags: Allscripts Enterprise EHR, Enterprise EHR, Enterprise EHR version 11 Upgrade, Upgrades, v11

The configuration and workflows relating to the Core Meaningful Use objective Record Smoking Status can get confusing; and recent information was released indicating a change in some of the setup for this measure.  Record Smoking Status requires that providers report that more than 50% of all unique patients 13 years-old or older seen by the eligible professional (EP) have “smoking status” recorded as structured data.  CMS has altered its reporting requirements for this measure so that now reports should only include the CDC smoking statuses.  Those smoking statuses include:

• Current Every Day Smoker
• Current Some Day Smoker
• Former Smoker
• Never Smoker
• Smoker, Current Status Unknown
• Unknown if Ever Smoked

You may be asking yourself, what do I do because providers at my practices have been entering terms other than the ones above as the patient’s smoking status?  Allscripts has developed a script that links previous smoking terms to the terms required to meet the measure in order for the provider to get credit on all smoking terms documented.  One thing to keep in mind when running the script is that it does not always match the terms on the patient’s chart to the most accurate CDC term.  For instance, a denial of smoking documented on the patients chart could fall under two separate CDC terms, “Former Smoker” and “Never Smoker”, but since the script can only link to one term, it chooses “Unknown if Ever Smoked”.  “Unknown if Ever Smoked” is not the most accurate, but the provider does get credit for the Meaningful Use measure. 

Because the script does not give the most accurate information for reporting, it is recommended that providers discontinue using the “denied” option when documenting smoking statuses and add the CDC smoking diagnoses to their quick list for easy reference for physicians.  Providers should attempt to use the CDC smoking terms to identify a patient’s smoking status as often as possible.

The CDC smoking diagnoses can be added to provider’s quick lists using SSMT.  The Content Categories of Favorites: Patient Hx – Active Problem or Favorites: Patient Hx – Social History can be utilized to identify the quick list items.  The steps are as follows:

1. Manually add all of the CDC smoking diagnoses to a user’s social or active problems list. (depending in which problem section the providers will be documenting the smoking status)
2. Extract for that user the Favorites: Patient Hx – Active Problem or Favorites: Patient Hx – Social History content categories from SSMT.
3. Open an Excel spreadsheet.
4. Highlight the whole spreadsheet, right click, and choose Format Cells.
5. Choose the Category of Text and click OK.
6. In SSMT, use CTRL+A to highlight all the text and CTRL+C to copy the text.
7. Paste the text in the Excel spreadsheet.
8. Copy columns B through J and paste on a new Excel spreadsheet. With the same formatted cell settings.
9. In column A, type the username of the provider you want to add the favorites to.
10. Make sure a Y is in the column labeled TopFavoriteFlag and in the column labeled Create.
11. Repeat steps 8 through 10for all providers that need the smoking statuses added to their Quicklist.
12. Copy all fields and paste them into SSMT.
13. Click the Import button.
14. Confirm the import worked for a few users.
15. Repeat these steps if setting the quick list in both Active and Social History problems.

It is important to note that the CDC smoking terms were delivered in Q3 and Q4 2010 Medcin releases.  It is required that these releases be installed in Enterprise EHR in order to meet the Record Smoking Status Meaningful Use objective.  In Allscripts Enterprise EHR^TM version 11.2 HF 9, the Record Smoking MU Alert will be linked to the CDC smoking terms and the provider will be able to reconcile this alert by selecting the appropriate term from the list of smoking terms.

An additional recommendation for configuration includes setting the TWAdmin preference Smoking Status for Patients 13 and Older is Not Documented to “Show in My Alerts”.

The configuration and workflows for the Core Clinical Quality Measure Preventative Care and Screening Measure Pair: Tobacco Use Assessment and Tobacco Cessation Intervention is often confused with the configuration and workflows for the Meaningful Use measure Record Smoking Status.  Although the terms used for recording the smoking status are applicable for recording tobacco use, additional workflow is required to meet the Quality Measure.  The Quality Measures can be reviewed in more detail in the Quality Measures PDF on the Allscripts Client Connect website.

Tags: Allscripts Enterprise EHR, Meaningful Use

Client – UMass Memorial Health Care

Project:  UMassMemorial V11.2 Upgrade

Project Timeframe:  February 7, 2011 – June 13, 2011

Client Contact: Emily Lazaros, Allscripts Application Manager

“I would like to take this opportunity to tell you of our experience with our Galen upgrade team.   Troy Forcier and Kristie Gilbert are, in a word, fantastic.  They are professional and knowledgeable, and have been with us on this upgrade every step of the way.  Kristie’s project management skills and proficiency with the application are exceptional and Troy is about as calm a person as I have ever come across.  This gives us, the client, a real sense of comfort.  And as the IT Ambulatory EHR lead for this upgrade, in an organization of this size, that is invaluable.

….

Last, but not least, we have had lots of laughs and fun together through this process.  Thanks to them and Galen for helping to make our 11.2 upgrade a success.”   –Emily Lazaros, Allscripts Application Manger at UMass Memorial Health Care

 UMass Memorial Health Care is the largest health care system in Central and Western Massachusetts, and the clinical partner of the University of Massachusetts Medical School. The Medical Center has a total of 12,350 employees with approximately 1,700 physicians and 3000 registered nurses representing clinical expertise in Cardiology, Orthopedics, Oncology, Emergency Medicine, Surgery, Women’s Health and Children’s Medical Services.   UMass, on the cutting edge of technology, utilizes Allscripts Enterprise Electronic Health Record^TM (AE-EHR) as a means to help with continued excellence in clinical care and patient service.  Over the last several months UMass has worked, very successfully, with Allscripts and Galen Healthcare Solutions to upgrade their AE-EHR product to version 11.2.

The underlying motivation for this version upgrade was of course, Meaningful Use.  While there are incentives for moving to the new version, the idea of having to implement new functionality with potential workflow impact is regarded with dread.  There are dozens of models for how to complete an upgrade, most of which are painful.  The vendor and we, as your consultants, must take ownership over finding the best model for your practice to reduce the pain of upgrading.  Since Meaningful Use is the ‘next big change’ in healthcare, this change needs to happen for all medical practices across the US.  So the question remains, how do you increase your chances of success? Your Galen consultants will help lead the way.

The duration of this particular upgrade project was a brief 19 weeks, leaving us little time to configure the new AE-EHR version 11.2 functionality and guide UMass towards decisions that would qualify them for all Meaningful Use criteria.  In addition to a rapid project timeline we encountered other challenges: the release of process documentation simultaneously to the stages defined in our plan and shifting resource allocation as priorities changed.  Throughout the entire process, though, we were able filter the information, analyze the functionality, provide appropriate guidance, and enjoy the camaraderie of a great group of UMass team members!  We can now take great pride in knowing we were helping thousands of people use their version 11.2 AE-EHR product in a Meaningful Way.

A week after UMass has transitioned to end users, the real challenge of analyzing their data and incorporating their new configuration into their daily lives will prove to be a reality once the Galen team returns to assist with the Stimulus Set.  I know we are all up for the challenge!  Our willingness to help our clients, to test our knowledge of the latest cloud technologies and data reporting and to pass it along will be a very rewarding journey.  If the final product can be as great as the first steps in helping UMass upgrade their base AE-EHR version 11.2, then sign us up…Galen is ready to go! 

UMass was a fantastic group to work with and we look forward to helping them implement the Stimulus Set.  Congratulations to the staff at UMass for a successful upgrade!  We also appreciate the positive feedback from UMass and plan to make the same impact with other clients.

Tags: Allscripts Enterprise EHR, Enterprise EHR, Enterprise EHR version 11 Upgrade, Meaningful Use, Successful EHR Implementation

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

WellSpan Health has just made the move from Allscripts Enterprise EHR’s version 10 to V11. It’s Go-Live Monday and it’s quiet in the command center. How did we get here? 400 Doctors, 1900 total end users, 4 external MSO sites and 60 internal sites up on the EHR, and close to 40 of them completely paperless. 1pm on Go-Live Monday and we have had 125 calls. That is less than 1% of end users calling in with anything. The calls that we are receiving are typical of any go live. Some PCs were had issues with the Allscripts (ActiveX) controls and end users still learning their way around in a new system. We have entered one support ticket into the vendor. What are the elements that led to this success?

The Client Team

The client team at WellSpan Health is deep, and knowledgeable. They take pride in partnering with their physicians, and the physician partners drive the design of the EHR. The physician champions have been intimately involved in the project from classroom training to Go-Live. Their schedules have been adjusted throughout the course of the project to be able to provide clinical oversight to the build process and to act as liaisons with the leadership team internally with the organization. The build and configure team is made up of multiple analysts, three lead analysts and two physician champions. Some of these team members typically work with other products or in specific areas (with Dragon Dictate, with the practice management system, Allscripts Scan, etc.) but have been brought in to meet the staffing needs of the project. All of the people that worked on the build and configuration, as well as the technical staff and the desktop team have been working in conjunction with each other through the entire process.

Testing

The testing of the system was diligent and thorough. There was one person on the team who was a designated testing coordinator. Testers worked through every workflow used in the organization multiple times. The physician champions worked through their workflows and ensured that they had a through understanding of the system and were prepared to discuss the system and provide support to their colleagues. Their testing plan included 16 people working full days in a lab, hammering on the system. They paced their testing with internal issue resolution – they would complete one week of testing and follow it with one week of internal issue resolution, and then test again. They continued this pattern for 6 weeks. This testing plan allowed for their team to become intimately familiar with the new features of the application and clearly validate their build decisions.

End User Training

End user training lasted for a month prior to go-live and provided many options for learning for individuals with different learning styles. There was introductory information available online and a very clear and valuable webcast for end users designed by the client team. Classroom sessions in a lab were offered in 2 hour session and 4 hour sessions by the education team. The client also created a Citrix training environment where end users could log in and practice prior to the V11 deployment. The week before Go-Live, the education team offered V11 Workshops.

Deployment

The Command Center is fully staffed with help desk staff, analysts, the project manager, desktop team along with the Upgrade Consultant and Upgrade PM. Over the course of the weekend there was a dial-in number that administrators could call into to check the process of the upgrade. There is a three tiered issue resolution process in place and as of 2pm on Go-live Monday, only one issue has not been able to be resolved on-site and been logged into the vendor. In addition to the issue resolution process in place, the physician champions are available today to go directly to practices where physicians would be better served by talking to another physician about the workflow and the presentation of the system.

The client knew that even with the thorough education provided, there would be a learning curve for their end users on the initial days logging into the new system. Provider schedules have been reduced for the week of go-live in order to support the end users and to give them time to adjust to their new navigation and adjustments to workflow.

WellSpan Health is live on V11, end users are in and practicing medicine…and it’s quiet here in the command center. While I am normally a person who thrives on a sense of urgency and loves solving problems – I am glad that today is quiet; it means my client has done a really excellent job.

For additional information regarding Galen Healthcare Solutions’ upgrade / professional services please contact max.henson-stroud@galenhealthcare.com or visit www.galenhealthcare.com/touchworks

Tags: Allscripts Enterprise EHR, EHR, MSO, v11