1 / 16

CDM Data Analytics Using a RIM approach

CDM Data Analytics Using a RIM approach. Diane Gutiw PhD SAIC Canada Health Solutions Business Unit. CDM Data Analytics Discussion …. The Business Problem Overview of CDM Workflow Overview of the need for Data Analytics Support in V3 messaging and RIM How to implement

fawn
Download Presentation

CDM Data Analytics Using a RIM approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CDM Data AnalyticsUsing a RIM approach Diane Gutiw PhD SAIC Canada Health Solutions Business Unit

  2. CDM Data Analytics Discussion … • The Business Problem • Overview of CDM Workflow • Overview of the need for Data Analytics • Support in V3 messaging and RIM • How to implement • BioSense as potential solution for CDM

  3. The CDM Business Problem • Multiple disease conditions • Diabetes, CHF, COPD, HBP, Asthma, Renal, Depression, Arthritis, Alzheimer's, Epilepsy, Hepatitis, CF, Eating Disorders, Obesity, Cancer, Anemia, AIDS/HIV etc. • May be overlap in conditions • Treatment focus is disease management not cure • CDM Clinician collaboratives • Data sharing based on treatments and outcomes rather than POS data • Challenges of data collection • Challenges of data standardization/normalization

  4. Potential Data Sources EMR Drug Repository SHR RIM EMR EMR Lab Repository Pharmacy Pharmacy DI Repository Provider Repository Location Repository ADT Client Registry ADT ImmunizationRepository

  5. CDM Workflow

  6. Support in Messaging • Supporting Messages: • Lab • Diagnostic Imaging • Immunization • Prescription • ADT • … • Gaps identified in existing reporting for CDM

  7. Gaps in HL7 v3 Messaging • Use existing Registries/Repositories as “source of truth” • CDM elements available in RIM • Clinical data specific to CDM not in any existing RMIM • Data required for CDM Analytics outside of existing repositories: • Clinical background (smoking cessation, diet, weight loss) all available in SNOMED • Concept of Collaborative Teams • Includes combined assessment, referrals, treatment, hospitalizations and adjusted treatment pattern for CDM • Treatment refusals, testing negation indicators and lifestyle adjustments/refusals critical to data analytics • And then how to consolidate data and extract for “meaningful use”?

  8. Benefits of a RIM-based solution • Supports data modeling requirements • Supports standardization • Supports normalization • Extends to multiple conditions, treatments, outcomes • Supports reporting needs

  9. BioSense Solution BioSense Solution: To provide a technology platform which simplifies the enablement of public health reporting in a healthcare-centric environment, satisfying the requirements of HITECH and “meaningful use” objectives relative to Public Health.

  10. BioSense Architecture • A toolset that can be run standalone, or can be integrated into an existing system or system interface. • An interface that allows loose coupling.  This allows it to be integrated into proprietary platforms such as Microsoft .NET. • A design to support Public Health reporting, and flexible enough to support future health reporting requirements. • Interoperable • Hardware and software vendor independent. • Able to collect appropriate and targeted hospital/jurisdictional data.

  11. POS Hospitals & Clinics Retail Pharmacy Rx POS Labs BioSense System Extract, Transform, Load (ETL) Data Warehouse Secure Data Network Secure Messaging Data Marts Integrator Data Broker SAS Analytics Rhapsody Rhapsody The Integrator “listens” to the source’s HL7 traffic and places needed data on-line Receives source data, un-batches and transforms HL7 files to XML & send XML to queue Provides a guaranteed message delivery service across the internet Informatica Centralized Data Repository Provides Certificate based authentication services Application specific, de-normalized & decentralized data Apply business rules to data and load Data Warehouse Application Public Health Users And CDM Users SAS WebLogic ESRI LifeRay Portal Bio-Intelligence Users

  12. Example: Stand-alone Solution for Surveillance PHORS leverages SAIC’s healthcare and HL7 messaging knowledge. The PHORS architecture is designed to allow Infection Control Practitioners (ICPs) to define detection rules which are then stored in a rules based engine and used by web services to identify patient data to assist ICPs in managing and reporting of Hospital Acquired Infections (HAI) Public Health Open Reporting System (PHORS) NATIONAL HEALTH SAFETY NETWORK BIOSENSE ELR BIOSENSE

  13. BioSense Features • Additional reporting available • Can add other characteristics or reports for local needs • Supports a multitude of data feeds • Configurable by the end user • You select the characteristics of the records • Controllable by the end user • Can require user approval prior to reporting

  14. Next Steps…. • BioSense currently in production in US for Public Health • BioSense currently receives > 4 million clinical records daily • Batch (Not Real Time) • 913 Veterans Affairs (VA) facilities • 375 Department of Defense (DOD) facilities • Real Time • 117 facilities from 24 Hospital Systems • 536 facilities from 9 Syndromic Systems • 2 National Reference Labs (LabCorp and Quest) • >35,000 retail pharmacies (PerSe, McKesson RelayHealth) • BioSense to be presented to Canadian Public Health and CDM business users • BioSense to be adapted to meet CDM requirements as POC

  15. Questions or follow up … • Diane Gutiw gutiwd@saic.com

More Related