Patch notes

Every level, in order

How Mediora was built, phase by phase. 'Audit' entries are the passes where we re-tested a finished part against the running system and fixed what we found before moving on.

Next level

What's coming

From our roadmap. Not built yet, so not on any plan.

Roadmap
  • Not included: Live evaluation of the assistant's answers against real clinic conversations
  • Not included: Patient self-service booking
  • Not included: Multi-branch clinics
  • Not included: Insurance claims
  • Not included: A regional compliance review

Shipped

  1. Phase 7.5Audit

    The clinical record, checked line by line

    • Every rule about who can read and write notes and prescriptions was re-tested against the running system before release.
    • Fixes were confirmed by re-running the same test that found the problem.
  2. Phase 7.4New

    A doctor's own day

    • Doctors get 'My day': their appointments, their weekly roster and their leave, in one view.
    • The shared clinic calendar stays visible to doctors, so everyone knows how busy the afternoon is.
  3. Phase 7.3New

    Prescriptions

    • Write prescriptions with drug, strength, form, dose, frequency, duration, quantity and instructions.
    • Issued prescriptions are frozen. A correction voids the original and links a replacement, so what the patient was handed stays readable.
    • Print on A5 from the browser, with a VOID watermark on voided prescriptions.
  4. Phase 7.2New

    Clinical notes

    • Chief complaint, diagnosis and free-text notes, one note per visit.
    • Drafts are private to the doctor writing them. Signing makes a note permanent; corrections are addenda.
    • Receptionists can't open clinical notes. The owner can read signed notes.
  5. Phase 7.1New

    The clinical record's foundations

    • Notes, addenda, prescriptions and prescription items, each isolated per clinic from the moment they existed.
    • A signed note can't be edited by anyone; the database enforces it.
  6. Phase 6.9Audit

    The assistant's settings and activity, audited

    • Re-tested the assistant's settings, knowledge base, usage and activity screens against the running system, and fixed what we found.
  7. Phase 6.8New

    Ready to run in production

    • Separate health and readiness checks, so a server isn't sent traffic before it can serve it.
    • Browsers can only call the API from approved addresses; the server refuses to start without that list.
  8. Phase 6.6New

    The assistant gets a control panel

    • Owners set the assistant's name, extra instructions, booking and cancelling switches, escalation keywords and handoff message.
    • An activity log records every turn: replied, handed to staff, skipped or failed, and why.
    • The dashboard counts conversations the assistant handled and the ones it passed to staff.
  9. Phase 6.5New

    A knowledge base the assistant can search

    • Write questions and answers about parking, insurance, what to bring. Edits apply to the very next message.
    • When the assistant can't find an answer, it hands over instead of guessing.
  10. Phase 6.4New

    A safety check before every reply

    • Emergencies and requests for a person are caught first, by fixed rules that don't depend on AI, in English, Roman Urdu and Urdu script.
    • Everything else goes to one assistant that answers and books using your real calendar.
  11. Phase 6.3New

    The assistant can check and book

    • Tools to list services and doctors, check availability, book, look up and cancel a patient's own appointments, and hand over to staff.
    • Bookings go through the same rules as your receptionist's, and the assistant can't override them.
  12. Phase 6.2New

    One answer per burst of messages

    • Patients who send three short messages in a row get one reply, not three.
    • A conversation a person has taken over is never answered by the assistant.
  13. Phase 6.1New

    Foundations for the assistant

    • Per-clinic assistant settings, switched off until the owner turns them on.
    • Assistant replies are counted against the plan, separately from template messages.
  14. Phase 5.6Audit

    Campaigns, audited

    • Re-tested sending, retries, cancelling mid-campaign and per-recipient results, and fixed what we found.
  15. Phase 5.5Audit

    WhatsApp setup and templates, audited

    • Tested against a real WhatsApp Business account.
    • Added a way to restart a conversation with an approved template after WhatsApp's 24-hour window closes.
  16. Phase 5.4Audit

    The inbox, audited

    • Re-tested message intake, delivery ticks, takeover and assignment against the running system, and fixed what we found.
  17. Phase 5.3Audit

    The scheduling engine, audited

    • The double-booking guarantee, daylight-saving arithmetic and rescheduling held up under testing. Smaller issues were fixed.
  18. Phase 5.2Audit

    The patient registry, audited

    • Searching by a phone number the way a patient reads it aloud, like '0300 123', now finds them.
  19. Phase 5.1New

    Confirmations and reminders

    • Every booking and reschedule sends a WhatsApp confirmation with a template you choose.
    • Reminders go out at a lead time you set, on a queue of their own so a big campaign can't delay them.
  20. Phase 5New

    The front desk

    • A real-time shared WhatsApp inbox with takeover, assignment and read receipts.
    • Patients keyed by phone number, created automatically from their first message.
    • Doctor rosters with split shifts, dated leave, and booking that refuses double bookings.
  21. Phase 4.1Audit

    Dashboard, plans and audit log, audited

    • Re-tested daily totals in clinic time, plan limits and the audit trail, and fixed what we found.
  22. Phase 4New

    Dashboard, plan limits and audit log

    • Daily totals calculated at midnight in each clinic's own timezone.
    • Plan limits checked on the server, with a clear message when one is reached.
    • Every change recorded with who made it, when and from where.
  23. Phase 3New

    WhatsApp Business connection

    • Connect your WhatsApp Business account; access tokens encrypted at rest.
    • Message templates submitted to Meta, with approval status synced back.
    • Broadcast campaigns sent from a queue that respects Meta's rate limits.
  24. Phase 2.1Audit

    Seat counting, fixed

    • Closed a way to exceed a plan's doctor limit by suspending and reactivating staff.
  25. Phase 2New

    Team and services

    • Invite receptionists and doctors with a temporary password they change on first sign-in.
    • Suspend anyone instantly. Archive services instead of deleting them, so old invoices and reports stay correct.
  26. Phase 1New

    The foundation

    • One system for many clinics, with each clinic's data separated by the database itself.
    • Clinic profile, timezone and opening hours.

Continue?

Set up your clinic in an afternoon. The free plan needs no card and no sales call.

Or book a demo