From the June 1999 Issue

A New Look At EDI

Broken Promises...Or Wasted Efficiencies?

Data Mining, Distributed Networks, And The Laboratory

Software Components: Which Ones Solve The Implementation Problem?

Voice, Data, Video Network Offered With 1-step Shopping

Kids Under The Weather: A Rainbow Of Care For Sick Children

Be Creative In Your Approach To Healthcare IT Staffing

Beam Me Up, Scotty

Resource Management And Scheduling: Managing Basic Costs

Streamline The Registration Process With EMPI

The Information System Professionals Behind The 100 Top Hospitals

Track Trends In Staffing Enterprise-wide

 

Business of Healthcare

Resource Management and
 Scheduling: Managing Basic Costs

Ask for systems that provide both clinical and financial scheduling.

Q&A with Michael Meisel

Healthcare organizations recognize that effective management of staff resources is critical to their success. Staffing typically commands 60 to 80 percent of a provider organization's total budget. Allocating staff resources to deliver consistent, cost-effective, quality care is a tough challenge.

Michael Meisel is President and CEO of RES-Q Healthcare Systems, a division of Object Products, Inc. In addition, he serves as a Senior Vice President of Object. Since 1987, Meisel has directed the development, sales and support of software applications for resource management and staff scheduling. In this interview, he comments on the evolution and direction of these systems.

Q: In the past, what features and functions did users, especially in hospital settings, look for in scheduling systems? What were the main business problems they were trying to solve?

A: During the 1980s, hospitals, in particular nursing departments, were just beginning to assess how computers might help them effectively schedule staff. In fact, until the middle of that decade, less than 200 hospital-based employee scheduling systems were installed in the U.S. Then in the late 1980s, when the severe nursing shortage reached crisis proportions, hospitals frantically scrambled for solutions to reduce resources required to provide adequate staffing for their units.

Back then, nurse managers were looking for basics—the ability to create a schedule to meet core staffing requirements and to evenly distribute staffing coverage across the week and for all shifts. Of course, they also wanted to reduce the amount of time spent managing the scheduling process itself.

Q: In the past 10-15 years, how have users' demands changed?

A: They still want to achieve balanced schedules that meet basic staffing needs, but now coverage is not the only issue. To meet demands to more effectively manage resources, and to cope with budget constraints, cost has become a much more important component of the scheduling process, along with skill competencies and workload balancing.

Q: So, has budgeting become integrated with staffing in employee resource management systems?

A: Yes. Users demand that systems provide tools to predict staffing needs and adjust for skill-level mix and associated costs as patient volume and workloads change. They have to be able to cost out scheduling and staffing decisions in real time as well as forecast staffing needs and costs for future budgeting.

Q: How has the increasing pace of mergers and consolidation and the development of new types of healthcare delivery systems affected resource management and staffing systems?

A: It would be difficult to overstate the impact. To keep pace, systems have evolved from single-department products to true enterprise-wide applications in order to unify staffing and scheduling, and thereby manage labor resources and costs, across entire healthcare organizations. So, solutions must support enterprise-wide functionality and have the underlying technology to scale up as healthcare organizations grow ever larger.

Q: Have changing regulatory requirements impacted scheduling systems?

A: Accreditation requirements certainly have. According to the Joint Commission on Accreditation of Healthcare Organizations (JCAHO), you have to have current competency assessments for all staff. Thus, in resource management and scheduling systems today, we have to integrate information on employee competencies and credentials as well as automate tracking of information on employees' continuing education. Systems have to be able to show users whether various staffing scenarios are not only cost-effective but also whether they meet JCAHO standards. This has evolved into an entirely new feature set integrated within resource management and scheduling solutions.

Q: Have decision support and reporting requirements become more important?

A: Absolutely. Again, 10-15 years ago, the basic requirement of resource management systems was to produce balanced staffing schedules. Today, data analysis and reporting, both in real time as well as for retrospective and prospective analysis, are critical requirements. Healthcare organizations now use resource management and scheduling systems to decrease overtime, minimize the use of expensive outside staffing resources and maximize the use of intra-staff and cross-facility floating. Decision support features in scheduling systems help users effectively manage labor resources and reduce costs enterprise-wide.

Q: Are there examples of such cost savings?

A: Many of our clients have achieved real dollar savings through productivity gains and time savings. Improving staff allocation reduces overtime and outside agency costs, often resulting in thousands of dollars in savings each month. In addition, automation provided by resource scheduling applications typically saves in excess of 200 hours per pay period by reducing the amount of time spent in manual schedule preparation and modification, timecard verification, and staff certification compliance.

Q: Over time, have the users changed too? Do different types of healthcare professionals now access scheduling applications?

A: As computers have become more readily accessible with the advent of networking technology and decreasing hardware costs, more and more organizations are realizing the benefits of computerized employee and patient scheduling applications. These systems are no longer limited to nursing or surgery departments. Centralized scheduling is becoming the "one-stop shop" for all appointment and resource scheduling throughout entire healthcare organizations. Surgeons are on-line viewing their upcoming surgery schedule and booking their own cases into pre-defined blocks of time. Even support departments, like dietary and environmental services, are scheduling their employees in the same system once dedicated only to nursing.

Q: What have been some of the most difficult hurdles in implementing scheduling systems?

A: As with any system of this magnitude, there are now so many features available to the user that many systems are often underutilized. I call this the "word processor syndrome." While most of us use word processing applications to type letters and so forth, how many of us truly utilize all of the available features such as desktop publishing, mail merge, etc.? The bottom line is that a well-defined project plan and progressive education and training are key factors in successfully implementing a scheduling system. Ongoing training and system reviews are also critical to ensure that users are getting maximum benefit from these comprehensive resource management tools.

Q: Is the Year 2000 issue the biggest technical problem today for resource management and scheduling solutions?

A: It's the number one issue in the market, no question.

Q: I know it's not as simple as just adding the required extra characters to date fields, but why is it so complicated to make software Year 2000 compliant?

A: The simple answer is the constraints and shortcomings of prevailing technology. But, let me explain in a bit more detail. With conventional software technologies, developers construct applications around screens that users see and use. Code is scattered across an application in various small snatches that are "glued" to the screens. So, even a seemingly small change to one part of an application typically requires re-writing of the code behind lots of separate screens. Then, you have to test and re-test the entire application because a modification to any one part of the software can easily break some other part of the code. In addition, conventional software works by applying code to data stored separately in various files and tables in databases. This means that to implement a change, you not only have to make the programming changes to modify code, you also have to make file and table structure changes. It all takes an enormous amount of time and effort, and it's very costly. Our client/server product line was designed from the start with eight-character date definition, so we thereby imbedded the century into all date displays and calculations. Modifying our older products to handle dates beyond 1999 was a tougher job.

Q: What are your clients saying about the future direction of resource management and scheduling systems?

A: They are asking for systems that provide tools to make informed scheduling decisions by predictively showing them both the clinical and financial impact of these decisions in an environment shaped by constantly shifting resource demands as well as ever increasing organizational size and complexity. In addition, as healthcare delivery becomes more integrated across the entire continuum of patient care, there is a tremendous need to secure productivity gains and cost reductions from the application of resource management and scheduling systems in ambulatory settings. In particular, I believe that these solutions will have substantial benefits for physician group practices and integrated delivery systems as they seek to effectively manage staff resources. These solutions can help them deliver cost-effective, quality care and thereby manage value.

Q: Is there a demand for integration with other healthcare information system applications?

A: Since the scheduling process touches on so many aspects of healthcare delivery—from patient appointments for offices visits, lab tests, and operative procedures to scheduling of care givers, equipment, and other resources necessary for the orderly and efficient care of the patient—scheduling must be an integral component of any clinical management application and tightly integrated with the entire patient care delivery process.

Q: What specific features of scheduling applications are especially important in clinical management systems?

A: Clinical systems need to integrate management of the entire patient care process with the business process of healthcare, and scheduling applications can ensure that all resources required to deliver appropriate care are available at the right time in the right place. This requires that the scheduling system identify and resolve resource conflicts, handle resource or task precedence (for example, the results of a lab test or a patient-centered outcomes survey may be required prior to a patient's office visit), and provide a predictive view of resource utilization for planning future needs. In addition, resource costing is a key element. By providing both resource availability and cost information, it is now possible to manage the patient care process in order to maximize resource utilization while maintaining the lowest possible cost.

Q: Object Products builds solutions with your Organic Architecture, which uses object oriented technology (OOT). How does that address the requirements for integration of scheduling in overall clinical management systems?

A: In contrast to traditional software development tools, OOT departs from the screen-centered construction of features and functions in written code that manipulates data stored separately in tables. Instead, objects are self-contained units that encapsulate code and data. The key is that objects, once created, can be easily re-used. The Organic Architecture takes full advantage of OOT and, uniquely, limits code to the architecture itself. And, in our system, all applications are built upon the same integrated database. So, the scheduling features and functions in different parts of the system will use the same underlying objects and the same data. For example, a disease management or outcomes coordinator scheduling a health status questionnaire for a patient and a clinical trials manager scheduling a follow-up contact with the same patient for recruitment into a study are using the same underlying objects. And, if the outcomes coordinator schedules and implements a survey with the patient, the resulting information is immediately and automatically available to the clinical trials staff.