welcome everyone we are happy you can join us for this session We will do some more formal introductions in a bit but wanted to first go over some housekeeping items with you
• Webinar will last about 60 minutes
• Access to recorded version
• Participants in ‘listen only’ mode
• For technical issues, request assistance through the Chat box
Webinar Instructions
Presenter
Presentation Notes
Before we begin, I need to cover a few “housekeeping” items. We are recording today’s session, which will last approximately 60 minutes. We will post a link to the recording and the presentation slides to the HUDExchange in the near future. During this training, all participants will be in “listen-only” mode. We encourage you to submit content related questions in the Q&A box, located on the right side of your screen. Please feel free to submit questions at any time. Should you experience any technical difficulties, please request assistance by using the Chat box, and we will respond to them. If you have trouble hearing the audio through your computer speakers, please request assistance using the Chat box or connect your audio using your phone.
• Please submit your content related questions and comments via the chat box. Send to everyone
• Please submit any technical issue related questions via the Chat box. Send to Host
• Host will work directly with you to resolve those issues
Webinar Instructions
Presenter
Presentation Notes
Before we begin, I need to cover a few “housekeeping” items. We are recording today’s session, which will last approximately 60 minutes. We will post a link to the recording and the presentation slides to the HUDExchange in the near future. During this training, all participants will be in “listen-only” mode. We encourage you to submit content related questions in the Q&A box, located on the right side of your screen. Please feel free to submit questions at any time. Should you experience any technical difficulties, please request assistance by using the Chat box, and we will respond to them. If you have trouble hearing the audio through your computer speakers, please request assistance using the Chat box or connect your audio using your phone.
About NHSDC
The National Human Services Data Consortium (NHSDC) is an organization focused on developing effective leadership for the best use of information technology to manage human services. NHSDC provides information, assistance, peer to peer education and lifelong learning to its conference participants, website members and other interested parties in the articulation, planning, implementation and continuous operation of technology initiatives to collect, aggregate, analyze and present information regarding the provision of human services.
NHSDC holds two conferences every year that convene human services administrators primarily working in the homeless services data space together to learn best practices and share knowledge. The past 3 events have been put on with HUD as a co-sponsor. Learn more on our web site www.nhsdc.org.
After this virtual conference is over, NHSDC will be sending out a survey to learn about your experience. Please help us by signing up for emails and participating in the survey!
Presenter
Presentation Notes
Joan This is pretty exciting this is the 1st time NHSDC is doing a live version of their conference. NHSDC has designed this conferences and allowed homeless services specifically around data to come together and share knowledge and best practices Its where you can talk about hmis and data without getting a dazed/confused or about to fall asleep look Hoping you leave this 3 day virtual conference –with some best practice and ideas to try NHSDC surveys
• Review identified common challenges for completing HMIS project set up.
• Provide attendees with key considerations for more advanced HMIS project set up and possible solutions for common challenges.
• Identify the proper set up structure and hierarchy for the HMIS Solution used in your local CoC.
• Learn about resources available for project setup (documentation and subject matter experts).
Learning Objectives
5
Presenter
Presentation Notes
We had a 101 session yesterday where we covered the basics of project set up today we will be taking a deeper dive Take some of those not so straightforward project set up cases and provide guidance Leave you with the resources you are going to need when setting up these projects
Meet the Presenters: Joan Domenech
6
• Program Manager, Corporation for Supportive Housing
• Current areas of work: Unsheltered Homelessness TA,
• Current areas of work: HMIS Data Lab- focused on HMIS Software
Providers, System Administration, HMIS Data Standards, work
with federal partners, and Sage
• Previously: Case Management, Program Supervision, CoC
Leadership
• No single project in HMIS may have more than one project type
• Onboarding procedure can save you many headaches• Communication between CoC, HMIS Lead and Agency
being on boarded is key• Know the reporting requirements• Have a procedure for correcting data involve vendor
when needed• Use available project setup resources
Important Project Setup Reminders
8
Presenter
Presentation Notes
We covered these in project set up 101 but wanted to bring them back as a reminder No single project in HMIS may have more than one project type! Communication is Key Consult with organization administering the project and the CoC Lead Agency regarding appropriate responses for PDDEs. Project Type (data element 2.02) and Funding Sources (data element 2.06) are particularly critical. Know your reporting requirements - Understand the reporting requirements for each project in the HMIS. This is critical! It’s better to take the time to set up a project correctly than have to come back and fix it later. Have a procedure for correcting data - If an issue is identified after project starts operating, work with HMIS vendor to ensure any changes made to set up will not negatively impact historical data. Use available project setup resources.
Project Set Up Resources
9
General Information Manual
Continuum of Care (CoC) Program CoC Program – HMIS Manual
Emergency Solutions Grants Program ESG Program – HMIS Manual
Housing Opportunities for Persons With AIDS HOPWA Program – HMIS Manual
Projects for Assistance in Transition from Homelessness (PATH)
PATH Program - HMIS Manual
Runaway & Homeless Youth RHY Program – HMIS Manual
VA SSVF VA Program – HMIS Manual
FY2020 HMIS Data Standards Interactive Data Standards Tool
HMIS landing page should be bookmarked and be your first stop for all things hmis We aren’t going to go through all of the different funder components and project types. That information is available in project set up 101 or in the following resources. Here are the 6 federal partner programs (CoC, ESG, HOPWA, PATH, RHY & VA) Each of the federal partner programs using HMIS has a specific manual. Currently the manuals describe project set up for the federal partner program and components and what data elements are required to be collected. The manuals for each of the programs can be accessed through these links or in the HUD exchange. Other Program Resources I found helpful: How to determine project type: https://www.hudexchange.info/resources/documents/coc-program-sso-housing-component-decision-tool.pdf show tools, ESG manual, CoC Manual, Webinars, https://www.youtube.com/watch?time_continue=1437&v=EDOWWlebCVY
8 top project set up challenges Project Descriptor Data Elements (PDDEs) Multiple funding sources Ensuring project types are compatible and all applicable data elements are collected. New/demo funding sources (e.g. Youth Homelessness Demo or Pay for Success) Multiple subrecipients Project type changes Project closures/consolidations/transferring Reporting (project-level and system-level) Comparable databases
Project Set Up Challenges: PDDEs
11
PDDE’s ?
PDDE’s are the building blocks of an HMIS.
They enable the HMIS to: • associate client-level records with the various
projects that the client will enroll in
• clearly define the type of project the client is associated with the entire time they received housing or services
• identify which federal partner programs are providing funding to the project
• track bed and unit inventory and other information, by project
Presenter
Presentation Notes
(virtual candy to whoever can type in the chat what pddes stands for) Data collection for projects – we are pretty used to collect data on the persons, well pddes are the data collected on projects. They enable us to (read slide ) They are not always given as much importance as they should setting these up incorrectly will start you of on a unsuccessful road and really hinder you in all your reporting and data accuracy Overview of PDDEs Project Type and Federal Partner Funding Sources are particularly critical as they are the basis for setting up client-level data collection and for reporting. When you create an assessment of any type there is a specific set of questions that you have thought about and that you set up in a specific manner to be able to collect and report on information. And PDDes are set up in a similar way to allow us to identify the organization, specific project and project details to which an individual client record in an HMIS is associated. The project descriptors are generally managed in an HMIS by a system administrator, not a user. Updates to PDDEs They are created at initial new project set-up within the HMIS and are intended to be updated, as needed, on a regular basis by the system administrator, no less than once annually. The HMIS Lead, in consultation with the CoC, should develop a plan and timeline for routine review and updates to PDDEs Usually happens during HIC review I find it easier to update as the changes happen and having specific people doing the changes – you know what they say about to many cooks in the kitchen Relation to reporting Correct use of the 2.02 Project Information and 2.06 Funding Sources data elements will help assure that projects are identified for correct visibility and are able to generate reports required for each of the Federal Partners as reporting parameters will be based off of one or both of these elements 2.01 Organization Information- name of agency/organization 2.02 Project Information - (project ID, project Name, operating start date, operating end date, project type) 2.03 Continuum of Care Information- (CoC code and geocode based on the location in which the project operates) 2.06 Funding Sources -(select appropriate component , grant identifier, Grant Start Date (the first time a CoC grant was provided to this project) grant end date) 2.07 Bed and Unit Inventory Information- only for lodging projects (updated at least annually and when there are significant changes)-
If there are different 'Bed and Unit Inventory' Bed Types for a project i.e. one record has 'Bed Type = Facility Bed', and one record has 'Bed Type = Voucher Beds', should these be two separate projects set up in HMIS?
• Yes • No
Presenter
Presentation Notes
Poll Title: If there are different 'Bed and Unit Inventory' Bed Types for a project i.e. one record has 'Bed Type = Facility Bed', and one record has 'Bed Type = Voucher Beds', should these be two separate projects set up in HMIS? Yes
13
Poll
I have a tenant based rental assistance project that is funded to operate in CoC A but sometimes people are housed in CoC B because of unit availability. Do I need to enter more than one CoCCode in 2.03?
• Yes • No
Presenter
Presentation Notes
Poll Title: I have a tenant based rental assistance project that is funded to operate in CoC A but sometimes people are housed in CoC B because of unit availability. Do I need to enter more than one CoC Code in 2.03? Enter multiple CoC codes only when projects are specifically funded to provide lodging and/or services across a geographic area that includes more than one CoC (i.e. some VA-funded SSVF Projects). In cases where funding spans multiple CoCs, funding recipients are expected by the Federal Partners to participate in the HMIS implementation of each CoC in which they operate projects. This expectation may be satisfied either by direct data entry into each HMIS or by entering data into a single HMIS and providing exports of client-level data to each HMIS, with appropriate agreements in place between the CoCs involved. See the manual for more information. https://www.polleverywhere.com/multiple_choice_polls/N24CpAHMOeK5IVgsDDuzH
14
Poll
Do I need to update Bed and Unit Inventory Information each time there is a change in beds and/or units?
• Yes • No
Presenter
Presentation Notes
Poll Title: Do I need to update Bed and Unit Inventory Information each time there is a change in beds and/or units? No - see next slide for explanation
More on Bed and Unit Inventory
15
Type of “change” Update needed in Bed and Unit Inventory?
ES project originally had 10 units with 20 beds. A large family entered the project and now there are 25 beds in use.
No – this is a minor fluctuation in project operations.
A fire happened in the PSH apartment building and instead of 20 units, the building only has 15 habitable units. Due to severity of damage, the units won’t be available for occupancy for several months.
Yes – create an “end date” for the 20 units of PSH as of the date the units went offline. Create a “start date” for the 15 units still online as of the same date. Once the units are repaired and available for occupancy, a new inventory record should be created.
A PSH project with 15 beds/units had a portion of its funding reallocated in the CoC process and now only has funding to operate 5 units of PSH.
Yes – this is a permanent funding change and the 15 beds/unit should have an inventory end date added. The 5 remaining units will have a new start date added.
Presenter
Presentation Notes
Q: Do I need to update Bed and Unit Inventory Information each time there is a change in beds and/or units? A: No. The Bed and Unit Inventory Information only needs to be updated if there are significant changes in project operations.
• A single project may have more than one funder.• Verify that funding sources can be combined in a single project using
the project set up tool.• Examples of when you cannot combine multiple funding sources in one
project:• Street Outreach, Prevention, & RRH funded by multiple ESG
jurisdictions• UNLESS, your HMIS has the functionality to:Separate the clients served in a combined project for each ESG jurisdiction; andProduce a valid CAPER for each ESG jurisdiction.
Project Setup Challenge: Multiple Funding Sources
16
Presenter
Presentation Notes
The project setup tool is a guide, your HMIS may have additional functionality to enable reporting by funding source.
How to set up a project: Explore project set up tool
17
Presenter
Presentation Notes
Purpose of the tool: to provide guidance about how that project setup impacts data collection requirements https://www.hudexchange.info/resource/4898/hmis-project-set-up-tool/ The updated Homeless Management Information System (HMIS) Project Set Up Tool provides a general framework to support project setup in HMIS by system administrators. It assists system administrators in ensuring that all HMIS participating projects are set up using the appropriate HMIS project types and are collecting the required data elements. Accurate setup is critical for enabling your HMIS to generate System Performance Measures and project-level reporting to federal funders. Using the HMIS Project Set Up Tool, system administrators will be able to enter up to three federal funding sources for a project to determine if they are compatible and are able to be used in a single project in HMIS. If the sources are not labeled “inconsistent program components,” they may be joined as a single project. The tool will indicate which HMIS project type should be selected in the HMIS as well as show each of the required HMIS data elements for the funding sources selected. If you believe your system has the ability to allow the selected funding sources to be combined because of specialized functionality within the software, despite any warnings by the tool, please check with your HMIS Vendor/Provider before making any changes.
Project Set Up Challenge: Multiple Funding Sources
Some projects may receive funds from multiple funding sources for different eligible activities. For example, a project may receive a grant for residential operations/leasing costs and another grant for services. HMIS Lead has two options here:
Option 1: Create one project in the HMIS that both the housing provider and the service provider jointly share and record data, or
Option 2: Create two separate projects, one for the housing provider and another for the service provider
18
Presenter
Presentation Notes
It’s important to note the difference between option 1 and 2. In order for Option 1 to work, both the housing and service provider must openly share and record data. This is sometimes not possible. For example, if the residential subsidy were PSH and the services were provided through a HOPWA grant, the service provider may ‘close off’ the data related to the HIV services provided to the project participant. In this case, the data is not shared, and Option 2 should be used and the SSO project will be affiliated with the residential project.
Setting up a project with multiple funding sources
If Option 1 is chosen:The Project Type (data element 2.02) will be the appropriate residential project type (e.g., TH, PSH, etc.), and the Federal Partner Funding Sources(data element 2.6) will identify both funding sources / component types for the project
If Option 2 is chosen:The housing project will have an appropriate residential Project TypeThe services project will have a Project Type of ‘Services Only.’ Service Only projects can then be affiliated with the residential project and data can be linked.
Youth Homelessness Demonstration ProgramYHDP funding can be used in innovative ways; take care to ensure accurate project setup by project typeYHDP Communities are encouraged to collect Runaway Homeless Youth Program (RHY) data elements in addition to CoC Program data elements.YHDP Communities are required to submit additional data in their Annual Performance Reports
Examples – housing navigator projects that may be services only projects but also have rental assistance funding. Or, diversion projects – could be SSO or could be RRH. Host Homes are not an HMIS defined project type – rather, use the program model and funding component to best determine the appropriate HMIS project type. YHDP Projects can serve category 2 or 3 of homeless definition, ensure that CLS is being collected Review RHY Program manual for additional guidance about the RHY data elements Optional - Live demo of Supplemental Reporting Tool and YHDP Dashboards to stress importance of accurate project data
21
Only one CE project in
HMIS
No CE project in
HMIS
Single CE project
accessible by 1 or more
partners
Single CE project
accessible by 1 or more
partners
Single CE project
accessible by 1 or more
partners
Multiple CE projects set
up for different sites or
phases of the process
“Catch All” CE project setup to
supplement existing
data collection
TH
ES
SO
RRH
PSH
TH
ES
SO
RRH
PSH
TH
ES
SO
RRH
PSH
TH
ES
SO
RRH
PSH
Project Setup Challenge: Coordinated Entry
Presenter
Presentation Notes
Reminder that CE Data Collection implementation deadline pushed back to October 2020. Still have time to refine and improve setup and data collection for CE projects in HMIS. There are a multitude of ways to set up CE projects in HMIS. These are EXAMPLES of setups that fall along the spectrum , but there are undoubtedly more that would work in different CoCs with different realities. Create yours based on what you HAVE and what you WANT. HUD wants project setup to be flexible and to accommodate your system design, your privacy and security needs, and the reality of your HMIS-participation, especially among front-door projects like street outreach and shelters. Additional resources & guidance: Additional CE session tomorrow at 10:30am w/Abby. HMIS Leads can review CE Office hours call notes and recordings See the HUD Exchange Submit AAQs for specific questions
If setting up multiple subrecipients ensure:• HMIS Privacy settings allow recipient (or sys admin) to generate
reports across all projects.
Project Setup Challenge: Multiple Subrecipients
22
Presenter
Presentation Notes
- specific examples include CE projects that operate across multiple projects. Or, PH projects with subrecipients. Need to be able to run aggregate reports across projects to de-duplicate within the system to ensure accurate reporting.
Project Setup Challenge: Project Type Changes
23
• Sometimes Field Offices permit project type changes to occur through grant amendments.
• Points to consider before changing a project type:• Do you (or recipient) have appropriate documentation from the HUD Field Office
permitting this change? It is important to maintain documentation of any project type changes.
• Determine the most appropriate time to change the project type. Ideally, if a project type change occurs, it happens at the end of an operating year so as to not have two different project types operating during the same reporting year.
• Changing a project type mid-year may result in some data not being collected (i.e. a TH project changing to RRH will not have housing move-in date)
Presenter
Presentation Notes
Project type data from esnaps is provided to Sage. Sage validates all uploaded reports to the data provided by esnaps. If you have a project that changes it type from what was awarded in esnaps, you will get an error. In order to change anything in Sage, you will be required to provide this documentation.
• Consolidating projects in HMIS• Beginning in the 2018 CoC Program Competition, grant recipients
had the option to consolidate up to 4 eligible renewal projects into one grant.
HUD released A Blueprint for Understanding How They Work in early 2019.HUD will soon release additional guidance for project consolidations, closures, and transfers.
• There are several options for handling grants that are consolidated or eliminated but the preferred method to use in the HMIS is to administratively move the entire client record from the old project to the new project.
• Exiting and then re-entering a client should only occur in very limited situations.
• The method used must be determined by the HMIS System Administrator and the recipient entities involved and must be decided prior to the end of an operating year.
25
Project Setup Challenge: Consolidation
Option 1: Administratively move complete records from one project to another in HMIS
Using this method, a client record is “selected” by the system administrator and “moved” to a different project. By doing this all of the history of the client in a project and the integrity of the record remain in-tact.
Identify the project in HMIS that is to be used for the surviving grant or where recipients of a grant that has terminated will now be participating in. This project may be an existing project in the HMIS or a totally new project that multiple providers will access for some consolidations.
26
Project Setup Challenge: Consolidation Option 1
Presenter
Presentation Notes
Go over consolidation Option 1 The process: Identify the project in HMIS that is to be used for the surviving grant or where recipients of a grant that has terminated will now be participating in. This project may be an existing project in the HMIS or a totally new project that multiple providers will access for some consolidations. At the end of the operating year of the terminating grant or closing project, generate the APR for the operating year from the HMIS (prior to moving records). Thoroughly review the APR generated and upload the CSV into Sage to ensure there are no errors. All information needed for reporting on clients for grants other than HUD should also be extracted prior to the change. The system administrator will then move the project record of all stayers into the surviving grant’s project. No data entry is required. The system administrators must then close the terminated project in HMIS, following all protocols of the HMIS system, and being sure to record an operating end date in 2.02 Project Information for the terminating project, record the inventory end date(s) in the terminating project and adjust the data 2.07 the Bed and Unit Inventory for the surviving grant’s project. Managing data entry: On the day after the operating year of the terminating grant has ended, data for all new clients must be entered into the surviving grant’s project. Until the records for stayers have been moved to the surviving grant’s project, all updates must continue to be made in the client record in the terminating project.
Option 2: Reassign the project to the new recipient in HMISUsing this method, all client records of the project are given to the surviving project simply by reassigning the project to another organization in the HMIS.
Project Setup Challenge: Consolidation Option 2
27
Presenter
Presentation Notes
If your HMIS software does not have the functionality to move client records or the cost of moving the records is prohibitive, you may also simply change the relevant Project Descriptor Data Elements (PDDEs) to reassign the project to the new provider. This method requires that the organization operating the current housing must consent to the record transfer. The CoC’s HMIS Privacy and Security Policies must not be violated and may require an update to allow for transfers. Records may be edited to remove data other than what is required to be collected by the HMIS Data Standards (e.g. case notes, encounter notes, treatment information, etc.) to maintain client confidentiality, should the organization elect to do so. It is important to note that once the records move to the new recipient there might not be access to those records by the organization which originally collected the information. All information needed for reporting on clients for grants other than HUD should be extracted prior to the change. If the original recipient needs to maintain access to the historical data, involved providers and the HMIS Lead should work together to develop a plan for providing this data to the original grant recipient as needed (e.g. read only access to historical project and client records or changing data sharing settings). Depending on who has access to the client’s record in the project of the surviving grant client consent may require it to be updated.
Project Setup Challenge: Consolidation Option 2
28
The System Administrator, on the day after the end of the operating year, will change the following information in the HMIS:
• PDDE 2.01 Organization Information – Reassign the project to the organization operating the target project by changing the Organization ID and Name in the existing project.
• PDDE 2.02 Project Information –Do not change the Project ID or the project type. Edit the project name, housing type, and target population as needed.
• PDDE 2.03 Continuum of Care Information – Update the CoC information, adding geocode and address information as needed.
• PDDE 2.06 Funding Sources – Add or edit new grant identifiers and start/end dates. Incorporate the funders associated with the closing project into the new target project.
• PDDE 2.07 Bed and Unit Inventory Information – Update bed and unit inventory as of the date the consolidation or transfer occurs. Remember to update this in both the terminated project(s) and new project.
Presenter
Presentation Notes
If your HMIS software does not have the functionality to move client records or the cost of moving the records is prohibitive, you may also simply change the relevant Project Descriptor Data Elements (PDDEs) to reassign the project to the new provider. This method requires that the organization operating the current housing must consent to the record transfer. The CoC’s HMIS Privacy and Security Policies must not be violated and may require an update to allow for transfers. Records may be edited to remove data other than what is required to be collected by the HMIS Data Standards (e.g. case notes, encounter notes, treatment information, etc.) to maintain client confidentiality, should the organization elect to do so. It is important to note that once the records move to the new recipient there might not be access to those records by the organization which originally collected the information. All information needed for reporting on clients for grants other than HUD should be extracted prior to the change. If the original recipient needs to maintain access to the historical data, involved providers and the HMIS Lead should work together to develop a plan for providing this data to the original grant recipient as needed (e.g. read only access to historical project and client records or changing data sharing settings). Depending on who has access to the client’s record in the project of the surviving grant client consent may require it to be updated.
Option 3: Exit client from one PH project and start in another PH projectUsing this method, all historic information about the client remains in the original project and the surviving project will document the information on the client as of the date of project start. This option will result in clients appearing in reporting as not literally homeless at project start, not chronically homeless, and loss of any positive income outcomes obtained in the first project. Record a client exit in the original project as the date of move out. Select “Permanent housing (other than RRH) for formerly homeless persons” as the destination.Record a project start date in the new project the day after the exit from the old project. Remember to enter the housing move-in date.Record all data elements as they are on the date of project start in the targeted project.
Project Setup Challenge: Consolidation Option 3
29
Presenter
Presentation Notes
***When a client has been exited and entered into a new project, the Additional Information form in every APR following the move must indicate to HUD that this person(s) has moved from one PSH or RRH project to another due to the specifics of the situation. Documentation of homelessness should be transferred from the original project to the target project There are cases, such as when another PH project is determined to better serve a client, in which an exit in one project and a start in another is unavoidable, but for purposes of closing or transferring whole projects the exit/start method should be a last resort due to the reporting concerns it produces. When a client has been exited and entered into a new project, the Additional Information form in every APR following the move must indicate to HUD that this person(s) has moved from one PSH or RRH project to another due to the specifics of the situation. Documentation of homelessness should be transferred from the original project to the target project. If the target project is required to serve chronically homeless persons, documentation of chronic homelessness must move from the original project to the target project. Documentation of disability must be generated again by the target project to ensure the client meets the requirements of the project they are moving to.
Option 4: Leave existing project in HMIS
There is no requirement that the projects in HMIS change.
Project Setup Challenge: Consolidation Option 4
30
Presenter
Presentation Notes
If a single organization is operating projects where a grant consolidation occurs, The recipient organization can continue to record client data in the existing HMIS projects and for reporting, generate the required report (e.g. an APR) across all of the projects that have been consolidated into a single grant, into one CSV APR Report. Selecting all of the projects for the single CSV APR will ensure de-duplication and be representative of all clients served by the grant. If the consolidation of grants involves multiple organizations, the projects still do not have to be consolidated in HMIS. Generate a single report across all of the relevant projects funded by the grant. HMIS sharing/security settings and policy may need to be reviewed/updated so that the recipient can generate the report across multiple agencies, or the HMIS System Administrator may be required to generate the report.
• It’s best to identify problems or issues before the project begins operating and reports are due.
• Project type in HMIS must align with reporting requirements. • Sage will not accept a CSV APR/CAPER upload for a project different
than the project type funded.• RHY and SSVF Reporting Repositories rely on project type for upload.• System Performance Measures and LSA rely on accurate project
types.• LSA in particular relies heavily on PDDEs
• Incorrect project typing may result in missed data collection requirements.
Project Setup Challenge: HMIS Reporting
31
Presenter
Presentation Notes
Relation to reporting Correct project set up will help assure that you are able to generate reports required for each of the Federal Partners Benefits of accurate data , and being to able to use existing reports like Lsa/stella P to its max
A comparable database is a relational database that meets• all HMIS Data Standards; and• the minimum standards of HMIS privacy and security requirements,
including HUD’s most recent reporting standards and comma separated value (CSV) format specifications.
Project Setup Challenge: Comparable Databases
32
Presenter
Presentation Notes
Overview of comparable databases What are the requirements? How to know if it is a comparable database Where people go wrong
Discussion: Identifying and correcting project set up issues
33
• What are some project set up checks you can do proactively so you are not waiting for errors in one of the required reports to know you have set up issues?
Presenter
Presentation Notes
Instructions: Use the chat in Adobe Connect for participants to interact e.g. do you look at project list regularly? Does someone else review too? Are you comparing inventory year over year? Do changes make sense?
Don’t be afraid to STOP and Ask A Question
Resources
34
To submit a question to the HMIS AAQ portal:Select “HMIS: Homeless Management Information Systems” in the “My question is related to” drop down list on Step 2 of the question submission process.
Presenter
Presentation Notes
Know who to contact with questions Subscribe to hud mailing list Takeaway how to interact - HUD data SME - you should go to to talk about those nuances submit an AAQ, indicate that their question is related to HMIS, and then the AAQ desk can triage the question to the particular federal partner’s SME
Questions?
35
Reminder: HUD is offering a Certificate-of-Completion for completing four of the seven sessions within the HMIS Foundations track.
To earn credit for completion of this session, please make sure you included your contact details when the session began.
HUD Certificate of Completion
36
Presenter
Presentation Notes
HUD is offering a Certificate-of-Completion for individuals that attend a short topic track on HMIS Foundations. The attendee will need to complete four of the seven sessions being offered in this track. Providing this certificate of completion is one way to boost professionalism in the field. Sessions: HMIS Project Set-up 101 (Monday 12pm ET) Implementing Effective Contract Negotiation and Relationship Management Strategies 101 (Monday 1:30pm ET) HMIS Governance 101 (Tuesday 10:30am ET) HMIS Project Set-up 201 (Tuesday 12:00pm ET) HMIS Project Monitoring (Tuesday 1:30pm ET) Achieving a Quality and Stable HMIS Staffing Pattern (Wednesday 12:00pm) HMIS Lead Monitoring (Wednesday 3:00pm ET)
