Prove it by joining a national database
(Editor's note: As more and more managed care organizations ask for benchmarking data, it may benefit your practice to join a disease-specific national database. Physician's Managed Care Report offers some tips on getting started in this area from three groups who have ventured into the new territory of database benchmarking.)
In the managed care era, measuring your practice's clinical outcomes is necessary. Indeed, it's often required under the terms of your contract with a managed care organization. After all, if you don't measure it yourself, the MCO will likely measure it for you.
The answer for many practices can be to join a national database. But experts say success depends on good planning.
"There are strong advantages to joining a national database," says John Cockerham, MD, associate professor of pediatrics at Georgetown University Medical Center in Washington, DC, and an outcomes management consultant. "But you can't just say, `We'll do outcomes tomorrow.' It requires a great deal of thought about what you're collecting."
A national database can jump-start your outcomes management program because it generally provides the data collection tools, approved software vendors, regular reports, and trend charts. But can it collect the information you want to know? How much data are you required to provide? Can you start slowly, perhaps with just one indicator?
"Don't try to implement a complete and total outcomes management program at once," advises Cockerham. "Do it in small pieces. Limit the scope of the project at the outset to something that's easily accomplished."
For example, an orthopedic practice that joins the Musculoskeletal Outcomes Data Evaluation and Management System (MODEMS) project of the American Academy of Orthopaedic Surgeons in Rosemont, IL, may choose to begin by measuring outcomes following treatment for low back pain. The academy has extensive data collection modules for all parts of the body, as well as for pediatric patients and patient satisfaction.
National database projects can benefit those who are experienced in outcomes management as well. For several years, Mid-Carolina Cardiology in Charlotte, NC, gained a wealth of knowledge from the group's own home-grown outcomes management surveys. Complication rates and variations among physicians declined in the group's angioplasty procedures.
But after a while, the cardiologists wanted a bigger yardstick. "They looked pretty good next to each other, but they didn't have any idea what anyone else was doing, " says Joanna Younts, a Dallas-based outcomes consultant who was formerly outcomes director for the cardiology group.
However, Younts and her colleagues needed to convince some physicians who were outside the practice but affiliated with the same hospital to sign onto the project. Physician support is critical to the success of your database project, so you need to actively seek input even from those who are less favorable toward it, advises Younts. "First and foremost, involve the physicians in the decision-making process."
Here are some other considerations when deciding whether to join a national database:
· Determine who is responsible for data completion.
As Mid-Carolina Cardiology considered involvement with the American College of Cardiology database, a task force considered the increased demands for data. Presbyterian Hospital in Charlotte actually maintains the database for the cardiology group, so hospital representatives, as well as Younts and her physicians, were involved. A national database organization expects you to have every data element for every physician at every reporting period, says Younts.
Concerns about data collection prompted the task force to make strict rules about who would collect the data and who would be responsible for making sure it was complete. The conclusion: Individual physicians must ensure the data are accurate and complete. While the project will have a manager, the buck stops with the doctors.
"The hospital agreed that they would suspend privileges for physicians who did not take responsibility for their data," says Younts.
· Evaluate your staffing needs and process changes to collect data.
"You have to rewrite people's job descriptions and make them responsible for collection and entry," says Cockerham. That may require reassigning tasks or even hiring another employee.
Depending on the size of the database, you may not need a full-time outcomes manager. But if you designate a clerk, nurse, or office manager with responsibilities, you need to make sure to give that person enough time to fulfill them.
In fact, senior management must provide visible support so staff realize this is a priority, he says. An outcomes management task force should review the practice's patient care process to determine the best time to give patients the questionnaires, and who will administer them or assist the patients.
Some outcomes projects may rely heavily on chart review or data you can cull from your practice database, or a project may require physicians or techs to log information during a procedure.
Keep in mind, also, that the hospitals your physicians are affiliated with are now required by the Joint Commission on Accreditation of Healthcare Organizations to conduct quality improvement projects. You may need to provide some data, or you may want to link your outcomes management to theirs, notes Cockerham.
In fact, you may save time and money by working with an affiliated hospital on an outcomes project, such as reducing cesareans. The hospital may provide staff support and patient education - and you will still get outcomes data to use in marketing yourself to managed care organizations.
2. Consider the technology demands and additional costs you will incur.
Presbyterian Hospital had just purchased a new advanced computer system when the hospital and Mid-Carolina Cardiology decided to join the American College of Cardiology database. But then a possible problem emerged: The database only works with a select group of approved vendors. The company that produced the hospital's new system wasn't on the list.
"We sort of panicked," recalls Younts. But the president of Medical Dynamics, a software firm in Columbia, SC, assured her the company already had begun the process to become an approved vendor. Younts advises groups to consider such issues when purchasing new computer technology and to look carefully at the technology requirements and costs before committing to join a database.
In conducting a technology assessment, you should determine how you must transfer your data to the database, and whether you need interface capabilities with another entity, such as an affiliated hospital that may share data with you, says Cockerham. Will you need to buy new computers? If so, add that into your costs.
After calculating the costs and burdens of implementing an outcomes system such as this, you may feel it's hardly worth the trouble. But now consider the costs of not doing it. They may ultimately be much higher in loss of managed care contracts and competitive advantages, says Cockerham. Outcomes data can tell you how effectively you are practicing medicine while giving you valuable marketing material.
Right now, not everyone has jumped on the outcomes bandwagon. Thus, says Cockerham, "you will achieve market differentiation when you embark on this plan."