01 / APTAppointments & chairs
Multi-site, multi-chair scheduling with provider rules, treatment-length templates, waitlist fill and online booking that respects your real availability.
Most practice management systems are built for one surgery with one front desk. When you are running four sites, a shared clinical team and a recall list in the tens of thousands, you start working around the software instead of with it. We build the system that fits how your group actually runs, on .NET and Azure, with your data staying yours.

Why they call us
Separate databases, separate reports, no single view of the patient who moves between your practices. Group-level numbers get rebuilt in a spreadsheet every month.
Six-month recalls, overdue hygiene, unscheduled treatment plans. It works when someone has the time to work it, and quietly decays when they do not.
Per-chair licensing that rises every renewal, export formats that make leaving expensive, and a roadmap you do not get a say in.
What’s in the platform
Every organisation starts from the same core and diverges within weeks. The modules below are the starting point, not the ceiling.
Select a zone to see what it does
01 / APTMulti-site, multi-chair scheduling with provider rules, treatment-length templates, waitlist fill and online booking that respects your real availability.
02 / RECAutomated recall cycles over SMS and email, escalation rules, and a live view of who is overdue and by how long, per site and per provider.
03 / CLNStructured, templated charting with per-procedure notes, consent capture, medical history versioning and a full audit trail on every edit.
04 / IMGOdontogram and perio charting linked to imaging, with DICOM-capable storage and bridges to the sensor and OPG software you already run.
05 / BILProcedure-code driven invoicing on CDT or ADA item codes, payment plans, terminal integration and end-of-day reconciliation that matches what the practice manager counts.
06 / CLMClaim submission and on-the-spot claiming, gap and benefit calculation, rejection handling, and a queue that shows exactly which claims are stuck and why.
07 / INVConsumable levels by site, reorder thresholds, supplier ordering, and instrument tracking with sterilization cycle records for audit.
08 / RPTProduction per provider, chair utilisation, recall conversion, treatment-plan acceptance and site comparison. One dataset, no monthly spreadsheet.
Customization
Most vendors stay vague about this until you are mid-contract. Here it is up front, so you can price the gap before you commit.
The AI layer
Off-the-shelf systems bolt a chatbot onto a decade-old database. We build the intelligence into the workflow, using the same engineering we ship for enterprise clients on Azure AI.
Answers, qualifies, books into the live diary and escalates genuine emergencies to the on-call clinician. Built on the same voice-agent stack behind our MyHeartLine product.
Flags high-risk bookings from history, lead time, treatment type and site, so the front desk confirms the appointments that actually need confirming.
Turns a chairside conversation into a structured, editable note against the right tooth and procedure. The clinician reviews and signs, so nothing is filed unread.
Ranks the overdue list by likelihood to book and clinical urgency, instead of working it in alphabetical order.
Surfaces accepted-but-never-booked treatment plans across every site and drafts the follow-up for a human to send.
A grounded assistant over your own reporting data. "Which site lost the most hygiene hours last quarter?" answered from your records, with the query shown.




Integrations
We integrate rather than replace, so what already works keeps working.
Compliance & data
Hosted in your Azure tenancy or ours, in the region you choose. Full export in open formats at any time, contractually. No hostage clause.
Consent capture, retention schedules, access logging and breach response designed against HIPAA in the United States, and the Privacy Act, Australian Privacy Principles and state health records legislation in Australia.
Every clinical record change is versioned with author and timestamp. Role-based access down to field level, MFA, and exportable audit trails.
How the build runs
We sit with your practice managers and clinicians, map how each site actually runs, and audit what is in your current database. You get a written scope and a fixed price before anything is built.
Scheduling, patient records, clinical templates and billing stood up against your real fee schedules and appointment types. You are clicking through working software from week four.
Imaging bridges, payments and accounting connected. Historic patient, clinical and financial data migrated with a reconciliation report you sign off.
One practice goes live with us on hand. Front desk and clinical training, a two-week hypercare window, then the remaining sites follow on an agreed schedule.
A named engineer, an agreed response SLA, and a quarterly cycle where you decide what gets built next. You own the source code.
Questions
For a single surgery, usually yes, and we will tell you that on the first call. The maths changes at around three sites, or wherever per-chair licensing, workarounds and manual reporting start costing more each year than the build would have. Ask us to model it against your current renewal.
Yes. Migration is a defined phase with its own reconciliation report: record counts, financial totals and clinical history checked before go-live. Where a vendor restricts exports, we have extracted from database backups and reporting endpoints before. We assess feasibility during discovery, not after you have signed.
You keep the source code and the data. We hand over the repository, the Azure infrastructure definitions and the documentation, and we will brief an incoming team. The whole point of a custom build is that you are not renting your own operations.
Encrypted in transit and at rest, hosted in the region you choose, role-based access down to field level, MFA, and complete audit logging on clinical records. We design against HIPAA for US practices and the Australian Privacy Principles and state health records legislation for Australian ones, and we will walk your compliance adviser through it.
No. Every AI capability is optional and switchable. Clinical AI is review-and-sign by default, so nothing is written to a patient record without a clinician approving it. Several groups start with reminders and reporting only, and add the rest once they trust it.
A Microsoft-certified core engineering team, with specialists brought in for imaging, integration or migration work as the scope needs. You get named engineers and direct access to them, not an account manager relaying messages.
Most groups do. A common first step is one module alongside your existing system, usually recalls or group reporting, proving the integration and the value before committing to a full replacement.
Thirty minutes, a working demo build, and an honest answer about whether a custom platform is right for you. If off-the-shelf is the better call, we will say so.
You’ll speak with engineers, not account managers.
PanaceaLogics
Typically replies within an hour
Hi there! 👋 How can we help with your project?
Start chat on WhatsApp