Skip to content
    Iterum Systems

    Digital Health

    Active Deployment

    Lantern

    A mobile resource platform that helps people in crisis find services they can reach now.

    Publicly functioning project

    Illustrative scenario using the real project. Listings do not establish service availability.

    Discuss one operational problemEvidence classifications & examplesRelated paid services
    Resource NavigationBehavioral HealthCommunity Services
    Visit live project

    System Phase

    1. Concept
    2. Prototype
    3. Pilot
    4. Production
    5. Demonstration
    Version
    0.9
    Current Phase
    Pilot
    Originally Developed
    2023
    Last Updated
    2025-10
    Maintainer
    Iterum Systems

    Origin Context

    Where this system came from

    Environment
    Outreach teams serving people experiencing homelessness or behavioral health crisis across urban and rural areas.
    Trigger
    Existing directories could not answer where a person could go immediately, so staff fell back to memory and phone calls.
    Constraint
    Users may have low-end phones and intermittent connectivity, while service details change frequently without one reliable directory owner.

    The Problem

    Why this system exists

    Directories, PDFs, and phone trees describe available resources but rarely answer where someone can go now. Hours, weather, transportation, and eligibility change; outreach workers compensate with memory and repeated calls. People in crisis encounter that friction when time, battery, and attention are already limited.

    The Solution

    How it works operationally

    Lantern normalizes service information, then filters it by current conditions such as time, weather, and transportation. It presents a short, actionable set of options on a phone and routes field corrections back to the catalog.

    Core Capabilities

    What the system provides

    Actionable service results

    Listings are ordered by what a person can use now, not by directory taxonomy.

    Weather response

    Severe conditions elevate appropriate shelter, warming, and cooling resources.

    Reachability context

    Results account for how someone can get to the service.

    Field-ready access

    The interface is built for low battery, intermittent connectivity, and urgent use.

    System Components

    What the system is made of

    Field-first mobile interface

    Interface

    Mobile-first UI optimized for low-battery, low-connectivity, high-stress use.

    Resource catalog

    Data Model

    Structured record of services with hours, eligibility, location, and reachability attributes.

    Weather and transportation signals

    Automation

    Automated inputs that elevate shelter, warming, cooling, and reachable resources based on live conditions.

    Update workflow

    Workflow

    Lightweight process for outreach staff and providers to correct listings from the field.

    Implementation Model

    How it functions in practice

    Inputs

    What the system requires

    • Community service directory data
    • Weather and alert feeds
    • Transit and reachability reference data
    • Field corrections from outreach staff and providers

    Process

    What the system does

    • Ingest and normalize service records against a shared schema
    • Apply weather, time-of-day, and reachability filters at query time
    • Present a short, actionable list rather than a full directory
    • Route field corrections back into the catalog

    Outputs

    What it produces

    • Ranked list of services a person can act on now
    • Alerts elevating shelter and warming resources during severe weather
    • Reduced call load on outreach coordinators
    • A cleaner shared directory over time

    Dependencies

    What must remain true

    • At least one accountable data steward per region
    • Provider willingness to keep hours and eligibility current
    • Reliable weather and transit data sources
    • Continued field feedback from outreach staff

    Where It Works

    Environments

    Homeless ResponseCommunity HealthBehavioral HealthNonprofit Operations

    Intended operational contribution

    What this system is designed to support

    • Designed to shorten the path from immediate need to a reachable service.
    • Reduces the directory work repeated by outreach staff.
    • Creates a field correction loop for changing service information.

    Current Limitations

    What this system does not solve

    • Does not create services where none exist.
    • Accuracy depends on providers updating hours and eligibility promptly.
    • Does not replace direct outreach relationships.
    • The pilot has not been validated across every regional context.

    Start the Conversation

    Interested in solving a similar operational problem?

    Discuss one operational problem

    Related Systems

    Explore the portfolio

    Data & Analytics

    Cognos Operating System

    Open

    Social Services / Homelessness

    Housing Stabilization Training (HST)

    Open

    Healthcare Operations

    ILOS Operations Framework

    Open

    Workforce Development

    Relational Mirror Model (RMM)

    Open

    Business Intelligence

    Reporting Core

    Open

    Population Health

    Rural Tool — New Mexico Demo

    Open
    View all systems →

    Related documented professional work

    Where this system has been applied

    These are documented professional-work contexts, not an Iterum commercial client list or former-employer endorsement. Descriptions below are not independently verified performance results.

    Environment

    Behavioral Health Organization

    Standardized documentation, report recipes, validation processes, and reusable reporting infrastructure.

    Environment

    Community Resource Platform

    Centralized navigation with weather alerts, transportation resources, and community services.