GratisAI health · separate recorded clinic waiting time from consultation time · local-first FREE TIER 1 Free Run Available
queue-time strip · paper ticker strip

Separate Recorded Clinic Waiting Time from Consultation Time

A clinic visit can take an hour without an hour of clinician contact. Record three clocks once, then keep the waiting segment separate from the consultation segment before discussing scheduling or access with the practice.

1 · Visit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The queue-time strip processes Visit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: an appointment felt like one undifferentiated hour. After: observed waiting and consultation minutes have separate, inspectable denominators.

2 · Read the queue-time strip

Observation arithmetic only: this does not diagnose, assess care quality or establish a service breach. Ask the clinic's scheduling team to confirm how interrupted or overnight visits should be recorded; discuss clinical concerns with a qualified clinician.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the queue-time strip

Use clocks from the same local day and the same time source. Check-in means the moment you actually registered, not the appointment time printed on a reminder. Consultation start and end refer to one continuous segment you can identify; if a visit contains several separate contacts, do not pretend they form one uninterrupted consultation. Give visits anonymous codes rather than names, diagnoses or provider identifiers. The review percentage is your own discussion threshold, not a service standard. Several visits may be pooled only when you intend to compare the same recording convention. An early check-in inflates the measured waiting period without establishing a delay attributable to the clinic.

Boundary and sources

Observation arithmetic only: this does not diagnose, assess care quality or establish a service breach. Ask the clinic's scheduling team to confirm how interrupted or overnight visits should be recorded; discuss clinical concerns with a qualified clinician.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this queue-time strip for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a queue-time strip. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Visit code | check-in HH:MM | consultation start HH:MM | consultation end HH:MM; the setting is Waiting-share review mark (%). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.