Patient check-in
Patients find their appointment, catch what changed (address, insurance card, pharmacy), answer the screening question and sign. The desk stops retyping clipboards and starts with what's new.
In the demoRapidKiosk turns a tablet into an always-on check-in desk. Patients find their appointment, update what changed and sign by touch, the front desk sees them arrive in RapidDashboard, and between patients the screen is a poster.
The tablet signs itself in and opens the check-in full screen, the way it does every morning. Pick a front desk, tap the poster and check in. Nothing here is stored or sent anywhere.
About a minute at the tablet replaces the clipboard, the photocopied insurance card and the front desk retyping it all. Every screen has one question and buttons sized for a thumb.





The front desk sees it in RapidDashboard. Each check-in lands on the clinic's front-desk board: who's here, for which provider, what changed and how long they've waited. The poster reads the same board to show the live wait.
The kiosk doesn't change: a poster while it waits, a few big questions, a signature, and the result on RapidDashboard. What changes is who walks up and which Rapid app is behind the screen.
Patients find their appointment, catch what changed (address, insurance card, pharmacy), answer the screening question and sign. The desk stops retyping clipboards and starts with what's new.
In the demo
Name, company, who they're seeing, the safety rules and a signature. The host gets a text and the visit is logged in RapidDashboard.
In the demo
Scan the ticket's QR code with the front camera, confirm, and pick sessions and a 1:1 demo. Every arrival lands on the event board.
In the demo
Escape closes the kiosk app for staff with a keyboard. The desktop has every check-in app and the Control Center for Wi-Fi, sound and Kiosk Mode.
Visitors type their address and watch the roof get measured and priced on the big screen.
RapidRoofing → Trade show boothBooth QR pages turn a scan into a booked meeting. The kiosk is the screen they walk up to.
RapidTradeshow → The counterOne tap on the sign-in screen switches the same tablet to RapidTablet, and Remi takes the notes.
RapidTablet → Service deskTeam load and the queue on an always-on screen, in team totals.
RapidSideKick → Shop floor and break roomProduction, safety and on-time shipments on a screen that never falls asleep.
RapidDashboard →A check-in screen fails in boring ways: it falls asleep, it lands on a login prompt, it loses Wi-Fi, or a patient closes the app. Each of these jobs handles one of them.
After a reboot it shows the edition chooser, counts down, signs in and opens the check-in full screen. Any tap stops the countdown.
Sign-in + countdownKiosk Mode turns off sleep, screen blanking and power saving in one tap. Kio's face tells you which way it's set.
Kio awake / asleepNew Wi-Fi password? The Control Center lets the front desk join a network, swap speakers or dim the screen without a keyboard.
Control CenterCheck-in, sign-in and dashboards run full screen with no window controls. Escape closes only kiosk apps, so staff can get out and patients can't stumble out.
Full-screen appsThe screen never sleeps or dims. The desktop pill and the taskbar both say ON, with the tablet's address for remote help.
Normal power saving comes back after hours. One tap turns it on again.
Stock Linux shows 16-pixel tray icons and gray dialogs. RapidKiosk replaces each one a person touches with a big, branded screen.





RapidKiosk is plain Debian underneath. Each step below replaced one piece of stock Linux that a patient or the front desk would touch. All of it was built by describing it in plain English to an AI coding assistant.
A Surface Go 2 with Debian and XFCE. The front cameras needed out-of-tree drivers, so the check-in can read an insurance card, a ticket QR code or a badge.
One folder of SVG art (Kio, the wordmark, the icon) renders every branded piece: the boot menu, a splash where Kio bobs while dots pulse, the wallpaper and the account picture. Debian stays Debian underneath, marked with the standard VARIANT_ID=rapidkiosk, and an apt hook re-applies the branding after updates.
The login screen is a web page: a big clock, then one button per edition. If it ever crashes or takes more than 45 seconds to load, the stock sign-in screen takes over, so the tablet can always be signed in to.
Three tiny tray icons became one large button that opens an iPad-style panel. The panel is a web page; a small Python service reads Wi-Fi, sound, Bluetooth and battery and applies what you tap.
One switch covers every way the screen can go dark. A tiny listener closes the full-screen app in front only if it was started as a kiosk, so the Escape key never closes someone's normal window.
The check-in is a web page that opens full screen on sign-in. It shows a poster until someone taps, asks one question per screen, and clears itself 20 seconds after each check-in so the next person never sees the last one.
RapidDashboard joins a company's systems into one datalake and builds the dashboards and apps. RapidOS is the shell that puts those apps on a device people can touch. RapidKiosk and RapidTablet are the two editions on the same tablet.
The platform: your systems joined in one datalake, with live dashboards, apps and AI on top. It builds the check-in and the board the front desk watches.
The shared shell on the device: the sign-in screen with edition buttons, the Control Center and the big taskbar button. Each edition is its own session on top.
The always-on public screen with Kio: patient check-in, visitor sign-in, event check-in, and a poster in between.
The conversation assistant with Remi: it takes the notes at the counter and files them to RapidDashboard.
At a clinic the same tablet does both jobs. Between patients it is the poster and the check-in. When a patient steps up to talk, one tap on the sign-in screen switches it to RapidTablet, and Remi takes the notes.
It's a scenario with a made-up clinic and patients, there to show the idea, and the demo stores nothing. Before a clinic uses it with real patient information, it needs its own HIPAA review, a business associate agreement and a connection to the practice's own scheduling system. Talk to us before you plan on it.
It's a poster: a welcome, the live wait time and this month's reminders, like flu shots. A tap anywhere starts the check-in, and 45 seconds without a touch brings the poster back.
Yes. The demo has three front desks on the same tablet: a clinic, a plant lobby and a trade show. Each is a web app RapidDashboard builds for you, so the questions, the branding and where the answers go are yours.
No. It is Debian Linux with the XFCE desktop, styled so people who use Windows 11 or an iPad feel at home. Debian stays the base, so normal updates, drivers and security patches keep working.
It boots to the sign-in screen, counts down, signs in to RapidKiosk and opens the check-in full screen by itself. Anyone who taps during the countdown stops it and can pick an edition instead.
Full-screen apps have no window controls. The Escape key closes them only for staff with a keyboard, and only for apps started as kiosk apps. Separate accounts for the kiosk and for staff are the next step.
It was built and tuned on a Surface Go 2, but the pieces are ordinary Linux and web pages, so any small x86 tablet or mini PC with a touch screen can run it.
The sign-in screen, desktop and Control Center are copies of the tablet's own pages, fed with sample data. The check-in is the kiosk app built for this example; every patient, visitor and company in it is made up.
Clinics, lobbies, booths and shop floors. RapidDashboard builds the app, and RapidKiosk keeps it on.