An enterprise comes in as an anchor sponsor: it funds capabilities that become permanent public goods, connects its systems to archives its patients own, and staffs a human layer drawn from its own communities. KISOP has no software licenses, seats, or data to sell a health system. The flagship is a program families meet on their hardest day: Activate the Family Around a Loved One — free to the family, because you funded it.
The sponsor pays once; the capability belongs to everyone, permanently, with the sponsor's name on its provenance record. The person keeps the archive. Nobody, including us, gets to own the middle.
Activate the Family Around a Loved One turns your discharge into an enrollment moment. The patient leaves with a working plan: their records land in an archive they own; the family becomes an organized circle with scoped views; the plan of care becomes a week that runs — walks scheduled with family and nearby neighbors, supplies bought cooperatively at circle prices, the primary caregiver's own load watched. Free to every family, because you sponsored it. And it says so.
The family-facing page (→ activate-the-family.html) is written the way families read the family-facing page. What it does for you shows up where your operators already look: readmissions and transitions, kept follow-ups, coverage continuity at the moment of maximum attention, and retention that compounds, because the family's tools live in your edition of the platform.
The unit an enterprise sponsors is an edition: the platform's primitives configured to your environment and your values, plus the capabilities you fund into existence. Nine components:
| Component | What it does |
|---|---|
| Continuity Archive | Person-owned archive seeded from your systems at enrollment (bulk FHIR export). EHR-agnostic; survives divestitures, joint ventures, and vendor changes. Your master patient index reconciles identity inside your walls; the archive anchors it with the person outside them. |
| Resilience Brief | An always-current, printable one-page brief: medications with look-alike flags, allergies, conditions, coverage, contacts. When enterprise systems go dark, the patient is the redundant node. |
| Episode Journeys | Pre/post runbooks for surgical episodes and discharges; preparation, medication reconciliation, recovery with a movement thread; every episode deposits into the person's archive at close. |
| Coverage & Benefits Companion | Watches coverage cliffs (renewals, transitions), prepares paperwork, routes to financial assistance, activates benefits people already have. Converts uncompensated care into covered care. |
| Community Helper Circle | Your existing trust network may include family caregivers, friends, parish nurses, community health workers, home health aides, and other local helpers. Each person's profile shows their actual training, certification, or professional license. Every session is bounded and scoped. A helper keeps no copy. |
| Family & Caregiver Threads | Scoped access for the circle, shared calendars, and a load gauge on the caregiver's own burden with respite prompts. The caregiver is a user in their own right. |
| Meaning Layer | Every surface at a verified reading level, in the languages your communities live in, with registry-backed terms and side-by-side bridge views. Consent is only real if meaning survives translation. |
| Values Thread | A partition for what your definition of whole-person care includes (for a faith-based system: advance care planning, proxy documents, chaplaincy scope), configured to your ethical directives. |
| Integration Surface | FHIR R4 / TEFCA-aligned exchange. Your systems access the person's archive as consent-gated guests; append-only audit visible to both sides; read-mostly; no rip-and-replace. |
An edition stays on the common codebase. Every component composes from the same primitives every community gets: what you fund, all communities eventually inherit, with your provenance attached.
The edition's capabilities, built as permanent public goods: the funded jobs on our open board, your name on each one's provenance record.
The FHIR/consent gateway into your estate, the master-patient-index handshake, the open registers, and ongoing support.
Recruiting from your own communities, training, credentialing, and session compensation: the human layer that makes engagement real.
A per-member component tied to logged events can replace part of the fixed fee at scale. We are open to earning it, because the log makes earning it provable.
The working numbers (planning ranges, formulas, and every assumption labeled for replacement by your actuals) live in the business case we walk with you. There is no public rate card. Ten data requests and two weeks of part-time attention from one data analyst and one mission lead make the model yours.
Six levers, each with an exposed formula and each auditable in the platform's own append-only event log (attribution you can inspect):
Coverage continuity. Renewals kept and eligible people enrolled: uncompensated care becomes covered care. The largest lever, and the most mission-shaped one.
Kept appointments. Family booking, transport noted, reminders in the right language at the right reading level; freed slots backfilled.
Value-based performance. Care gaps closed at the person, adherence supported at home, patient-reported data flowing with consent.
Readmissions and transitions. Discharge instructions that survive the handoff: plain language, reconciled medications, an activated family.
Retention and episode capture. The family's tools live in your edition; ambulatory episodes get a before and an after.
Administrative deflection. People who hold their own records stop paying you in phone calls and release-of-information requests.
Deliberately not summed into any total we show you: resilience value (person-held archives create no new central honeypot, and they keep working when your systems don't) and mission value, counted in lives and reported to the people you answer to. We put no price on it.
No exclusivity, ever. Whatever you fund, every community gets. Our charter forbids selling anyone a fence around it.
No data. The person owns the archive. Neither you nor we own it. There is no central store of your patients' information to buy, breach, or subpoena.
No lock-in. We built a way out from the start. If the partnership ends, your communities keep their archives and every funded capability. Money spent here builds permanent community infrastructure either way.
No engagement metrics. Time-in-app is a failure measure on this platform. What we report: outcomes, kept visits, retained coverage, caregiver load, and an unconsented-access count whose only acceptable value is zero.
Ninety minutes. We walk the business case levers against your actuals and demo the archive reference build. Bring your data lead, your mission lead, and your security lead; each has a different first question and we want all three.
Discovery. A named pair from your side, ten data requests, two weeks part-time. Our assumptions get replaced by your numbers; the model becomes yours.
A pilot sized to be provable. Two communities, twelve months, enrollment at the moments continuity breaks: discharge, surgery, coverage renewal, caregiving onset, with weekly open registers you can audit.
Scale on evidence. Lever rates locked from the pilot's log.
Health systems are first, on purpose: the flagship program lives at your doors. Associations, foundations, companies, and governments sponsor capabilities; Ways to work together maps those lanes.
No enterprise sponsorship has been signed yet. We are in our first anchor-sponsor conversations now, and the first sponsor shapes the edition and the pricing with us.
The platform is early and says so in public. The single, dated inventory of what is built, tested, and still designed is the build log — one page, updated every time reality changes, and the build log governs every claim on this page. The plan for preventing fraud, waste, and abuse has its own page.
Being first is the offer: a chance to put your name, permanently, on infrastructure your communities keep forever.
Write to us → "interest" on the main site, and say you're coming from this page. You'll get a human answer, in whichever of our languages you prefer.