Attendance (QR Check-in/out)
Feature Overview
Attendance solves a real problem for hospital-based doctors: CPD credits for mandatory meetings (M&M rounds, Grand Rounds, Journal Clubs, Teaching Sessions) are currently uncaptured — they happen but go unrecorded. Matt's goal is to make this effortless and automatic: a doctor walks into a meeting, scans a QR code in seconds, and the CPD hours flow directly into their portfolio without any manual data entry.
The system has two sides:
- Hospital Admin — creates meetings, generates the QR code to display on a projector/screen at the start of the meeting, sees who attended, has a manual tick-off fallback for those who couldn't scan
- Doctor — opens the app, taps the camera icon, scans the QR, and checks in. CPD credit lands in their plan automatically when the meeting closes.
This is part of the broader Hospital Admin feature set (#1861), which gives clinical medical officers and hospital administrators tools to manage their doctors: meetings, attendance, staff lists, and anonymised performance insights.
Original Vision
Meeting Types (from #1892)
Hospital admins create meetings with predefined types:
| Type | CPD Credit |
|---|---|
| Morbidity & Mortality (M&M) | Configurable per hospital |
| Grand Rounds | Configurable |
| Journal Club | Configurable |
| Teaching Session | Configurable |
| Other | Configurable |
Each meeting has: title, type, date/time, location, status (scheduled → in-progress → completed → cancelled), and cpdHours (decimal).
Future enhancement: calendar integration (Outlook/Teams, Google, iCal) — explicitly noted by Matt but deferred.
QR Code Check-in/out (from #1893)
- Time-limited QR code generated per meeting (encodes meetingId + token)
- Admin flow: Create meeting → Generate QR → Display on projector/screen → View attendance list → Manual tick-off for non-scanners → Mark complete
- Doctor flow: Open app → tap camera icon → scan QR → check-in confirmed → check-out at end
(or auto-checkout on meeting close). Auto check-out was superseded on 2026-09-25: Matt said "it shouldnt be automatically checking out users" (#12466). Seeattendance.checkout.no-automatic-checkout. - Check-in methods:
qr_code(self-service) ormanual(admin tick-off, recordsverifiedBy). Self-service check-in is QR-only — a doctor can never record their ownmanualattendance;manualrows are written only by the hospital admin's tick-off (#12481) - Push notification reminder for upcoming meetings
CPD Auto-credit (from #1894)
The highest-value part of the feature: zero data entry for the doctor. When a meeting is marked complete, the system automatically:
- Finds all verified attendees (QR or manual)
- Creates a CPD activity record for each: category chosen per doctor from the meeting type's eligible categories (lowest bucket — see below),
hours fromhours for the time that doctor was in the meeting (Matt, 2026-09-26, #12464/#12472; drift, #12776)cpdHours - Links the activity to the source meeting (audit trail)
- Activity appears in doctor's CPD plan tagged with meeting reference
Hospital admins configure default CPD hours per meeting type. Open questions (resolved 5 May, engineering-led, Matt to ratify):
- Can admins override hours for individual attendees? Yes — admin can edit any attendee row in the meeting record, but each edit is audit-logged with admin userId + timestamp + reason. Defaults to the meeting-type hours; deviations surface on the cohort dashboard for compliance review.
- Can doctors edit auto-credited activities? No edit on the auto-credit fields (hours, type, source meeting). Doctors CAN add a reflection / supplementary notes to the activity. Edits to core fields would break the verification chain (Evidence Integrity Rule, see
cpd-home.md). - What if a doctor disputes attendance? Doctor flags the activity from the CPD plan view → routes a Notification to the Hospital Admin who owns the meeting. Admin reviews QR-log + manual roster, then either upholds (no change) or removes the credit (audit-logged). No silent deletions.
Nav / UX (Mar 2026 — #3960)
From the 25 Mar 2026 feature review with Matt:
- No expandable sub-nav — "Scan QR Code" is removed as a child page; the nav item never needs to expand.
- Direct navigation — clicking "Attendance" goes straight to the History page.
+icon triggers scanner — a+icon on the History page replaces the Scan QR child page; tapping it immediately opens the camera/QR scanner.- Camera icon in nav — the up-arrow nav icon is replaced with a camera icon to signal QR scanning.
Matt's 17 Apr 2026 Notion Brief — Requirements Update
Source: Attendance/Meeting Notion brief.
Hospital Admin flow
- Hospital Admin sets events / meetings that trigger CPD.
- Captures in-hospital occurrences (MDT, M&M, Audit, Grand Rounds, Teaching).
- PPP process: record → verify → store → optionally produce a Certificate. Engineering's proposed answer (Matt to ratify): ship without DoD digital signature in MVP — extra step adds friction; the QR-log audit trail + admin verification is already cryptographically defensible for AHPRA CPD purposes. Add DoD signature only if a B2B2C customer raises it as a contractual requirement.
- Attach / invite users individually OR by grouped Profile settings (e.g. Consultants + Non-Consultants of Orthopaedics at RBWH; or PGY1 at RBWH).
- Calendar function — not yet built.
User flow
- Unique QR code is produced per event.
- Consultant and Non-Consultant users scan the QR in and out of the meeting.
- System records time, verifies, logs the meeting, logs CPD activity, scores points.
Screenshots / UX changes called out by Matt
Regression-grade — each becomes a @regression BDD scenario:
- docs.professionalperformanceportfolio.com — Attendance journey: add an Exportable button to the journey view.
- Confirm clicking the camera icon opens the camera to scan the QR code (not another affordance).
Matt's 4 Aug 2026 Hospital Admin Console brief — Add meeting
Source: HOSPITAL ADMIN CONSOLE + DASHBOARD (last edited 2026-08-04; also summarised in #11220 and the #11773 slice). Matt's words: "Add meeting (creates timed-expiry QR code - only active 10 mins before meeting) - time - duration (affects CPD points) - location - CPD activity (should trigger appropriate category) - Invite users (individual or grouped) (NB user sign-out must occur within appropriately timeframe post meeting to prevent dishonesty ?whats the solution here - ?new QR code for user to OCR scan)". This "OCR scan" line is where the "OCR" in the Task 14 title comes from (Q8).
Matt's 25–26 Sep 2026 answers (GitHub)
Matt answered four engineering questions on GitHub. These are the newest Matt statements on attendance and they override the 4–5 May engineering-led decisions where they differ:
- CPD hours = time in the meeting (#12464, #12472 option 2): "The doctor scores cpd hours for the time they were in the meeting ... Not the whole meeting".
- No automatic check-out (#12466): "it shouldnt be automatically checking out users though to protect against people jsut checking in and then not attending the whole meeting".
- The admin sets the meeting's time, duration and location, and can extend it (#12465, #12466): "I see it as them setting a time for the meeting like any calendar event and then users checking in and checking out".
- The admin picks the CPD activity (#12467): "admin users should have option of cpd activity when they set the meeting".
- Still open from these threads: online attendees (Q1), the photographed-QR risk (Q7), scanning out (Q8) and the doctor who never checks out (Q9).
Rob's 26–27 Sep acting-PO rescopes on #12449 and #12450 (one scan in, no GPS check-out, a GPS plausibility check at check-in, an admin "needs closing" list) were posted after Matt's answers but have not been ratified by him. They are recorded as Q8, Q9 and Q12, not as ACs.
Open Questions
Questions for Matt. None of these has been posted to him from this refresh.
| # | Question | Source | Owner | Status |
|---|---|---|---|---|
| Q8 | Do doctors scan the QR out as well as in? Your 17 Apr brief says "Scan QR code in and out of meeting". Your 29 Jul Task 14 brief says the code may need to be "scanned in and out in real time". Your 4 Aug admin-console brief asks whether sign-out needs a "?new QR code for user to OCR scan". On 26 Sep you asked "Is the only way scanning a QR code for in and out". On 27 Sep Rob decided "no two-scan" on #12449: one QR scan in, then a Check out button in the app. Today the doctor scans in and taps "Check out". Should check-out also need a scan (for example a second code shown only near the end of the meeting)? | notion-attendance-meeting-brief; issue-11216; notion-hospital-admin-console; issue-12472; issue-12449 (Rob) | Matt | Open. Rob's one-scan decision stands until you answer. |
| Q9 | What does a doctor get if they never check out? You said someone who doesn't check out of an M&M must not end up with 8 hours (#12465), and that check-out must not be automatic (#12466). Rob proposed on #12450 that anyone still checked in after the scheduled end goes on an admin "needs closing" list, and gets no automatic credit until the admin confirms. Is that right, or should they get credit up to the scheduled end? | issue-12465; issue-12466; issue-12450 (Rob) | Matt | Open. Blocks part of #12776. |
| Q6 | How long after the scheduled end does the QR stop working? You said the admin sets the meeting time "like any calendar event" and can extend it (#12466), and that the QR "expires shortly after the meeting end" (#12472). Meetings now have a scheduled end (#12450), so today the QR stops when the admin completes or cancels the meeting, or at the scheduled end plus a fixed grace period (#12471). How long should that grace period be? | issue-12466; issue-12472 | Matt | Partly answered 25–26 Sep (admin sets the duration and can extend). The grace period is open. |
| Q7 | One QR for the whole meeting, given the photo risk? Rob changed the code on 26 Sep to one QR per meeting, valid until it closes (#12471), following your brief. On 26 Sep you said "in person someone could take a photo and send it around. Or take photo of it, leave the meeting and scan/log-off later", and asked whether it could be made screenshot-proof. Your 4 Aug brief also says the QR should only be "active 10 mins before meeting" (attendance.qr.active-from-ten-minutes-before). Is one QR per meeting still right, and what should stop a shared photo? | notion-attendance-meeting-brief; notion-hospital-admin-console; issue-12472 | Matt | Open. Rob's proposed answers are a GPS check at check-in (Q12) and time-based credit (#12776). |
| Q1 | How do online attendees check in and out? You asked about "digital meeting attendance" (17 Apr brief, 29 Jul Task 14 brief), and on 25 Sep said "we need to accomodate online attendees but protect against gaming and dishonesty". Engineering's 5 May proposal was a time-boxed magic link the admin pastes into the Zoom/Teams chat, valid for the first 10 minutes, with Zoom/Teams attendee-list import deferred. That proposal leaned on GPS / meeting-end check-out, which you have since ruled out (#12466). How should an online attendee check out? | notion-attendance-meeting-brief; issue-11216; issue-12466; issue-12472 | Matt | Open. Blocks #12779. |
| Q12 | Location check at check-in. You asked whether location "can be as accurate as a room in a hospital?" (#12465). Rob's answer (27 Sep, #12449): no, room-level accuracy isn't realistic. His proposal is a coarse check: at the scan, the phone's location is compared with the meeting location the admin set, and a scan clearly outside the radius is refused with "ask the admin to check you in manually". Is that acceptable? | issue-12465; issue-12449 (Rob) | Matt | Open. Rob's proposal, not yet ratified. |
| Q10 | Which CPD activities can an admin pick for a meeting? You asked for the admin to choose the CPD activity when setting the meeting (#12467). On 27 Sep you said the categories-and-activities table "Looks a bit sparse ie not all activities considered", and that "departmental" "could be a number of meetings including M&m, Hospital clinical meeting, audit etc". Your 28 Sep follow-up is unanswered. Which activities should the picker list? Rob owes you the table review. | issue-12467 | Rob, then Matt | Open. Blocks #12588. |
| Q11 | CPD-only users: when do they see Attendance? On 3 Jun you asked for Attendance on the CPD-only tier, since it "obviously wont work for users if the qr code/meeting isnt set by an admin tier person" (#7911). It was never added. Should it show when the user's hospital has an enterprise agreement, or only once they are invited to a meeting? | issue-7911 | Matt | Open. Blocks #12777. |
| Q4 | CPD auto-credit — admin override hours per attendee; doctors edit auto-credited activity? Engineering-led 5 May, Matt to ratify: admin override allowed (audit-logged); doctor edit forbidden on core fields, allowed on reflection/notes (see CPD Auto-credit § above). | engineering 2026-05-05 | Matt | Open. No newer Matt statement. |
| Q5 | Group-invite by Profile (e.g. Consultants Ortho RBWH) — in-scope now or deferred? Engineering-led 5 May: in-scope for MVP; implement as a filter on Profile (specialty + grade + hospital), saved on the meeting so future runs of a meeting series pick up current membership. | notion-attendance-meeting-brief; notion-hospital-admin-console | Matt | Scope answered: your 4 Aug brief says "Invite users (individual or grouped)", so it is in scope (attendance.meeting.invite-individual-or-grouped, #11773). The filter design is still engineering's and needs your OK. |
Resolved Decisions
- Q2 — Dishonesty protection (revised 26 Sep 2026, #12471; check-out part superseded 25 Sep 2026): one QR per meeting, valid until the meeting is closed — Matt's brief asks for a "Unique QR Code Produced - ?expires following meeting close to save dishonesty".† The 60-second rotation is kept as an optional strict mode (
QR_ROTATION_WINDOW_SECONDSset), off by default. Traced history: the brief names no rotation or window; on 28 Apr 2026 Rob proposed on the Notion page a rotating QR "(<=30s window); GPS check secondary"; on 3 May Matt replied "30 seconds seems a bit short but this overall sounds good" (no number given); Rob's 5 May summary turned that into "60–90s (tuned in UAT)" and this spec then recorded it as "(Matt, 4 May)" — that number and attribution were engineering's, not Matt's; on GitHub #12464 (25 Sep 2026) Matt said he does not recall saying 60–90s. Rob decided on 26 Sep 2026 to follow the brief (Option B on #12464); Matt's confirmation is pending (Q7).GPS-based check-out is the primary anti-abuse mechanism — when a checked-in user moves >100m from the meeting geofence OR the admin meeting-end timer fires, they are auto-checked-out (shipped #5717).Superseded 2026-09-25: Matt said check-out "shouldnt be automatically checking out users" (#12466). The GPS and meeting-end auto check-outs were also never wired up (#12445 found them to be only an enum and an uncalled endpoint; #12449 and #12450 are rescoped to match). Anti-abuse now rests on time-based credit (#12776) and the open Q7–Q9 and Q12. Admin-side "verify present" tick remains for edge cases. - Q3 — Certificate signature (Matt, 4 May): build the certificate in v1. Branded PDF certificate per
cpd.md § PDF — branding & layout, downloadable per attendance event (shipped #5716). Bulk export for all attendees of a completed meeting also shipped. No DoD digital signature in v1 — brand-marked PDF + QR-log audit hash is sufficient for the "back-end verification" promise.
Acceptance Criteria
QR Check-in/out — Built
- Schema
meeting_attendancewith checkInTime, checkOutTime, method, verifiedBy (#2435). - QR token service: time-limited generation + timing-safe validation (#2436).
- Check-in / check-out API endpoints (#2436).
- Manual tick-off endpoint for hospital admin (#2436).
- Admin UI: generate QR, display, attendance list, manual tick-off (#2437).
- Doctor UI: camera scanner, check-in/out confirm, attendance history (#2438).
- Security: auth checks + race-condition protection on check-in (#2455).
- QR camera opens on device (#3725 regression fix).
CPD Auto-credit — Built (Sep 2026, #12445)
- Meeting completion creates CPD activity for each verified attendee (#1894 schema).
- Activity type maps from meeting type;
hours from meeting config(hours superseded 2026-09-26 — seeattendance.credit.time-in-meeting). - ✅
attendance.credit.time-in-meeting— each attendee is credited CPD hours for the time between their own check-in and check-out, not the meeting's fullcpdHours. Built for attendees who checked in and out (#12776):completeMeetingcredits the span, capped at the effective meeting hours (attendedCreditHours). An attendee with no check-out is treated as checked out at the meeting's scheduled end, so they are credited check-in to scheduled end, capped (seeattendance.credit.no-open-ended-time; whether they should get anything at all is Q9). Supersedes "hours fromcpdHours" (#1894). ††† - ✅
attendance.credit.no-open-ended-time— a doctor who never checks out is never credited open-ended time: credit runs from their check-in to the meeting's scheduled end, never past it, and never more than the meeting's effective hours (attendedCreditHours; meetings now have a scheduled end, #12450). A doctor who checks in and never checks out therefore does NOT get the full hours unless they arrived at the start. Whether that is the right outcome, or whether they should get nothing until the admin confirms, is Q9. † - ⏳
attendance.meeting.admin-selects-cpd-activity— when setting up a meeting, the admin titles it freely and picks the CPD activity from the CPD activities table; the credit category comes from that activity's allocation, with the per-doctor lowest-bucket rule where it is eligible for more than one category. Not built: meetings still carry a meeting type, and the eligible-category lists per type (#12581) stand in for it (#12588). Which activities the picker lists is Q10. †† - Auto-credited activity links back to source meeting in CPD plan.
- Hospital admin configures default CPD hours per meeting type.
- QR check-ins and admin manual tick-offs (
meeting_attendance) are credited on completion alongside verifiedmeeting_attendees; completion is idempotent (status-guarded UPDATE + per-meeting credit dedupe) (#12445). - Credited activity carries the meeting title (description), a CPD category, and the exact hours — no rounding (#12445).
- CPD category is per doctor — the lowest bucket (#12467, #10824). Each meeting type has an ordered list of eligible categories, taken from the published CPD activities table (July 2026) rows that describe it; the first is the meeting type's own category. On completion each attendee is credited under the eligible category they have the fewest hours in this CPD year (UTC calendar year; non-archived activities), so two doctors at the same meeting can be credited under different categories. Tied on hours, or no hours in any eligible category, → the first (the meeting type's own category). A single-category meeting type always credits that category. This is the same rule as
cpd.activity.auto-select-categoryfor the manual form. It replaces the #12489 fixed category per meeting type. † † - The complete-meeting dialog counts the people completion will credit (verified
meeting_attendeesplus everyone inmeeting_attendance) via the additivecreditableAttendeeCountonmeetings.list, so it no longer says "No attendees" for a meeting that only has QR check-ins; the CPD Activities table shows the meeting title (thedescriptionfallback) for a meeting credit that has no linked activity (#12462).
Nav / UX — Built (Mar 2026, #3960)
- Attendance nav item never expands (no child pages).
- Clicking Attendance goes direct to History page.
+icon on History page opens QR scanner.- Camera icon replaces up-arrow in nav.
- ✅
attendance.nav.cpd-only-tier— CPD-only users whose organisation runs meetings through a hospital admin (active enterprise membership,meeting_managementnot switched off) see Attendance in Education & CPD, with the scan action; solo CPD-only users don't. Built under #12777 viaattendance.getAvailability. †
Meeting set-up — Matt's Sep 2026 answers and 4 Aug admin-console brief
- ✅
attendance.meeting.admin-sets-time-and-duration— the admin sets the meeting's start and end like a calendar event (End date & time on Create meeting / Edit meeting, default 2 h) and can extend a scheduled or running meeting (Extend action). Built under #12450:meetings.scheduled_end_at,meetings.extend; the QR hard expiry follows the real end. † - ✅
attendance.meeting.admin-sets-location— the admin who creates the meeting sets its location as a map pin (latitude and longitude, pre-filled from the hospital default, radius 100 m default;meetings.geofence_radius_m). Built under #12449. The pin editor shows a schematic preview, not a map tile (a real map is undecided, not built). How the location is used at check-in isattendance.checkin.location-plausibility. †† - ✅
attendance.meeting.invite-individual-or-grouped— in Manage attendance the admin invites a person (idempotent) or a group filtered by Profile settings (grade: consultant / non-consultant; specialty; the meeting's hospital) after seeing the match count; invitees appear as Invited until they check in. The filter is a one-off snapshot, not saved on the meeting. It matches speciality and grade only; PGY year and secondary specialities are not matched (Q5). The invite creates no notification for the invitee yet (#12982). There is also no reminder before a meeting starts (#12983). Built under #11773. † - ✅
attendance.qr.active-from-ten-minutes-before— the meeting's QR only checks people in from 10 minutes before the start (QR_EARLY_ACTIVATION_MS); an earlier scan is refused and writes no row, and the admin QR dialog shows when check-in opens. Built under #11773 now that rotation is off by default. † - ⏳
attendance.online.virtual-attendees— online attendees can check in and out without being in the room, with the same anti-gaming protection. Not built: self-service check-in is QR-only (#12481), so an online attendee can only be ticked off by the admin (#12779). The mechanism is Q1. ††
QR and check-out (May 2026 Q2 resolution, revised Sep 2026)
- One QR per meeting: the QR generated for a scheduled or in-progress meeting is accepted until the meeting is completed or cancelled, or until the hard expiry (scheduled start + 2 h + 15 min), whichever comes first; a scan after the meeting is closed is rejected with a clear "This meeting has been closed" message (#12471).†
- In that default mode the admin QR dialog shows "Valid until the meeting is closed" instead of a countdown and does not re-fetch the code on a timer; the QR renders at a visible size (#12443, #12471).
- Optional strict mode: setting
QR_ROTATION_WINDOW_SECONDSto a positive number restores the rotating QR — a token is accepted only for that many seconds from issue, and the admin dialog counts down that window and fetches a fresh code when it elapses (#5893, #12443). Unset (the default) means no rotation. This is a deployment-wide env setting; per-hospital storage is not built (found while fixing #12443). - A stale/rotated QR scanned by a doctor shows an inline "QR expired, ask for a fresh code" error and keeps the session — it is never treated as an expired login (#12444).
- A successful QR check-in shows the confirmation screen with a working Check Out button; the scan page does not crash (#12444).
- The scan page announces a rejected QR once (the inline alert only, no duplicate snackbar) and repeats no success snackbar; the check-in confirmation names the meeting checked into, taken from the additive
meetingTitlefield on theattendance.checkInresponse (#12460). - Scan-page buttons keep their visible label as the accessible name (guidance on
title), use sentence case, and meet the 44px touch-target floor (#12460, #7773). GPS distance auto-checkout fires when attendee leaves the meeting geofence (>100m) (#5717).Retired 2026-10-03. Superseded by Matt on 2026-09-25 (attendance.checkout.no-automatic-checkout). It was never wired up either: no client sends a geofence check-out and the meeting has no geofence (#12445, #12449).Admin meeting-end timer bulk-stamps remaining attendees as checked-out (#5717).Retired 2026-10-03, same reason.attendance.adminMeetingEndCheckOutexists but nothing calls it (#12450).GPS-denied users fall back to admin meeting-end checkout (#5717).Retired 2026-10-03, same reason.Superseded 2026-10-04 byattendance.checkout.no-automatic-checkout— attendees are never checked out automatically.attendance.checkout.scheduled-end-server-job(Rob, #12466/#12450: "remaining attendees are checked out at the scheduled end time (server job), even if the meeting overruns").- ✅
attendance.checkout.scheduled-end-server-job(#12450) — a doctor still checked in when the meeting's scheduled end passes is checked out AT that end (methodmeeting_ended) by an idempotent sweep. The sweep does NOT run at the scheduled end: on the NAS backend it runs from the shared daily scheduler tick (20:30 UTC) and lazily on attendance report/history reads and on completion, so an open row can stay open on a live admin list until the next read or tick, though the stamped time is always the scheduled end. Extending the meeting moves the end; a doctor's own earlier check-out is never overwritten; completing early checks nobody out. † - ✅
attendance.checkin.location-plausibility— at the QR scan the phone's location is captured; a fix clearly outside the meeting pin's radius (100 m default, less the reported accuracy) is refused with "Couldn't confirm your location - ask the admin to check you in manually"; a doctor who declines location still checks in and is flaggedno_location. Only the distance and accuracy are stored. The pin is an admin map pin pre-filled from the hospital default. Built under #12449. † - ✅
attendance.checkout.doctor-records-check-out— the doctor records their own check-out time from the check-in confirmation screen ("Check out"), and the time is stored onmeeting_attendance.checkOutTime. Whether check-out also needs a QR scan is Q8. ††
Certificate — Built (May 2026, Q3 resolution)
- Branded PDF certificate downloadable per verified attendance event (#5716).
- Admin bulk-export of certificates for all attendees of a completed meeting (#5716). Known gap (#12981): the export only includes attendees whose
meeting_attendeesrow isverified, and nothing sets that on a QR check-in, so it is empty for QR attendees until the eligibility rule is decided. Each file is named with the attendee's name (#12980). - Certificate carries the audit hash linking back to QR-log verification — no DoD signature in v1.
Tabular attendance report export — Built (Jun 2026, #7879)
- Admin exports the full attendee roster as a single CSV from the report dialog (#7879).
- Admin exports the full attendee roster as a single branded PDF table from the report dialog (#7879). The PDF export failed for every table export until #12980 (logo placed above the page padding broke the pdfme layout).
- Export columns match the
meetingAttendanceViewroster: Name, Check-in, Check-out, Check-in method, Check-out method (spec §103) (#7879, headers qualified #12458). - The on-screen attendance report and attendance tables also show human-readable Check-in method and Check-out method columns (the tables scroll sideways in a labelled, keyboard-focusable region on small screens), and doctor Attendance History rows show the meeting title (not "Meeting #N") (#12446).
- Doctor Attendance History is ordered most recent check-in first (attendance id descending as the tiebreaker) before pagination, so pages never repeat or skip rows (#12463).
Status
| Sub-feature | Status | Notes |
|---|---|---|
| QR token service + check-in/out API | ✅ Built | |
| Admin QR generation + attendance UI | ✅ Built | |
| Doctor QR scanner + history | ✅ Built | |
| Security hardening | ✅ Built | |
| QR camera bug | ✅ Fixed | |
| CPD auto-credit from attendance | ✅ Built | Time attended, capped; no check-out = scheduled end (#12776/#12472) |
| Nav re-baseline (Mar 2026) | ✅ Built | |
| One QR per meeting (until close) | ✅ Built | #12471; rotation optional (env), not per-hospital |
| Check-out at scheduled end (server) | ✅ Built | Rob 4 Oct: scheduled-end server job (#12466/#12450) |
| Doctor self check-out | ✅ Built | Check out button; scan-out is Q8 |
| Meeting time/duration/extend | ✅ Built | Start, end, extend (#12450); hours default to duration |
| Meeting location | ✅ Built | Admin map pin (schematic preview) + 100 m check-in check (#12449) |
| Admin picks CPD activity | ⏳ Not built | #12588 (Q10) |
| Invite users (individual/grouped) | ✅ Built | Individual + group by speciality/grade snapshot (#11773); PGY and saved filters are Q5; no invitee notification yet |
| QR active 10 min before start | ✅ Built | QR_EARLY_ACTIVATION_MS (#11773) |
| Online attendees | ⏳ Not built | #12779 (Q1) |
| Attendance on CPD-only tier | ✅ Built | #12777 (Q11 resolved: Matt 3 Jun, Rob 17 Jun on #7911) |
| Branded PDF certificate + bulk | ✅ Built | (Q3 resolution) |
| Tabular attendance report export | ✅ Built | CSV + single PDF roster from the report dialog (#7879) |
| BDD coverage | ✅ Current | Retired @issue-5717 auto check-out scenarios removed 2026-10-05 |
Open issues on label:feature:attendance (3)
| # | Title |
|---|---|
| #12776 | bug(attendance): meeting CPD credit is the full meeting hours, not the time the doctor was in the meeting |
| #12777 | feat(attendance): show Attendance on the CPD-only tier when the user's organisation runs meetings |
| #12779 | feat(attendance): let online attendees check in and out of a meeting (design blocked on attendance Q1) |
Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-10-05 | An admin can cancel a scheduled or in-progress meeting (its QR then stops checking people in and no CPD is credited). A meeting between its start and scheduled end reads In Progress and the In Progress filter finds it. A CPD activity credited from a meeting shows a Source badge naming the meeting, titled with the meeting type's display label. The invite panel lists everyone invited and how many matches were already invited. A doctor's own check-out reads Self check-out. The early-scan refusal quotes the open time in the scanner's time zone. Small polish: Create meeting buttons keep their visible name, the Status filter shows All Statuses, no pending-accounts 403 for a plain hospital admin. The Task 14 recording seed (seedTask14Recording.ts) marks the hospital admin persona as toured. | #0, #12904, #12905, #12906, #12907, #12908, #12909, #12910, #12911, #12912, #12913, #12914, #11216 | 5 Oct 2026 Task 14 audit defects D-02, D-03, D-04, D-06, D-08, D-11 to D-16 (Rob's decisions of 5 Oct 2026). The spec's meeting-cancel and status behaviour follow the existing closed-meeting QR rule (#12471). Open: group invite by PGY year needs a profile field that does not exist (Q5, Matt). Task 14 fix lane, Refs #11216. |
| 2026-10-05 | Spec corrected to shipped behaviour. Status table (time/duration, location, invites, QR 10 min, BDD coverage now built or current); admin-sets-location is built; no-open-ended-time is built (no check-out is credited from check-in to the scheduled end, capped, not the full hours); the scheduled-end sweep runs from the daily 20:30 UTC scheduler tick and lazily on reads, not at the scheduled end; group invite matches speciality and grade only and sends no notification; CPD hours default to the meeting duration in the form; the three retired @issue-5717 BDD scenarios are removed; the attendance PDF export fix (#12980) and the bulk certificate eligibility gap (#12981) are recorded. | #0, #11216, #12980, #12981, #12982, #12983 | Task 14 reachability check (5 Oct 2026) found the spec text stale against the code. No requirement changed. Open decisions are unchanged and still listed as questions. |
| 2026-10-04 | attendance.credit.time-in-meeting flips from drift to built for attendees who checked in and out. completeMeeting now credits each of them the time between their own check-in and check-out, capped at the effective meeting hours (was the full meeting hours for everyone). attendance.credit.no-open-ended-time stays not built. An attendee with no check-out still gets the full effective hours until Q9 is answered. | #12840, #12776, #11216 | Matt, #12464 (26 Sep 2026) "The doctor scores cpd hours for the time they were in the meeting ... Not the whole meeting", and #12472 option 2 (proportional credit). Q9 (what a doctor who never checks out gets) is still open, so that case is deliberately unchanged rather than invented. @regression @issue-12776 scenarios run the credit function in-process. |
| 2026-10-04 | Meetings gain a scheduled end (End date & time, extend action) and a location pin pre-filled from the hospital default. The QR only works from 10 minutes before the start. A check-in clearly outside the pin radius is refused and a doctor who declines location still checks in, flagged; the distance is shown to the admin. Attendees still checked in at the scheduled end are checked out at that end by a server sweep (meeting_ended). The admin can invite individuals or a Profile-filtered group. CPD-only users in an enterprise organisation see Attendance. attendance.checkout.no-automatic-checkout is superseded by attendance.checkout.scheduled-end-server-job; attendance.meeting.admin-sets-time-and-duration, attendance.meeting.invite-individual-or-grouped and attendance.qr.active-from-ten-minutes-before flip to built. | #0, #12449, #12450, #11773, #12777, #12459, #12523, #11216 | Rob's 4 Oct 2026 decisions on #12465/#12449 (admin map pin pre-filled from the hospital default, GPS decliners still check in), #12466/#12450 (check-out at the scheduled end by a server job) and #12472 (credit = time attended, capped); Matt's 4 Aug Notion brief ("only active 10 mins before meeting", "Invite users (individual or grouped)"); Matt 3 Jun / Rob 17 Jun on #7911 for the CPD-only menu. Task 14 lane, Refs #11216. |
| 2026-10-03 | The Attendance spec was refreshed for Async Task 14 (#11216) against Matt's 25–26 Sep 2026 GitHub answers (#12464, #12465, #12466, #12467, #12472) and his 4 Aug 2026 Hospital Admin Console brief. One AC is marked drift and filed as a bug. attendance.credit.time-in-meeting (#12776) is drift because completion credits every attendee the full meeting hours, while Matt said "the time they were in the meeting ... Not the whole meeting". The three GPS / meeting-end auto check-out ACs (#5717) are retired. Matt said on 25 Sep that check-out "shouldnt be automatically checking out users", and the code never wired them anyway (#12445). They are replaced by attendance.checkout.no-automatic-checkout (✅) and attendance.checkout.doctor-records-check-out (✅). Eight new not-built ACs are added. attendance.credit.no-open-ended-time is part of #12776. attendance.meeting.admin-sets-time-and-duration is tracked by #12450. attendance.meeting.admin-sets-location is tracked by #12449. attendance.meeting.admin-selects-cpd-activity is tracked by #12588. attendance.meeting.invite-individual-or-grouped and attendance.qr.active-from-ten-minutes-before are tracked by #11773. attendance.online.virtual-attendees is tracked by #12779 (new). attendance.nav.cpd-only-tier is tracked by #12777 (new). Open Questions are now a table. Q6 is narrowed to the grace period, and Q1, Q5 and Q7 are updated. New questions Q8 to Q12 are added. The Q2 resolved decision's GPS check-out clause is struck through as superseded. The Status table is rebuilt. notion-last-synced: is now 2026-10-03. | #11216, #12776, #12777, #12779 | Async Task spec refresh, Task 14 (#11216). The newest dated statement from Matt wins. Rob's 27 Sep rescopes on #12449 and #12450 (one scan in, a GPS check at check-in, a "needs closing" list) came after Matt's answers but Matt hasn't ratified them, so they are Open Questions (Q8, Q9, Q12), not ACs. Drift was confirmed by read-only code checks against real call sites: Meetings/index.tsx calls meetings.complete → completeMeeting → resolveEffectiveCpdHours. Code checks also showed that two claims in the 25 Aug #11773 scope check were wrong: "time/duration/location" is not built, and nothing uses AddAttendeeSchema. No BDD scenarios were added, per the spec-refresh rule (Rob, 2026-10-03). The @regression requirement sits on #12776. Three existing @issue-5717 scenarios in attendance.feature still assert the retired auto check-out. They are left for #12449/#12450 to remove. |
| 2026-09-28 | Meeting CPD auto-credit now picks the category per doctor. Each meeting type has an ordered list of eligible categories from the published CPD activities table (July 2026); on completion each attendee is credited under the eligible category they have the fewest hours in this CPD year, with ties and no-hours going to the meeting type's own (first) category. Replaces the #12489 rule of one fixed category per meeting type for every attendee. "CPD category mapped from meeting type" in CPD Auto-credit — Built and step 2 of CPD Auto-credit are reworded to match. | #12467, #10824 | Matt on #12467 (25 Sep 2026): "user specific, when cpd acitivities cross two categories - ie lowest bucket"; Matt on the 29 Jul 2026 call (#10824): "I want it to go to the emptiest bucket". Same rule as cpd.activity.auto-select-category. Open questions — (1) Matt also asked that admins pick a CPD activity (not a meeting type) when setting a meeting; not built here, the meeting-type eligibility lists stand in for it until that picker exists. (2) "Lowest" is measured in raw hours logged this year, as specced for the manual form, not as progress against each category's annual minimum; Matt to confirm if he meant the latter. (3) grand_round has no published row and stays Education-only; departmental uses the "Hospital clinical meeting" row (Review of Performance, Education). (4) Measuring Outcomes is now eligible for M&M, multidisciplinary, peer review and case presentation meetings because the published table marks it on those rows; #12489 had excluded it on the strength of the Drive "CPD Sheet". |
| 2026-09-27 | Self-service attendance.checkIn is now QR-only. The tokenless manual method is rejected by CheckInSchema (BAD_REQUEST) and refused by the service before any DB access; manual attendance is recorded only by a hospital admin via manualTickOff. The #12471 closed-meeting gate (completed/cancelled meetings refuse the QR) is kept on the QR path. | #12488, #12481 | A manual self check-in inserted a meeting_attendance row with no QR, scoping or meeting-status check, and completion credits CPD to every such row, so any user could claim CPD for a meeting they did not attend. The spec already defines manual as admin tick-off only; no client sent self-service manual, so no acceptance criterion changes. |
| 2026-09-26 | Attendance history (getMyAttendanceHistory) now orders by check-in time descending, then attendance id descending, before paginating. | #12469, #12463 | The query paginated with limit/offset and no ORDER BY, so a doctor paging through history could see rows repeated or skipped between pages. No acceptance criterion changes; most-recent-first is the order the history page already implied. |
| 2026-09-26 | One QR per meeting, valid until the meeting is completed or cancelled (or the hard start + 2 h 15 min expiry); the 60-second rotation is now an optional strict mode (QR_ROTATION_WINDOW_SECONDS, unset by default). Resolved Decision Q2 corrected — the "60–90s (Matt, 4 May)" attribution removed and the traced history recorded; Open Questions Q6 (meeting close / end time) and Q7 (Matt to confirm) added. | #12471, #12464 | Matt's Notion brief says "Unique QR Code Produced - ?expires following meeting close to save dishonesty"; the 60–90s window was engineering's summary, not Matt's words (Matt, #12464). Rob decided Option B on #12464, 26 Sep 2026; Matt's confirmation pending. |
| 2026-09-25 | Attendance report/attendee tables and CSV/PDF export now label the columns "Check-in method" and "Check-out method", and the tables scroll sideways in a labelled, keyboard-focusable region with a visible hint on small screens. | #12468, #12458 | Design review of #12454 found the bare "Method" header ambiguous and the 5-column table unreachable at 375px with no scroll cue. |
| 2026-09-25 | CPD auto-credit now credits QR check-ins and manual tick-offs on meeting completion (idempotent via a status-guarded UPDATE), with exact hours, the meeting title and a category mapped from meeting type; status Partial → Built. | #12461, #12445 | Check-in and tick-off wrote only meeting_attendance while completion credited only meeting_attendees, so real check-ins earned 0 credit; points were rounded (1.5 h → 2) and the activity carried no category. |
| 2026-09-25 | Admin QR rotates on the rotation window and renders visibly; stale-QR 401 no longer logs the doctor out; scan page no longer crashes after a successful check-in. | #12455, #12443, #12444 | Found by the #11216 click-through walkthrough. The 2026-08-25 code-level review had called the QR lifecycle built; running it showed otherwise. Also records that the rotation window is env-wide, not yet per-hospital as the spec claimed. |
| 2026-09-25 | The on-screen attendance report and attendee tables now show a human-readable Check-out Method column, the CSV/PDF export uses the same labels, and Attendance History rows show the meeting title instead of "Meeting #N". | #12454, #12446 | The check-out method (manual / GPS / meeting ended) was visible only in the export, and the history query never returned the meeting title so rows fell back to the meeting number. |
| 2026-06-01 | Add exportable tabular attendance report (CSV + single PDF roster) to the admin report dialog. | #7923, #7879 | Spec §103 requires an "Exportable" attendance report; the dialog previously only bulk-generated per-attendee PDF certificates, with no single tabular roster export. |
| 2026-05-13 | Drift re-baseline — added 5 ACs for shipped #5716/#5717/#5893 work, split Open Questions (Q2/Q3 → Resolved Decisions), fixed malformed YAML frontmatter, refreshed BDD count to 12. | #5342 | Spec drifted from reality after Matt's 4 May Q2/Q3 resolutions shipped — three follow-up PRs merged without spec updates. Q1/Q4/Q5 still pending Matt ratification so status remains partial-drift. |
| 2026-05-08 | Configurable QR rotation window per hospital, default 60s (Matt 4 May tuning of Q2). | #5895, #5893 | Matt's 4 May ratification of Q2 specified a 60–90s window vs the original 30s; per-hospital config lets the value be tuned in UAT. |
| 2026-05-08 | GPS distance auto check-out + admin meeting-end bulk check-out; extended check-out method enum on meeting_attendance. | #5892, #5717 | Matt resolved Q2 on 4 May — GPS-based check-out is the primary anti-abuse mechanism. QR rotation extended to 60–90s; auto check-out fires when attendee exceeds 100m geofence or admin triggers meeting end. |
| 2026-05-08 | Branded PDF certificate per verified attendance event, plus admin bulk-export of certificates for a completed meeting (Q3 resolution). | #5891, #5716 | Matt resolved Q3 on 4 May — certificate required in v1, not deferred. PDF carries the QR-log audit hash; no DoD digital signature needed. |
| 2026-05-05 | Apply Matt's 4 May Notion answers — Q2 (longer rotating QR + GPS check-out) and Q3 (branded PDF certificate in v1, not deferred). | #5713 | Matt resolved both open questions on the Attendance/Meeting Notion page; spec previously held engineering-led proposals. |
| 2026-05-05 | Awaiting-Matt sweep — Q1 digital-meeting verification (rotating magic-link in chat); Q2 dishonesty (rotating QR + geofence; full anti-abuse deferred); Q3 certificate signature dropped (QR-log already AHPRA-defensible); Q4 admin override allowed + audit-logged, doctor edit forbidden on core fields; Q5 group-invite-by-Profile in-scope for MVP. All five resolved engineering-led, Matt to ratify. | Five UX/engineering questions resolvable from project memories + AHPRA defensibility; no commercial input required. | |
| 2026-04-22 | Drift re-baseline — 12 ACs trimmed, #3960 marked closed | #5342 | See audit .drift-audits/attendance.md |
| Mar 2026 | Nav/UX changes agreed in feature review | #3960 | Rob & Matt call 25 Mar 2026 — simplify attendance nav |
| Mar 2026 | QR camera bug fixed | #3725 | Camera not opening on device |
| Mar 2026 | Full QR check-in/out system built | #2435–#2438, #2455 | New feature for hospital meetings |
Sources & Recordings
| Source | Notes |
|---|---|
| https://drive.google.com/file/d/1HDF4acVA0QKImQ29Wu0rp_kVIgb-VGFVg_XwcZnUV6E | Description pending SGD audit |