Appointment and Medication Reminders Sent From Inside the Clinic
Front-desk staff send reminders from a PC on the clinic network. Patient numbers and message logs stay in the clinic's own database, not in a messaging vendor's account.
What clinics actually send
Five message types cover most of the reminder workload. Each has a different timing rule and a different need for a reply.
| Message | Typical timing | Reply needed | Notes |
|---|---|---|---|
| Appointment reminder | 48 and 24 hours before | Yes — confirm or reschedule | Two reminders reduce no-shows more than one |
| Medication reminder | Daily or weekly | No | Keep the text short and free of dosage advice |
| Lab result ready | On result release | Optional | Never include the result in the message |
| Recall invitation | Per screening interval | Optional | Requires an opt-out route |
| Closure or emergency notice | Same day | No | Send early; do not schedule inside quiet hours |
Where patient data lives
Inside the practice. That is the whole point of running the gateway on your own network.
The contact list and the message log sit in a local SQL database on the clinic's PC or server. Export, backup and deletion are operations the clinic performs, not a request to a vendor.
We describe the product as suitable for HIPAA-aligned workflows; we do not claim that the software makes an organisation compliant. Compliance depends on your policies, your network, your staff training and your agreements with carriers.
Use the compliance guide for the checklist, and the privacy policy for what we do and do not collect.
Data map
| Phone numbers | Local SQL database |
| Message text | Local SQL database |
| Delivery status | Local SQL database |
| Vendor copy | None |
Two-way confirmations and rescheduling
A reply keyword can update the appointment state without anyone opening the inbox.
Confirm
A reply containing YES marks the appointment confirmed and sends the preparation instructions.
Reschedule
A reply containing CHANGE triggers a link to the booking desk or creates a callback task in your system.
Opt out
STOP sets a permanent flag and removes the number from every future reminder campaign.
Verification codes for patient portals run on the same gateway; see OTP and 2FA delivery.
Connecting to your EHR or PMS
Two paths work without a vendor-specific connector: a table the software watches, or an HTTP call from your system.
SQL outbox
Your system inserts a row into a table with number, text and send time. The gateway sends it and writes back the status. Works with MySQL, SQL Server and Oracle.
HTTP call
Your scheduling job posts to the local API when a reminder is due. The response carries the message id you can poll for status.
Both examples run on the local network only. The API is an Ultimate-edition feature; the SQL listener is available in every edition.
Capability and limits
Supports
Appointment, medication and recall reminders, two-way confirmations, local records, SQL and HTTP triggers.
Not supported
No clinical decision support, no result values in messages, no claim of HIPAA compliance for your organisation.
Depends on
Your policies, staff training, carrier terms and the accuracy of the contact list.
Vaccine fridge, sample storage or pharmacy temperature alarms: see cold chain SMS alerts for the same local-send design.
Clinic questions
Is the software HIPAA compliant?
No software can be compliant on its own. We say the product supports HIPAA-aligned workflows because data stays on your network and you control retention. Your policies, agreements and training determine compliance.
Can reminders include lab results?
We recommend not sending result values by SMS. Send a notification that the result is ready and ask the patient to contact the clinic or the portal.
How many reminders can a clinic send per day?
It depends on the modem and the SIM plan. A single modem handles a few hundred messages comfortably; a modem pool handles more. Test with your own hardware before a large recall campaign.
Does it integrate with our practice software?
If your system can write to a SQL table or call an HTTP endpoint, yes. There is no per-EHR connector to license.
What happens when a patient replies STOP?
The number is flagged permanently and removed from future campaigns, including lists imported later.