Maestra v1.6

Patient reminders

Settings now carries a Patient Reminders screen.

• Up to 5 reminders per account. Each one goes out by text message, by email, or by both, ahead of an appointment.
• Lead time runs from 15 minutes to 1 week, picked from 15, 30 and 60 minutes, 2, 3, 6 and 12 hours, and 1, 2, 3 and 7 days.
• Scope per reminder: one-off appointments, appointments in a series, or both.
• The wording is yours. Placeholders fill in the details: {patientName}, {practitionerName}, {when}, {date}, {time} and {timeUntil}, with Portuguese aliases that store the same keys, so a template keeps rendering after the account language changes.
• Text bodies hold up to 320 characters, email bodies up to 2000.
• Text messages go out only between 8am and 9pm, in the appointment’s own time zone.
• Text messages are one-way: patients cannot reply to them, so ask them to get in touch as usual.
• Email arrives from Maestra <[email protected]>, a send-only address. The practitioner’s own address is never exposed to patients.
• Two templates arrive with the account, “3 days before” and “1 hour before”, both inactive, so nothing goes out before they have been read.
• Every phone number and email address on a patient carries a flag for the one that receives messages, with the date consent was recorded. Set it per patient, or across several patients at once.
• Reminders are scheduled 30 days ahead. Anything further out is picked up on a later sync.
• The screen reads on any plan. Creating, editing, reordering and deleting reminders needs Pro.

Google Calendar

• Connect a Google account in Settings › Calendar Sync, then enable calendars one at a time, each with its own toggle.
• Busy time from the enabled calendars lands on the agenda as muted grey cards labelled Busy, subtracting availability wherever manual blocked time already did. They are inert: nothing to open, nothing to drag.
• Availability only. The connection reads free and busy times, so no event title, location, guest or organizer can reach Maestra even in principle. The scopes requested are calendar.freebusy and calendar.calendarlist.readonly.
• Read-only. Maestra appointments are never written back to Google.
• Each connection syncs on connect, then every 15 minutes, and Sync Now runs it on demand.
• The mirrored window runs from the start of the current UTC day to 180 days ahead. Past busy time is left out.

Your practice

• The practice page is now a board of the charts you pick. The catalogue holds twelve: occupancy, encounters over time, encounters by weekday, attendance mix, no-shows over time, hours booked, billed over time, received over time, outstanding over time, charges by settlement, payments by method and new patients.
• Up to twelve charts sit on the page at once, dragged into the order you want.
• Defaults follow the profession and are seeded once, so the page opens with something to read before any of it is arranged.
• One period selector at the top governs every chart on the page.
• Chart specs are encrypted on-device, like every other record.

Patient stages

• The Patients list header opens a stage board: one lane per stage, patients as cards inside their lane.
• Drag a patient from one lane to the next to restage them.

Getting around

• A patient or an appointment opens from whichever tab you are on, without being sent to another tab first.

Data protection

Zero-knowledge architecture: records are encrypted on-device, and Maestra’s servers store only encrypted data and cannot read it, including every amount, so Maestra cannot see what you earn. Audio and text processed during transcription and note generation are sent to specialized AI providers under data processing agreements, in line with GDPR, processed transiently and never stored. Full detail in the documentation.

Reminders are the first feature that sends anything to a patient, so the boundary is worth stating plainly. A reminder body is sealed on the device before the relay ever sees it, and the relay unseals it only to hand the message to the SMS or email carrier. The carrier therefore does see the message, which is why reminders are not zero-knowledge end to end: whatever is written into a reminder is what leaves, and nothing else does. The calendar connection is narrower still, since free and busy times are all it reads and nothing is sent out to Google.