Methods and Techniques for Integration of Small Datasets September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban.

Slides:



Advertisements
Similar presentations
Presents: The Blue Ridge H M I S.
Advertisements

The 4 T’s of Test Automation:
Introduction to Homeless Management Information Systems (HMIS)
Supportive Services for Veteran Families (SSVF) HMIS and the Impact of Outcomes in Prevention Services Sponsored by: National Center on Homelessness Among.
SHADoW in Michigan Barbara Ritter and Jim Davis. ●Using de-identified client-level information, the Statewide Homeless Assistance Data Online Warehouse.
Homeless Management Information System Donna Curley – HMIS Project Manager.
SSVF Program Launch: Establishing Services in Compliance with Goals and Regulations HMIS: Data Collection and Using Data for Program Monitoring and Decision.
CHAPTER NO 2.  Everything in history which has been planned was done in a highly predictable manner  Whatever you do whether launching a new product,
Supportive Services for Veteran Families (SSVF) Data Bigger Picture Updated 5/22/14.
Preparing Your Data for Analysis September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development Steve Poulin,
Designing the Data Warehouse and Data Mart Methodologies and Techniques.
Supportive Services for Veteran Families (SSVF) Data
Supportive Services for Veteran Families (SSVF) Webinar Series SSVF and the 2014 HMIS Data Standards 9/24/2014 Audio can be accessed through the following.
Supportive Services for Veteran Families (SSVF) Data HMIS Beyond Data Collection Updated 9/14.
6 th Annual Focus Users’ Conference Texas Reporting Presented by: Bethany Heslam.
Online Surveys A Look at Cardiff-TeleForm Denise H. Wells Planning and Research Central Piedmont Community College.
Open and Shared Information System OaSIS. SUNCOM’s Standard Business Process Centralized ordering for the enterprise Maintenance of an enterprise inventory.
HP Project & Portfolio Management Resource Management July 11, 2007 CIMpleBS.com/HP-PPM/Training-Resource Management.pps By Dan Gallagher See NOTES page.
ETL By Dr. Gabriel.
Best Practices for Documenting Software Licensing Compliance Presented By Mike Ludwig and Peggy Fish.
Overview of Mini-Edit and other Tools Access DB Oracle DB You Need to Send Entries From Your Std To the Registry You Need to Get Back Updated Entries From.
SERNEC Image/Metadata Database Goals and Components Steve Baskauf
Coordinated Entry.  Helping people move through the system faster  Sends households to intervention best fit from the start  Reduce new entries into.
1 Homeless Management Information System (HMIS) National Call Training Please Note – The audio portion of this training is available by dialing (800)
Introduction to System Administration Abram L. Hillson, New Jersey HMIS Collaborative Project Manager David Canavan, Canavan Associates Victoria Freeman,
Overview of the Mississippi Legislature’s Efforts to Revitalize Performance Budgeting June 11, 2015.
Database Design - Lecture 1
MDHI Community Meeting on HMIS Priority Communities Initiative May 13 th and 14 th, 2015.
Supportive Services for Veteran Families (SSVF) Data HMIS Lead and Vendor Training Updated 5/22/14.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Documenting the Participation of Fishing Vessel Crew Members in Alaska’s Commercial Fisheries Documenting the Participation of Fishing Vessel Crew Members.
Miscellaneous Excel Combining Excel and Access. – Importing, exporting and linking Parsing and manipulating data. 1.
North Carolina’s New Statewide Road Centerline Data Sarah Wray, GISP, CGCIOTim Sheldon, GISP Spatial Data ManagerBusiness Analyst Engineering Transportation.
1 Integrated Services Program The Virginia Metadata Training Workshop Summer, 2006 Lyle Hornbaker Integrated Services Program
Supportive Services for Veteran Families (SSVF) Data HMIS Lead and Vendor Training Updated 9/14.
A Level ICT Unit Implementing CBIS’s. Support Installing a new system is disruptive and the support program will need to be planned well in advance.
Project Administration Chapter-4. Project Administration Project Administration is the process which involves different kinds of activities of managing.
Building Marketing Databases. In-House or Outside Bureau? Outside Bureau: Outside agency that specializes in designing and developing customized databases.
Engaging Non-HUD Funded Providers September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development Dawn Lee,
Advanced XML Integration September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development David Talbot, Data.
Fred Berry (330) (330) Fax.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
7 Strategies for Extracting, Transforming, and Loading.
New England Region Homeless Management Information System PATH Integration Into HMIS Richard Rankin, Data Remedies, LLC Melinda Bussino, Brattleboro Area.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
Summit County, Ohio Homeless Management Information System.
HMIS Data Standards Client Outcome Measures National Conference Call Sponsored by: Office of Special Needs Assistance Programs (SNAPS) U.S. Department.
TROI – SPC Database Walkthrough Training Presentation Doc. USTP0213 Rev4.
Medical Eligibility Verifications 1. Medical Eligibility: Verifications Introduction After completing this course, you will be able to: Recognize shared.
Road Information System / Road Data Bank 10 April 2013 Lars Bergman M. Sc. In Civil Engineering Long Term Planning Swedish Transport Administration.
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
Session 6: Data Flow, Data Management, and Data Quality.
Tools and Techniques for Ensuring an Accurate HMIS Implementation Matthew D. Simmonds President Simtech Solutions, Inc. October 12, 2012.
Rethinking the Traditional Reporting Model Presented by: Edward Barber Simtech Solutions Inc.
TOPSpro Special Topics I: Database Managemen t. Agenda for Module I: Database Management  TOPSpro Backup/Restore Wizard  TOPS-TOPS Import/Export Wizard.
Distributed Reporting A Cost-Effective Alternative to Data Warehousing Matt Simmonds, Simtech Solutions John Yazwinski, Father Bill’s & MainSpring.
EASTERN PENNSYLVANIA CONTINUUM OF CARE STRATEGIC PLAN FOR COORDINATED ENTRY Status: Approved by Eastern PA CoC Governing Board on October 19, 2015 Revised:
September 18-19, 2006 – Denver, Colorado Sponsored by the U.S. Department of Housing and Urban Development Top Ten Reports: Presenting Data in Useful Formats.
Forum to improve your experience entering data into SRDR 1 SRDR is being developed and maintained by the Brown EPC under contract with the Agency for Healthcare.
Plan for Populating a DW
You Can Do It! Developing a Statewide Annual Report on Homelessness
Miscellaneous Excel Combining Excel and Access.
Electronic Records Management Program
Oil Analysis in the Digital Era
Normalization Referential Integrity
Data Quality By Suparna Kansakar.
Fred Berry (330) (330) Fax.
Lynnette Sieradzki (330) (330) Secretary (330) Fax.
OpenURL: Pointing a Loaded Resolver
HUD’s Coordinated Entry Data & Management Guide
Presentation transcript:

Methods and Techniques for Integration of Small Datasets September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development Deb Little, MISI Loren Hoffmann, Wisconsin Dept. of Commerce

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 2 The Landscape The Ideal All agencies in a continuum use the same HMIS The Reality Some agencies have invested substantial resources in their own system, which finally works “perfectly” Some agencies have multiple funders, some of which may require the use of another system or the reporting of data not collected by the HMIS of the CoC

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 3 Issues to Consider What are the Benefits? For the Community For the Participating Agencies For the Client What is the Goal of Integration? Unduplicated Count Service Coordination/Gaps Analysis Comprehensive Client Information

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 4 Where is the Problem? Why can’t I “just merge” the data?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 5 Data Issues to Consider What data is included? Where is it to be stored? Who has access? Who controls the data? Who owns the data? Who maintains or keeps it in synch?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 6 Data Issues What Data? Each field has its issues. Type - e.g., Name How many fields? Fname, Lname, Mname, suffix What about punctuation such as hyphens How is the data stored DOB vs. Age of client Picklist variations Education - 11 years of education vs. “some High School” How is it stored/coded Male vs. M vs. 1, etc

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 7 Where Is It Stored? Options for storing shared data: On the same server as the HMIS A neutral machine

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 8 Who Has Access? Who establishes the rules about the data? The integrated data has more value than the parts separately Who determines what is published? Who determines what is “cleaned” data vs. “raw” data? Who is able to release the data to another party?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 9 Maintenance As the data needs/rules change over time, what effort is to be made to update historic data? Are all data elements collected to be maintained?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 10 Options Centralized HMIS - used by everyone Dual Entry - agency enters data into multiple systems Those who have achieved either of these don’t need this session Integration Multiple systems maintained Data merged from multiple system (this session)

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 11 Issues to Consider Data elements necessary to achieve the goal? Only the Universal elements? Locally defined data elements? Frequency of data integration? Data Warehousing vs. Data Integration What are the political considerations? Identifying data vs. de-identified Who can view data? Who can release data?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 12 Issues to Consider (Con't) Who will be involved in the planning and decision making process? Where will the data be merged and stored?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 13 Resources to Consider Technical expertise Get them involved early Adequate budget Initial setup and on-going Available time Auditing tools How will we know how good the data are?

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 14 How to Make It Work Identify the appropriate model One way integration – independent agencies send data file for inclusion in central database Two way integration – agencies send data to and receive data from central system Data Warehousing *pros and cons to each method

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 15 Merge - Integration Options Real time Data transferred between two or more systems; each system is refreshed with data from the other Pro: Real time transfer between systems. Con: Very expensive; probably cost prohibitive for most CoCs.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 16 Periodic Integration Periodic transfer of data between two or more systems Pro: Periodic updates. Con: Time consuming; not real time; could be cost prohibitive for many CoCs.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 17 Periodic Merging for Analysis Only Aggregation of data from various system for analytical purposes only. Pro: Least expensive option; can generate unduplicated count. Con: No real time access to data; data is time limited.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 18 Rules Needed Define needed “integration rules” File format required (CSV, XML, other) Data auditing procedures How to handle “bad data”

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 19 More Rules Value Mapping  Determining when values in the database mean the same thing.  Database A: Male=1, Female=2, Transgender=3.  Database B: Female=1, Male =2.  Database C: Female = F, Male = M

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 20 And More Rules Record matching Determine whether a record in two systems are the same Do I add a second record representing the same client? What is the “rule” for determining that the client in two different records is the same client? Is this service already there? Record matching approach will vary depending on reason for merging and what is merged.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 21 Overall Process - Summary Data Conversion:  Create data standard: Per implementation.  Data mapping: Per system. Data Merging:  Export.  Validate.  Transport.  Validate Again  Import. Analysis:  As needed for reporting.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 22 Analysis Integration is not complete when all the data is merged into a single database. Additional tasks:  “Unduplication.”  Use data from multiple agencies to fill in blanks  Handle conflicting information  Extract data.  Distribute data.

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 23 Baltimore Integration Currently: Large metropolitan implementation 90 agencies, programs using designated HMIS 7 agencies utilize the same third party software 1 agency utilizes product developed in-house 1 agency in development of integration “bridge” Issues: Avoid duplicate data entry Establish single reporting tool for “Homeless Stats”

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 24 Wisconsin Integration Currently: Statewide implementation 130 agencies 2-3 agencies need to participate due to funding requirements Issues: Don’t want to do double entry Client confidentiality

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 25 Baltimore (Con’t) Results: Data integration file defined; includes universal, program and continuum defined data elements One way integration model – agencies not using designated HMIS send data in regular intervals to central database. No data returned Data passing quality controls is processed against live database Auditing tools utilized regularly to detect and eliminate duplicate files

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 26 What Is Collected? Only HUD required data is currently collected. Agency provides one client record per client Agency provides one service record per service event (3 services = 3 records) - link on UniqueID field Unduplication based on HMIS algorithm

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 27 Wisconsin Integration Results: Data will be collected periodically for reporting purposes only Data will be housed in a separate database, accessibly only to state system staff System staff will generate reports, distributing only de-identified information

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 28 Summary Integration: Is complicated Will cost $$ Is an ongoing cost (time and money) Can be done If managed properly, can be very cost effective and beneficial

September 13-14, 2005 St. Louis, Missouri Sponsored by the U.S. Department of Housing and Urban Development 29 The Moral of the Story... Anything is Easy, Once You Know How!