Data & interoperability

NOLO maintains records for programs and the organizations that run them, official routes and forms with the agency that owns each one, and guided journeys that connect a person’s situation to the steps and documents involved. Records carry the source they came from, the date that source was last checked, and an evidence label describing what kind of confirmation stands behind them.

The structure is enforced in code rather than by convention. An official route cannot be marked verified without both a named source and a check date — the type system rejects it. A document alternative described as officially accepted has to carry the accepting body, the conditions, an evidence excerpt, and a source URL, or it is not that kind of record. This is why UNKNOWN appears so often: a field with no source behind it has nowhere else to go.

Published coverage is Louisville Metro and the ring counties. It is uneven by category and is described that way on the homepage rather than as a single headline figure. Research inputs extend beyond published coverage; those are working material, not coverage, and are never presented as such.

Journey and route counts can be re-derived from the source repository at any time. If a figure matters to your work, ask for it with the derivation attached rather than taking a number from a slide.

The status labels, the evidence labels, and the rules governing when a record may be published are documented in full on Methodology & trust. Two properties matter most for anyone considering integration: verification is per-field, per-method and per-date rather than a badge on an organization, and conflicting information is preserved rather than overwritten, so a disagreement between two sources stays visible instead of resolving itself silently.

• No public API.The endpoints under /api are internal to the application, are excluded from search indexing, and are not a supported integration surface. Nothing here should be read as an API announcement.
• No published data license.Licensing and machine-readable public access are being formalized. Records derive from many sources with differing terms, and that provenance review has to finish before a license can be stated honestly. Until it does, no open-data license is claimed or implied.
• Not HSDS-conformant today.NOLO’s internal model is compatible in spirit with the Human Services Data Specification, and alignment with HSDS is an intended direction of travel. It has not been implemented or validated, and no conformance claim is being made.
• No bulk download.Extracts are produced by request and by agreement, so that the terms attached to the underlying sources travel with the data.

Researchers, public agencies, health systems, community partners, and civic-technology organizations can write to dustin@nooneleftoutside.org about a structured extract for a defined purpose, interoperability or schema alignment, an integration you are considering, or a correction to a record.

Say what you need the data for and what you would do with it. Requests that would require asserting availability, eligibility, or provider quality will be declined — those claims are outside what this data can support. Organizations considering a broader engagement should start at Work with NOLO.

A wrong or outdated listing is fastest to fix through Report a change, which routes into the same review queue.