01
Welcome patients with clarity
Turn your website into a reassuring first step, with the right service and an estimated next opening close at hand.
THE DIGITAL FRONT DOOR FOR MODERN CARE
Appointment booking APIs. A patient-first start.
Explore one branded booking experience an Australian practice could build around documented MediRecords appointment APIs. The demo is an integration example, not a ready-made MediRecords widget.
Demo available · Conditional live calls
Your brand, your story Designed for mobile Connected to your workflow
Appointment request received
Connected from the first click
A booking journey that feels like the practice patients already trust.
Own the first moment of care
The booking moment, connected
Connect every part of the booking moment.
A booking request is more than a time in a calendar. It is a handoff between patient and practice — make the journey clear, connected and easy to act on.
02
Connect the right choices
Guide patients through service and provider choices in a journey that feels personal, informed and easy to act on.
03
Keep the moment moving
A clear summary and confirmation keep the patient, your practice and the next step aligned from first click onwards.
One booking concept, in motion
Make every handoff feel seamless.
This interactive concept shows one elegant way a practice or integration partner could connect the patient, the practice and the next step in one considered experience.
Your brand, from first click to confirmation
A patient path built around how your practice works
Clear communications that keep people informed
One possible booking experienceStep 1 of 3
Choose a service
Start the conversation your way
Find a time
See an estimate from practice data
Behind the booking moment
From a first click to a considered confirmation.
Follow one possible integration path for Your Health Clinic. See what MediRecords Connect documents, what the concept app uses, and what an implementer must build.
An interactive explanation, not a live API request or booking.
Step 01 of 06Documented API
Start with the right front door.
Your Health Clinic is the welcoming setting for this example. A real integration first identifies the practice the patient intends to visit.
Capabilities along this step
- GET
/v1/practicesDocumented capabilityDiscover the practice and its identifier.
- GET
/api/public/locationsConcept app endpointLocation choice used by the concept app.
What this means
Practice discovery gives the journey a reliable starting point before any provider, service or time is shown.
What the implementer owns
An implementer maps its public-facing location names to the correct practice identifier.
See the patient-facing concept. Scenario playback only illustrates the journey: it never books or sends patient data. Configured tenants can support guarded live booking writes in the separate booking server.
Explore the booking concept Trial access requiredThe practice advantage
Turn booking into an operational advantage.
Reduce friction before the appointment
Give patients a clearer path to care and make fewer dead ends land with your team.
Guide demand with clarity
Make the right service and provider choices easier to find, understand and act on.
Keep the practice aligned
Keep patient communications clear, connected and consistent with the workflow behind the experience.
Good questions
Before you book a demo.
A few useful details, without the fine-print fog.
Yes. This concept demonstrates one way a practice or integration partner could build an appointment experience that sits inside a practice website and feels like part of its brand. It is an illustrative implementation pattern, not a booking widget supplied by MediRecords.
MediRecords provides documented appointment APIs; this site demonstrates one possible patient experience that could be built around them. It is not a ready-made MediRecords widget. A practice or its chosen implementation partner would own the implementation, hosting, design, integration, practice configuration and production readiness.
No. This is a concept for a patient-facing layer that could be designed around a practice's existing MediRecords appointment workflow. It does not replace that workflow or represent a MediRecords product commitment.
A custom implementation could use your logo, colours, service names, provider biographies and confirmation copy, and could be designed to sit naturally within your existing site. The exact experience would be shaped and delivered by the practice or its chosen implementation partner.
Times shown in the experience are estimates derived from your appointment data — they are not held or guaranteed. Once a patient submits a request, your configured booking workflow reviews and confirms it. The patient receives a confirmation at that point, keeping them and your practice aligned from first click onwards.
Put your practice in the conversation
Give patients a first step that feels like you.
Explore one possible booking experience, then consider how your practice or implementation partner could shape its own journey from first click onwards.
Launch the Appointment Booking ApplicationTrial access required