HMIS Newsletter: June 2025


 

Welcome to your Community Poll

Complete the Poll:

June 3rd was World Bicycle Day. What’s your favorite way to ride?

 Bike Poll

 

Results from last month’s poll: Thanks for taking the time to respond! Which do you love more as the days get longer…

🚗 35% chose - Road Trips and Windows Down, Music Up

🏖️ 25% chose - Sunny Beach Days and Summer Vibes

🌸 20% chose - Fresh Spring Blooms and Cool Breezes

🥶 15% chose - Honestly, Just Give Me A/C and Iced Coffee

🍋 5% chose - Backyard BBQs and Lemonade Stands

 


 

Upcoming Events

 

Coordinated Entry Monthly Assessor Credential Training (ACT): July 9th, 9:30 am

Register here

Users must attend an ACT training before they gain assessor access in the HMIS. 

 

[Q3] Quarterly HMIS Agency Leads and CE Trainers Meeting (Security Officers Invited): July 16th, 10 - 11:30 am

Register here

 As the Technical Administrator (Agency Lead) and/or CE Trainer for your agency, please join us to stay apprised of all the HMIS happenings within your community! Friendly reminder that attendance at this meeting is required. Security Officers are asked to join us for this July meeting to hear specific reminders about their role.

 


 

Clarity Human Services: June Feature Updates

 

Update:

Federally Recognized Tribes List

The core field Federally Recognized Tribes (federally_recognized_tribe) is updated to reflect changes noted in the 12/11/2024 Federal Register. To view the updates, click here.

Federally recognized tribes



Update: Update Offline/Inactive Status Functionality

The Automatic Offline Status functionality has been updated to take into account future pending occupancies. To view more information click here.

Offline Status

 


 

Proper De-Identification Process

 

Consent Refused Data Entry

Clients must give written consent to have any personal information stored in HMIS. Personal information continues to include not just names, exact dates of birth, and partial or full social security numbers, but also includes information that may not be identifying in and of itself, but when combined with other non-identifying information, may unintentionally lead to the identification of that person.

 

Important ❗

Providers serving domestic violence clients must NOT enter client personal information in Clarity Human Services. The following protocol must be used with all domestic violence clients. In addition, providers serving unaccompanied minors under 13 or clients with HIV/AIDS are subject to additional security restrictions. Please consult your HMIS Agency Lead for details.

 

What To Do when a Client Refuses Consent

In the event that a client refuses consent to have personal information stored in HMIS, the client’s consent should be entered as “No.” You can find the consent section, by clicking on the green Client Privacy Shield Icon.


 

Once the user has marked consent as no, then the consent refused/de-identified data entry protocol should be followed as described below. If one member of a household refuses consent, de-identified data entry protocol should be used for all members even if others are willing to consent.

 

Consent Refused Data Entry Protocol:

  1. From the search screen, click “Add Client”
  2. Click on the “consent refused” slider button to the right of the profile. The SSN, Name and Month and Day of Birth fields will be automatically filled with non-identifying values like in the clip below. 

 

        3. For the Date of Birth, you will see that 01/01/____ appears.

a.) Enter a year that is one or two years older or younger (for example, if the client's actual date of birth is 03/16/1980, enter 1982 or 1979 in the Date of Birth field).

b.) When you enter the year, an age appears.

c.) Make sure the age fits the appropriate age category for the client. If not, adjust the year.

 

        4. Enter Gender, Race, Ethnicity and Veteran status with real data (if it will not identify the client in any way)

        5. Leave Middle Name and Suffix blank

        6. Click on Add Record. The client ID that is generated when the record is saved will automatically replace the first name. The de-identified record should look like this after you save it:

 

 

Important Reminders

If a client profile has already been created before the Release of Information is refused, please contact the Help Desk at kcsupport@bitfocus.com to have the record de-identified. There should not be any reason to create a de-identified record manually. However if you do, make sure it contains the de-identified values in the example above, including replacing the first name value with the Client ID number.

 


 

Bitfocus is Hiring!

 

🌟 Join the Bitfocus team 🌟 

Bitfocus is hiring for multiple positions! Check out our job postings here 🔍