October 28, 2015

Front-line staff input helps build a better EHR system

By: OR Manager
Awards  
Share

Electronic health records (EHRs) are here to stay, but implementation and optimal use are still lacking. Respondents to the 25th annual OR Manager Salary/Career Survey identified many issues, including the amount of time it takes to document in an EHR, lack of integration with other systems, physicians not fully using the system, and weak reporting functionality (sidebar, p 15).

Many problems can be ameliorated or eliminated with better planning before launching a system, particularly by involving staff.

Jami Squitieri, BSN, RN

“Engage front-line staff early in the process so you get input during the build of the system,” says Jami Squitieri, BSN, RN, director of surgical services at Union Hospital of Cecil County in Elkton,

Maryland, which has an annual case volume of about 5,300 for its four ORs, two endoscopy suites, and cystoscopy and C-section rooms. “Then you’re not constantly putting out fires once you go live.”

Squitieri, who as a clinical analyst was responsible for the surgery module when a hospital-wide EHR was implemented, involved OR staff about 6 months before implementation. She and other experts share what it takes for a successful launch and what OR managers can do to manage bumps in the road during and after implementation.

 

Getting buy-in

Studies of attitudes toward EHRs have reported nurse dissatisfaction as long as 18 months after implementation. It’s worth noting, however, that in a 2015 study, nurses surveyed 5 years after implementation had an overall positive view of EHRs, although the perception that “computers can cause nurses to give less time to quality nurse care” persisted among many nurses.

Marion Sparks-McCall, RN, CNOR

Marion
Sparks-McCall, RN, CNOR

Buy-in begins with involvement. Marion Sparks-McCall, RN, CNOR, says, “You need to have a multidisciplinary team that I call the PITT crew—perioperative information technology team.” Sparks-McCall, who has experience as an OR manager, is founder of NurseWorks, LLC, in Hilton Head, South Carolina, which provides information technology (IT) services. “You could have the best implementation driver in the world, but you aren’t going to win unless the whole team is working in a synchronized way.”

Sparks-McCall says the team should include IT, perioperative staff, the OR manager, a surgeon, an anesthesiologist, a vendor representative (once a vendor has been chosen), and a clinical informaticist. She says clinical informaticists must now be in the lead position because they can facilitate discussion between clinicians and IT staff to design the best workflow.

Janice Kelly, MS, RN-BC, business leader for Syntegrity, a product from AORN that incorporates Standardized Documentation and the Perioperative Nursing Data Set into an existing EHR, agrees with Sparks-McCall about the value of a clinical informaticist. Kelly recommends having an individual who specializes in perioperative services, if possible.

“These nurses have an understanding of perioperative workflow as well as expertise in informatics,” says Kelly, who finds perioperative clinical informaticists in all sizes of hospitals, from critical access to large systems with multiple facilities. “They can translate between clinicians and IT technicians.” Kelly adds that Syntegrity, launched in 2010 and currently available in more than 400 hospitals, is updated annually to reflect practice changes.

Joni Padden, MSN, APRN, CNS-BC, CI-BC, says physician buy-in depends on finding a champion to advocate for the EHR. Padden is nursing informatics specialist for Texas Health Resources, which includes 25 acute care, transitional, rehabilitation, and short-stay hospitals in the Dallas-Fort Worth area.

Joni Padden, MSN, APRN, CNS-BC, CI-BC

Joni Padden, MSN, APRN, CNS-BC, CI-BC

According to Padden, a cardiovascular surgeon at one of the Texas Health hospitals said he received fewer calls from staff and risk management as a result of using standard order sets and the notes section in the EHR.

Physicians can help their peers see how the system can be used to ensure they receive proper reimbursement. “Once they figure out the benefits, they will push you to make it better,” Padden says.

If physicians aren’t using the system properly, “One of the first things is to observe and figure out why,” says Sparks-McCall. “They may not have understood specifically what they need to do, they may not have specific enough order sets, it might be hard for them to log in, or workstations aren’t convenient to their care areas.”

One common problem is that the physician workflow for the system may be cumbersome. “We recommend you do a thorough workflow assessment for physicians before implementation,” Sparks-McCall says. “You want to determine what their objectives are for the system and how you can meet their workflow needs.”

Buy-in also depends on being open to suggestions from staff, Squitieri adds. “Some ideas may not be feasible, but you need to provide feedback as to why something won’t work,” she says, noting that education promotes buy-in, too.

Staff at Union Hospital attended classroom training and 4 hours of hands-on documentation. Surgeons and anesthesia providers received training specific to their needs. “We used their time as wisely as possible,” Squitieri says.

 

Integrating with workflow

EHRs don’t exist in a vacuum, and integrating them into the workflow can be challenging, particularly in the OR. “The perioperative department has an extremely complex workflow,” Sparks-McCall says. “Patients go through multiple departments and are cared for by a large number of disciplines in a very time-compressed episode.”

Kelly says the EHR should reflect workflow. Involving the right people helps achieve that goal. “When we designed the record used in perioperative services, we went to the people who actually do the work,” says Padden. “It wasn’t something the IT people foisted on them.”

She adds it was important staff understand what the system would—and would not—do, so they did not have unrealistic expectations. Super users, staff who either volunteered or were selected by their managers, played an active role in assessing workflow and how the EHR would fit into daily practice. Padden asked that both day and night shifts be represented among super users.

Mapping the workflow must be detailed. “Early on, we created a spreadsheet of the current workflow,” says Squitieri, who sat down with each individual, starting with the scheduler, and identified step by step what each person did. This information was then used to fit the computer system to the workflow.

“It was very painstaking to collect the information, but it was crucial to our success,” says Squitieri. She discovered how the EHR could improve workflow, such as reducing excessive phone calls by providing information in the computer. Changes were worked out on paper first, and then in the computer.

To obtain a complete picture of workflow, Sparks-McCall recommends adding direct observation. “Nurses might not recall all of what they do, so watching them helps you map their work,” she says.

Rather than simply using practice data from the vendor to check how the EHR would integrate into the workflow, Squitieri used parallel testing. “We had an OR nurse use the EHR while working side by side with another OR nurse during an actual case to make sure it met workflow needs,” she says. “You want them to document as they normally would, so you can find problem areas.”

 

Playing well with other systems

When it comes to other systems, Squitieri recommends early testing. “IT did a lot of interface testing before we went live,” she says. “We were able to work out most of the bugs ahead of time.” For more robust testing, she also created scenarios in which something went awry.

Padden says some of the integration problems can be traced back to the initial days of EHRs. “When they first came out about 10 years ago, there was a ‘best in breed’ mentality,” she says. Each area purchased the system that worked best for that area, even though the systems might not work well together.

“What we have learned and what vendors have learned is that it’s more important to have an enterprise system [one system for the organization],” Padden says. “You need to be integrated.” She cautions that vendors might not volunteer information related to integration, so managers must ask specific questions about it.

 

Reviewing and revising

Sparks-McCall suggests that managers experiencing problems with interoperability should again review the workflow and assess where modifications can be made. “If you have a lab system that’s different from a documentation system, there are tools that can be used to connect the two,” she says.

For example, clinical context sharing helps carry patient information through multiple systems. “If I’m looking at patient John Smith in the OR EHR and then I go to the lab system, it will automatically bring up John Smith,” she says.

“The biggest problem during go live is that people don’t plan for enough human support,” Padden says, noting that although staff complete training and have sufficient practice time, “They get anxious and don’t think things through like they normally do.” For example, one staff member called Padden in a panic because she couldn’t contact pharmacy. “She forgot she could simply call,” Padden says. “People have to be there to provide support.”

In Squitieri’s case, she says, “We double-staffed the OR when we went live.” The super users who worked with the OR circulators included those from the postanesthesia care unit (PACU) who had been trained in the system. After 2 weeks, super users were in the OR to answer questions, but not in individual ORs, and about 6 to 8 weeks later, the two OR super users were phased back into staffing but remained available for troubleshooting.

“You need to make sure the EHR isn’t a giant repository of useless knowledge,” Padden says. “Those [managers] who get the most out of it are reporting experts. They know how to modify their reports or who to contact to get them modified.”

 

Getting good data

Reports can be scheduled in advance, for example, a manager might choose to review OR delay times daily, weekly, and monthly, or access that information in real time. “Managers need access to case cancellations, turnover time, and other information so they can optimize their use of staff,” Kelly says.

A system is only as good as the information users put into it, so managers have to be aware of what information they need as early as the build-out phase. “Know what data are important to you, and design to get it,” Padden says. “You need to know what you want and how you want to measure it.” She cautions against using “other” as a response option. “If you put ‘other,’ you’ll never get good data.”

Managers can use data to “hold surgeons’ feet to the fire,” Padden says. For instance, a manager could explain that a surgeon who is consistently late to start compared to other surgeons is less likely to receive first choice in room selection.

 

Addressing the time factor

Additional time for electronic documentation can be traced to its capabilities, Sparks-McCall says. “Because the electronic documentation lets you capture so much more information, you are doing more documentation and you are doing more review.”

One strategy to reduce time is to ask IT or the application design team to create “summary screens” that show only what each individual needs to see. For example, nurses want different information than what anesthesia providers want.

Other strategies include avoiding redundancies, where staff members are recapturing information already collected by other staff. For each field, Sparks-McCall asks, “Why am I documenting this?” and identifies which of the four possible responses apply:

• It satisfies a business need.

• It satisfies a patient safety need.

• It is a regulatory requirement.

• It is a professional practice requirement (eg, the information meets the AORN recommendation for documenting skin prep).

Staff may be able to review rather than reenter some of the information. Managers should ask, “Who owns the documentation of this information?”

In the past, nurses were often called on to document information that was the purview of other team members, such as anesthesia providers, to capture data for reporting and compliance.

“Now that all members are electronically documenting and if we are truly in an integrated system, why do nurses still need to document anesthesia information?” she asks.

Sparks-McCall says another option to speed up the process is to create templates or defaults. Squitieri has had success with this, for example, having the system automatically default to the supine position for a laparoscopic cholecystectomy.

 

Putting things into perspective

Squitieri’s experience has been that once staff get through a learning curve, EHR documentation time is about the same as on paper. “They [nurses] can document while they are in the room, take their computers to the PACU and document the handoff, hit save, and move on to their next patient,” she says.

And Kelly notes that part of the issue is simply human behavior in response to when documentation is completed. “Documentation has shifted to real time,” she says. “Many OR nurses are like me. I didn’t learn to chart as I went; I always did my care and then documented.”

She recommends managers explain to staff that the output of their data is being used immediately for many reasons, notably to help managers make more effective decisions, support research, use evidence-based practice, and suggest policy changes. “Nurses need to understand the value of their documentation,” Kelly says.

Padden takes a broader view of the time issue, believing it’s unfair to say electronic documentation inherently takes longer than paper once staff are up to speed. “If you were doing documentation correctly on paper, it would take just as long,” she says.

The difference is that EHRs prevent workarounds that are possible with paper, for example, completing paperwork before the patient enters the OR. “In some ways, electronic is faster because you can set up common document sets in the system,” she adds. Padden also notes that an EHR is safer than paper because it can alert the user to safety concerns.

“It’s not enough to keep staff engaged during the implementation process,” Padden says. “It’s a long-standing relationship.” She holds monthly calls with all perioperative super users to discuss what is working, what needs improvement, and any new components for the system (sidebar, p 16).

 

Seeking feedback

“We always have an open line of communication with our super users,” she says, noting that any interested staff member can request to be added to the super user distribution list. “They know we are speaking their language and can identify problems early.”

In addition, an anesthesia advisory council for EHR meets every other month; ad hoc teams from various surgical lines are formed as needed.

“We have a structured way to get information out to physicians,” Padden says. The system incudes fax, emails, phone calls, or even stationing someone in the surgeons’ lounge if information is highly important.

Sparks-McCall recommends designated staff stay involved in user groups and portals, some of which are provided by vendors. “You can put in questions to find out how others solved a problem similar to yours,” she says. “People are willing to share to help each other.”

She adds that another source is vendor support. “So often there is functionality that was never implemented. Ask if there are things you could be doing with the system that you’re not doing.”

If the EHR poses significant problems, OR managers might want to hire a consultant to collaborate with hospital staff and analyze the workflow.

If the manager lacks funds for hiring a consultant, Sparks-McCall recommends assembling a team, including an IT representative and someone from clinical informatics, to do an assessment; ideally, they should have been involved in the implementation.

“Assess where you are, how the system was designed, and where the gaps are, and then put a plan in place,” she says. Listening closely to concerns is crucial. “The solution might be as simple as modifying the interface or adding terms to the dictionary table.”

Kelly adds that many factors can contribute to problems with usability—screen layout, lack of standardization, lack of equipment where needed, redundancies, failure to notify staff of updates, and insufficient staff. She recommends AORN’s Guideline for Healthcare Information Management as a resource for building a system and for assistance in addressing problems.

 

Making a journey

“EHR is a journey, not a destination,” Padden sums up. “Staff work with it every day, and we can help them to make it more effective.” ✥

 

 

References

Harmon C S, Fogle M, Roussel L. Then and now: Nurses’ perceptions of the electronic health record. Online Journal of Nursing Informatics. 2015;19(1). http://www.himss.org/ResourceLibrary/GenResourceDetail.aspx?ItemNumber=39757.

AORN. Guideline for Healthcare Information Management. March 9, 2012. http://www.aornstandards.org/content/1/SEC28.extract.


OR managers’ views of electronic health records

As part of the 25th annual OR Manager Salary/Career Survey, we asked, “What challenges do you need to address in implementing and optimizing use of electronic health records (EHRs) in the OR?”

A total of 130 respondents commented. Some expressed concerns about the costs involved, and many mentioned time. Comments organized by the categories below reflect respondents’ key experiences and difficulties.

 

Technology challenges

• A full understanding of the program. I’ve been in this position for 2 years now, and I still find something that I didn’t know.

• Integration between systems (mentioned by several respondents).

• A good system that is easy to use.

• Optimizing the record for ease of use.

• Full access to computers by staff, and a system that is fully electronic vs half paper and half computer.

• Ease of use for nursing documentation.

• Acquiring an EHR that has a surgical module.

• Our system’s capabilities are very limited; reporting is not good.

• Conforming to new EHR and losing current functionality for reporting, patient tracking, and staffing.

• Decontamination of electronics.

• Need an easier method to find required documents during the preoperative phase.

• Implementing the charting process to communicate with the existing billing process.

• Our system is slow and unpredictable.

• We have had in place for 15 years. Challenge is adding regulatory mandated fields for compliance.

 

Staff and physician challenges

• Haven’t found a good flow yet. Single most frustrating issue for nurses in the OR.

• Being more thorough with charting.

• My staff is not computer literate. Most have been OR nurses for more than 20 years, and they’re accustomed to paper charting.

• Need the physicians to take ownership and complete documentation in a timely fashion. (Several respondents mentioned this issue, with some specifying anesthesiologists and others noting surgeons.)

• Distraction from care provided.

 

Time

• Currently using EHR in OR, but RNs struggle to complete documentation during procedures that are short. Would like to see more user-friendly software built that would give the RNs more time to spend with patients and less time on paperwork.

• Ease of documentation and time management for charting quicker cases in the OR.

• Challenge is the time it takes to complete documentation.

• Increases work time for the bedside and OR circulating nurse based on complexity of system and number of clicks. Very frustrating for the nurses.

• Takes longer to deliver care.

• Programs are cumbersome; RNs take too long to complete documentation.

 

Usefulness

• Development of great actionable reports.

• Data reporting.

• Documentation accuracy.

• Electronic health records are fully implemented in our OR. Our biggest challenge is that when changes need to be made for optimization, the eight facilities in our system must all agree.


Implementing and maximizing EHRs

Here are tips from those quoted in the article. Putting these into practice is the best way to ensure successful integration of an EHR.

• Involve staff early in the process to identify workflow, and then use the workflow to create the record.

• Train clerical staff to enter preference cards and scheduling information. “Clerical staff are much more cost-effective than nurses,” says Jami Squitieri, BSN, RN, director of surgical services at Union Hospital of Cecil County, Elkton, Maryland.

• Thoroughly test the system with “real life” patient information before going live, and have information technology staff test interfaces with other systems.

• Provide education specific to each user’s needs, and keep staff informed.

• Be sure each field in the EHR is needed and that the correct person completes it.

• Use defaults so staff don’t have to key in routine information, but be sure staff understand they still need to review the information in each patient record for accuracy.

• Have enough support staff when the system first goes live.

• Keep staff involved after implementation.

• Reeducate the staff annually. “Focus on more recent releases and upgrades to ensure everyone is still using the system correctly,” says Marion Sparks-McCall, RN, CNOR, founder of NurseWorks, LLC, Hilton Head, South Carolina. “Include it in annual competencies.”

• Put money in the budget to have perioperative staff involved in user groups online and at face-to-face meetings. “This type of networking builds knowledge and understanding of system capabilities, so it brings real value,” Sparks-McCall says.

Join our community

Learn More
Video Spotlight
Live chat by BoldChat