1. The Faculty Practice Plan of Northwestern’s Feinberg School of Medicine
Users’ Group Meeting
September 20, 2007
Disease Registries: Translating P4P and other Quality
Measures into EpicCare
2. Agenda
NMFF Overview
Epic Implementation History
Patient Registries History and Overview
Our Experience building a Disease Registry
After the Build
Lessons learned
2
6. Our Mission
Northwestern Medical Faculty Foundation is the
regionally and nationally recognized physician group
at the Feinberg School of Medicine, Northwestern
University. Our physicians and staff use innovative
clinical practices and technology and a
multidisciplinary approach to provide optimal patient
care and service. We support the clinical and
academic activities of the Feinberg School and
create an environment where the best medical
practices are demonstrated and learned.
6
7. NMFF Overview
About Northwestern Medical Faculty Foundation (NMFF)
Private, independent academic faculty practice plan
founded in 1980
Multi-specialty group practice for over 600 member
physicians who are all full-time faculty of Northwestern
University’s Feinberg School of Medicine (NU FSM)
Physician led
Not for profit
Provides care for indigent patients
7
8. NMFF Overview
Northwestern Medical Faculty Foundation Facts
Over 600 physicians and 1,101 staff at the end of FY06
17 departments, 34 specialties
Just under 571,000 outpatient encounters in FY06
Total clinical revenue $346 million in FY06
We occupy roughly 268,000 square feet of clinical space
for outpatient care in the Ambulatory Care Center (ACC)
8
9. NMFF Overview
Relationship to Northwestern University Feinberg
School Of Medicine (NU FSM)
NMFF members are full-time NU FSM faculty
• Clinical care of patients
• Ground breaking clinical research
• Training next generation of physicians
Faculty for over 600 medical students and 500 residents
and fellows (11,000 hours of teaching)
NMFF’s Ambulatory Care Center provides the venue for
outpatient teaching and clinical research
9
10. Epic Implementation History
Epic Implementation History
• Pilot: 1996 NLM Project to Pilot EpicCare in GIM
• Awards: 1998 Davies Award Winner
• Implementation in 31 specialty practices (2001 – 2006)
• 97% Implemented in 32 specialties (2007)
• Non-Implemented Specialties
• Reproductive Endocrinology and Infertility
• Ophthalmology
• Trauma/Critical Care
• Epic Products: Bridges, Clarity, EpicCare, Identity, MyChart
• Epic Version: Epic Fall 2006 version (Spring 2007 IU1 upgrade
scheduled for October 2007)
10
11. Epic Implementation History
EpicCare Implementations in Specialty & Sub-Specialty Areas
Allergy Lynn Sage Breast Center
Anesthesia/Pain Medicine Maternal Fetal Medicine
Cardiology Nephrology
CardioThoracic Surgery NeuroBehavior
Dermatology NeuroSurgery
Endocrine/Metabolism Northwestern Ovarian Cancer Early Detection Program
Gastroenterology Orthopedics/Sports Medicine
General Internal Medicine* Otolaryngology
General Neurology Plastics Surgery
General OB/GYN Psychiatry
Geriatrics Pulmonary
GI-Endocrine Surgery Reproductive Genetics
Gynecology Oncology Rheumatology
Gynecologic Surgery Surgical Oncology
Hematology Oncology Travel Medicine/Immunizations
Hepatology UroGynecology
Immunotherapy Urology*
Interventional Radiology Vascular Surgery
*MyChart Department 11
12. Agenda
NMFF Overview
Epic Implementation History
Patient Registries History and Overview
Our Experience building a Disease Registry
After the Build
Lessons learned
12
13. Patient Registries History & Overview
Patient Registry Definitions
“A database designed to store and analyze information about the
occurrence and incidence of a particular disease, procedure,
event, device, or medication and for which, the inclusion criteria
are defined in such a manner that minimizes variability and
maximizes precision of inclusion within the cohort.”
--- Dale Sanders, Northwestern University Medical Informatics Faculty, 2005
“Computer Applications used to capture, manage, and provide
information on specific conditions to support organized care
management of patients with chronic disease.”
--”Using Computerized Registries in Chronic Disease Care”; California Healthcare
Foundation and First Consulting Group, 2004.
13
14. Patient Registries History & Overview
AHRQ’s Patient Registry Definition
“A patient registry is an organized system that uses
observational study methods to collect uniform data (clinical
and other) to evaluate specified outcomes for a population
defined by a particular disease, condition, or exposure and
that serves one or more predetermined scientific, clinical, or
policy purposes.”
The National Committee on Vital and Health Statistics
describes registries used for a broad range of purposes in
public health and medicine as "an organized system for the
collection, storage, retrieval, analysis, and dissemination of
information on individual persons who have either a
particular disease, a condition (e.g., a risk factor) that
predisposes [them] to the occurrence of a health-related
event, or prior exposure to substances (or circumstances)
known or suspected to cause adverse health effects."
http://effectivehealthcare.ahrq.gov/reports/registry/registry.htm
14
15. Patient Registries History & Overview
History of Patient Registries
Historically, the term implies stand-alone, specialized products and
clinical databases
Long precedence of use and effectiveness in Cancer
• 1926: First cancer registry at Yale-New Haven hospital
• 1935: First state, centralized cancer registry in Connecticut
• 1973: Surveillance, Epidemiology, and End Results (SEER)
program of National Cancer Institute, first national cancer registry
• 1993: Most states pass laws requiring cancer registries
Pioneered by GroupHealth of Puget Sound in the early 1980s for
diseases other than cancer
• “Clinically related information system”
15
16. Patient Registries History & Overview
Types of Registries
Product Registries
• Patients exposed to a health care product, such as a drug or a device.
Health Services Registries
• Patients by clinical encounters such as
– Office visits
– Hospitalizations
– Procedures
– Full episodes of care
Referring Physician Registry
• Facilitates coordination of care
Primary Care Physician Registry
• Facilitates coordination of care
16
17. Patient Registries History & Overview
Types of Registries
Scheduling Events Registry
• Facilitates analysis for Patient Relationship Management (PRM)
• Can drive reminders for research and standards of care protocols
Mortality registry
• An important thing to know about your patients
Research Patient Registry
• Clinical Trials
• Consent
Disease or Condition Registries
• Disease or condition registries use the state of a particular disease or
condition as the inclusion criterion.
Combinations
17
18. Patient Registries History & Overview
Varying Benefits
How do I analyze patient
trends and outcomes for
a disease?
Clinicians
How are my clinicians
managing diseases?
Physician Organization Registries Consumer
How do I know which
How does my drug drug/procedure works
perform in disease best for me?
prevention and cure?
Drug Manufacturer
18
19. Patient Registries History & Overview
Uses for Patient Registries
To observe the course of disease
To understand variations in treatment and outcomes
To examine factors that influence prognosis and quality of life
To describe care patterns, including appropriateness of care and
disparities in the delivery of care
To assess effectiveness
To monitor safety
19
20. Patient Registries History & Overview
Current Trends measuring Quality using Registries
The IOM defines quality as “the degree to which health services for
individuals and populations increase the likelihood of desired health
outcomes and are consistent with current professional knowledge.”
Quality-focused registries are being used increasingly to assess
differences between providers or patient populations based on
performance measures that compare:
• Treatments provided or outcomes achieved with “gold standards” (e.g.,
evidence-based guidelines)
• Comparative benchmarks for specific health outcomes (e.g., risk-
adjusted survival or infection rates)
20
21. Quality Management Reporting - Example Patient Registries History & Overview
Eligible Satisfied Rate
Preventive Services
Cervical Cancer Screen 223 146 65%
Mammogram 138 83 60%
Colorectal Cancer Screen 355 143 40%
Pneumonia Vaccine 144 33 23%
Osteoporosis Screened or on Treatment 75 44 59%
Cardiovascular Disease
HTN: good BP control (mean or last <= 140/90) 310 196 63%
CAD: antiplatelet medication 62 54 87%
CAD: lipid lowering medication 65 54 83%
CAD: Beta blocker post-MI 12 10 83%
CAD: ACE/ARB if DM or LVSD + CAD 25 19 76%
CHF: anticoagulation for AF + HF 6 5 83%
CHF: ACE/ARB if LVSD 3 3 100%
CHF: beta blocker if LVSD 3 3 100%
Diabetes
Last Hba1c <= 7 87 37 43%
Last Hba1c <= 9 87 66 76%
Good BP control (mean or last BP <= 130/80) 83 39 47%
Good LDL control (<100) 87 49 56%
Nephropathy: screened or on ACE/ARB 87 64 74%
21
22. Patient Registries History & Overview
Getting the most out of your disease registry (Our Interpretation)
Consistent profiling for prospective, predictive intervention
• The goal is to keep people off of disease registries, but first you have to
know how those who are on the registry, got there…
Outreach communication to patients
• Reminders about care and intervention
Ensuring a common understanding for inclusion, exclusion and disease
management.
Quality of care reporting (e.g. P4P)
• Cost effective & treatment efficacy to payers & employers
• Feedback reports to physicians about their care practices
Process improvement projects for service line clinical programs
• Use trend analysis to find possible process deficiencies that affect patient
care
Population reporting and analysis for research (e.g. Epidemiology)
22
23. Agenda
NMFF Overview
Epic Implementation History
Patient Registries History and Overview
Our Experience building a Disease Registry
After the Build
Lessons learned
23
25. Our Experience Building a Disease Registry
Patients exist in one of three states, relative to a patient registry
On Registry: The patient is a member of a particular registry; i.e., they fit the
inclusion criteria
Off Registry: Patient was once a member of a registry and fit the inclusion criteria,
but is now excluded. The exclusion could be “disease free.”
At Risk: The patient fits the profile that could lead to inclusion on the registry, but
does not yet meet the formal inclusion criteria, e.g. obesity as a precursor to
membership on the diabetes and or hypertension registry.
Disease Registry
At Risk On Registry Off Registry
25
26. Our Experience Building a Disease Registry
Patient Registry Vision
• How do we define a particular disease?
• Who has the disease?
• What is their demographic profile?
• Are we managing these patients according to
accepted best protocols?
• Which patients had the best outcomes and why?
• Where is the optimal point of cost vs. outcome?
26
27. Our Experience Building a Disease Registry
Disease Registry Exclusions
The industry will need standard vocabularies for excluding patients
• Removing patients from the registry whose data would
otherwise skew the data profile of the cohort
“Why should this patient be excluded from this registry, even
though they appear to meet the inclusion criteria?”
– Patient has a conflicting clinical condition
– Patient has a conflicting genetic condition
– Patient is deceased
– Patient is no long under the care of this facility or physician
– Patient is voluntarily non-compliant with the care protocol
– Patient is incapable of complying with the care protocol
Disease Registry
At Risk On Registry Off Registry
27
28. Our Experience Building a Disease Registry
Our disease registry is populated by patient care cycle
Original Diagnosis Continued Care Continued Care Cured
Patient Data
How do I build this?
(Clinical, Business, etc)
Pay for
Pay for
Pt. included in Disease Reg. Performance
off Original Diagnosis Performance
measures
measures
Disease Registry
28
29. The Healthcare Process and Transactional Systems at NMFF
Patient Data lies in various data sources
Billing &
Billing and AR Claims Claims Processing
Accounts
System Processing System
Receivable
Registration & Orders & Encounter Results & Patient
Diagnosis
Scheduling Procedures Documentation Outcomes Perception
Results Surveys
ADT System Diagnostic systems Pharmacy Electronic
Master Patient Index Lab System Medical Record
Radiology
Imaging
Pathology
Cardiology
Others
29
30. The Northwestern Campus : Multiple, Collaborative, Organizations
Physician Office X
Billing &
Billing and AR Claims Claims Processing
System
Accounts System
Processing
Receivable
Registration &
Scheduling
Diagnosis
Orders &
Procedures
Encounter
Documentation
Results &
Outcomes
Patient
Perception EDW
A single data perspective
on the patient care process
Pharmacy •Diagnostics Surveys
•ADT System Diagnostic systems Electronic
•Master Patient Index •Lab System Medical Record •Pharmacy
•Radiology
•Imaging
•Pathology
•Cardiology
•Others
Billing &
Billing and AR Claims Claims Processing
System
Accounts System
Processing
Receivable
Billing &
Billing and AR Claims Claims Processing
System
Accounts System
Processing
Receivable
Registration & Orders & Encounter Results & Patient
Diagnosis
Scheduling Procedures Documentation Outcomes Perception
Registration & Orders & Encounter Results & Patient
Diagnosis
Scheduling Procedures Documentation Outcomes Perception
Pharmacy •Diagnostics Surveys
•ADT System Diagnostic systems Electronic
•Master Patient Index •Lab System Medical Record •Pharmacy
•Radiology •Diagnostics Surveys
•Imaging •ADT System Diagnostic systems Pharmacy Electronic
•Master Patient Index •Lab System Medical Record •Pharmacy
•Pathology
•Cardiology •Radiology
•Imaging
Hospital Y
•Others
•Pathology
Physician Office Z
•Cardiology
•Others
30
31. Our Experience Building a Disease Registry
Original Diagnosis Continued Care Continued Care Cured
Patient Data
(Clinical, Business, etc)
Pay for
Pay for
Pt. included in Disease Reg. Performance
off Original Diagnosis Performance
measures
measures
How do I build this?
Disease Registry
31
32. Our Experience Building a Disease Registry
Basic steps to build a disease registry
Identify stakeholders
Identify data points necessary to define, include and exclude in disease registry
Identify source of data points
Build registry
Address data quality issues
32
33. Our Experience Building a Disease Registry
Identifying Data Points & Data Sources
Inclusion codes based entirely on ICD9, which is a good place to start, but
not specific enough
• Heart failure codes for study inclusion
– 398.91, 402.01, 402.11, 402.91, 404.01, 404.03, 404.11, 404.13, 404.91, 404.93, 428.xx
• Exclusion criteria for beta blocker use†
– Heart block, second or third degree: 426.0, 426.12, 426.13, 426.7
– Bradycardia: 427.81, 427.89, 337.0
– Hypotension: 458.xx
– Asthma, COPD: see above
– Alzheimer's disease: 331.0
– Metastatic cancer: 196.2, 196.3, 196.5, 196.9, 197.3, 197.7, 198.1, 198.81, 198.82, 199.0,
259.2, 363.14, 785.6, V23.5-V23.9
• † Exclusion criteria were only assessed for patients who did not have a medication
prescribed; Thus, if a patient was prescribed a medication but had an exclusion criteria, the
patient was included in the numerator and the denominator of the performance measure. If
a patient was not prescribed a medication and met one or more of the exclusion criteria, the
patient was removed from both the numerator and the denominator.
Acknowledgements to Dr. David Baker, NU Feinberg School of Medicine
33
34. Our Experience Building a Disease Registry
What does a Diabetes Disease Registry Look Like Elsewhere?
34
38. Our Experience Building a Disease Registry
Our First Design
Keep it as flat as possible
Use consistent naming standards throughout
Keep design minimalist
38
39. Our Experience Building a Disease Registry
Our Extensible Design
Motives
Consistent profiling for prospective, predictive intervention
Outreach communication to patients
Quality of care reporting (e.g. P4P)
Process improvement projects for service line clinical programs
Population reporting and analysis for research (e.g. Epidemiology)
Key Design Considerations
Used clinician input for building & defining institutional definition of the disease
Stakeholders input in defining inclusion & exclusion criteria
Disease Registry metadata contains inclusion, exclusion criteria
Added a reason for inclusion description for disease registry
The disease registry data model was built to tie the patient identity back to data points in the
data warehouse which includes all EMR data sources.
39
40. Building our Disease Registry (i.e. Diabetes)
Epic-Clarity di abet es ( r egi st r i es_ dm)
Column Name Data Type Allow Nulls
ETL Package
Problem List mrd_pt_id int
birth_dt datetime
death_dt datetime
Orders gender_cd varchar(20)
problem_list_diabetes... int
encntrs_diabetes_dx_... int
Encounters
orders_diabetes_dx_n... int
meds_diabetes_dx_num int
Cerner last_hba1c_val float
last_hba1c_dts datetime
Inclusion
Problem List and max_hba1c_val float
Exclusion max_hba1c_dts datetime
Criteria min_hba1c_val float
Orders for min_hba1c_dts datetime
Specific tobacco_user_flg varchar(50)
Disease
alcohol_user_flg varchar(50)
Encounters Registry
last_encntr_dts datetime
last_bmi_val decimal(18, 2)
last_height_val varchar(50)
IDX
last_weight_val varchar(50)
CPT’s Billed data_thru_dts datetime
meta_orignl_load_dts datetime
meta_update_dts datetime
Billing Diagnosis meta_load_exectn_guid uniqueidentifier
40
42. Agenda
NMFF Overview
Epic Implementation History
Patient Registries History and Overview
Our Experience building a Disease Registry
After the Build
Lessons learned
42
46. After the Build
Strategies for managing bad data
Proactive Measures
Define feedback mechanism to report bad data in the source system to
the appropriate data owner.
Prevent future input of bad data in the source systems
• Add data validations in the user interface.
Reactive Measures
Define the ability to flag erroneous data in the data marts (disease
registries)
Eliminate erroneous data from analytical reporting
46
48. After the Build
Tying Disease Registries back to Point of Care
Ideally disease registry information should be available at point of care
• Guideline-based intervals for tests, follow-ups, referrals
• Interventions that are overdue
• “Recommend next HbA1C testing at 90 days because patient is not at
goal for glucose control.”
How do you implement this in Epic?
• Invoke web services within epic programming points to display
information inside epic
• Invoke external web solutions within hyperspace
• Write data back in epic
– FYI Flags
– CUIs
– Health Maintenance Topics
– Etc.
48
49. Agenda
NMFF Overview
Epic Implementation History
Patient Registries History and Overview
Our Experience building a Disease Registry
After the Build
Lessons learned
49
50. After the Build
Lessons Learned
Clinical Sponsorship is necessary.
Agile development methods are useful in getting user buy-in
• They are quick
• They demonstrate work product
Defining registries shouldn’t be limited to only ICD-9 defined diseases
Try to include the reason a patient is added into a registry.
Measure and Insight can be equally significant to registries other than
disease based
Need to prioritize which data sources have highest value (esp. when you
have more than one EMR source)
Creating a “data bus” to traverse all available data points will create new
opportunities for discovery and research.
50
Editor's Notes
Welcome. Background on how for 4 years been focused on getting physicians to use the mdeical record. Natural evolutions has led me to look at the data they ‘ ve entered. Talk about how todays presentation will talk about definition of disease registries, an noverview of current trends, summary of our experience and suggestions for standardizing registries as a component for EpicCare.
Today ’s outline: Background on NMFF; Brief touch on Epic ’s implementation and Epic product use Disease (Patient) Registry overview Our Experiences building the registry and then using the registry Followed by lessons learned and a look at the future.
So out in Lake Michigan we look upon the gold coast neighborhood of chicago. Here is the Northwestern Campus off to the left
Here is the Feinberg Pavillion (IP) and Ambulatory Care Center (taller on right) where NMFF owns 7 floors of space. Nice part is our campus is redominanatly this building and those within a block radius.
Here is the latest addition one block away; Prentices womens hospital scheduled to open Oct 20 th (about 1 month) which features 1 million square feet and is being labeled as an all digital hospital.
Here is the NMFF missions statement which probably looks similar to yours.
So NMFF was founded in 19080 as a privately owned multispecialty practice plan. The 600 member physicians lead the company and are full-time faculty of Northwestern University ’s Feinberg School of Medicine.
For comparison purposes to perhaps how we relate to you; here are some statistics; We have approximately 1700 staff and physicians in 34 specialties who see roughly 571,000 outpatient encounters within 268,000 square feet of the ACC.
The NMFF members relate to NU-FSM as full-time faculty and provide 11,000 hours of teaching within the ACC venue. (Outpatient)
History of Epic and NMFF is rather lengthy and began in 1996 under an NLM project in GIM. In 2001, NMFF decided to roll out EpiCare to the remaining specialty practices over the next five years. Today, EpicCare is implemented in 32 specialty areas and awaits implementation in REI, Opthal, and Trauma/critical care. The mark from 31 to 32 was the addition of Psychiatry. How imbedded our we with Epic, we use Bridges, Clarity, EPicCare, Identity and mychart. We utilize interfaces heavily as our practice management system is IDX and the hospital lab system (mysis) is our reference lab. Original Epic associated with NMH Davies Award winner for NetReach project was given to NMH under published work of Dr. Paul Tang. http://www.himss.org/content/files/davies_1998_nmh.pdf Implementation Requirements included Meds, Orders, LOS, Diagnosis and documentation sufficient to support LOS via Charting Tools or Dictation. Did not require use of Allergy, History and In-Basket but strongly recommended 31/32 implementations occurred through 2006. 31 implementations represented 91% of way. 32 nd implementation was psychiatry NMH uses Cadence Were on Classic version of EpicCare for first two implementations na dthen made the jump to Hyperspace. Non-Implemented: REI, Ophthalmology, Trauma/Critical Care 316/326 = 96.9% (After Psychiatry) 296/326= 90.8% (Less Psych) 780 concurrent users
Here is a listing of our specialty and subspecialty areas. So note there is more than 32. I think whats important in demonstrating an organization that is specialty driven is how it affects the culture of the institution. We tended to aim to please or finesse the system to meet their needs rather than dictate use. As a government we might be characterized as a federation of states. Non-Implemented: REI, Ophthalmology, Trauma/Critical Care Users like Transplant, Pathology, Radiology, Anesthesia use read-only and/or hospital transactional systems Is MyChart department More than 34 specialties, actually 36 because some of these are subareas within specialties or practices
So background is out of the way, let ’s talk about patient (disease) registries.
At first we focused on the definition “A database designed to collect… We also ran across other ’s definition. Here you have California Healthcare Foundation and First Consulting Groups definition in 2004
Then on May 16 of 2007 Agency for Healthcare Research and Quality provided a definition and 235 page manual on how to construct a patient registry. We came to a similar conclusion though on defining disease registries; there are many definitions. We finally concluded that the best definition for our purposes is similar to the National Committee on Vital Health Statistics; we wanted “an organized system for the….” I point this out because we include the component of risk factors or predisposal so the scope of our measures may lend additional insight into the disease.
In doing this, we searched to see how far back a documented registry could be found. We found evidence of patient registries existing for Cancer as far back as 1926.
It should be noted that there are other types of registries beyond patient or disease based registries that are effective to different stakeholders: Product Registry might be useful to drug, equipment or device manaufacturer Health Services may look at a particular visit type or procedure to conduct analysis Referring physician and primary care registries may lend insight that facilitates coordination of care
Scheduling event registries may help drive reminders and patient relationship Mortality Registry: An important thing to know Research Patient registry might lists consents and those on clinical trials Disease or Condition registries are the ones we are utilizing and focusing on disease states
Different stakeholders perceive and may benefit from the value of registries in different ways. For example, For a clinician: registries can collect data about disease presentation and outcomes on large numbers of patients rapidly, thereby producing a real-world picture of disease. For a physician organization, a registry might assess the degree to which clinicians are managing a disease in accordance with evidence-based guidelines, focus attention on specific aspects of a particular disease that might otherwise be overlooked, or provide data for clinicians to compare themselves with their peers. From a payer ’s perspective, registries can provide detailed information from large numbers of patients on how procedures, devices, or pharmaceuticals are actually used and on their effectiveness in different populations. This information may be useful for determining coverage policies. For a drug or device manufacturer, a registry might demonstrate the performance of a product in the real world, meet a post marketing study commitment, develop hypotheses, or identify patient populations that will be useful for product development, clinical trials design, and patient recruitment. The U.S. Food and Drug Administration (FDA) has noted that “through the creation of registries, a sponsor can evaluate safety signals identified from spontaneous case reports, literature reports, or other sources, and evaluate the factors that affect the risk of adverse outcomes such as dose, timing of exposure, or patient characteristics.”
A patient registry can be a powerful tool to observe the course of disease; to understand variations in treatment and outcomes; to examine factors that influence prognosis and quality of life; to describe care patterns, including appropriateness of care and disparities in the delivery of care; to assess effectiveness; to monitor safety; and to change behavior through feedback of
IOM defines quality. Registries are increasingly becoming poplular to compare differences between providers or patientpopulations based on performance measures. Measuring quality . Registries may be created to measure quality of care. The IOM defines quality as “the degree to which health services for individuals and populations increase the likelihood of desired health outcomes and are consistent with current professional knowledge. ” Quality-focused registries are being used increasingly to assess differences between providers or patient populations based on performance measures that compare treatments provided or outcomes achieved with “ gold standards” (e.g., evidence-based guidelines) or comparative benchmarks for specific health outcomes (e.g., risk-adjusted survival or infection rates). Such programs may be used to identify disparities in access to care, demonstrate opportunities for improvement, establish differentials for payment by third parties, or provide transparency through public reporting. There are multiple examples of such differences in treatment and outcomes of patients in a range of disease areas.
Here is an example of a report furnished in our institution which demonstrates a physician ’s complaince with quality based measures cited by our intitutional
At NMFF, we decided that our disease registries would promote: Consistent profiling for porspective and predictive intervention. Remember, we want to include those with risk factors or predispositions for the disease so we can lend analysis into the full longitudinal care. The goal is to get people off of the registries..but first you… Outreach communication- want to educate patients and remind them about care and intervention A common vocabulary and use for setting inclusion and exlcusion criteria as well disease management Enable P4P reporting Promote process improvement projects alligned with out priority clinical programs (our strategic inititiatives) Population reporting and analysis
Our target registries at NMFF. Want to begin build by having the end in mind. Include both large “n” and small “n” diseases The ones in bold were prioritized by our clinical leadership for two reasons: ongoing research efforts emphasis on priority clinical program
We then looked at our definition of a registry (disease or risk factor) and establsihed that our patients exist in one of three states relative to a registry. On-Off- At-Risk Questions can be asked at each state: At Risk What is the best intervention strategy to prevent these patients from reaching the On Registry state? Timing, treatment plans, lifestyle changes On Registry What is the historic profile of these patients and how do we apply that profile to intervene with At Risk patients? Are we managing their care plan according to best practices? Is it possible to move these patients to the Off Registry state? If so, how? Off Registry What are the exclusion criteria? What changed about the patient ’s inclusion criteria? For those patients who no longer fit the inclusion criteria, what role did our care plan play? Can we apply that care plan to other patients and move them from to the Off Registry state?
Once we determined the patient scope, we began to move to the build and how are patients might get on the registry. So we looked at seeting out to define the possible types of data that would be helpful in defining the patients to include into our data. We also looked at including additional soruces of information like cost and reimbursement as likely data points. We ’re trying to look beyond the world of ICD9 and CPT to define our registry.
We also looked at exclusions. What sort of conditions may exclude a patient from the data and are sufficient functionalities or standard vocabularies in place which exclude the patient. Non-compliance may be due to refusal, religious, or financial aspects.
In the end: we thought of a picture of the care process… We thought about our care process and again wanted to be able to look at the longitudinal care plan and our ability to records patient data, funnel it into our registry so we could analyze the data effectively to support such measures. Thus began the question. How do I build a repository of patient data that includes the possible data points in clinical, business, cand research systems.
So again, we outlined the processes that make up patient care and thought about the varying processes that could populate the patient care database. Then we thought about the systems that collect this information The typical healthcare process is envisioned in this manner Overlay the systems that represent these processes and a complex web emerges. The typical data transmission is done via HL7 and sometimes we do things like convert our data points into a text report to share them with the EMR so the ability to measure becomes more complex.
We quickly realized that we (NMFF) don ’t even have all the healthcare data points. given the disparity of informational systems; aggregating the data in a common location became essential so we set out on building an Enterprise Data Warehouse (EDW) to create a single data perspective on the patient care process.
So we had a plan for the patient data but what about building the disease registry?
We outlined these basis steps to building the disease registry. Sometimes we even shopped for stakeholders as we went along but this wasn ’t preferred.
An example of the data points; inclusion/exclusion criteria we set up for chronic heart failure
So in part of good due diligence, we started a journey to find similar disease registries.
University of Washington Physicians Network
Harvard Vanguard
Harvard Vanguard cont.
So at last we were ready to attempt our first registry and invoked these motives on our data tables. Keep flat which means try to do as much as possible in one table. Use consistent naming and data types throughout all our registries. Keep design minimalist which was an attempt not to start with complex star schemas but only end there
So with our data structures in mind, we summarized our motives and key design considerations. We noted quickly that we could build quicker with stakehodler involvement, could display our information via a disease registry metadata browser and could validate information so we quickly added the reason for inclusions into the registry as a trackable data point. Because we are building in an EDW and we had the patient identity uniquely know, we could quickly add additional data points
When we set out to build the diabetic one. The first round consisted of focusing on the Clarity data points but we also had other viable sources we could extend the model to. Again this quickly revealed how the reason for inclusion would be helpful. We built the ETL package and began populating our registry.
Here is an example of a parameterized report that echoed back information on the disease registry.
So we built a registry, we even built a few more registries and began to look at the data
Here is the BMI distribution of patients on our obesity disease registry. Slightly skewed to the right as you would expect. Looking at the data immediately drew quesations. As this is the patient ’s current BMI, who are the patients with BMI’s between 20-25? Are they at risk? Did they have bariatric surgery?
We also saw bad data and looked at possible explanations
Finding bad data leads to investigation. 7359 pond babies Investigation leads to the root cause
So this lead us to develop strategies for managing bad data; We believed in not altering the bad data but reporting it back to the source system ’s data owner for follow-up. They could correct the date They may alter the user interface to eliminate the input of bad data In an effort to use the disease registry, we would flag the data as bad so we could set queries to ignore use.
Eventually, we were able to tie it all together: By this we found a champion who wanted to look at patient ’s admitted with MI to see how we might be able to better manage our patients. We took everyone with an admit of a 410 or 411 ICD-9 for a given month and looked at the orders post discharge. We removed our deceased patients and look at those patients with LDL orders and classified them in separate management categories. The rest of the population was deemed unmanaged since they didn ’ have any LDL orders. But we looked at this set a little more and found that 49 of these “unmanaged” patients still had an order of some kind in our system and hence were on campus and potantially an opportunity for improvement existed: Perhaps their LDL ’s were self reported. Perhaps they had more serious conditions While this is ongoing, it points out interesting opportunity for improvement in process, data collection.
It ’s great buidling registries and lending insight, but the information is best if it is tied back to point of care. The registry info and best practice guidelines need to be at a point in the care process where the physician can effectively use them. In a specialty institution like ours this typically leads to use in many placesof EpicCare. We believe web services lend a reusable and secure method to do this. Choosing the right data point may be a variable task.