Why Your HMIS Compliance Problem and Your Coordinated Entry Problem Are the Same Problem
Written for HMIS system administrators. It works at the level you work at, inside named data elements and named report tables, because that is where the thing it describes was decided.
A director of housing services at a homeless services nonprofit got on a call with us ahead of a scheduled demo and, before anyone asked her a question, named three things that were wrong.
Her staff document the same client conversation twice on the same afternoon, once into HMIS and once into a separate electronic health record, because the interface between the two is still being built. Her data quality problems never quite go away. And there is a cap on how many of her people can hold an HMIS login at all, because the lead agency that owns the HMIS pays for every seat.
This is one organization, so read her as an illustration rather than a measurement. Her role and her sector are the only details given here, and her employer is deliberately not named. The shape will be familiar anyway.
Inside her building those three complaints belong to three different people. The double documentation is an integration project on a vendor timeline. The data quality lands on whoever owns reporting. The login cap is a budget conversation with the agency above her. Three owners, and none of them can close another one's ticket.
All three trace back to one paragraph of federal regulation that anyone can open. Two of them reach it directly. The first reaches it by one more step, and that step is set out below rather than skipped over, because it is the part a reader who does this work will test first. We have argued before that most housing systems were built to report rather than to run. That is the architecture. The seam itself is narrower, and narrow enough to point at.
One Regulation Hands Out Two Jobs and Connects Neither
The duties of a Continuum of Care are set out by HUD in title 24 of the Code of Federal Regulations, part 578. Section 578.7, "Responsibilities of the Continuum of Care," is the one that lists what a Continuum has to do, and it hands out both of the jobs behind those three complaints a few lines apart.
Under the heading "Operate the Continuum of Care," paragraph (a)(8) requires the Continuum, "In consultation with recipients of Emergency Solutions Grants program funds within the geographic area, establish and operate either a centralized or coordinated assessment system that provides an initial, comprehensive assessment of the needs of individuals and families for housing and services." Two sentences follow, one requiring a policy for people fleeing domestic violence and one saying the system "must comply with any requirements established by HUD by Notice." Three sentences in total. No data system is named, no accountable party is named, and no data quality plan is required.
Then paragraph (b), headed "Designating and operating an HMIS," gives the same Continuum five numbered duties. Designate a single Homeless Management Information System for the geographic area. Designate an eligible applicant to manage it, known as the HMIS Lead. "Review, revise, and approve a privacy plan, security plan, and data quality plan for the HMIS." Ensure consistent participation by recipients and subrecipients. Ensure the HMIS is administered in compliance with HUD's requirements.
One job arrives with a named system, a named owner and a required data quality plan. The other arrives as a policy obligation and a pointer to a Notice that had not been issued yet. Her org chart inherited that shape, and so did her budget lines, and so did the category of software she gets to choose between, which is why a reporting module and a case management module still arrive on separate quotes. Somebody in her building owns her data quality plan because paragraph (b) says somebody must. Nobody owns the coordinated entry equivalent, because paragraph (a)(8) never asked for one.
Why the Same Conversation Gets Typed Twice
Her first complaint has two causes, one behind the other, and they need keeping apart.
Step one, and it is the one her staff would name. No interface exists between the HMIS and the electronic health record, so the conversation gets typed into both. The missing interface is the immediate cause. Nothing in HUD's schema types anything twice, and a piece that claimed otherwise would be wrong on the mechanics.
Step two is why that interface is still not built. This is the part that is decided in a federal document, and it is a weaker claim than saying the regulation caused the double entry. It is also the one that survives being checked. Open the FY 2026 HMIS Data Dictionary and put two kinds of element side by side.
Element 4.02, Income and Sources, runs to 18 fields. Fields 3 through 17 each name an income source, from earned income and unemployment insurance through SSI, SSDI, TANF, child support and a catch-all "Other source," and every one of them carries a dependent field for a monthly dollar amount. Health Insurance has 12 fields and names each insurance type. Non-Cash Benefits has 8. The fields and their meanings are fixed in all three, with local renaming allowed on a handful of response labels and nothing else, because all three feed named tables on the annual report.
Element 4.19, Coordinated Entry Assessment, has seven fields, and the dictionary is explicit about which of them count: "Fields 1-4 and field 7 will be required for reporting purposes. Fields 5 & 6 are included as placeholders for communities who currently do, or want to in the future, collect CE Assessment questions, answers, and results in HMIS." Fields 5 and 6 are the assessment itself, the questions her staff ask and the score that decides who gets housed first. On the structure of those, the dictionary says there is "no specified structure or format for an assessment."
Fields counted directly from the FY 2026 HMIS Data Dictionary, U.S. Department of Housing and Urban Development. The 4.19 count is the five fields the dictionary states are "required for reporting purposes"; the assessment questions, answers and score sit in two further fields the dictionary calls placeholders.
Five fields record that an assessment happened, which is what a report needs. The content of it is a container, and a container gets filled locally.
The assessment content therefore has no schema, and it ends up wherever each community put it. One of the places it lives in her organization is the electronic health record, which knows what a clinician needs and nothing about element 4.19. A vendor building faithfully to this specification produces a validated, dollar-precise form for 4.02 and a configurable container for 4.19.
That is what step two comes to. An interface between two specified elements is a mapping between named fields, and somebody can quote a price for it. An interface into a container is a mapping that has to be invented for every community that filled the container differently, and it is priced per implementation, scoped late and moved down a roadmap when something dated arrives ahead of it. Element 4.19 did not put her staff in front of two screens. It is the reason the thing that would take them off two screens has been coming for a while.
Why Data Quality Problems Outlive Every Clean-Up
Six of the 70 tables in the FY 2026 CoC APR and ESG CAPER programming specifications grade data quality, Q6a through Q6f. One of them measures nothing but delay. Q6e is titled "Data Quality: Timeliness," and its entire structure is six buckets of elapsed days, counted separately for project start records and project exit records. HUD built a ruler for the distance between the work and the record.
Row labels reproduced from table Q6e in the HMIS Programming Specifications for the CoC APR and ESG CAPER, FY 2026, U.S. Department of Housing and Urban Development. Counted separately for project start records and project exit records. The table carries no published figures.
Her third complaint puts that ruler under load. A worker without an HMIS login cannot record anything at the moment the work happens, so what happens instead is a note on paper or in the health record, entered into HMIS later by whoever holds a login. That interval is what Q6e counts. A licensing decision made one level above her surfaces in a federal data quality table as her finding, and by the time the annual report hands that finding back, the window for acting on it closed months earlier.
The Annual Report Does Not Look at Coordinated Entry at All
Coordinated entry is carved out of that report entirely. The specifications state that they are "applicable to all project types except Coordinated Entry projects," and that APRs for those projects "must be generated using the HMIS Programming Specifications for Coordinated Entry APR (CE APR)." Two reports, two universes, and no table anywhere in the CoC APR that looks at coordinated entry.
Counted row by row from the Table of Questions in the HMIS Programming Specifications for the CoC APR and ESG CAPER, FY 2026, U.S. Department of Housing and Urban Development. Coordinated entry projects are excluded from this report and covered by a separate Coordinated Entry APR.
So the assessment work her staff repeat into two systems every afternoon is invisible to the report her funding depends on. Nothing in the reporting architecture requires the prioritization list and the enrollment record to be one record, so in most implementations they are two, graded separately and owned separately. The household pays the difference in repeated intakes.
Her three complaints have three owners and one origin. The first reaches that origin through the missing interface, as the two steps above set out. The other two reach it directly.
The Strongest Case for Three Separate Problems
A CoC lead could take that list apart item by item, and would not be wrong to. The health record interface is an integration project on a vendor roadmap, so buy the connector or wait for it. Data quality is a training and monitoring discipline, and HUD requires a data quality plan precisely so that somebody owns it. The login cap is a line in the lead agency's budget, and no architecture makes a seat free.
Behind all three sits the sturdier version of the same argument. HUD's data standards are externally imposed, and no system design makes 4.02 optional or shortens the 60-day window around an enrollment anniversary. The APR is a federal report with a federal deadline and a submission path through Sage. Coordinated entry is governed by a separate HUD Notice, runs on an assessment tool her community chose, and follows prioritization policy her CoC board votes on. Different governing documents, different accountable bodies, different failure modes. On that reading, a vendor claiming one architecture fixes all three is selling a consolidation she pays for twice, once in license and once in migration.
Half of that is correct, and it is the half worth conceding first. The volume of data HUD asks for is fixed, and a better-built system does not remove a single field.
Where HUD's Own Documents Undercut the Separation
HUD never asked the reporting system to run coordinated entry. Its Coordinated Entry Management and Data Guide quotes the Coordinated Entry Notice at length, and the passage is worth having whole rather than in the convenient half.
"HUD does not require CoCs to use their HMIS as part of their coordinated entry process. However, many communities recognize the benefit of using this option to complement their mandatory HMIS recordkeeping and have incorporated HMIS into their coordinated entry. HUD encourages communities to use HMIS, but recognizes that other systems might be better or more quickly able to meet the community's coordinated entry needs. HUD expects that, even when using a data management system other than HMIS, the CoC works toward being able to use HMIS for coordinated entry or toward having a system that seamlessly shares data with HMIS."
The last sentence decides the argument and is the one usually left off. HUD's stated expectation is a second system that shares its data with HMIS seamlessly, which describes the interface her organization is waiting on. She is already living inside the arrangement HUD sanctioned. What HUD never supplied was a schema for the data to travel over, so the crossing gets built by hand, one integration project at a time.
The schema's own history shows which parts were load-bearing. The element that would hold her coordinated entry assessment was retired and brought back inside two months. The FY 2024 HMIS Data Standards Manual, released in May 2023, lists 4.19 Coordinated Entry Assessment and 4.20 Coordinated Entry Event as retired, with 4.21 Coordinated Entry Activity introduced in their place. The July 2023 revision then records "Remove 4.21 CE Activity" and "Reinstate previously removed 4.19 Coordinated Entry Assessment and 4.20 Coordinated Entry Event data elements." By FY 2026, element number 4.21 has been given to Sex. Over the same stretch the Universal Data Elements were renumbered, combined and reworded, and none was removed and then reinstated. Stability follows what feeds the report to Congress, which HUD says is what those elements are for: "The UDEs are the foundation on which the Longitudinal System Analysis (LSA) is developed. The LSA informs the Annual Homeless Assessment Report (AHAR), which provides Congress with national estimates of the current state of homelessness across the United States and the use of homeless assistance programs."
The regulation sets when data must be recorded and never when it must be discovered. The dictionary requires an annual assessment with an Information Date "no more than 30 days before or after the anniversary of the Head of Household's Project Start Date," and it requires a fresh record each year: "Regardless of whether the responses have changed since project start or the previous annual assessment, a new record must be created for each subsequent annual assessment such that it is possible to view a history, by date, of the values for each data element." It also requires the assessment to update "both the Head of Household's record and any other household members at the same time." Nothing in it requires anyone to find out the anniversary is coming. Whichever system holds the enrollment decides that, and that is where the shape of her burden gets chosen: continuous, or annual and all at once.
What Changes When the Build Order Is Reversed
Take those three complaints again, in her order, and put the operational layer underneath the reporting layer instead of bolting it on top.
The double documentation. If the assessment holds its questions, answers and score as structured fields, which is exactly what element 4.19 declined to specify, then those fields exist to be read by anything else that needs them. The five reportable fields of 4.19 fall out of records already being kept. This does not build her interface for her, and nothing here should be read as saying it does. What it changes is the price of building one, because the mapping is then between two sets of named fields rather than into a container somebody has to survey first.
The data quality. If a case manager can record at the moment of the conversation, on a phone, in a shelter, the interval Q6e measures collapses toward zero without anybody running a clean-up project. A checked field at entry is worth more than a data quality plan enforced at submission, because one of them happens while the client is still in the room.
The login cap. This one does not disappear and should not be promised away. The seat count belongs to the lead agency and stays there. What changes is which work needs a seat. If the operational record lives alongside the HMIS rather than inside it, holding the tasks, the referrals and the documents, the people doing the work sit in a system they are licensed for and the HMIS receives clean output from it.
That reversed order is what CUBE84 builds. Housing360 is the HMIS, and it appears on HUD's HMIS vendor report validation list for FY 2026 at software version 2.0, with an APR CSV validation dated 12 August 2026. Care360 carries the coordinated entry work alongside it. The argument above holds whether or not either name reaches a purchase order.
Four questions will tell you which order your own systems were built in. None of them needs a vendor in the room.
Does anything raise an enrollment anniversary before the window opens, or does a report find it after the window closes?
When a referral goes out, does the receiving provider inherit the assessment, or re-ask it?
Is your coordinated entry score a queryable field, or a value inside a document?
Does your data quality plan describe checks at entry, or checks before submission?
None of this removes a HUD requirement. It moves the moment of truth from the reporting cycle to the day the work happens, which turns audit exposure into something a team can still act on.
The webinar named the architecture. Section 578.7 shows the paragraph where it was chosen, and the director with three complaints is living in all three of its consequences at once.
Sources
24 CFR 578.7, Responsibilities of the Continuum of Care (eCFR, current text). Paragraph (a)(8) on the centralized or coordinated assessment system, and paragraph (b)'s five HMIS duties.
FY 2026 HMIS Data Dictionary, U.S. Department of Housing and Urban Development. Field counts for elements 4.02, 4.03, 4.04 and 4.19, the placeholder language in 4.19, and the annual assessment requirements.
HMIS Programming Specifications: CoC APR and ESG CAPER, FY 2026, HUD. The 70-row Table of Questions, the six Q6 data quality tables including Q6e timeliness, and the exclusion of coordinated entry projects.
FY 2024 HMIS Data Standards Manual, HUD, version 1.7. The revision history recording 4.21 Coordinated Entry Activity added and then removed with 4.19 and 4.20 reinstated, and the statement that the Universal Data Elements are the foundation of the Longitudinal System Analysis.
Coordinated Entry Management and Data Guide, HUD. Quoting the Coordinated Entry Notice on whether a CoC must use its HMIS for coordinated entry.
HMIS Vendor Report Validation, HUD Exchange. The FY 2026 row for CUBE84 / Housing360 / software version 2.0, APR CSV, validated 12 August 2026.
The three complaints that open this article come from one CUBE84 outbound conversation with a director of housing services at a homeless services nonprofit, recorded before a scheduled demo. The organization is not named and there is no link, so this source cannot be audited by a reader. That is a deliberate choice and it is the weakest evidence in the piece.
