After transitioning from a paper-based data and operations management system to one that uses relational database software, Lahey Hospital and Medical Center (LHMC) in Burlington, Massachusetts, saved more than $1 million in product purchases in 2017. The surgical value analysis committee (VAC) evaluated 150 product requests and managed the conversion of three large suites of products to alternate vendors. Rebates for meeting product use agreements made possible through vendor loyalty contracts amounted to $589,000.
LHMC, a 335-bed acute care hospital, is part of Lahey Health, a system of hospitals northeast of Boston with more than 1,400 local providers in adult and pediatric primary care spread among community group practices and five hospitals. LHMC employs more than 500 physicians, including 125 surgeons, and more than 1,300 nurses.
The surgical VAC is one of several value analysis committees at LHMC that collaborate to optimize cost, quality, and clinical outcomes. Use of customized software to support all of the surgical VAC’s functions—notably, evaluating non-commodity products and physician preference products and equipment for the OR—has been highly successful.
The committee is also responsible for:
• evaluating and managing surgical-related group purchasing organization (GPO) savings opportunities and bundled product transitions
• setting up and administering product trials
• ensuring effective communication between stakeholders and administrative decision-makers
• tracking product savings opportunities and rebates.
Committee members include the vice chair of the department of surgery (committee chair), three senior staff surgeons, the chief nursing officer of surgical services, the nursing administrative lead, service lead nurses, the OR supply chain specialist, the financial director of surgical services, a surgical technician, a GPO representative, and the administrative director of value analysis.
Four years ago, the VAC was reorganized with a newly appointed chief of surgery. The VAC’s goal was to increase data-driven decision-making and create workflows that produced consistent and measurable results.
At the time of the transition, the basic activities of the VAC—including minutes, attendance, meeting proceedings, decisions, and trial outcomes—were entirely paper based. Committee members were often unfamiliar with the products being presented, and most of the reimbursement and quality information came from the provider who was requesting the product.
There was no consistent way to compare the requested product’s financial impact with the financial performance of the existing product. Several deficiencies were noted:
• multiple unresolved agenda items
• inconsistent recording of attendance
• no premeeting preparation
• lack of product familiarity
• incomplete product information
• lack of stakeholder involvement
• inability to assess multiple related products for financial impact
• no real-time financial data for decision-making
• inconsistent product trial preparation and follow-up
• lost trial results
• no ability to send reminders for trial completion
• open trials without any data or follow-up.
To improve this process, we first observed and recorded existing workflows, which were not consistently followed. Previous improvement efforts weren’t sustained under a paper-based system, and we clearly needed software support to provide a structured environment for consistent process performance. We used the plan-do-study-act healthcare improvement model to facilitate the transition.
We initially used Filemaker’s relational database software (Filemaker Pro 15 version 15.0.2.220 8-20-2016), although we could have used any commercially available relational database. A relational database stores data in tables that relate to one another through one or several unique identifiers. For example, basic information such as specialty, department, and contact information for a product requester can be stored in one table and linked to records of all of prior product requests in another table.
These data can be pulled together very easily in a report format. Relational databases are quite common in healthcare data management, and there should be ample expertise within any healthcare facility to create such a database.
The new software improved several functions of the committee, and premeeting functions were enhanced, thereby maximizing time efficiency. Workflows using our initial in-house database are very similar to our current workflows using a national vendor’s software product. Product requests are entered via a link on our facility’s home page. The OR supply chain analyst enters the requested products into a products table along with its associated costs, description, and any supporting documentation such as Food and Drug Administration MAUDE (Manufacturer and User Facility Device Experience) reports. Additional related products and equipment are also entered to provide a total cost profile.
If the product is supplanting a product already in use, the existing product costs are entered to provide net financial data. The day before each committee meeting, key committee members meet to ensure the information is complete and to plan activities such as preliminary discussions about the product requests. The requests are added as agenda items, and reminder emails with the meeting date and time are sent to the requesters.
Typical in-meeting committee activities include reviewing product requests, identifying and updating product savings opportunities in coordination with the GPO, trial setup, and trial results review. Ad hoc committees often study the impact of product conversions with key members who are high-volume users of the products being considered.
The committee meeting is run with the software visible on an overhead projector. Attendance, minutes, and unresolved agenda items from prior meetings are reviewed. Each product request is reviewed with links to peer-reviewed publications, videos, and direct links to images of the product being discussed.
The product requester attends the meeting in order to clarify any issues and to enhance engagement. Trials are planned in real time, complete with product-specific parameters and measurement modes (eg, continuous scales or pass/fail). The criteria for a successful trial are established in collaboration with the requester and committee members. Stakeholders are defined and included in the trial as appropriate. Between-meeting activities include tabulating trial results and reminders for trial participation.
After we transitioned to the new software, the committee was energized, and workflows improved. Having developed the software in-house, we were able to incorporate changes quickly and efficiently. Over a 3-year period, we modified the software so that new improvements were rarely needed.
During the initial phase of implementing our in-house software conversion, the committee chair and OR finance director spent 2 to 3 hours per week to fully incorporate the software into the workings of the committee through an iterative process of improvement. Before we converted from our in-house software to the vendor’s software, we shared our existing software-based workflows with the vendor. Once the conversion occurred, we spent no more than 2 hours per week over a 4-month period to align the software to the required workflows. The vendor handled the programming changes, using customizable software.
Our surgical VAC serves as a model for other value analysis teams in Lahey Health, and we believe this would not have been possible without the incorporation of database software management into our committee’s operations. Our vision to expand this local knowledge and success of the system led to a request for proposals from national software vendors.
By transitioning to a national vendor’s software platform, we took our experience in our local committee and generalized it to the system. We identified several vendors and engaged a vendor with software that was quite similar to what we had developed. Having a mature local software product with established workflows eased the transition to the vendor’s software and facilitated communication so that the vendor was able to quickly incorporate our needs into the product. The vendor was able to go live within 4 months.
It’s important to plan and implement workflow changes as much as possible within the existing structure and using existing resources before the new software is introduced. That way, the software can be used to support existing workflows and enforce accountability with those workflows while also offering the flexibility to incorporate process improvements.
The software will need continuous improvement, especially within the first few months or years, depending on the complexity of the underlying work processes.
Database tools bring a myriad of advantages over paper-based systems, including data transparency, searchable data, enhanced communications, aligned and organized workflows, and detailed documentation. Including key stakeholders in the software development process ensures that the values of the committee are upheld. We had the participation of a surgeon as well as finance and supply chain staff throughout our transition.
Sharing ideas, technological advancements, standardization of protocols and supplies, supply utilization, cost-saving initiatives, and contracting leverage are just some of the successes achieved by value analysis teams.
Often, one hospital becomes aware of a new product or technology and requests approval for use at its facility through its surgical VAC. The requests are reviewed at the system level, and an analysis is done to gauge the benefits to the patient and the surgeon, potential cost reduction/savings, additional revenue potential, strategic advantages, and potential volume growth and standardization. If the request is approved, the decision is then shared with the rest of the Lahey system so that the other surgical areas within our system become aware of the opportunity. These processes are seamless and efficient, thanks to a common systemwide software platform.
Working with a software vendor to share ideas and help develop and customize the software is important to success. Creating and developing software in-house, using commonly available database software, is very successful in laying the foundation for a rapid and successful deployment of a professionally created and supported software product from a national vendor.
Our workflows were well established and supported by our software. Expanding this technology to our system required a more sophisticated and professionally supported software product that incorporated our established workflows and experienced-based software needs. ✥
The authors (L-R) are with Lahey Hospital and Medical Center in Burlington, Massachusetts: Robert Dolan, MD, is vice chair, department of surgery; Kristen Murphy, MBA, is director, surgical services; and Edward Aiello is director of value analysis, supply chain.