A practice website and a clear appointment workflow

We help organise service information and the journey from choosing a time to handling a booking request. The website and appointment workflow should explain what the user has done and when confirmation from the practice is still needed.

Tell us about your appointment workflow

Choosing a time · example
Tuesday14:00Example
Wednesday10:00Example
Thursday14:00Example
Appointment · draft request

Service
Example consultation
Selected time
10:00

A request is not confirmation of an appointment.

An example journey from choosing a service to requesting an appointment.

Information before an appointment

We organise service descriptions and practical information supplied by the practice. The responsible person approves their accuracy. We design a readable mobile view and contact route. The scope concerns the website and booking workflow, not medical advice or clinical records.

Services, providers and calendars

We agree services, provider assignments, availability and calendar rules. An implementation can use STAR modules, including STAR Appointments. Configuration depends on the practice’s workflow; installations do not all have the same features or connections.

A request is not always a confirmed appointment

Users should know whether they selected a proposed time, submitted a request or received confirmation. We agree messages for each state and how changes are handled. Submitting a form alone does not promise an available appointment.

Demonstration example: “Team A — Calendar A” and “Team B — Calendar B” lead to an appointment request. An operator reviews it under the agreed rule. The diagram does not show real availability, people or patient information.

  • Team A

    Calendar A — rules to be agreed.

  • Team B

    Calendar B — rules to be agreed.

  • Appointment request

    An operator reviews the request.

Demonstration example. Fictional data; not a customer implementation. A request is not confirmation. No real appointment times or personal data.

Notifications and operator tasks

We agree what information reaches the team and how staff identify requests that need action. Notification wording should reflect the request’s status. SMS, payments and additional integrations are separate scopes requiring a provider, configuration and testing.

Roles and information collected

We define operator permissions, necessary fields and retention rules. Information is not collected simply because another form field can be added. The service does not promise a clinical system or electronic medical records. The process owner supplies approved privacy and handling arrangements.

Preparation and acceptance

Prepare the service list, roles, calendar rules, confirmation process and approved messages. Do not send clinical histories or patient information for the initial discussion. You receive the agreed website layouts, appointment workflow, configuration and operator guidance.

Checks cover service selection, validation, revised answers, storage, retries, notification and, separately, receipt. We review permissions and whether messages reflect the actual state. Test boundaries and any integrations are explicitly documented.

Product experience

Jacek Moczydłowski.
Website and application.

The website introduces the practice and its services; the application guides visitors to select a time and request an appointment. It connects information with customer service.

Next step

Describe the booking rules and operators’ work without patient information. That is enough to start discussing the scope.

Tell us about your appointment workflow

Have a quick question? Get in touch.