kint regimen.
care decisions, planned within the rules.
Hospitals and care providers get a plan for the decisions that run the house, for example rosters, theatre slots, beds and home care tours. Each plan states the rule that binds it and the solver's gap: how far from best it can be.
Care decisions couple across staff, rooms, beds and days. A roster built by hand covers the shifts. When the works council asks whether it was the fairest one, the answer has to come from the model.
what the house is doing.
- Admissions, discharges and bed occupancy
- Staff, contracts, hours and leave
- Theatre bookings and the outpatient calendar
- Stock of drugs, blood products and supplies
what to do next, and why.
- Which nurse and physician works which shift, within working time law and wishes
- Which case goes into which theatre and slot, within staff and equipment limits
- Which patient gets which bed, and when the next elective admission fits
- For home care: which caregiver visits whom, and in which order
every shift, with its reasons.
This screen shows one week of the roster for ward 4, with the rule that binds it and the record per change.
the platform builds and checks it. it runs as your solution.
Loading the product screen
POST /v1/solveresponse200 {"plan": 274, "bound": 274, "gap": 0.0}illustrative| change | shift | nurse | wish | state | record |
|---|---|---|---|---|---|
| C-03 | Mon early | T. Aydin | early shifts | approved | run 2209 · model v9 |
| C-07 | Wed late | M. Schulz | none | approved | run 2209 · model v9 |
| C-11 | Fri night | J. Wolf · senior | none | approved | run 2209 · model v9 |
| C-14 | Sat night | N. Brandt · senior | weekend off | proposed | run 2217 · model v9 |
| C-15 | Sun early | L. Roth | weekend off | open | run 2217 · model v9 |
- plan
- 274 pts
- bound
- 274 pts
- state
- optimal
On Saturday two seniors are free, and the night needs one of them. One more senior from the float pool would meet the open wish for the weekend off.
- data
- staff list and wishes 07:40
- model
- v9, reviewed by the ward lead
- solver
- CP, settings pinned
- result
- bound and gap stored
- released by
- ward lead
your planning software · kint inside
your systems call kint
run by kint · hosted in Germany
kint works inside the planning software, under the vendor's name. kint for software vendors
Your systems send the data and get the plan back with the solver's bound and gap: how far from best the plan can be. the kint api
Your team plans, kint runs the solution, hosted in Germany. managed operation
the questions hospitals and care providers ask.
regimen answers each one with a plan and the rule that binds it. The solver's gap shows how far the plan can be from the best one.
Who works which shift next month, within working time law, skill mix and the wishes of the team?
ReturnsA roster per person and day, with the staffing rule that binds and the wishes it meets.
Which case goes into which theatre and slot this week, within surgeons, anaesthesia and equipment?
ReturnsA theatre plan per room and day, with the resource that limits throughput.
Which patient gets which bed today, and when does the next elective admission fit?
ReturnsBed assignments per ward with isolation and specialty rules kept, plus admission dates.
How do the MRI, the chemotherapy chairs and the outpatient clinic fill their slots?
ReturnsSlot plans per device and day that keep capacity free for urgent cases.
Which caregiver visits which patient at home, in which order, with continuity of care kept?
ReturnsTours per caregiver with time windows and qualifications matched.
behind the hospital systems you already run.
Data comes in as read-only exports. Approved plans go back only through an API you control; the hospital system decides whether to apply them.
- One month of data: staff, contracts, wishes and demand per shift, as an export or JSON.
- The rules planners apply, including working time law and works agreements. kint's decision agent drafts the model from them.
- A person who releases the plan. An approved workflow then runs whenever your systems call it, and each plan waits for that release.
Each roster, theatre plan and bed assignment states the rule that shaped it and the gap of the plan behind it.
On the same engine, home care tours, caregiver continuity and patient transport run in one model. Each plan keeps its record: data, model version and release.
they record and book. regimen decides.
Hospital systems own the data and the workflow. The planning inside them often follows fixed rules or happens by hand, one ward at a time. regimen plugs in as the decision layer.
| Category | What it does | What regimen adds |
|---|---|---|
| Hospital information systemsHIS · PDMS | Hold patients, orders and occupancy. Planning follows fixed rules. | Bed and admission plans with the binding rule stated, solved across wards at once. |
| Rostering softwareduty rosters · time tracking | Record shifts, hours and leave. The roster itself is built by hand. | One model that weighs working time law, skill mix and wishes, with a record per change. |
| Theatre and outpatient planningbooking · scheduling | Book rooms and slots one request at a time. | A stated gap and a record per plan. The plan is one you can explain to clinicians and the works council. |
plan the next roster with a record.
Bring one month of roster data: staff, rules and demand. We show you the plan that keeps the rules, the rule that binds it, and the solver's gap: how far from best it can be.
- For
- Hospitals, clinic groups, care providers
- Sits behind
- HIS · rostering · theatre planning
- Use cases
- all industries
- Contact
- hello@kint.pro