Best Practice (Bp Premier) + AI Healthcare
Add an automation layer to the practice management system your GPs already work in. Recall, reminders, waitlist backfill, scribe notes and after-hours phone answering — all reading from and writing back to Bp Premier, with Bp remaining the clinical record of truth.
Why Bp Premier Practices Need an Automation Layer
Bp Premier is a capable clinical system and it is not the problem. The problem is everything that happens around it — the recall list nobody has time to work, the reminder calls, the cancelled slot that goes unfilled, the notes written at 8pm. Bp records all of it faithfully. It was never designed to do it for you.
Bp Is the Record of Truth
Any automation that asks a GP practice to move its clinical record somewhere else has already failed. Bp Premier holds the history, the scripts, the results and the medico-legal record, and it should keep holding them. The right architecture layers communication and administrative automation around Bp — reading what it already knows, writing back through supported interfaces, and never asking your clinicians to work anywhere other than the system they trained on.
The Workload Sits Outside Bp
The tasks that consume your reception team are not data entry — they are conversations. Ringing patients whose care plan review is due, chasing the ones who did not answer, filling the slot that opened at 9:40am, taking the call that came in after close. Bp tells you these things need doing and produces the lists. The doing is manual, it competes with the queue at the front desk, and it is the first thing dropped on a busy day.
Recall Lists Only Grow
GP recall is relentless: GP Management Plan reviews, Team Care Arrangement follow-ups, health assessments, cervical screening, bowel screening for eligible patients, immunisations, and results that need a conversation. The RACGP Standards require a recall and reminder system, and Bp gives you one. But a list is not an outcome. Every item that ages out is a patient who did not get recalled and MBS-funded care the practice never delivered.
What the Bp Premier Integration Does
Six capabilities, each reading from and writing back to Bp within an explicit scope you control. Turn any of them on or off independently — most practices start with recall and reminders.
Bidirectional Sync With Bp Premier
A connector reads your Bp appointment book, patient demographics and recall entries on a throttled schedule, and writes back only within an explicit, logged scope. Bp stays the clinical record of truth — the AI layer never becomes a second system your team has to reconcile.
- Reads appointments, demographics, recall and reminder entries
- Writes bookings, recall status and communication history back to Bp
- Throttled queries and off-peak batching to protect the practice server
- Every write logged with timestamp, trigger and reversible scope controls
Automated Recall From Your Bp Recall List
The RACGP Standards require general practices to run a recall and reminder system. Most practices have one in Bp and no time to work it. The AI takes the list you already maintain and actions it, patient by patient, on the day each item falls due.
- Works your existing Bp recall list rather than a parallel database
- Message copy written per recall reason, not one generic template
- Care plan reviews, health assessments and screening recalls handled separately
- Recall marked as actioned in Bp the moment the patient books
Reminders and Waitlist Backfill in the Bp Appointment Book
Multi-channel reminders with confirm, cancel and reschedule handled without reception picking up the phone. When a patient cancels, the freed slot is offered to your waitlist immediately and the first confirmed patient is booked straight into Bp.
- SMS, email and voice reminders with one-tap confirm or reschedule
- Cancellations trigger instant waitlist outreach, matched to clinician and slot type
- First confirmed patient booked into the Bp appointment book automatically
- Replies logged against the patient record instead of stranded in a phone
AI Scribe Notes Landing in the Bp Patient Record
The scribe captures the consultation and files a structured draft progress note against the right patient in Bp. The clinician reviews, edits and signs off. No copy-paste between an AI tool and the record, and no note enters the file unreviewed.
- Structured draft notes filed against the correct Bp patient
- Clinician review and sign-off required before anything is finalised
- MBS item prompts surfaced at the point of documentation
- Unreviewed drafts flagged so documentation gaps do not accumulate
After-Hours Phone Answering That Books Into Bp
Calls arriving when reception is closed are answered, triaged against your rules, and booked into a real slot in the Bp appointment book. Urgent presentations are escalated to your on-call arrangements rather than parked in a voicemail nobody hears until Monday.
- Calls answered outside opening hours, weekends and public holidays
- Bookings written into genuinely available Bp appointment slots
- Escalation rules for urgent symptoms, following your practice protocol
- Call summaries and outcomes logged against the patient record
Australian Hosting and Privacy Act Handling
Bp data stays in Australia. Patient information is processed on Australian infrastructure under the Privacy Act 1988 and the Australian Privacy Principles, with no offshore processing and no transfer to jurisdictions your patients never agreed to.
- Australian-hosted processing — no cross-border disclosure under APP 8
- TLS 1.3 in transit, AES-256 at rest, scoped credentials you can revoke
- Full audit log of every read, write and patient communication
- Consent and communication preferences tracked per patient
Each capability has its own deep-dive: the patient recall system, appointment reminders, the AI medical scribe and after-hours answering. This page covers how they attach to Bp specifically.
Bp Premier + AI vs Bp Premier Alone
Bp Comms already sends appointment SMS, and for plenty of practices that is enough. The gap opens where a message needs a reply actioned, a list needs working, a slot needs filling, or a phone needs answering at 7pm.
| Feature | Bp Premier + AI Healthcare | Bp Premier Alone | Manual Process |
|---|---|---|---|
| Patient Recall | Automated outreach + booking | Recall list only | Reception phone calls |
| Appointment Reminders | Multi-channel + smart timing | Bp Comms SMS | Staff phone calls |
| Waitlist Backfill | Instant automated | Manual | Manual |
| Two-Way SMS Handling | |||
| After-Hours Phone Answering | |||
| Scribe Notes Into the Record | |||
| Communication Logging | Automatic to Bp record | SMS only | Manual entry |
| Staff Time Required | Near zero | Moderate | Hours daily |
If you are weighing this against engaging a call centre, our comparison against medical answering services sets out the difference that matters most to a Bp practice: an answering service takes a message for your reception team to action, whereas an integrated layer books the appointment into Bp itself.
Setup Process for Bp Premier Practices
Bp Premier typically runs on a server inside the practice rather than behind a public cloud API, so this is not a five-minute OAuth connection. Budget one to two weeks — most of which is scheduling, not engineering.
Practice Assessment
We confirm your Bp Premier version, whether Bp runs on a server in the practice or a hosted desktop, who supports your IT, and how your recall reasons and reminder protocols are currently structured.
Connection Session
We connect to your Bp instance using scoped, revocable credentials alongside your practice manager and IT support. This is the step that needs a diary slot — everything else is configuration around it.
Configure Scope and Templates
Recall reasons, reminder timing, message copy and write-back scope are configured to your practice. Many practices start with recall write-back on and appointment write-back off, then widen the scope once they trust it.
Supervised Go-Live
The AI starts contacting patients while we watch closely for the first two weeks, tuning reminder timing, recall sequences and escalation rules against how your patients actually respond.
Where Your Bp Data Goes — and Where It Does Not
For practice managers and the IT support who will ask the hard questions before anything touches the Bp server.
Connection Architecture
Bp Premier stores its data in a Microsoft SQL Server instance, usually on a server in the practice. We connect through the Bp partner interfaces where they are available for your version, and otherwise via a scoped, read-limited service account against that instance. Nothing is installed on clinician workstations.
Sync Mechanism
Appointment and recall changes are polled on a short throttled cycle so the appointment book stays current, while heavy work such as full recall list extraction is batched outside consulting hours. If the connector drops, Bp is unaffected and the queue reconciles when it reconnects.
Data Residency
Patient information is processed and stored on Australian infrastructure. There is no offshore processing, which means no cross-border disclosure to justify under Australian Privacy Principle 8, and no foreign jurisdiction with a claim over your patients' records. A data residency statement is available for your practice accreditation file.
Write Scope and Revocation
Every write category — appointments, recall status, communication history, draft notes — is individually toggleable and individually audited. Credentials are scoped and revocable from your side at any time. Revoke them and the AI layer goes quiet; Bp carries on exactly as before.
Practices claiming the PIP eHealth Incentive already upload shared health summaries from Bp each quarter — see My Health Record AI integration for how AI-assisted summary preparation fits alongside that obligation without changing who signs it off.
Bp Premier vs Other Supported Practice Software
Australian practices run on different systems, and the integration shape changes with each one. If you are still choosing — or running more than one system across sites — start here.
Cliniko
Cloud-native with a public API, so it connects in minutes rather than weeks. Common in allied health and increasingly in general practice.
See the Cliniko integration →Medical Director, Genie, Zedmed
Other established Australian systems, each with its own data model and connection path. Scoped individually at the assessment call.
AI for GP clinics →Bp VIP.net and Bp Allied
Best Practice Software's specialist and allied health products — related to Bp Premier but different underneath, and scoped as separate integrations.
AI for medical specialists →Not sure which capabilities to start with, or how to evaluate a vendor asking for access to your clinical database? Read how to choose healthcare AI software before you sign anything.
Frequently Asked Questions
The questions Bp Premier practice managers and their IT support ask before connecting anything to the clinical record.
The integration targets the recent named releases of Bp Premier — Jade, Saffron, Orchid and later — running on a supported Microsoft SQL Server instance. Older releases can usually still be connected, but the data available and the reliability of appointment book write-back vary, so we confirm your exact version at the assessment call before quoting any timeline. Bp VIP.net, used widely by ophthalmology and other specialist practices, and Bp Allied are different products with different data models underneath: both can be integrated, but they are scoped separately rather than treated as Bp Premier. If you run Bp on a hosted or managed desktop rather than a server in the practice, mention it at the assessment stage — it changes how we connect, not whether we can.
It is deliberately asymmetric. Reads are broad: appointments, patient demographics, recall and reminder entries, and the follow-up items your team relies on. Writes are narrow and explicit. The AI can book, move or cancel appointments in the Bp appointment book, mark a recall as actioned, record communication history against the patient, and file a scribe-generated note as a draft progress note for clinician sign-off. It does not edit existing clinical content, does not alter past notes, and does not touch billing records. Every write is logged with a timestamp and the trigger that caused it, and each write category can be switched off independently — some practices run recall write-back enabled and appointment write-back disabled for the first month, then widen the scope once they trust it.
It should not, and the architecture is built around that risk. Bp Premier is usually the busiest thing on the practice server during consulting hours, so the connector reads on a throttled schedule with query limits, batches heavy work such as recall list extraction outside peak times, and holds no long-running locks. Nothing about the AI layer sits between your clinicians and Bp: if the connector stops, Bp keeps running exactly as it does today and your team keeps booking, consulting and recalling as normal. The clinical record itself is unchanged in structure — entries are added through supported interfaces rather than by modifying the underlying database schema, so your Bp upgrades and your Best Practice Software support arrangements are unaffected.
Your Bp recall list stays the source of truth — the AI works it rather than replacing it. Reception or the clinician flags a recall in Bp exactly as they do now, with its reason and due date. The connector reads that list, and when an item falls due it starts a personalised outreach sequence on the channel the patient has consented to: SMS first, then email, then a voice call for non-responders. Message copy is written for the recall reason, so a cervical screening reminder does not read like a care plan review. When the patient books, the appointment is created in the Bp appointment book and the recall is marked as actioned, so it drops off the list without anyone typing anything. Non-responders are escalated back to your team with the full contact history attached.
Yes, but as drafts requiring clinician sign-off, not as finished records. The scribe captures the consultation, generates a structured note, and files it against the correct patient in Bp for the treating clinician to review, edit and approve. Until the clinician signs off it remains a draft and is clearly marked as one. This is not a technical limitation we are working around — it is the design. Under AHPRA expectations the clinician remains the author of the clinical record and is accountable for its accuracy, so an AI-generated note nobody has reviewed has no business sitting in a patient file. Drafts left unreviewed are flagged so documentation gaps do not quietly accumulate. The AI medical scribe page covers the capture and sign-off workflow in detail.
Plan for one to two weeks rather than the same-day connection a cloud system allows, because Bp Premier typically lives on a server in your practice rather than behind a public API. The sequence is: an assessment call to confirm your Bp version, hosting arrangement and recall protocols; a connection session with your practice manager and whoever supports your IT, which is the step that needs scheduling; configuration of recall reasons, reminder timing, message templates and write-back scope; then a supervised go-live. Most of the elapsed time is coordination, not engineering. Plans start from $499 per month for a single-practitioner practice, and the assessment is free — the pricing page sets out multi-practitioner and multi-location options.
Put Your Bp Recall List to Work
Book a free assessment and we will confirm your Bp Premier version, map your recall reasons, and show you exactly what the integration would read and write before you commit to anything.
Prefer to talk it through? Call +61 3 9999 7398