Tipulog and Clinic Management: One Appointment, Five States - Calendar, Billing and Reminders in One Flow

A clinic appointment passes through five states - booked, confirmed, attended, charged and recorded - and each state produces a different record and sometimes a message. Israeli clinic management systems such as Tipulog and Tiffulit hold all five in one place, which is exactly why they are a separate product from a calendar.

The five states of a single appointment

That table is the whole process. Most clinics complaining about "chaos" actually hold three of these states in a calendar, one in a receipt book and one in a spreadsheet, then try to join them at month end.

Look at the third column. Only two rows produce an outbound message. Everything else is internal writing, which is the opposite of what most people picture when they say "clinic automation".

Why is the reminder not the automation?

Because a reminder is an outbound message and automation is a state change. The difference shows up in one question: what happens when the patient replies.

A system that sends a reminder and does nothing with the answer has saved somebody one phone call. A system that receives an attendance confirmation, marks the appointment confirmed, and flags an unconfirmed appointment as a candidate for release has changed the calendar's occupancy. Tipulog presents reminders and attendance confirmation as part of the calendar itself, and Tiffulit presents automatic reminders and attendance confirmations over WhatsApp and SMS. Both, in other words, treat the reply rather than only the send.

That is also why the channel matters: a channel the patient can answer in produces a new state, while a one-way channel produces only a reminder. The channel comparison is covered in SMS versus WhatsApp versus email for reminders.

What happens when a patient cancels forty minutes before?

This is the case where a system differs from a calendar. Four things need to happen, and only the first is obvious:

• The slot is released in the calendar and shows as available in online booking.
• The cancellation policy is evaluated. If a deposit was taken, what happens to it is a rule defined in advance rather than an argument in the moment. Tiffulit presents online deposit collection, which is exactly why that capability exists.
• The waiting list fires. Whoever asked to be notified on a cancellation gets a message, and the first to confirm takes the slot.
• The cancellation is written to the patient record. Three last-minute cancellations are a pattern, and anyone not recording them cannot see it.

The rule underneath all four: anything you expect to see in a report at year end has to be written the moment it happens. A cancellation that was not recorded does not exist.

What does "registered with the Tax Authority" actually mean here?

The Israel Tax Authority maintains a register of software intended for managing a computerised accounting system, and that register is publicly searchable. A software vendor applies, and the software receives a registration number.

Tipulog states on its site a registration number of 214901, for the categories "physician's diary" and "advance patient registration diary". That is a verifiable claim: you go to the register on the Tax Authority site and search for the software name.

What such a registration is not: the Tax Authority notes that a registration certificate does not constitute approval of the software's correct performance or of its compliance with bookkeeping instructions. The registration is a fact about the software, not a guarantee that your use of it is correct. What is actually required of you is a question for whoever keeps your books.

For choosing a system it remains a useful signal: it is verifiable, it does not change with every marketing campaign, and you can check it before committing.

Medical and personal data: what is a fact and what is not

Patient data is personal data, and information about a person's health is more sensitive than a name and phone number. That is a statement about the category of information, not a legal instruction.

What follows from it at the design level:

• Role-based permissions. Reception needs times and contact details. A visit summary is a different field entirely. Tipulog presents staff management and permissions as a separate module.
• The outbound message is not the place for clinical content. A reminder says when and where. Naming the treatment in the message body puts information into a channel you do not control.
• An employee who leaves. Revoking access is an action that has to be defined, not something remembered.
• Data exports. If information leaves into a spreadsheet for a report, that spreadsheet is another copy living outside the permission model.
• External parties. HMOs and insurers are additional participants in the information flow, and Tipulog presents financial management with them as part of its billing module.

The Privacy Protection Authority publishes the regulatory framework on its official site, and that is the place to read rather than relying on a summary.

What to have defined before switching systems

• Which of the five states in the table you genuinely track. If you do not track "charged", no system will fix that for you.
• Who marks an appointment as attended, and when. If it happens at the end of the day from memory, the data is not reliable.
• What the cancellation policy is and what happens to a deposit, written so it can be configured as a rule.
• Who sees what, by role rather than by personal trust.
• How you get the full history out if you decide to change systems.
• Who is responsible for reminders actually going out, and how you discover in the morning that yesterday's did not.

Related: automation for clinics, reducing no-shows with appointment reminders.

Sources

• Tipulog - about the system
• Register of software for computerised accounting systems - Israel Tax Authority
• Privacy Protection Authority - gov.il