Dina Dickerson, MPH Office of Family Health Public Health Division

1. FamilyNet From Silo to Data Mart to Data Warehouse Dina Dickerson, MPH Office of Family Health Public Health Division

2. FamilyNet FamilyNet is Oregon’s encounter-based data system consisting of a suite of applications that support services provided by the Office of Family Health. Today, the data in FamilyNet is not integrated into a single view of the client.

3. Problem: Legacy Database Silos • Duplication of clients across Programs • Duplication of effort by users • Redundant, often conflicting, data • Lack of standardization in data and policies • Old technology • High maintenance costs • Limited access to the data for evaluation • Large volume of clients managed • Some are popular with Providers & Staff

4. Legacy Database Silos: Redundant, Error Prone, Non-Standard Source: Office of Family Health Information Management Survey, September 2007

5. Legacy Database Silos: Old Technology, High Costs, Limited Access Source: Office of Family Health Information Management Survey, September 2007

6. Legacy Database Silos: Large Volume of Clients Managed Source: Office of Family Health Information Management Survey, September 2007

7. FamilyNet Vision • Capability to do assessment of OFH populations to improve health status and better serve our community’s needs. • Source: FamilyNet Strategic Planning September 2007

8. FamilyNet Strategic Planning Goals • Information is available on demand and shared as broadly as possible • Data is managed to maximize Program effectiveness • Partners value and incorporate FamilyNet data into their operations • Public Health Information Record is available to Clients, Providers and Partners • Source: FamilyNet Strategic Planning September 2007

9. Assess Community Measure Intervention Extended Family OFH Population Women (primary focus on children) Child FamilyNet Strategic Planning Goals • Source: FamilyNet Strategic Planning September 2007

10. Matrix of Common Functionality and Roles

11. Solution: Address Common Functionality and Roles • Functionality • Referrals • Screening for Program eligibility • Program enrollment • Guideline-directed care plans • Service delivery coordination • Encounter documentation • Service accounting • Outcome evaluation • Surveillance Source: Office of Family Health Information Management Survey, September 2007

12. Solution: Address Common Functionality and Roles • Roles • Client • Family • Staff • Program • Administrator • Provider • Agency/Partner • Sponsor • Legislature Source: Office of Family Health Information Management Survey, September 2007

13. Solution: Tools to Improve Program Effectiveness and Efficiency • Decision support • Program eligibility and alternatives for ineligible clients • Guideline-directed care plans • Alerts and reminders to encourage compliance • Required elements captured for client encounters • Data elements mapped to standards • Health Information Exchange • Electronic Medical Record • Practice Management System

14. Development Occurs in Phases • Phase 1: Changes to Operations Data • Phase 2: Data Marts • Phase 3: Data Warehouse • Phase 4: Public Health Information Record

15. Data Silo to Data Mart to Data Warehouse

16. Phase 1: Changes to Operations Data • Changes required to Online Transaction Processing systems • Optimized for data entry and editing and pre-defined reporting • Designed to manage daily operations

17. Phase 1: Changes to Operations Data

18. Phase 2: Data Marts • Programusers have immediate and ad hoc needs for data • Data Marts= Operational Data Stores • Program-specific and may be a subset of the data • Flattened, de-normalized files organized for ease of data extraction • Not mapped to standards • Not de-duplicated for Clients acrossPrograms • Program users can query and report their data

19. Phase 2: Data Marts

20. Phase 3: Data Warehouse • Links client data across programs • Maps data to standards • Provides tools for data analysis • Improves external reporting • Enables surveillance • Enables decision support • Enables health information exchange

21. Phase 3: Data Warehouse

22. Phase 4: Public Health Information Record • Enables a single view of client data • Enables clients to view their own data • Enables Providers and Partners to access their client records on demand • Uses web-based technology

23. Phase 4: Public Health Information Record

24. Amount of Data Decreases with Each Layer

25. FamilyNet: Data Silo to Data Warehouse Meets Goals of Strategic Planning • Information is available on demand and shared as broadly as possible • Data is managed to maximize Program effectiveness • Partners value and incorporate FamilyNet data into their operations • Public Health Information Record is available to Clients, Providers and Partners • Source: FamilyNet Strategic Planning September 2007

26. Acknowledgements Katherine Bradley, Ph.D. Administrator, Office of Family Health J A Magnuson, Ph.D. Informaticist, Office of Disease Prevention & Epidemiology Laura Zukowski, BA Operations & Policy Analyst, Office of Family Health Frank Steinkellner, PMP FamilyNet Project Manager, Office of Information Services

27. Contact Information Dina Dickerson, MPH Manager, MCH InformaticsOffice of Family HealthOregon State Public Health Division800 NE Oregon St., Suite 805Portland, OR  97232Phone: 971.673.0256Fax:  971.673.0250BlackBerry:  503.545.0515Dina.Dickerson@state.or.us