emiac.
Readiness, as software.

A white-label member portal for regional healthcare coalitions. One place for documents, discussion, calendar, funding, and the deliverables the coalition owes its state health department. Live for its first coalition since June 2026, delivered continuously since.

• Role-based access

  Members, advisory board, staff, admins. Org email domain is a verification signal; admins approve every account.

• Community board

  Threads, replies, follow notifications tuned so nobody gets mail about conversations they did not ask for.

• Document library

  Categories, search, version tracking, role-gated downloads, meeting records with linked materials.

• Shared calendar

  Meetings, training, exercises. Registration links, filtering, ICS subscribe, automated reminders.

• Work plan tracker

  Cooperative-agreement deliverables by budget period, owner, and status. Staff-only, reportable to the state.

• Funding requests

  Opportunities, requests, an approval workflow with history, and a ledger of what was endorsed.

• Forms

  Staff-built forms with identity autofill from the member profile and submission limits.

• Notifications

  Email and in-app, per-member preferences, deadline alerts, announcement banners.

Why it is different

1. 01Built from a real coalition RFP by someone who attends those meetings, so the modules map to how coalitions actually work: work plans by budget period, corrective-action tracking, advisory-board tiers, state deliverables.
2. 02Every coalition is its own tenant: its own database, its own deployment, its own domain, branding stored as data. Nothing is shared between clients, and a coalition can walk away with its data.
3. 03Continuous delivery with a bug pipeline that starts inside the product. A member reports a problem from the app or by email; it is triaged, fixed, verified, and shipped, with the reporter told what changed.
4. 04Viewport-fit surfaces designed for the way staff use it: on a phone between meetings, on a laptop during one.

The hospital-side platform. It owns the full cycle a facility gets surveyed on: hazard analysis, exercise design and conduct, after-action reporting, the emergency operations plan, and the compliance evidence behind all of it.

• Hazard vulnerability analysis

  Database-backed scoring models across a facility hierarchy. A living dataset, not a once-a-year PDF.

• Exercises

  Scenario design driven by the HVA. The AI conducts the tabletop, scores it, and hands the team a transcript and evaluation.

• After-action reports

  A-la-carte composition from a library of 50+ components across 26 accreditations, each cited to a public authority.

• Emergency operations plans

  Composable EOP builder with a 12-check pre-emit linter reading the same canonical lists surveyors read.

• Compliance tracker

  Standards library, element status per facility, evidence, binders, interview Q&A, survey findings, readiness scores.

• Survey-ready export

  DOCX and XLSX out the door with render fidelity checked against Word gold fixtures.

• Regulatory watch

  Weekly automated check of 42 CFR 482.15 for text changes, so the standards library never drifts silently.

• Multi-facility, role-gated

  Facility hierarchy, versioned document library, plain-language audit log, installable as an app.

Why it is different

1. 01Every after-action component cites the public authority it satisfies. The document that comes out is the survey binder, not a draft someone still has to reconcile against the standard.
2. 02The AI does the work a consultant would charge for: it conducts the tabletop, scores the exercise, lints the plan, and flags the gap. The team keeps the judgment.
3. 03The standards are watched, not remembered. Regulatory text is checked automatically and the library carries its own version history.
4. 04The whole cycle lives in one dataset, so the hazards you scored drive the exercises you run, and the exercises you run drive the corrective actions you track.