Skin check booking
Patients pick a visit type, such as a full-body check or a follow-up, and see open slots from the clinician they prefer.
SIZ Group designs and builds a dermatology patient self-service app where patients request prescription refills, book skin checks, get reminders and see what happens next after a biopsy. Each project starts with a free scoping call and ends with a written proposal.
Dermatology offices handle a steady mix of planned and urgent work. Full skin checks are often booked months ahead, while a patient with a new rash or a question about a biopsy may call the same morning. Refill requests for topical treatments arrive by voicemail, fax and portal message, and each one needs a clinician decision before anyone replies.
The breaks happen where those channels meet. A biopsy result may be ready but not yet released to the patient, and the front desk gets asked about it three times. A refill request sent to the wrong inbox waits a day. Nobody can see every open item in one place, so the patient feels the delay first.
Most dermatology practices run an electronic health record and a practice management system for scheduling, charting and billing. ModMed is widely used in dermatology, and athenahealth serves many specialty groups, while smaller offices often pair their system with a standalone scheduling tool. The app should read availability and visit status from whichever system the office runs, rather than create a second schedule that staff must keep in step.
Pathology results usually come through a lab portal or an interface feed. Before showing anything to a patient, we would confirm whether result status can be shared safely and whether release rules, such as waiting for the clinician's review, can be built in. Payments and reminders would run through established services such as Stripe and Twilio.
The most costly mistake is releasing sensitive results too early. A biopsy result shown in the app before the clinician has spoken to the patient causes alarm and extra calls. The app should hold results until the clinician releases them, and it should say plainly that a result is still under review.
Another mistake is building one flow for everything. A cosmetic consultation, a medical skin check and a refill request each have different rules for who sees them and how fast they are answered. We would map each request type with the office before designing any screen.
Patients pick a visit type, such as a full-body check or a follow-up, and see open slots from the clinician they prefer.
A structured form with medication, pharmacy and reason, routed to the clinician who manages that treatment.
Tells patients when a biopsy or lab result is expected and holds the result until the clinician has reviewed it.
Pre-visit questions, a medication list and a photo upload for a spot the clinician wants to see before the visit.
The main cost drivers are the request types, the number of booking rules and the systems the app must connect to. A practice that wants live pathology status and photo uploads for rash checks needs more build than one that handles bookings and refill messages. The starting point is a mobile app at $4,500, and the final figure follows the scope written into the proposal.
We keep scope under control by splitting the work into phases. The first release usually covers booking, requests and reminders. Photo uploads, result notifications and payments can follow once the team has learned what patients actually use, and each phase is quoted separately so the owner decides when to add it.
The front desk must trust the app before patients will. We would show the team how each request appears in their queue, how a refill is routed to the clinician and how to explain that a result is pending. Staff who can answer the question inside the app will not need to repeat it on the phone.
Patients will find the app through the after-visit summary, a QR code in the waiting room and a link in the appointment reminder. We would start with one clinician's patient list, watch how requests come in, and then widen the rollout to the full practice.
A short script keeps the phone line and the app saying the same thing. When a patient asks about a pending result, the answer is that the result is still being reviewed, the clinician will call, and the app shows that same message. Writing the script with the office is quick, and it saves many repeat calls.
Owners usually care about three numbers: how many routine calls the front desk takes each week, how quickly a refill request gets a reply and how many booked skin checks are kept. We agree on a baseline from the months before launch and track each figure on a simple dashboard.
Patient feedback is the fourth measure. A short question after each booking, such as how easy it was to find a slot, shows where the flow still causes friction. We would review those answers monthly and adjust the screens or the wording rather than assume the design is right.
The starting point for a mobile app is $4,500. Request types, whether photo uploads are included and how many systems the app must connect to all shift the figure, and each of those lines appears in the proposal.
Only when your clinicians decide a result should be released through the app. The app can show that a result is pending and when the office expects to speak with the patient, and it holds the result itself until the clinician approves it.
Yes. Each visit type can carry its own booking rules, questions and clinician, so a cosmetic consultation never lands in a medical queue. We set those rules with your office during scoping.
Photos attach to the visit, sit behind access limited to the clinicians and staff who need them, and never stay on personal phones. Where HIPAA applies, we agree on safeguards and a business associate agreement before the build touches protected health information.
Bring your request types to a free scoping call and receive a proposal that itemizes the build.