- Ya
- 26 Agosti 2026, 07:39 UTC
- Mwandishi
- kamo
- Ahadi ya
- db0efd5
The two things a practice does all day that the app could not do. Both APIs have been on the server the whole time; neither had a screen, so the front desk could see the day and check people in without being able to put anybody on it, and a clinician could sign one note at a time from inside a chart they had opened for another reason. BOOKING. Patient first, then visit type, clinician and date, then the times the schedule actually has free. Slots come from the server's availability rather than a grid drawn here — a calendar that renders every fifteen minutes and lets somebody click one will book into a lunch break, a blocked afternoon, or a slot that filled while the page was open. The list refreshes after every booking, because two people booking the same morning is ordinary, and a failure says so rather than inviting a retry into the same conflict. Remaining capacity is shown rather than a bare "available": a slot is not always one person, and a group or double-booked template says so. SIGNING. Three queues, and the middle one is somebody else's problem. "Mine" is what this clinician owes; "awaiting my countersignature" is what a scribe or student wrote and cannot sign themselves, which blocks THEIR day, so it is called out separately and carries the more urgent tone. "The practice" is the manager's view. Countersigning happens in the list; signing does not. Signing your own note means reading it, so that opens the chart. Countersigning is an attestation about work already reviewed — and the queue at least shows a supervisor exactly how many they are attesting to. The masthead badge is what the clinician owes, not the practice's total: a practice-wide backlog on a personal tab reads as a personal one.