We ship weekly and write the notes ourselves. No marketing-flavored bullet points — just what changed, why we shipped it, and what to watch for.
A clinic's jurisdiction drives its insurance rail, HIE routing, date and currency formats and compliance surfaces, so it can no longer fall back to a default. Both it and an admin contact are now mandatory when an account is created.
Patient and insurance names were stored as split variants that could disagree with each other. They are now a single canonical field, so search, PDFs, claims and messaging all render the same spelling.
Notifications now deliver over push alongside in-app, email, SMS and WhatsApp, through Firebase Cloud Messaging with OAuth2 service-account auth. An unconfigured adapter reports itself rather than pretending to send.
WhatsApp privacy-LID digits were being read as the patient's phone number, which could attach a reply to the wrong contact. Conversation state is now keyed per JID, so identity holds for the length of the thread.
The staff inbox can be cleared down. Threads archive or delete without taking the patient record with them.
Inbound patient messages can be answered automatically and turned into a booked appointment, with an independent on/off switch per channel. With no configuration row every channel is off and messages reach only the staff inbox.
A store-ready mobile shell with committed native projects, push registration, deep links, and an opt-in biometric app-lock that triggers after five minutes of inactivity and fails open when biometrics are unavailable.
Clinical red flags are matched structurally in both English and Arabic, with negation handling and a full audit trail, so a flag is raised on what a note means rather than on a substring appearing inside it.