Alignment Integration / community and social services
health, social services, coordinated care
The work between agencies is where people get lost.
Every agency knows its own part. Nobody holds the space between: who has the next step, what was already tried, and whether that referral landed anywhere.
Captured from the live method demo. No real person, no client data.
01
What we build for this sector
Written from inside this work, for agencies where the coordination takes more out of the day than the service does.
-
one
The whole pathway, not just your part
Where a person sits across the services touching them, and who owns the next step. On paper that gap is nobody's problem, so nobody fixes it.
-
two
Reporting that comes out of the work
Funder reporting usually gets rebuilt at quarter end from memory. Make it while the work happens and there is nothing to rebuild.
-
three
A map of the whole person
The biopsychosocial and spiritual reading you already work in, held as connected factors with the evidence behind them. You get it back as a report.
-
four
Consent built in from the start
Who can see what, under whose consent, and what happens when it is withdrawn. In this sector that decides whether the system can exist at all.
demo live
Diagnostic and intervention map
One view of the map, the whole person health version. It shows how the layers are read and how a plan is weighed before anyone commits.
Every map is written up as a holistic research and intelligence report: what the layers said, where acting changes the most, and the evidence under each move.
in development
Coordinated services and referral pathways
A working demo of the pathway view above, built on a generic community rather than a real one. Not open yet.
02
Three portals already built
Each one runs in your browser and you can read the screens yourself. All three demos hold sample data. No real service, no real community, no client record.
demo live
Community safety and well-being portal
Built for a community safety partnership, where police, health and social services sit at one table. It holds the situation table record: who was brought forward, which agencies took a part, and what happened after. Referrals move between partners inside the portal instead of over the phone.
demo live
Multi-agency hub portal
A coordination surface for a hub where homelessness, addictions and health services sit together and several partner agencies work one caseload. Staff see referrals, capacity and the day's activity for the programs they are responsible for. It is multi-tenant, so each organization signs in to its own data.
demo live
EMR staff portal
A staff portal built over the EMR these teams already work in. Frontline workers and program managers get one dashboard per program: caseload, referrals in and out, and what is due this week. The record stays in the EMR and we do not replace it.
03
How it works underneath
The same engine runs every build we do. Three ideas cover it. The longer version is on the home page.
- one
- It captures what happens as it happens, so the record is not written afterwards from memory.
- two
- Overnight it separates the noise from what mattered, so the morning read is short.
- three
- A person with authority over the work governs what becomes the record. That is the whole governance model, and it is deliberately boring.
What we are not claiming, and this matters most in this sector: this is not an electronic medical record and does not replace one. We do not hold client health data, and we do not publish outcome numbers we have not measured. Where a build would touch personal health information, that is a consent conversation first.
Not what you came for