01
Common infrastructure
Durable, versioned workflows, controls, records, and quality structures intended to express what must be true regardless of location.
Platform / Operating Model
An operating model, designed for reuse
Kinvie's architecture is designed around common operating infrastructure, local configuration, and licensed-operator accountability — so future implementations can begin from a governed foundation rather than rebuild every element independently.
Architecture
Three layers
The architecture is deliberately layered so that common operating logic stays separate from local, jurisdiction-specific requirements — so local configuration adapts the same core rather than forking it.
- 01
Common operating infrastructure
- Systems
- Workflows
- Evidence
- Services
- 02
Local configuration
- Jurisdiction
- Workforce model
- Service model
- Policy
- 03
Operator-specific environment
- Operating data
- Local decisions
- Records
Decision layer
- Human decisionsAccountable, consequential, retained
- AI-assisted coordinationBounded support, under human authority
Accountable people remain responsible for consequential decisions.
Layers
How the layers divide
02
Local configuration
Jurisdiction-specific settings — service area, rates, local requirements, and contacts — designed to be expressed through configuration rather than material forks of the common core.
03
Operator-specific data
The intended architecture would preserve operator-specific data and access boundaries, separated from every other operator.
Long-range scope
Domains the long-range operating model may connect
These are long-range domains the operating model is being designed to connect — the intended operating scope across the care-at-home lifecycle, with regulated decisions and records remaining with the licensed operator.
01
Client lifecycle
Intake, assessment, service planning, and coordination support.
02
Service delivery
Scheduling support and visit verification, with configurable rules.
03
Workforce readiness
Configurable readiness gates: qualification, clearance, training, and competency, with expiry tracking.
04
Quality & risk
Incident and complaint tracking, corrective actions, and periodic review.
05
Records & compliance support
Record structures and retention support, with records remaining the operator's responsibility.
06
Reporting
Reporting designed around each operator's own data and access boundaries.
Next step
Want to explore the operating model Kinvie is developing?
We'll walk through the intended architecture and where the boundaries sit.