1. Decision and Care plan
Services, frequency, durations, constraints, and relationships become structured planning data.
Visit data lifecycle
From care decision to completed visit
Caire turns each visit into a living data product: decision, care plan, schedule row, route, mobile execution, and follow-up stay connected in Caire Core.
Current page
Visit data lifecycle
From care decision and master data to mobile execution.
A visit improves when data does not break
When visits change or get completed, signals feed a continuous learning loop. Planners can see what happened, why it happened, and what should be reviewed next time.
2. Master data and resources
Clients, employees, skills, service areas, and shifts define which visits are possible.
3. Optimized visits and routes
Caire Core creates candidates that weigh continuity, travel, time windows, and workload.
4. Mobile execution
The caregiver sees the visit, documents, checks in, and reports deviations directly.
5. Follow-up
Outcomes and quality are compared with the plan so the next schedule can improve.
Lifecycle diagrams
The old platform flows, rebuilt as product diagrams
These diagrams preserve the source platform logic: decisions become templates, templates become dated visits, optimization creates a planner-approved candidate, and mobile execution feeds the next planning cycle.
Diagram 1
Decision to completed visit
The full path from approved care decision to mobile execution and continuous learning loop.
Loading diagram...
Diagram 2
Three-layer visit architecture
The old platform document's Layer 1, 2, and 3 model rewritten in Caire Core language.
Loading diagram...
Diagram 3
Constraint hierarchy
Use the simplest tool first: precompute when possible, use time windows broadly, and reserve hard dependencies for real requirements.
Loading diagram...
Diagram 4
Template inheritance cascade
Service-group defaults flow into the visit template and materialize into individual dated visits.
Loading diagram...
Diagram 5
Lifecycle states
The visit moves from draft to optimized plan, mobile execution, and learning for the next period.
Loading diagram...
Data flow from source system to execution
The source system and Caire Core keep the visit lifecycle aligned from decision to mobile execution.
| Layer | Decision | Master data | Execution |
|---|---|---|---|
| Source system | Care decision and approved services | Client, address, service, and time rules | Completed visit and deviation status |
| Caire Core | Planning interpretation | Visit graph, staff, skills, shifts, routes | Mobile execution, audit trail, and follow-up |
Why this matters operationally
The visit lifecycle prevents planning data, mobile execution, and reporting from becoming separate realities. That is what makes AI scheduling explainable and audit-friendly.
See AI scheduling