Friday, June 3, 2011
Thursday, June 2, 2011
ACO Series, Part I
Tuesday, April 26, 2011
Plug and Play Business Intelligence?
As I was speaking to a potential client recently, I realized that someone had tried to sell her BI in a box. Even with our appliance Integra, I would not dare call it a plug and play solution. Why? There is so much that needs to happen before you get useful information out of your BI initiative. Out of the box, Integra includes the following:
· The ETL (extract, transform and load) software required to connect and integrate data.
· A semantic dictionary of healthcare terms for mapping source data to target data
· A data warehouse (customizable to house EMR, financial and other data).
· Pre-loaded metrics
· A fully integrated BI reporting solution.
· Pre-built reports.
· The hardware to house all this.
And you still wouldn't call that BI in a box, you ask? Absolutely not! And here is why. Even with all of this functionality built in, there is one thing missing. No prizes for guessing what it is. What is missing is “YOUR" data! Guess what, without that, the greatest BI in a box solution won't be of much use to you.
So let's take a look at what needs to happen before this becomes the BI 'Solution' that works for YOUR organization.
· Implementation Planning – During this initial phase the following will occur:
o Gather full set of reporting requirements.
o Gather testing requirements.
o Gather production deployment requirements.
o Identification of systems of record (SOR) and the tables/fields needed to satisfy the end reporting requirements.
o Mapping documents for each SOR are created. These documents include:
§ Source field name, data type and format.
§ Target field name, data type and format.
§ Cleansing requirements for each field.
§ Business logic needed to translate from source to target.
o Create development, testing and implementation plans for the next phases of this project.
· Customization – The actual customizations are created during this phase.
o Data for each SOR is gathered.
o Cleansing ETL processes are created for each source record.
o ETL processes are created and unit tested for each SOR.
o Reporting cube(s) are customized to support reporting requirements.
o Reports are created/customized and unit tested to requirements.
o At the end of this phase, the hardware is delivered to your site and the processes are connected to your SORs.
· Testing – Testing will be performed to the requirements which typically includes:
o Systems Integration Test (SIT) – Full nightly runs are performed and system is tested for correct technical functionality.
o User Acceptance Test (UAT) – A test bed of users are allowed to use the system to ensure requirements have been met from a business/clinical viewpoint.
· Production Deployment – The system is moved to your production environment and the system is made available to your users for consumption.
So folks, next time someone tells you that there is a plug and play solution for BI that does all of these things automagically, please call me right away! I would like to see this wondrous new thing and pay my respects. You can reach me at kishore@metaanalytix.com
Monday, April 11, 2011
Mental Health
Monday, February 14, 2011
Accountable Care Organization - Achievable?
What is an ACO?
Here is a recent example of an ACO definition taken from a 2010 article co-authored by Elliot Fisher:
ACOs consist of providers who are jointly held accountable for achieving measured quality improvements [note that “measured quality improvements” is synonymous with report cards] and reductions in the rate of spending growth. Our definition emphasizes that these cost and quality improvements must achieve overall, per capita improvements in quality and cost, and that ACOs should have at least limited accountability for achieving these improvements while caring for a defined population of patients.
ACOs may involve a variety of provider configurations, ranging from integrated delivery systems and primary care medical groups to hospital-based systems and virtual networks of physicians such as independent practice associations. All accountable care organizations should have a strong base of primary care. Hospitals should be encouraged to participate, because improving hospital care is likely to be essential to success. But in contrast to others’ definitions, we believe that this need not be an absolute requirement for all ACOs (Mark McClellan et al., “A national strategy to put accountable care into practice,” Health Affairs 2010;29:982-990).
Hmmmm....confused enough? Well, in my ongoing quest to simplify or "Englishify" everything, I'll take a stab at it in my own way. The basic premise of an ACO is this:
1. Improve Quality of Care
2. Reduce Cost
3. We will hold you accountable for 1 and 2. Simple enough? Not so fast....
Someone once told me, "if you ask a question once, you might look dumb. But if you don't ask it, you'll stay that way". So here are the questions:
1. Who is going to hold you accountable? (Let's say CMS)
2. How are they going to hold you accountable? (Let's say they come up with measures that you have to track and report)
3. Define "defined patient populations"? (This my friends, I have no idea what it means)
So my real question is, if they do come up with the answers to the questions above and define ACOs, is it an achievable goal? The answer is, Absolutely! Improving quality of care while reducing cost of care is a very achievable goal. In fact, you should do it before they make you do it! The technology exists today. All you have to do is take one look at our KnowledgePath report and go home happy knowing that you have the technology and reporting capabilities available at your fingertips.