EHR interoperability, regulations top patient record concerns
A comprehensive collection of articles, videos and more, hand-picked by our editors
The biggest effect of installing or upgrading an EHR system may not be on the clinical or business sides, but on the revenue side.
Interruption of cash flow is understandable with any change to business processes that support the revenue cycle. However, implementing an EHR can be particularly disruptive, according to Patrick McDermott, the former system vice president for revenue cycle at Presence Health in Chicago. He went live with his first EHR at that organization in 2011. McDermott, who currently serves as senior vice president of revenue cycle for California's Sutter Health, spoke at this year's Healthcare Financial Management Association's Annual National Institute conference.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
"When we went live with our first EHR, we had zero experience [at Presence Health]," McDermott said. In fact, few healthcare providers around the country had experience with EHRs at the time.
Over the course of several years, Presence Health rolled out EHRs throughout its 12-hospital system in Illinois in six separate go-lives. "It was six consecutive marathons," said McDermott. He offered six best practices to minimize the effect of an EHR implementation on revenue. The secret to successfully implementing an EHR is not in the design and build stages, but in the pre-planning and post-go-live follow up.
Pre-planning an EHR roll-out
1. Establish a central command set-up. "If you're highly centralized, you're in a good position," McDermott said. "But if not, think of it as an opportunity to get into a SWAT team mode, to work more closely with these departments that don't fall under [a central] control or influence, and to get better future results."
Presence Health learned this the hard way. At the outset of its EHR project, the health information management (HIM) department was independent from both the clinical and revenue cycle departments. The scale of the project and its wide-ranging effects at times created friction between the HIM, clinical and revenue cycle teams and the clinical departments.
2. Seize the opportunity for standardization. Implementing an EHR system presents such a dramatic departure from past business processes that providers should take it as an opportunity to standardize systems and workflows, as well as eliminate legacy systems when feasible.
Patrick McDermottSenior vice president of revenue cycle, Sutter Health
For example, Presence Health had a multitude of scheduling systems. "Scheduling is where the revenue cycle really begins," McDermott said. Installing the EHR system served as the vehicle to standardize scheduling across the enterprise, which in turn eliminated a lot of re-keying and other redundant work.
He cautioned, however, that even the most comprehensive EHR system still falls well short of being one size fits all, such as when it comes to reporting capabilities. Any health IT director who believes that a new EHR system will eliminate the need for any reporting bolt-ons will be sadly mistaken, McDermott said.
3. Mitigate for revenue dips. "You have to set the expectation that there is going to be a short-term decline in revenue performance," McDermott said. For 30 days after his first go-live, Presence Health's cash flow dropped by 25%, he said.
The objective is to make that drop in revenue as shallow as possible, return to normalcy rapidly and to make each subsequent go-live better from a revenue perspective than the previous, he said.
4. Keep an eye on state and federal policy changes. During McDermott's first implementation, the state of Illinois decided to delay Medicaid payments to providers from 30 days to 180 days. "It was a compound fracture," McDermott said. The 25% drop in cash flow from the EHR implementation, combined with the delay in Medicaid reimbursements, exacerbated revenue collection problems.
In 2015, providers must deal with the switch to ICD-10 and recent changes to Section 501(r) of the IRS code. "These are interlocking strategies with EHR," he said. For example, with ICD-10, "if you don't document, you can't code it," says McDermott. "Clinical documentation and coding have to be on the same team."
Post go-live steps
5. Meet and meet often. "During the first 30 days after go-live, we met every single day, all the department heads," McDermott said. The team reviewed financial results of the previous day compared to other months and verified that figures were correct or on target.
"This was the best tactic for mitigating revenue [fluctuations]," he said.
6. Document missteps and create guidance. "As we were about to head into the first go-live, we understood we made a lot of mistakes," McDermott said. "After the first go-live, take time to document those mistakes. Document them and turn them into tactics."
After conducting an evaluation of Presence Health's first go-live, McDermott's team produced a 12-step, mitigation risk go-live plan based on everything that went wrong. For example, one unintended consequence of the EHR go-live was a sudden increase in the time it took to register people -- from an average of eight minutes per patient to 24 minutes. Among the reasons:
- Documents scanned into the EHR at registration were not properly attached to the patient record, mainly because this was the first time staff had ever used a scanner. This required additional emphasis in the training.
- Registrars consistently typed in the wrong county code, the result of a flaw in the design of that page of the registration window. This was something that had been missed in user testing, which in future rollouts was made more thorough and rigorous.
Finally, to prevent patient registration lines in future implementations from growing out the door, McDermott's team made sure there was budget for additional temporary staff.
By applying the lessons learned in the early implementations, Presence Health was able to minimize cash flow interruption to well below industry standards. The system's vendor warns its customers that the average increase in accounts receivable days out is a week; three Presence Health's hospitals not only beat the average, but one hospital only saw an increase of 2.7 days, putting them among the top 25% percent of performers, according to McDermott.
Revenue cycle pros consider ICD-10 aspects
Clinical analytics pushes forth in revenue cycle management
SaaS helps health system keep $22.7 million in payments
Risk adjustment coding tech captures additional revenue of $62 million