Iterum Systems · Operational problem-solving for Medicaid, behavioral health, housing / homelessness, crisis & public systems
Organizations spend considerable time and money addressing symptoms of problems they haven’t fully understood.
Iterum examines how people, policies, resources and decisions interact in one piece of work—a stalled referral, an unreachable provider, an unowned handoff, a report nobody agrees on. We test the accepted explanation, then develop a practical response that works in the real operating environment.
We start with the problem. Not a product.
First engagement: a bounded assessment of one breakdown you define. You receive an evidence and workflow map, tested causes, ownership gaps and a prioritized repair plan.
Assessment scope & deliverables →Start with the breakdown
Related working evidence
Cognos Operating System — Documented system / prior professional experienceReporting Core — Documented reporting frameworkHow we think
01
The complaint that starts the work is usually a symptom. Trace where the decision, handoff or report actually goes wrong.
02
Policy, staffing, data, funding and frontline practice are often managed apart. Examine how they interact in the same piece of work.
03
Treat “staff aren’t following the process” or “we need new software” as hypotheses. Test them against records and the people doing the work.
04
Name the change, who owns it, what it depends on and how anyone will know whether it worked.
05
A clarified owner, SOP or definition is often enough. Software is built only when the problem requires it.
Where we work
Experience in these sectors comes from Maurice Cloutier’s professional history. The method may apply in other settings, but no results are claimed outside the work described here.
What we’ve developed
These projects came from working a specific problem. They show the reasoning, not a product catalogue.
All developed work, documented designs & professional history
In development / testing
AI-assisted referral decision support designed around source provenance, feedback and human verification.
Illustrative decision scenario
Design example only. No deployed accuracy or client outcome claim.
Public demonstration
Explore geographic access constraints; the separate Nevada platform documents prior professional work.
Illustrative decision scenario
Illustrative scenario using a real demo—not live provider availability. Nevada history is not an Iterum client engagement.
Documented framework / prior professional experience
Translate housing-related benefit requirements into authorization, referrals, documentation and audit workflows.
Illustrative decision scenario
Illustrative application of documented work. No payer endorsement or universal compliance claim.
Documented system / prior professional experience
Align reporting definitions, source lineage and governance around an operational question.
Illustrative decision scenario
Illustrative scenario—not a verified customer result or employer endorsement.
Documented reporting framework
Make reporting definitions, reconciliation and accountability repeatable.
Illustrative decision scenario
Design application—not measured ROI or an attributed commercial case study.
Deployed training site / documented design
Six modules for practical transition skills, with a pre/post/follow-up evaluation model.
Illustrative decision scenario
Illustrative application. Active deployment features and access arrangements require confirmation; improved housing outcomes are not proven here.
Publicly functioning project
No-account service navigation, weather safety and English / Spanish access.
Illustrative decision scenario
Illustrative scenario using the real project. Listings do not establish service availability.
Public framework
A trauma-responsive, nonclinical workforce framework for reflection and relational engagement.
Illustrative decision scenario
Conceptual practice scenario—not therapy, a clinical intervention or a proven treatment outcome.
Work with Iterum
Path 1
A bounded operational assessment of one recurring breakdown.
You receive: Evidence and workflow map, tested causes, ownership gaps and a prioritized repair plan.
Path 2
Turn assessment findings into an actionable response strategy.
You receive: Sequenced changes with proposed owners, dependencies, acceptance checks and a scoped next step.
Path 3
Scoped workflow, training or technology implementation.
You receive: Depending on scope: reporting repair, program SOPs and readiness checks, training rollout, or a decision-support prototype.
Scope, dependencies and fees are agreed in writing before paid work begins. No outcome or turnaround is guaranteed. Assessment scope & deliverables
Specific engagements behind the three paths
Assessment
A scoped review of one operational problem: intake, evidence and workflow mapping, causal and ownership analysis, and a prioritized repair plan.
One agreed breakdown. Implementation is scoped separately.
Assessment scope & deliverables Discuss one operational problemImplementation
Apply Reporting Core’s approach to one reporting chain: agree what a metric means, trace how it is calculated, and assign responsibility for exceptions and changes before rebuilding a dashboard.
Work within agreed existing tools and source constraints. Makes upstream data problems visible; correcting them requires a separate scope.
Inspect Reporting Core Discuss one operational problemImplementation
Translate a benefit or program requirement into work staff can carry out.
State and payer requirements must be supplied and verified. Not legal or licensure advice.
Discuss one operational problemCustom build
Test a specific operational decision before committing to a larger build.
A prototype is not a clinical decision-maker or a guarantee of provider availability.
Discuss one operational problemMaurice Cloutier, principal, has more than 20 years across Medicaid community care coordination, behavioral health, housing, homelessness, crisis response and public systems—including director-level statewide operational responsibility.
Iterum grew out of repeatedly finding that the visible problem was not the one causing the failure. The software projects on this site exist because a specific problem needed them; the judgment that located the problem is the service.
That experience includes translating program requirements into frontline work, cross-sector implementation, nonprofit / Continuum of Care participation and relational engagement. Lived experience of homelessness informs the attention to what happens after a referral or placement.
This is Maurice’s professional history, not a list of Iterum commercial clients. Former employers do not endorse Iterum. No historical outcome figures are claimed here.
Speaking & Field Engagements
Conference Session
Nevada Statewide Homelessness Conference
Housing Stabilization Training addresses what follows placement: the skills, support, and operating structure that help housing hold.
Placement is not stabilization.
Discuss one operational problem
What is happening, what does it cost operationally, and what has already been tried? We’ll clarify fit and scope before discussing paid work.
Do not submit confidential client or member information, health records, case details or other sensitive personal data.
maurice@iterum.systemsIterum Systems is Maurice Gerard Cloutier’s sole-proprietor practice. Clark County DBA registration is not yet submitted or approved. No payer contracting or regulated-compliance certification is represented.