Paste a tab-separated list copied directly from the source system. Pick the matching format, then Import. Existing patients (matched by MRN) are updated in place; jobs are preserved.
Save the entire list (patients + jobs) to a file you can keep, copy between browsers, or share with another user. Loading offers Replace or Merge.
Lines after PLAN: become Normal-priority jobs when you save. Re-saving only adds new lines — existing jobs stay put.
Starter text for every new patient note this session. The first line is typically the round name and the consultants (e.g. ICU AM WR — Dr Smith). Lines after PLAN: are where you list jobs.
No patient information is ever sent to a server or any third party.
webrounds is a client-side ward-rounds tracker. Modern web encryption and storage (browser localStorage, WebRTC DTLS, app-layer AES-GCM-256) mean your list lives only in this browser — or, when you explicitly start a Connect session, flows directly to a colleague's browser over an end-to-end-encrypted link. Patient data is never transmitted to a server or a third party. Local data also auto-wipes after 13 hours of inactivity, so a forgotten browser tab on a shared workstation doesn't leak yesterday's list.
Anonymous usage analytics (event counts only — page load, import succeeded, note saved — never patient data) are beaconed to /api/events on this domain so we can see which features get used. You can turn this off in Preferences below.
Connect opens a direct peer-to-peer link to your colleague's browser. Patient data is encrypted in transit twice: by WebRTC's mandatory DTLS layer (which protects every WebRTC connection), and by an app-layer AES-GCM-256 key derived from your passphrase via PBKDF2. The signalling server (Cloudflare) only ever sees connection metadata (IP addresses, codec preferences) — it never sees your passphrase, never sees your list, and stores nothing after the connection ends. Both you and your colleague type the passphrase locally; it never travels over any network. Two peers per session in this version. Brief network blips (wifi switching, etc.) auto-reconnect; closing the tab ends the session for everyone — start a fresh Connect.
Save writes the entire list to a JSON file on your device at a location you pick. Save files are plain JSON, not encrypted — chosen deliberately so you can inspect or hand-edit them, but it means a saved file contains patient identifiers in readable form. Treat it like any other clinical document: store it somewhere safe, share it only over channels you trust, and delete it when it's no longer needed.
Closing the tab keeps your data; clearing site data wipes it. There is no password and no recovery — a saved file is the only backup.
QR codes generated with qrcode-svg (MIT). Passphrase generator uses the EFF long Diceware wordlist (CC BY 3.0).
Live sync over WebRTC. Patient data goes directly between your browsers, encrypted with a passphrase the server never sees. Both users need to be online at the same time.
Pick or generate a passphrase. You'll share it (along with the code we give you) with your colleague verbally — they need both to decrypt your list.
Tell your colleague:
Anyone with the QR can join — only show it to the colleague you're pairing with.
Scan with your phone camera to auto-join. Anyone scanning this code gets the passphrase, so don't leave it on screen.
Waiting for them to connect…
You already have in this browser. How should the file be applied?