CCT Admin Decision Workflow

1. Who is who

• LiveDr Roland is the CCT lead. He is both a CCT doctor and the CCT manager. T-242, T-249
• LiveThe "CCT Admin role" is a limited admin role for the CCT team. A person with it uses the CCT planning page and the CCT Set Up screen as an admin, and nothing else of the admin area. Full admins give or remove the role on Admin › Staff › Med Admin (the "CCT Admin" sub-category). T-242, T-250
• LiveAdmins (full admins of the app) can do everything a CCT Admin role holder can. T-242
• LiveManager and clinician. In the change rules (section 3):
  • a manager is a full admin or anyone with the CCT Admin role;
  • a clinician is any active CCT team member whose CCT role is not Admin or Operations (so doctors, and nurses, therapists or social workers if they are added to the team);
  • a non-clinician admin (a manager who is not on the CCT clinical team) can plan, call and ask, but cannot set safety limits, approve, decline or override;
  • a CCT team member who is Admin or Operations and has no admin role can read, but cannot change a visit;
  • a person who is both manager and clinician (Dr Roland) is treated as a clinician wherever the rules differ.
  T-309, T-311, T-312
• LiveEach doctor edits their own patient list. A doctor who does not have the CCT Admin role can change only their own day plan and their own roster sessions, and visits that are theirs or of their own patients. Any CCT doctor may change the details on any patient card (see “Any CCT doctor can edit any patient card” below); whose list a patient is on stays as the next two rules say. "Own patients" means: they are the patient’s preferred doctor, or the patient is planned with them (from a week ago on), was seen by them in the last 30 days, or has a "no date yet" visit with them. A doctor can add to their day only a patient who is already theirs or planned for them. The database refuses anything else and the screens say why; "View as" cannot be used to change another doctor’s plan. Admins and the CCT Admin role (Dr Roland too) may change anyone’s. T-341
• LiveAdding a patient to a doctor’s list is the CCT Admin’s. Only an admin or the CCT Admin role makes a new card or sets a card’s preferred doctor (that is whose list the patient is on). A doctor cannot put a patient on their own list or on another doctor’s. T-341
• LiveOne door for a new patient. A new patient card is made only by the New patient wizard on the CCT Admin page (Initials and Postal code; it also sets the first-visit window). The database refuses a new card sent any other way — an older phone or Waypoint, or a card made in a browser while signed out — with the words “New patients are added by the CCT Admin with the New patient wizard (CCT Admin page). This card was not saved.”; what was sent is kept in the database’s log for the CCT Admin. Changes to an existing card are not affected (the phones already in use included). T-381
• LiveTaking a patient off a doctor’s list needs a reason. Clearing or changing the preferred doctor, archiving the card, or setting it to Discharged or Deceased is done by the CCT Admin (or an admin) or by that patient’s own doctor, always with a reason from the list (Discharged from CCT care, Care moved to another doctor or team, Assigned to the wrong doctor, Admitted to hospital, Deceased, Moved out of area, Patient declined, Duplicate card, Other) and a few words. One entry goes in the patient’s communication log: who, when and why. A card is never deleted outright; it is archived. On the phone see “On the phone” below. T-341
• LiveOff the list: no typed words when the reason says it all. Duplicate card, Admitted to hospital and Moved out of area (and Deceased) need no typed words; Other, Assigned to the wrong doctor, Care moved to another doctor or team, Discharged from CCT care and Patient declined still need a few. When the card’s status is Admitted, Discharged or Deceased, that reason comes already chosen (still changeable). The database checks the same rule. On the phone too (phone: store build seq 23). T-381
• LiveEvery change to a patient card needs a reason. Anyone who changes a card — any detail, the safe limits, a new card, archiving — gives a reason, the CCT Admin too. Saving asks first, from a short list: New information from the patient or family, Correcting a mistake on the card, Contact details changed, Address or access changed, Visit plan changed, Clinical review, Assigned to a doctor’s list, Other (Other needs a few words; words are optional for the rest). Taking a patient off a list uses its own list and always a few words (above). The database refuses a change without a reason and says why. The change and the reason go in the patient’s communication log as ONE entry per save: who, when, what changed, why. A new card’s reason is its referral (“New referral”), filled in by the form. Values the app works out by itself (travel times, the card colour, “last seen”) need no reason and are not logged; a change made by the system with no one signed in (an import, a scheduled job) is not blocked and is logged “By system”. Visit changes keep their own reasons. On the phone see “On the phone” below; until the phone apps are updated from the store, a card change made in an older phone app is refused with the database’s words. T-343
• LiveA card change: the reason comes chosen from what changed. When everything changed on the card is of one kind, saving asks with the reason already chosen: the mobile, email or family contact → Contact details changed; the address, unit, lift or access → Address or access changed; how often, how long or which days → Visit plan changed. One click (or Enter) saves; the reason can still be changed. A mix of kinds, the status, the safe limits or the notes ask as before, with nothing chosen. The database still needs a reason for every card change (T-343). Waypoint and the card on the CCT Admin page. On the phone too (phone: store build seq 23). T-381
• LiveAny CCT doctor can edit any patient card. The details on a card and its safe limits can be changed by any CCT doctor (a CCT clinician), not only the patient’s own; every change goes in the patient’s communication log with who, when and the reason. A CCT team member who is not a clinician (Operations) sees the card read only. Adding a patient to a list (a new card, setting the preferred doctor) stays the CCT Admin’s, and taking one off stays the CCT Admin’s or the patient’s own doctor’s. Plans, sessions and visits stay each doctor’s own. T-344
• LiveOn the phone: the same reasons and the same rights. In the phone app (/m, and the iOS and Android apps once they are updated from the store), saving a patient card that changes something asks “Why are you changing this?” first, with the same list and words as Waypoint (Other needs a few words); “Cancel: change nothing” saves nothing. A save that changes nothing asks nothing. A new card goes up with “New referral” (no extra question), and making a new interval the regular one at the end of a visit goes up with “Visit plan changed”. Deleting (archiving) a card asks a second time and then the reason for taking the patient off the list, with a few words; only the CCT Admin or the patient’s own doctor (the card’s preferred doctor) can, and for anyone else Delete is shut and says why. “+ New patient” is the CCT Admin’s; for anyone else it is shut and says why. A CCT team member who is not a clinician (Operations) sees the card read only. The phone has no preferred-doctor or Discharged / Deceased control, so Delete is its only way to take a patient off a list. When the phone cannot ask the database who you are (offline), nothing is shut and the database decides. Needs a store build. T-343, T-341, T-344
• LiveThe CCT planning page (desktop app) is for Dr Roland and the admin team: patient list, the week's sessions, the selected session and the planning tools. Everyone else who opens it sees the week calendar only. Its menu name is "CCT Admin" (was "CCT Roster" until 24 Oct 26). T-249, T-251, T-337
• Live"CCT Roster" is renamed "CCT Admin" in the menu, tab, heading and messages. The role keeps its name and reads "CCT Admin role" wherever both appear (Admin › Med Admin, messages). T-337
• LiveWaypoint (the /cct/ page) is for Dr Roland's medical team: My week (my sessions and patients), the Session planner (map and route) and Communications. A doctor who is not an admin sees no patient list there; the map takes its space. T-282, T-284
• LiveA "RosterEngine" link in Waypoint. Everyone signed in to Waypoint (every CCT doctor, not only the managers) has a "RosterEngine" link at the top. It opens the main app on the tab they last had open there; if that tab is one they cannot open, or nothing is remembered, it opens Home. Each person's last tab is remembered for them, so on a shared computer you never land on the last person's tab. No new sign-in is needed. Inside the CCT Admin page's patient card the link is not shown. T-345
• LiveThe "RosterEngine" link also returns to the sub-tab. Inside a tab that has sub-tabs, the link opens the sub-tab each person last had open there: on the CCT Admin page, Roster or Admitted to Hospital; its Performance (Admin › CCT Performance) rather than CCT Set Up; any Admin sub-tab, at either level. A sub-tab that person cannot open, or one no longer there, is ignored and the tab opens as it always did. Each person's sub-tab is remembered for them alone. The old CCT Roster address still opens the Roster. The link keeps opening RosterEngine in the same browser tab. T-345
• LiveView as. A full admin or a CCT Admin role holder can pick a doctor in Waypoint and see that doctor's week and messages, read only. T-282
• LiveCCT Performance page is for admins and the CCT Admin role. Rows per doctor are seen by Dr Roland and the admins only; doctors never see a per-doctor row. A patient is overdue the day after their last visit plus their review interval (no grace days). T-255
• LiveHome Medical and IHH are always counted and reported separately, never as one combined number. A patient is not under both at the same time. On the CCT Performance page, "Visits per home session" shows one rate for Home Medical and one for IHH (each service's visits divided by that service's sessions held), with ASH sessions and visits on cards with no service said on their own lines; the demand card gives the budget and the visits needed per session for each service. In the question box, a count of sessions ("how many sessions next week", "sessions per doctor") is given per service, and "visits per session" for the whole team is one rate per service. One doctor's own rate is split the same way: on the Performance page's team table each doctor has one row per service (Home Medical visits in Home Medical sessions, IHH in IHH), each set against that service's own team range, and in the question box "visits per session by doctor" gives one row per doctor per service, with a middle value per service. T-340
• LiveTime to first visit leaves out patients referred before the visit history began, on the CCT Performance page and in the question box, until the older history is loaded. The visit history begins on the date of the oldest visit on record. Both screens say how many patients were left out ("2 referred before 29 Jun 26 left out"), because for them the first visit on record may not be the first visit. T-340, T-328
• Live"Changes and calls" panel on CCT Performance, for admins and the CCT Admin role only (the database refuses anyone else). Counts only: no patient, no name and no message text. Four parts: visit changes in the period by kind and by reason, and how many were allowed as a clinical exception; card changes by the reason given (a change made by the system, one made before reasons were asked for, and one whose reason is not on today's list are counted apart); change requests waiting now, by how long they have waited (under 1 day, 1 to 2 days, 3 to 7 days, over 7 days) and how many were escalated, with how many were raised and decided in the period and the middle time to decide; and calls (confirmation calls by outcome, and calls logged on a card, in and out, by what they were about). T-340, T-327
• LiveASH (All Saints Home) is counted in sessions. All Saints Home is a nursing home that buys home-medical consult time: SLH doctors see its residents on site, in half-day sessions with no patients listed in the session. On the CCT Performance page ASH has its own line, “ASH (All Saints Home)”: the ASH sessions held in the period (a doctor on the roster, the session over, the doctor not on leave), week by week, by calendar month (a month cut by the period, or still running, says so) and by doctor, alphabetical. Never a visits-per-session rate, because there are no patients in an ASH session to count. T-340 D4
• LiveDemand against capacity is judged over a window that grows with the history. “What the team did” (visits done and home sessions held a week, for each service) is counted over the last 4 weeks while the visit history (from the oldest visit on record) is under 12 weeks, then over the last 12 weeks; the switch happens on its own. The window counts back from today whatever period is chosen, never from before the week visits began. The demand card says which window it used and why, and, while it is 4 weeks, the day it will move to 12. T-340 D4
• LiveA doctor’s “Logged same day” needs 10 taps to show and 30 for a percentage. On the CCT Performance team table, a doctor’s share of visits tapped Completed or Missed on the visit’s own day shows once 10 of their visits carry a tap time, as “x of y” (under 10: “too few”), and as a percentage only from 30. These minimums are a starting point and will be revisited once there is baseline data. T-340 D4
• LiveManager view | Clinician view. A person who is both can switch which buttons the screen shows. The switch changes only the screen; the database applies the same rules in both views. T-316
• LiveOne view choice across the CCT pages. The same Manager | Clinician switch on the CCT Admin page, on the patient card (in Waypoint and inside the CCT Admin page) and in Waypoint, remembered once per person and followed at once by any page already open. The CCT Admin page opens in Manager view and Waypoint in Clinician view until the person picks. Only a person who is both a manager and a clinician sees the switch. A change request addressed to you (named or copied) shows Approve / Decline in either view. T-337
• LiveNew patients come in through one door. A new patient is added on the CCT Admin page with New patient (the wizard), never in Waypoint: Waypoint no longer offers “+ Add patient” when signed in, so every referral gets its first-visit window and its notice to a doctor. In the wizard only the Initials and the Postal code must be typed; the referral date (today unless changed), where it came from and the contact mobile are optional (a mobile that is given must be 8 digits). The service reads “IHH (Palliative)”, and the “First visit within” box is wide enough to read. T-381
• LiveA new referral reads “First visit by …” and Auto-fill places it in time. On the CCT Admin page a new patient’s card says “First visit by Thu 29 Oct” (urgent ones in the warning colour; “First visit overdue” once the window has passed) and is sorted on that date. Auto-fill treats the first-visit window as the patient’s due window and places the patient on a session inside it, the preferred doctor first; it no longer skips a new referral until the window has passed. T-381
• LiveManager view: a person who is also a clinician decides without switching. In Waypoint’s Manager view, a person who also holds the clinician role can approve or decline a visit-change request and set a patient’s limits without switching to Clinician view. A person who is only a manager still cannot: the buttons are not shown, and the database refuses anyway. T-381

2. Planning visits

The week

• LiveWeek planner. Drag a patient onto a session (each session has a named doctor). "Copy last week" starts from last week's plans; "Clear plans" empties this week's sessions (the roster itself is not changed). Each patient card shows the last visit (how many days ago, by which doctor) and marks a card already planned this week. T-249, T-251, T-252
• LiveThe session clock. Morning (AM) 08:30 – 12:30, afternoon (PM) 13:30 – 17:30, the same on every CCT page. A route opened from a PM session starts at 13:30. T-332
• LiveA session opened from My week is half a day. In Waypoint, opening one session (for example the morning) from My week shows only that session’s visits; a change made there never touches the doctor’s other half-day: the afternoon’s visits and their booked times stay as they were. Taking a visit off the open session takes it off the day. T-377
• LiveOpening Waypoint books nobody. Opening or reloading Waypoint never puts a patient on anyone’s Visit List: a visit is booked only when a person adds it. T-378
• LiveOne list: the CCT Admin page shows the doctor’s own Visit List too. Each Home Medical or IHH session on the CCT Admin page now shows, and counts, the visits on that doctor’s own Visit List for the day (the phone and Waypoint list, where every reschedule lands), marked Visit List. A visit goes in the morning session if its booked time is before 13:30, otherwise the afternoon; a visit with no time, or with no session in its half-day, goes in the doctor’s first session that day; a visit the roster already placed in a session stays there. The × and the time button of a Visit List visit change it on the doctor’s list (with a reason, as always). For now Optimise, Reverse, Clear session and Move session change only the patients the roster itself placed, and the page says so. T-376
• LiveOne list for each doctor’s day. A doctor has ONE list of visits for each day: the Visit List on the phone and in Waypoint. The CCT Admin page’s sessions show that list. A visit with a booked time goes in the morning session if the time is before 13:30, otherwise the afternoon; a visit with no time stays in the session it was booked into; with neither, it goes in the doctor’s first session that day. Everything done on the CCT Admin page — adding or removing a patient, Optimise, Reverse, Clear session, Move session, Auto-fill, Copy last week — changes the doctor’s own list, so the doctor sees it on the phone straight away. A phone or page that has not been updated yet, saving the doctor’s day, never removes a visit someone else booked after it last synced, and no out-of-date save brings back a visit that was cancelled or released meanwhile: only its own changes are saved. When two doctors swap sessions in one save, their patients swap too. When the hospital app moves to one list, every patient already booked on a session joins the doctor’s list in that session’s half (morning or afternoon), with no message sent. T-376 T-381
• LiveA session needs a doctor before patients go on it. A patient cannot be added to a session with no doctor; give the session a doctor first. T-376
• LiveChanging a session’s doctor moves its visits. The visits of that half-day move to the new doctor’s list. When a doctor is marked on medical leave and the session loses its doctor, the visits stay shown in that session (still on the sick doctor’s list) until a cover doctor is given; then they move to the cover doctor. Moving a session to the other half of the same day keeps its visits and notes the change in each patient’s log (“AM → PM”). T-376
• LiveTwo people changing the same day. A change made on the CCT Admin page or in Waypoint carries the list as it was when the person looked at it, and only what that person changed is applied. A visit someone else booked on that day in the meantime stays on the list; it is never taken off by a change made on an older copy. In Waypoint, with one session of the day open, a visit booked into the other half of the day stays in that half and does not join the open route. T-376
• LiveVisits not in any session are listed. A visit on a doctor’s list on a day when that doctor has no Home Medical or IHH session (for example, imported before the roster was made) is listed under the week on the CCT Admin page as “Not in a session”, with the day, the doctor, the patient and the booked time, and a button to the card. Give the doctor a session that day, or move the visit with Change visit…. T-376
• LiveA visit outside a session on a doctor’s leave day is flagged. In the “Not in a session” list under the week, a doctor who is on leave that day (all day, or the morning or afternoon) is marked “on leave …: move these visits”, and “Patients planned” counts these visits too. A visit cannot be added to a doctor’s list on a leave day from any screen or by an import: the database refuses it (T-346; checked again for an import on 28 Oct 26). T-381
• LiveNo visits on a public holiday or a weekend. A patient cannot be added to a doctor’s list on a public holiday, a Saturday or a Sunday, from any screen or by an import, as the roster has no session then; the refusal names the day (“… is a public holiday (Deepavali): no CCT visit is booked on it. Choose a working day.”). Taking a patient off such a day is always allowed. T-381
• LiveDates in dialogs read dd Mmm yy. Session details, Change doctor and Add slot show the day as “Tue 27 Oct 26”, as every other date on the CCT pages. T-381
• LiveRemoving a session, or resetting the week to the template, asks what happens to its booked visits. One question names the booked visits and offers both: Cancel them (each with a reason, the same check as cancelling one visit, all or none; the doctors are told) or Keep them on the doctor’s Visit List (nothing is cancelled; they show under the week as “Not in a session”, or in the doctor’s other session that day, until someone moves them). Nothing else is asked after it. A visit already past stays on the doctor’s list. A roster restore that removes and re-creates sessions cancels nothing: the visits stay on the doctors’ lists and show in the restored sessions. T-376 T-381
• LiveReset to template always asks first. Even when the week’s services already match the template, Reset names how many sessions and doctors it removes and waits for a yes; it no longer wipes the week’s doctors in one click. T-381
• LiveA public holiday shows a session that still has visits. A session saved on a public holiday whose doctor still has visits that day is shown on the holiday (“Public holiday · the doctor’s session still has N booked visits — move them”, with the patients to open), not hidden behind “— closed —”. Nothing can be added there; open the card and move the visit. T-381
• LiveChanging or clearing a session’s doctor: the reason comes chosen. When the session has booked visits, Clear doctor asks with “Session doctor cleared” already chosen and Change doctor with “Session doctor changed” (still changeable; “Other” needs a few words), so one click confirms. The checks come first: a doctor on leave that half-day is shown greyed as “On leave” (there is no override for leave), and a doctor already in another session that half-day is refused before any reason is asked. T-313 T-381
• LiveA CCT Admin can mark a CCT doctor on medical leave. “On medical leave” on a session is offered to full admins and CCT Admins. It files a 1-day MC as pending (for the usual approval), takes the doctor off that day’s CCT sessions (their visits are held for cover) and asks the doctor to apply: the “Medical leave — please apply” message comes from RosterEngine (the system), whoever marked it. A CCT Admin can do this only for a CCT doctor; anyone else is for an admin. T-381
• LiveA refusal says why. When the database refuses a session change because the doctor is on leave that half-day, or because an All Saints Home session has no patient list, the page shows its reason (for example “Dr X is on Annual leave that AM”) instead of “try again in a moment”. T-381
• LiveAuto-fill due places each overdue and due patient into a session with room (which session: the preferred doctor, then the shortest drive, below). It:
  • never books a patient twice: anyone already booked in a later week (looked ahead 90 days) or on a doctor's Waypoint day plan is skipped and named in the message;
  • leaves a session that has already started alone (AM after 08:30, PM after 13:30 today);
  • says what it placed and what it skipped, for example "No IHH session this week";
  • never picks a patient marked Admitted, On hold, Discharged or Deceased (dropping one on a session by hand asks first);
  • if it cannot read the other weeks, it places nobody and says so.
  T-332, T-280
• LiveFinding a patient. While you type a search, the "Match the selected session's service" box is ignored, so a patient is never hidden by a session you clicked earlier. T-332
• LiveAuto-fill also skips a patient with a "no date yet" visit that is due or upcoming. T-332, T-340
• LiveAuto-fill: the preferred doctor, then the shortest drive. Auto-fill chooses each patient's session this way (until 24 Oct 26 it was "the last doctor first"):
  • The preferred doctor first. If the card names a preferred doctor and that doctor has a session with room on or before the patient's safe limit (the due date plus the days the visit may move later: the card's own limits, else the default for its review frequency, section 3), the patient goes with that doctor, without asking.
  • Within 2 working days, no question. If the preferred doctor's first session is past the safe limit but at most 2 working days after another doctor's first session, the preferred doctor is still kept, without asking.
  • Held for next week. If the preferred doctor has no session this week but has one later that is inside the safe limit (or within those 2 working days), the patient is held for that doctor: nothing is booked, and the message says for whom and when.
  • Otherwise Auto-fill asks. The patient is listed under Auto-fill's message with the preferred doctor's first session and a suggested session with another doctor who can see them sooner. Nothing is booked for that patient until you press a button: Use the suggested doctor, Keep the preferred doctor and book late (past the safe limit, so only a clinician may choose it; anyone else uses Change visit… on the card, which sends the request), or Leave unplaced. Each answer is saved with its reason, who instead of whom and why, in the patient's log.
  • No preferred doctor on the card: the patient's usual doctor (most visits in the last 180 days, at least 3) is preferred where the drive is about the same; never asked about.
  • Shorter rounds, not even sessions. Among the sessions allowed, Auto-fill picks the one that adds the least driving to that doctor's round, trying the patient at every place in the round (the measured drive times on the cards, not a straight line). It keeps a session under 85% full where it can, but does not spread patients out to even the sessions: some sessions fill up, others stay light.
  • It also counts days after the due date, a visit too early for the safe window, the card's own AM / PM and days, a session with no doctor, and each doctor's usual areas for that half-day (learned from completed visits and the doctors' own day plans, by postal sector only; a doctor needs at least 5 completed visits before it counts).
  • It then puts each session it touched in the shortest driving order, and says for every patient why: the day, the doctor, "(preferred)" or "(usual doctor)", the stop number, the areas before and after, the minutes of driving it adds and how full the session is.
  • It never uses a session whose doctor is on leave that half-day (the message lists them), never books a patient who already has a future booking, never adds to a session that has started, and never changes a patient card.
  T-342
• LiveAuto-fill: four follow-ups and the request it raises itself. Auto-fill also does this:
  • Pick another doctor…. Beside Use, Keep and Leave unplaced, a patient Auto-fill asks about has Pick another doctor…: a list of this week's sessions with room for that patient (any CCT doctor, the right service, not started, the doctor not on leave that half-day), each saying how full it is and whether it is past the safe limit. The same checks as the other answers apply: past the safe limit only a clinician books it; for anyone else Auto-fill sends a request (below), never a silent booking.
  • The preferred doctor is told. When a patient is booked with someone other than the preferred doctor, Auto-fill also posts one short entry in the patient's comms log To the preferred doctor (it shows as NEW for them): "Your patient (initials and postal code) was booked with Dr (name) on (date, AM/PM) because (reason)". One entry per patient each time Auto-fill runs; none when the booking is with the preferred doctor.
  • After the preferred doctor: the usual doctor, then the last visiting doctor. If the card names no preferred doctor (or the preferred doctor is not the one booked), the usual doctor counts for the patient; with no usual doctor, the doctor of the most recent completed visit counts instead. Neither is ever asked about. The message says "(usual doctor)" or "(last visiting doctor)".
  • Leave is checked for every week a hold can reach. A patient is held for the preferred doctor only on a session whose doctor is not on leave that half-day, in any later week up to the patient's safe limit (half days count: the doctor is at work for the other half). If a week's leave cannot be read, nobody is held for a session that week, and the message says so.
  • Keep, book late, by someone who is not a clinician, sends the request. Auto-fill books the patient on the suggested session and sends the request to move the visit to the preferred doctor's later session (the same request, routing and log entry as Change visit…). The message says the visit is waiting for the doctor's answer; nothing moves until a clinician decides. A clinician's Keep still books late straight away, as a clinical exception.
  T-342
• LiveDrive times come from the app’s own route server. When a patient or a starting place is added, Waypoint and the phone measure the drive times to and from every other place on the list on the app’s own route server, reached only by a signed-in CCT member — no longer on the free public OSRM demo server abroad. What leaves the page: the postal code goes to OneMap (Singapore government) to find the block; the block’s map coordinates, with those of the other places on the list, go to the app’s own route server. Never a name, initials or unit number. The map’s route lines come from the same server. If it does not answer, the drive times are straight-line estimates and the page says so; nothing is sent to the public server instead. The phone apps installed from the App Store and Google Play keep using the public server until the next store build. T-351
• LiveEvery leg has its own drive time. When a route shows a leg whose patients have no drive times stored on their cards (a card from the HMS list or the New patient wizard), Waypoint and the phone ask the app’s own route server for that day’s stops in one go, show its times and distances, and keep them on that device. Until it answers, or if it cannot, each leg is a straight-line estimate and the page says so — never the same 10 minutes for every visit. Optimise waits for the measured times before it orders the visits (phone: store build seq 23). T-388
• LiveEach doctor's routes are recorded. For every doctor, day and half-day the app keeps the order of the areas visited (the first two digits of the postal codes, nothing about the patient): from completed visits in the order they were tapped, and from the doctor's own Waypoint day plan. Only CCT staff can read the summary; Auto-fill uses it to keep patients on a doctor's usual round. T-342
• LiveThe calendar: details on hover, time and order on the right. On the CCT Admin page, pointing at a visit in the week (or at its initials) shows what it is and why: the visit type (for example "Urgent / subacute review"), why it is planned (a provisional schedule agreed on a date, the review frequency and how due it is, or no visit on record yet), its place in the doctor's round and its time (the expected arrival, and the booked time if one was set). The time and the order are not printed on the calendar itself (it would be crowded): the session panel on the right lists each visit in order with its number, arrival time, booked time, type and why. The arrows that change the week sit beside the week's dates. In Waypoint, arrows beside the session's day move it to the previous or next working day (weekends and public holidays are stepped over). T-349
• LivePatients under each doctor. The week can list each session's patients (initials and postal code, in visit order) under the doctor's name: on a wide screen automatically, on any screen with "Show patients". T-308
• LiveNo session for a doctor who is on leave that half-day. A doctor cannot be put on a CCT session, given patients in one, or have a session dragged onto a morning or afternoon they are on leave. A full day of leave blocks both the morning and the afternoon; a morning off blocks only the morning; an afternoon off only the afternoon (on a leave of several days, a half-day mark on the first day is the morning off, on the last day the afternoon off). "On leave" is the leave the CCT week planner shows: approved leave, and medical, hospital or sick leave still waiting for approval; a "no on-call" or "no weekend" day is not leave. While you drag, a half-day the doctor is away is not a drop target and says why ("Dr X is on leave that morning (AM), 27 Oct 26 (Annual leave). Choose another doctor or another session."). The database refuses it on every path: the CCT Admin page, Solve CCT, pin or assign, moving a session, changing a visit's doctor, a doctor's day in Waypoint, and the phone. There is no override. A session that was planned before the leave was filed is never moved or deleted: it is marked "Doctor on leave — needs cover" on the CCT Admin page (and listed on CCT Performance) until someone covers it. Removing or re-ordering the patients already in such a session (or in that doctor’s day in Waypoint) is always allowed; only adding a new patient is refused (a bug fix: the database had refused a re-order or a removal there; fixed 24 Oct 26). Restoring an old roster snapshot is refused as a whole if any restored session would fall on a doctor's leave. Solve CCT reads leave the same way (a half day no longer takes the doctor's other half; a no-call day no longer takes the day). T-346
• LiveNo patients in an ASH (All Saints Home) session. An ASH session is a half-day at the nursing home with no patient list, so no patient can be planned into one: not by dragging a patient onto it, not by Auto-fill, not by “Pick another doctor…”, not by the “Back home” booking on the Admitted to Hospital list, and not by Change visit… or moving a whole session. A session that has patients cannot be changed into an ASH session. While you drag, an ASH session is not a drop target and says why: “ASH (All Saints Home) sessions have no patient list — choose a Home Medical or IHH session.” The database refuses it on every path, in the same words. Auto-fill looks only at Home Medical sessions for a Home Medical patient and IHH sessions for an IHH patient (before this, it treated an ASH session as fitting any patient). Patients planned into an ASH session before this rule are never moved or deleted: the session is marked “ASH — no patient list: move these patients” on the CCT Admin page until someone moves them (taking them out, or re-ordering them, is always allowed). Days before today are a record and are left alone. Waypoint’s day planner saves to the doctor’s day, not to a roster session, so it is not affected. T-340 D4

Words, dates and the look of the CCT pages

• Live"Visit length" is the one word for how long a visit takes: the CCT Admin page's stops say "visit length 30 min" and Waypoint's Session planner says "Visit length" (both said "consult" before). The phone app still says "Expected consult time" until the next store build. T-340 C9, T-330
• LiveWaypoint's week controls are on the right. In My week, "Show patients", the week arrows and Today sit on the right of the title, as on the CCT Admin page. T-340 C10, T-330
• LiveIHH is written "IHH (Palliative)" where its full name is shown (the service on a card, on Waypoint and on the phone); a short tag still says "IHH". T-340 C11, T-330
• LiveDates on a patient card and in the communication log read dd Mmm yy, with the weekday in front where the card shows it: "Tue 13 Oct 26", and "Fri 23 Oct 26 · 13:58" for a message. Waypoint and the phone app (the phone's store apps at the next store build). T-340 C12, T-330
• LiveOne look across the CCT pages: the same font pair (Fraunces for headings, Inter for text, JetBrains Mono for figures) and the same primary blue on the CCT Admin page, Waypoint and the phone's CCT screens. T-340 C13, T-330

Visit length and time

• LiveVisit length. Until 24 Oct 26 the card held one length that every visit used; now each visit has its own (next rule). T-321, T-324
• LiveA length per visit. A first visit is 60 minutes and a routine visit 30 minutes unless changed. Any visit can be 15, 30, 45, 60, 75 or 90 minutes. An odd length already on a card (say 35) is kept and shown as "custom". Every length change is logged. The phone uses each visit's own length too (the store apps need a new build). T-324, T-325
• LiveSet time. The time of a booked visit can be set on the same day and session. It needs a reason, is not counted as a reschedule, and is logged ("time set 10:30"). T-323
• LiveSet time asks a reason only for a confirmed visit. When the nurse’s call has confirmed the visit (or the visit is marked “Family confirmed”), Set time says the patient or family were told a time and may expect it, and asks why; any other visit’s time is saved at once and logged (old → new, “not asked: the visit was not confirmed”). The same on the card’s Edit of a planned visit. The database checks the call itself. As drags on the phone (T-361). Waypoint and the CCT Admin page. On the phone too (phone: store build seq 23): its Set time row shows a Reason box only for a confirmed visit. T-381

Visits with no date yet, and provisional schedules

• Live"No date yet." Plan a visit without a date by choosing one of five shortcuts: within this week, next week, back to the regular frequency, next month, in 3 months. Weeks are always Monday to Friday. The card shows its state: Due now, Planned, Met, Lapsed or Upcoming. T-286
• LiveGiving it a date closes it. When the visit is planned on a day inside that range ("Plan this visit" or Set time), the "no date yet" row is closed and the log says so. T-326, T-323
• LiveProvisional schedule at the end of a visit. The doctor records what was agreed with the patient: a date (and time), or "in N weeks / months". A date stays provisional until the manager or doctor puts it on a plan. The doctor can also make it the patient's regular review interval. T-299, T-296
• LiveThe review due date comes from, in order: an open provisional schedule or "no date yet" visit; else the last completed visit plus the review frequency; else the referral date plus the review frequency; else the booked day. T-309

New patients

• LiveAdding a card in Waypoint ("+ Add patient") is for admins and the CCT Admin role. Every card is shared with the whole CCT team on every device. T-245, T-284
• Live"New patient" on the CCT planning page. A manager makes the card (initials, postal code and unit only, plus contact and referral). Its safety limits read "awaiting clinician" until a clinician sets them. T-309

Admitted to hospital: the holding list

• LiveMarking a patient Admitted to hospital frees their visits. A patient is marked Admitted to hospital in any of three ways: the card's status, a call logged on the card as "Patient admitted to hospital", or a visit cancelled with that reason. Each time, a dialog first names every visit still booked ahead (day, time or AM / PM, doctor) and nothing changes until you confirm. Then: the card is marked Admitted to hospital (one entry in its log, with the reason); every visit ahead is cancelled with the reason "Patient admitted to hospital" (one entry each in the log, the doctors told, as for any cancellation); and the patient goes on the Admitted to Hospital list. The usual rules still apply to each visit: a patient whose limits say "no cancel" needs a clinician (a request is sent and the visit stays booked until it is decided), and a doctor without the CCT Admin role cannot release another doctor's visit of a patient who is not theirs (it stays booked and the dialog says so). T-349
• LiveThe call-again date. Every patient on the list has a date to call again: 2 weeks from the day they were marked unless changed in the dialog or on the list (any day from today to 180 days ahead). Logging a call on the card (anything but "No answer" or "Wrong number") while the patient is still in hospital moves it to 2 weeks after that call, unless a later date was already set. The patient card shows the date, read only. T-349
• LiveThe Admitted to Hospital page. A sub-tab of the CCT Admin page, beside Roster and Performance, with the number of patients on it. One row per patient: initials and postal code, service, doctor, admitted since (the day it was marked in the app; the hospital admission date itself is not known to the app), the last call (date, outcome, by whom) and the call-again date. Sorted ready for next call by default: patients back home first, then the call-again date, overdue first, then the soonest; it can also be sorted by admitted since, patient or doctor. From a row: open the card, log a call (the card's own Log a call), change the call-again date, release visits still booked, or mark the patient back home. T-349
• LiveBack home. "Back home" puts the card back to Active (one entry in its log) and suggests a visit in the next 2 weeks near the visits already booked: Auto-fill's own choice (the preferred doctor first, then the session that adds the least driving to a doctor's round, the card's safe limits and AM / PM in the score), never a session that has already started and never one whose doctor is on leave that half-day. You can book the suggestion, choose any other session on the Roster, or plan any date and time on the card. The patient stays on the list, marked "Back home — to book", until a visit is booked (or done) on or after the day they came home. T-349
• LiveEvery way of setting the status keeps the list right. A card marked Admitted to hospital anywhere (the phone included) is on the list; a card set back to Active becomes "Back home — to book"; a card set to On hold, Discharged or Deceased, or archived, leaves the list. Only the three ways above, on the CCT Admin page and in Waypoint, release the visits ahead after the dialog; on the phone the status alone changes (its visits are released from the list's "Release…" button) until the next store build. Auto-fill never books a patient marked Admitted to hospital. T-349

Deceased, Discharged and On hold

• LiveDeceased or Discharged releases every booked visit. Marking a patient Deceased or Discharged (on the card in Waypoint, or on the card opened from the CCT Admin page) opens one dialog that names every visit still booked ahead, whichever doctor holds it. Nothing changes until it is confirmed. Then every one of those visits is released (cancelled with the reason "Patient deceased" or "Discharged from CCT care", one entry each in the patient’s log); a death or a discharge does not wait for the patient’s limits or for the doctor who holds the visit. An open visit with no date is closed. The preferred doctor gets one New entry, and every doctor who held one of those visits is copied. Any other way the status is set (an older phone, for example) releases the visits too. On the phone the card’s Status opens the same sheet, naming the same visits (phone: store build seq 23); the Visit List and the Patients list show a card’s status when it is not Active. T-381
• LiveDeceased: the reason is Death; date and cause are optional. The patient comes off the list as a discharge with the reason "Death"; no typed words are needed. The dialog offers the date of death and the cause of death; neither is required. Discharged still needs a few words saying why. On the phone too (phone: store build seq 23). T-381
• LiveAdmitted to hospital on the phone (store build seq 23) frees visits as Waypoint does. Setting a card’s Status to Admitted to hospital on the phone opens one sheet: the booked visits this person may release are named and released (each “Patient admitted to hospital”), any that need a clinician are named (a request each, still booked until decided), and another doctor’s visits are named as kept; a call-again date (2 weeks unless changed); the patient goes on the Admitted to Hospital list. A database without this step: the status is saved as before. T-381
• LiveOn hold needs a reason and a date to reactivate. Putting a patient On hold asks why (Overseas travel, Patient or family asked for a break, Staying elsewhere for now, or Other with a few words) and a reactivation date (30 days ahead unless changed; up to a year). The visits booked before that date are released; visits on or after it stay. The patient is listed on the Admitted to Hospital page as On hold; on the reactivation date the card switches back to Active by itself (a daily job at 00:10, watched like every scheduled job), with one log entry “On hold ended — reactivation date reached”, and the Admitted to Hospital page lists the patient as “On hold ended — call to book” until a visit is booked. "Resume and book" sets the card Active earlier and suggests a visit, as Back home does. On the phone the card’s Status → On hold asks the same reason and date and names the visits released and kept; Status → Active resumes it (phone: store build seq 23). T-381
• LiveWho puts a patient On hold, and who brings them back. Only the CCT Admin or the patient’s own doctor (the card’s Preferred doctor) can put a patient On hold, change the hold’s date or reason, or set an On hold patient Active again — the same people as for Deceased or Discharged. Another CCT doctor still sees the card and can change its other details. In Waypoint the card’s Status does not offer On hold (or Active, for an On hold patient) to anyone else, and “Resume, then book” says who resumes; on the phone, Save says so (phone: store build seq 23); the database refuses anyone else on every screen, an older phone included. The daily job that ends a hold on its reactivation date is not affected. T-385
• LiveA patient who is not Active is not booked. A Deceased patient is never booked (the database refuses it from any screen or import). A Discharged, Admitted or On hold patient is not booked either: the screen offers the way back in one tap (Discharged: the CCT Admin sets the card Active again, a re-referral; Admitted: Back home; On hold: Resume), then books. This replaces "Add anyway" on the CCT Admin page and on Waypoint, and Waypoint’s Plan a visit now asks too. On the phone, Not at home does not open Change visit for a Deceased or Discharged patient, and says why; an Admitted or On hold patient’s kept visit can still be moved (phone: store build seq 23). T-381

3. Changing a visit

Every change (move, cancel, change of doctor) goes through one checked dialog that asks for a reason and shows which days are safe.

• LiveThe safe window. A visit may move from (due date − "earlier" days) to (due date + "later" days). In the date picker safe days are green with a ✓, unsafe days red with a ✗. Weekends and public holidays are not offered. T-311
• LiveDefault limits by review frequency. These are placeholders, waiting for the clinical team to confirm them. Read from the test database on 24 Oct 26 (none confirmed yet):

  Review frequency	Later (days)	Earlier (days)	Reschedules in 90 days
  First visit	2	0	1
  Urgent	2	0	1
  Weekly	3	2	2
  Monthly	7	7	2
  Quarterly	14	14	3

  Only a clinician can change these defaults. T-309, T-312
• LiveLimits for one patient are set by a clinician on the card (Visit preferences › Safe changes): later and earlier 0 – 60 days, 0 – 20 reschedules, an optional note, and "no cancel" (cancelling this patient always needs a clinician). Managers can read them but not change them. T-309, T-311
• LiveThe reschedule cap. Once a patient has had the allowed number of reschedules in the last 90 days, the next one needs a clinician. T-311
• LiveA cancel, then a new booking, counts as a reschedule. Booking a patient whose visit was cancelled in the last 14 days counts as one reschedule toward the cap (logged “Booked again after a cancel”). At the cap a clinician may book it (marked as an exception). When anyone else books it at the cap, it becomes a request to a clinician: the patient is not booked, the screen says so (“Not booked: sent to … to decide”), and the request carries the day, the doctor and the time asked for. It goes to the doctor of that visit (then the usual doctor, the CCT lead, the escalation backup, as every request), and shows in the requests waiting for a clinician. Approve books it, with the time asked for, as the clinician’s exception (the day’s checks still apply: leave, a holiday or weekend, the patient’s status); Decline leaves it unbooked and tells the person who asked. A second try while one is waiting makes no second request. A clinician who books the patient meanwhile closes the request (the person who asked is told). An older phone or page that does not ask for a request is still refused, in the database’s words. There is no safe-window check on the new booking. Moving a visit, and cancels for Deceased, Discharged, On hold, Admitted or Replaced, do not count this way. Every screen, the phone included, because the database does it. T-381
• LiveWhat needs a doctor and what does not.
  • Inside the safe window, under the cap: done at once by a manager or a clinician.
  • Outside the window, over the cap, or cancelling a "no cancel" patient: needs a clinician.
  • A change of doctor never needs a clinician (a reason is still asked).
  T-311
• LiveA manager's change that needs a clinician becomes a request. Nothing moves. The screen says who it was sent to ("Sent to Dr X. Nothing has changed yet."). Who it goes to is the next rule. T-311, T-312, T-338
• LiveOnly clinicians approve or decline — and the person a request was escalated to. A clinician approves (as a clinical exception) or declines; both are one tap and a few words are optional — an approval with no words is recorded with the reason "Approved" (T-350). When a request was escalated (next rule) to Dr Roland or Dr Kevin Awyong, that person may approve or decline THAT request even if not set up as a CCT clinician — no other request. The manager sees the answer, the doctor's name and reason under "Answered by a doctor". T-311, T-338
• LiveOnly clinicians override. A clinician who makes an out-of-limit change sees a warning, gives a reason and clicks to confirm; it is applied at once and flagged as a clinical exception. A non-clinician can never override. T-311, T-338
• LiveAn overdue visit may move EARLIER without a doctor. Anyone with the CCT Admin role may move an overdue visit to an earlier date (closer to its due date) without asking a doctor. The reschedule cap and "no cancel" still need a clinician. Operations staff still cannot change visits. The log says it was allowed without a clinician, and these days show green in the date picker. T-336
• LiveWho a request goes to, and leave escalation. For a request from a non-clinician:
  • first the doctor of the visit, else the patient's usual doctor (from the card); the usual doctor is copied;
  • if that doctor is on leave today or on the day of the visit (or no CCT doctor is named), it goes to Dr Roland (the CCT lead), and the original doctor is copied so they see it on their return;
  • if Dr Roland is on leave too, it goes to Dr Kevin Awyong (the escalation backup);
  • if everyone in that chain is on leave, it still goes to Dr Roland, and the entry says nobody was available;
  • "on leave" is the leave the CCT week planner shows (approved leave, and a pending MC / hospital / sick leave); a half day does not count (the doctor is at work for the other half); "no on-call" and "no weekend" days are not leave;
  • the request in the log and the Change dialog say who it goes to and why ("Dr X is on leave until 30 Oct 26 — this will go to Dr Roland, the CCT lead.").
  Who the CCT lead and the escalation backup are is a setting, not built into the app. T-338
• LiveYour own visits only. A doctor without the CCT Admin role moves, re-assigns, cancels or times only a visit on their own day or session, or a visit of their own patient; a whole session only when it is theirs. A visit of another doctor’s patient on another doctor’s day shows "Another doctor’s visit: the CCT Admin or that doctor changes it." T-341
• LiveMoving a whole session. "Move session…" (or dragging a session to another day / AM-PM) moves every patient in it as a group. A preview shows each patient's verdict (inside the limits, needs a doctor, cannot move, and why). You can choose "all or nothing". Each patient is checked, logged and their doctors told. T-314
• LiveA reason is always captured where a person acts. Dragging a booked patient to another day asks (Move / Add another / Do nothing) and a move asks for a reason. A first booking asks nothing. Editing a card asks for a reason (section 1, T-343; this sentence said “optional” until 25 Oct 26). T-311, T-313, T-343
• LiveMore than one visit booked by hand. A patient may have more than one visit booked, for example an ad hoc review today and the routine review 2 months later. When a visit is booked by hand (dragging a patient onto a session on the CCT Admin page, the Session planner in Waypoint, "Plan a visit" on the card) and the patient already has a later visit, the app asks first: keep both (book this visit as well), or bring the later visit forward to this day instead (the checked Move dialog opens on that visit with the day filled in: the safe limits and a reason apply). On the CCT Admin page an earlier visit is offered as "Move" in the same question. Auto-fill keeps its own rule: it never books a patient who already has a future booking. The database itself has no one-visit rule; before T-349 the question was skipped on a week still from the CCT Set Up template, and Waypoint and the card never asked. T-349
• LiveAny future appointment is named, with three answers. Booking a patient by hand (CCT Admin page, Waypoint’s Session planner, the card’s Plan a visit) who already has a LATER visit booked — however far ahead (before, only the next 62 days were looked at on the CCT Admin page) — names every later visit and offers exactly: Cancel the future appointment — with more than one, Cancel the future appointments (N) — (this visit is booked first, then ALL the later visits are cancelled together, each “Replaced by another visit”, no typing; every cancel is checked first and if one would be refused or needs a clinician (the patient’s limits), none is cancelled, everything stays, and the page says which visit and why; a booking that went to a clinician as a request is not a booking, so nothing is cancelled), Cancel this booking (keep the future appointment), or Keep all appointments. This replaces Keep both / Bring forward / Do nothing. On the CCT Admin page a visit on the same day or before is still offered as Move (a reason and the limits, as before). On the phone, Change visit (after Not at home) asks the same when the new day is before another booked visit; Enter means Keep all appointments (phone: store build seq 23). T-381
• Live"Change visit…" from the card. A visit held by a roster session has "Change visit…" on the card's Visits row, and the card line on the CCT Admin page says the next visit ("Next: Tue 3 Nov AM · Roland — Change…"). Both open the same checked dialog for THAT visit, in any week (move or cancel; the limits, the reason, requests and notices are unchanged). The dialog has a time of day on the new day ("2pm", "2.30 pm", "14:30"), so "Thursday 2 pm" is one change; a time outside the session (AM 08:30–12:30, PM 13:30–17:30) is said, not refused (the doctor must agree). A visit that only a roster session holds keeps that time on the new day (a day-plan stop holds it). Set time also takes "2pm" and warns outside the session; a stop whose route arrives more than 30 minutes before the booked time says so. T-333
• LiveVisit outcome on the phone. On the phone's Route, a stop's button is "Visit outcome…" with three choices. Completed: as before (the visit is recorded and the end-of-visit sheet asks about the next visit). Not at home: the visit is recorded as not done ("Missed · Not at home", for the next doctor to read) and the phone goes straight to Change visit: pick the next day (and a time if agreed); the database checks it before anything is saved, with the same safe limits, the leave block and the request to the doctor as everywhere else. Running late: one entry in the patient's log for the CCT Admin team, with the expected time. Telling the family or the next patient from the phone is planned, not built. T-350
• Live“Route” is now “Visit List” on the phone, and a visit has four outcomes. The tab reads Visit List; Stats sits at the bottom of it instead of being its own tab. Each stop’s ▲▼× row is gone: the order is changed by dragging the ≡ handle only, and a visit comes off the day through Visit outcome → Cancel (the fourth choice, with a reason: T-368). Reverse and Clear session are gone from the phone. T-354, T-363
• LiveDragging a visit on the phone. On Today’s visits and the Visit List, hold the ≡ handle, drag, and let go: the visit follows the finger, a line shows where it will land, and it moves the moment it is released; the change is written to the patient’s communication log (the moved visit’s new time, with the reason “Other” for a plain drag). If the database refuses it, the visit goes back and the phone says why. A visit the nurse’s call has confirmed warns first (“may not be home at the new time”) and asks why from the time-change reasons before “Reorder anyway”; its log entry says “visit was confirmed, but rescheduled by user”. T-355, T-357, T-361
• LiveOptimise works around confirmed visits. A visit the nurse’s call has confirmed keeps its booked time; Optimise re-orders only the other visits, around it (the day waits for a confirmed visit if it would arrive early). When there are confirmed visits, pressing Optimise first says which ones keep their time (“Confirmed visits keep their booked time: TSK 10:00”) with Proceed / Cancel. If the confirmed visits cannot all be kept (two too close for the drive between them), nothing is changed and the message says which clash and by how much. Optimise also runs on its own when a visit comes off the day (cancelled, or moved to another day), and says “Visits optimised”; the doctor may still drag visits afterwards. A visit whose time moves by 15 minutes or more gets one entry in its communication log; smaller shifts are not logged. Live on the phone’s Visit List and Waypoint’s Session planner (where adding a visit also re-optimises). Not yet on the CCT Admin page, which orders roster sessions rather than the doctor’s day plan — that is an open decision for Kevin. T-362
• LiveOptimise runs at once. No Proceed / Cancel question any more: Optimise (and Reverse) run straight away and the message says which confirmed visits kept their booked times (“1 confirmed visit kept its booked time (TSK 10:00)”). The rule that confirmed visits keep their time stays. Waypoint and the CCT Admin page. On the phone too (phone: store build seq 23). T-381
• LiveThe phone: the morning and the afternoon are two routes. The Visit List shows a Morning (AM) route and an Afternoon (PM) route, each from its own start (the morning from the start chosen on the session card, 08:30 unless changed; the afternoon from 13:30) and back to its end place. A visit’s half-day is the one-list rule: its booked time (before 13:30 = morning), else the session it was booked into, else the session chosen on the session card; a visit with no time says AM or PM. Optimise, a drag and the times that follow them stay inside each half: an afternoon visit is never given a morning time (the database refuses that too). Phone: store build seq 23. T-381
• LiveThe phone records a visit under the signed-in doctor. The session card’s Clinician box is fixed to the doctor signed in on the phone, as on Waypoint; Completed, Not at home and a logged visit are recorded under that name. Before, the box could be changed and a visit was recorded under another doctor’s name. Phone: store build seq 23. T-381
• LiveThe phone changes a day by the difference. When the phone changes a doctor’s day (a drag on the Visit List), it says what it saw, so the database applies only the difference and keeps a visit someone else booked meanwhile, as Waypoint and the CCT Admin page already do. Phone: store build seq 23; the apps already in the stores still replace the day. T-376, T-381
• LiveDragging a visit on the phone (store build seq 23) asks why only if it is confirmed. As Set time: moving a visit the nurse’s call has confirmed asks why; moving any other visit asks nothing and is logged “not asked: the visit was not confirmed” (it used to be logged as “Other”). T-381
• LiveBooked times follow the day. After a visit is dragged or the day is optimised, the booked time of every visit that is not confirmed becomes its new expected time (logged only when it moves 15 minutes or more). A confirmed visit keeps the time agreed with the patient. T-364
• LiveCancelling a visit on the phone needs a reason. Visit outcome → Cancel asks why (Patient declined, admitted to hospital, deceased, moved out of area, duplicate booking, clinical decision, Other with a few words) and goes through the same checked change as Waypoint: the safe limits, one entry in the patient’s log, and a request to a clinician when the limits say cancelling needs one. T-368
• LiveSet time and length on the phone. A Route stop can set the time ("2pm", "2.30 pm" or "14:30") and the length (15 to 90 minutes) of that one visit, with a reason, as on Waypoint; a time outside the AM (08:30–12:30) and PM (13:30–17:30) sessions is said, not refused. The route's session card has AM 08:30 and PM 13:30, the same session clock as the other CCT pages. The patient card on the phone has the same fields as Waypoint (status, housing, a second contact, preferred doctor, days and time, the window the family can receive us), with the same rules: any CCT doctor may change it and is asked why; only the CCT Admin sets the preferred doctor; only the CCT Admin or the patient's own doctor takes a patient off a list. T-350
• LiveNavigate from the phone. On the phone's Route, each stop not yet done has Navigate: choose Waze, Google Maps or Apple Maps (Apple Maps on an iPhone only) and the app starts directions to that stop. "Navigate the rest of the day" sends the stops not yet done, in route order from the next visit, to Google Maps or Apple Maps (Waze takes only one place at a time); a day of more than 10 stops is split into parts of 10 (stops 1–10, 11–20, …) — open the next part when you reach the end of one. Only the postal code leaves the phone, as the word Singapore and the six digits: never the patient's name, initials, unit number or any label. Once sent, the trip is kept by that app under the doctor's own account (Google and Waze keep trip history; Apple says it does not tie it to the account). Each doctor's app is remembered on that phone and offered first; tap another to change it (no account setting). The iOS and Android apps offer only the navigation apps installed on the phone, from the next store build; the web phone page (/m) offers them all. Whether each app finds the right building from a postal code alone has not yet been tried on a real phone. T-350 #4

4. The communication log

• LiveEntries. Each patient card has Internal communications: date and time, author, message. Entries cannot be edited or deleted. A reply makes a thread, at most 4 levels deep. Each message shows From, To, CC, date and time, the message, and pills for why you see it. T-279, T-283, T-287, T-288
• LiveTo and CC. Send to "any doctor", to a named doctor, or to a role (Nurse, Therapist, MSW, Admin, Operations). Copy (CC) up to 8 team members by name and / or roles. Roles other than doctors are labels until those staff have logins. T-282
• LiveAll roles can post to the communication log. Anyone on the CCT team may write in it, whatever their role (Doctor, Nurse, Therapist, MSW, Admin or Operations); someone not on the CCT team is refused. The roles are one list kept in the database, and the To, CC and filter lists in Waypoint are read from it. Home Nursing and Home Therapy are already on the list, switched off: switching one on (with Kevin's word) makes it appear in To, CC and the filter with no change to the apps. A role that is switched off cannot be written to or copied. Note: once switched on, a Home Nursing or Home Therapy member counts as clinical for the change rules, because the rule is "every role except Admin and Operations". T-340, T-279
• LiveUrgent. An entry can carry a red Urgent flag. An urgent entry addressed To a named doctor is also pushed to that doctor’s phone (see Urgent push). T-279, T-284, T-335
• LiveNEW and "seen on". Each entry is NEW for a doctor until that doctor has seen it, even if others have; then it reads "seen on dd/mm/yy". Filters: New, Direct to Me, My Patients (I am the usual doctor), My List (seen by you in the last 30 days or planned with you in the next 30). A patient is in one of the two lists, not both. T-285
• Live"My Patients" means the same everywhere. In the communication log (Waypoint and the phone: the My Patients and My List filters, what counts as NEW and the receipts) a patient is yours when you are the preferred doctor, or the usual doctor (most completed visits in the last 180 days, at least 3, no tie), or the next planned visit is with you — the same meaning as the question box. My List stays: seen by you in the last 30 days or planned with you in the next 30, and not already in My Patients. T-340
• LiveMy Patients shows every message about your patients. In Waypoint and on the phone, the My Patients filter now lists every message about your patients, whoever it was sent to (for example a nurse writing to the CCT Admin about your patient). One you have not read is marked NEW there, from the last 30 days. The New filter and the red count on Messages are unchanged: they still count only what is meant for you (To you, a copy to you, or to your role). T-359
• LiveCommunications Log on Home. On the Home page (the phone app and the desktop RosterEngine) a “Communications Log” section appears just above “Your upcoming” when something is new. It shows counts only: “N new messages to you” — new messages addressed to you by name (not a copy to you, not a message to your role) — and, for a CCT doctor, “N new messages about your patients” — unread messages about your patients, whoever they were sent to, from the last 30 days. Both count messages a person wrote; the automatic entries (such as “Visit booked”) are not counted, as Messages hides them by default. An urgent one is counted in red. Tapping a line opens Messages on Direct to me / My patients (on the desktop, Waypoint’s Communications). Reading the message (Mark read) takes it off the count. The “about your patients” line has a switch in the phone app’s Settings → Notifications (“New messages about my patients”): on by default, saved to your account so it applies on the desktop too. The section is not a push notification. T-359
• LiveSystem entries. The app writes short system entries for changes, requests, calls and limits. They are dashed and grey, and "Hide system entries" hides them (remembered). Requests waiting for you are pinned at the top with a "N requests waiting, jump to it" strip. T-311, T-312
• LiveEvery doctor involved is told. When a visit moves or changes doctor, the doctor it leaves, the doctor who receives it and the usual doctor all get a notice; the manager gets the doctor's answer. Any change to a card or a visit leaves an entry saying who did it (a named person, or "system"). T-312, T-313
• LiveRead receipts. A doctor presses Acknowledge on a system entry; the log records "Log read receipt by Dr X on dd Mmm yy, hh:mm". To disagree, the doctor starts a new thread with the manager ("Disagree – start a thread"). T-312
• LiveEvery decision point is logged. Each request (with where it went and why), approval, decline, clinical exception, earlier move of an overdue visit, move, cancel, time or length change, change of doctor, limit change and Auto-fill booking writes exactly one clear entry: who, when, what, why. Move session writes one entry per patient and ONE notice for the doctors (To one, the others copied); a session’s doctor, half-day or day changed through the session itself (Change doctor, On medical leave, Solve, the grid) writes one notice per patient. A request that is overtaken (its visit moved, re-assigned or cancelled by someone else) is closed, and that change's own entry says so and copies the person who asked. T-338
• LiveThe communication log on the phone. The iOS and Android apps have a Messages view (its button shows how many entries are NEW for you, red when one is urgent) with the same filters as Waypoint (New, Direct to me, My patients, My list, All) and "Hide system entries". Each message is one card: Urgent / New / Seen pills, the date and time (dd Mmm yy · HH:MM), the patient's initials (tap them to open the patient's card on its Log tab), From, To and CC. A patient card has Details and Log; the Log is newest first and says who has seen each entry. You can reply, write a new message (To one person or role, CC others, Urgent), mark an entry read, and Acknowledge a system entry sent to you. The phone uses the same database calls as Waypoint, so both show the same thing. It needs a connection; the phones get it with the next store build. T-334, T-350
• LiveOn the phone, a request is never hidden. When system entries are hidden (the default), the phone’s Messages still shows every open Approve / Decline request addressed to you, pinned at the top; the other system entries stay hidden. Waypoint is unchanged: with system entries hidden its log leaves requests out and the banner “N requests waiting · Jump to it” leads to them. T-365
• LiveApprove or decline a request from the message. A request for you (a visit change past the safe limit, T-338) shows in the log with two buttons. Decline is one tap and Approve is one tap: no reason is asked for either, and a few words are optional. An approval with no words is recorded with the reason "Approved" (it is still a clinical exception, flagged in the log). The decision goes back to the sender and into the log exactly as it does from Waypoint, which has the same two buttons on its request; who decides and where a request goes (T-338) do not change. T-350, T-338
• LiveUrgent push. An Urgent entry addressed To a named doctor is also sent to that doctor's phone as a notification, through the same notification service the app already uses; tapping it opens the message. A request that needs the doctor's decision is sent the same way. The notification says only who it is from, never the patient or the message (it passes through Apple / Google). It reaches only doctors with the app and notifications on; urgent ones also come in the quiet hours. An entry to "any doctor" or a role is not pushed. T-335
• LiveOnly “admitted” and “a concern” calls reach the doctor’s phone. A logged call whose outcome is “Patient admitted to hospital” or “A concern” is urgent and pushed to the doctor’s phone, at any hour. “Wrong number”, “wants to reschedule” and “wants to cancel” are still flagged and NEW in Messages, but are not pushed. T-381
• LiveEvery “new” number counts what its list shows. With “Hide system entries” on, Waypoint’s Communications count and each card’s count leave the system entries out, exactly as the list does; switching it changes the counts at once, and the count no longer jumps between two numbers. With it off, everything NEW is counted, as before. The phone does the same: its Messages count and a card’s Log count leave hidden system entries out (an open request is still counted, as Messages still lists it) (phone: store build seq 23). T-381
• LiveA cleared doctor is written in words. When a visit’s doctor is cleared (for example On medical leave) and the visit waits for cover, its entry reads “Dr X → no doctor yet (awaiting cover)”, not “Dr X → ?”. T-381
• Live“Seen on” reads dd Mmm yy; Waypoint fits a phone. In Waypoint an entry you have read says “seen on 20 Oct 26” (it said 20/10/26), as the phone does. On a phone-width window Waypoint’s tabs wrap onto two lines, so the Communications count and “N requests” are always in view; “My week” no longer carries a NEW badge. T-381

5. Calls

• LiveNo confirmation call for a Deceased or Discharged patient. "☎ Calls" never lists a patient marked Deceased or Discharged, so no family is rung to confirm a visit that will not happen. T-381
• LiveConfirmation calls. Before a doctor goes out, a manager rings the patient, usually 1 – 2 working days before (the call window is a setting of 1 – 5 days; it is 2 today). "☎ Calls" lists who to ring, tomorrow first. T-310, T-312
• LiveLogging the call. Outcomes: Confirmed, No answer, Wants to reschedule, Wants to cancel, Wrong number; and who you spoke to. "Wants to reschedule" opens the Change dialog on that visit. Doctors see the result on each stop in My week (green = confirmed, ⚠ = visit soon and not confirmed, red = wants a change). T-310
• Live"Log a call" on the card for any call, in or out (including calls the patient or family make to us): the outcome (information given, visit confirmed, wants to reschedule, wants to cancel, admitted to hospital, a concern for the doctor, no answer, wrong number, other), who called or answered, a note. It writes one row and one system entry in the card's log, to the doctor of the next visit (else the usual doctor), the usual doctor copied; "wants to reschedule / cancel", "admitted", "a concern" and "wrong number" are flagged. After "wants to reschedule / cancel" the card offers the checked dialog for the next visit (one click; nothing is changed for you). Admins, the CCT Admin and CCT clinicians may log a call; every CCT person can read them. T-333

6. The question box

• LiveAsk the patient cards in plain words, typed or by voice (for example "patients not seen for more than 2 months"). The cards sort and filter to the answer. T-318
• LiveRule-based, no AI model at answer time. The box follows written rules. When it does not understand a word it says which word and offers what it can do; it does not guess. A small AI model was tested and not used. T-318, T-329
• LiveIt sees what the app sees. It can answer from the cards, visits, sessions, the change log, requests and the communication logs, reading only what your own sign-in can already read. Message and reason text is never sent to an AI model. T-331
• Live"Urgency" means how overdue the review is: most overdue first, then weekly before monthly before quarterly. Such an answer is marked "check this". T-321
• LivePer-doctor figures stay open to everyone who can use the box (a team of 3 doctors). Revisit if the team grows. T-328
• LiveMove, cancel or time ONE visit by typing or voice ("move ZTL's visit from Tue 3 Nov to Thu 5 Nov 2pm", "cancel ZAH's visit on Friday, admitted") opens the checked Change dialog (or Set time) filled in, with "From your words: …". Nothing changes until you click, and every check, limit, reason and request applies as usual. When anything is unclear it asks with buttons, it never guesses: two patients with the same initials, two upcoming visits, a weekday that could be this week or the visit's week, a weekend or public holiday, no session that day, two sessions that day. A reason is filled only when the words clearly say one from the list (never "Other"). Only people who may change visits get it ("You cannot change visits" otherwise). By voice, initials and postal codes are taken only when the speech runs on this computer (as before); "this visit" means the card in front of you. Changes of many visits at once ("cancel all…") are refused as before. The sentence is never sent to an AI model, and the question log keeps it with patient details hidden. T-333
• LivePlaces: areas, districts and landmarks. The box understands Singapore places, typed or by voice: planning areas and neighbourhoods ("in Toa Payoh", "West Coast", "Katong"), the regions ("east side", "the north", "north east"), postal districts ("district 20", "D15"), everyday names ("AMK", "CBD", "Jurong" = Jurong East and West), and landmarks: near an MRT or LRT station, a hawker centre or a polyclinic means within 800 m (about a 10-minute walk) of it ("near Bishan MRT", "around Tampines interchange"). A card is placed from its own postal code, planning area and map pin, on your screen; nothing about a patient is sent anywhere (the place list is public data, kept in the app). Overlaps are normal: one card is in its region, area, district and near several stations at once. When a word could mean two things ("near Bishan": the area or the station) the box asks; it never guesses. Cards it cannot place (no map pin for "near") are left out and the answer says how many. T-347
• Live"My patients" (also "mine", "for me", "assigned to me") means the patients where I am the usual doctor OR the preferred doctor OR the doctor of the next planned visit, and the chips say so. A young service has few usual doctors (that needs 3 visits in 180 days), so the usual doctor alone left the list nearly empty. Another doctor's patients ("Dr Lim's patients") still means the usual doctor, marked as assumed. Since Kevin's "A" (24 Oct 26) the SAME meaning is used everywhere: the Communications filters (My Patients; My List = seen in the last 30 days or planned in the next 30, and not My Patients) and Waypoint's "My patients" button in the planner's patient list, which asks the database rather than working it out itself. T-340 B5, T-327
• DEV onlyWeekly review. Every Monday at 09:00 the questions the box could not answer are reviewed and rule fixes proposed. Fixes are built only after Kevin agrees. The question log hides patient details and never stores answers. The hospital app keeps no question log yet (switched off there), so the review reads the test site's questions only. T-322, T-320

7. Decision log

Every decision that shaped the CCT rules, newest last within each day. Kevin's words are quoted as written. "not recorded" means the source does not hold his exact words.

How this page is kept

This page is the one place the CCT team (Dr Roland, the CCT doctors and the admin team) can read how the app decides things. It is a standing instruction (Kevin, 24 Oct 26) that any change to a CCT rule or process updates this page at the same time: the rule in its section, and a dated row in the Decision log with Kevin's words, what was built, the T-number and whether it is Live or DEV. When a change goes to the hospital app, its mark turns to Live.

If something here does not match what you see in the app, tell Dr Roland or Dr Kevin Awyong. The app is right about what it does today; this page is then out of date and will be fixed.