Health Practice Management · GP clinical software
Best Practice
integration & API.
Major Australian GP clinical software — we build the patient-facing experiences it doesn't cover.
BP What is Best Practice?
Best Practice in plain English.
Best Practice Software is a major Australian GP and specialist clinical software platform, widely used by Australian general practices. It handles clinical records, prescribing, MBS/PBS billing, pathology integration, and practice management. Independently developed in Bundaberg, Queensland.
What businesses use it for
Common Best Practice
use cases.
- 01 Clinical record management for GP and specialist practices
- 02 Electronic prescribing and PBS submission
- 03 MBS billing and Medicare claiming
- 04 Pathology and imaging result management
- 05 Referral and specialist correspondence
- 06 Reporting and practice analytics
Why custom?
Beyond the default Best Practice integrations.
Best Practice is one of the two dominant clinical software platforms in Australian general practice (alongside Medical Director). We build the patient-facing and operational layers most practices need: branded portals, online booking, structured intake, telehealth flow, and integration with the rest of the practice stack.
What we build with Best Practice
Common Best Practice integrations.
Branded patient portal connected to Best Practice records (within compliance bounds)
Online booking integrated with Best Practice appointment system
Structured intake forms that pre-populate clinical records
Telehealth flow tied to Best Practice patient records
Practice website with appointment booking and referral capture
Patient communication automation respecting Best Practice data
What you can expect
What a Best Practice integration usually delivers.
Patient and appointment data that stays consistent
Information stays aligned between Best Practice and the tools around it, removing the manual double-entry that introduces errors into clinical records.
Recalls and reminders that run themselves
Automated recall and reminder workflows triggered from Best Practice events, reducing missed appointments and the load on reception.
Reporting beyond the built-in screens
Dashboards that combine clinical and operational data, so practice managers get the picture they need without manual exports.
Designed around health-data sensitivity
Australian data residency, encryption in transit and least-privilege access, supporting the practice in meeting its privacy and security obligations.
Commonly paired with
Best Practice works with the rest of your stack.
How we build
Production-grade.
Not Zapier in a trench coat.
Every Best Practice integration we ship handles failure properly: idempotent jobs, retry logic, dead-letter queues for unrecoverable cases, and observability so you can see exactly where data is at any moment.
Tested
Real test suite, real edge cases. Not just "it worked once."
Observable
You see what is happening — events logged, errors surfaced.
Maintainable
Documented, version-controlled, handed over properly.
More Health Practice Management
Other health practice management platforms we connect.
C Cliniko
Cloud-based PMS for allied health — we build patient portals, multilingual content, and bespoke integrations.
N Nookal
Allied health PMS popular with multi-practitioner clinics — we add patient portals and integration depth.
MD Medical Director
Major Australian GP clinical software — we build patient-facing portals and integration layers.
H Halaxy
Cloud allied health PMS with built-in client booking — we add bespoke portals and integration depth.
FAQ
Common questions about Best Practice integration.
Can you build patient portals on Best Practice?
Yes — we build branded patient portals that integrate with Best Practice via supported APIs and connector layers, respecting the data residency and privacy constraints clinical software requires.
Where does patient data sit in Best Practice?
Best Practice typically runs on-premises in the practice. Custom integrations must engineer for explicit data flow controls and Australian data residency.
How does Best Practice compare to Medical Director?
Both are major Australian GP clinical software platforms. Best Practice is independently owned and Bundaberg-based; Medical Director is owned by Telstra Health. Functionality is broadly comparable for the patient-facing integration we typically build.
Related reading
Thinking we’ve published on this kind of work.
Cliniko API integrations: practitioner's guide for AU clinics
A practitioner's view of the Cliniko API surface — what it covers, where it stops, and the integration patterns Australian allied-health practices use to build the layer Cliniko doesn't ship natively.
Mindbody to Cliniko migration: technical realities for AU clinics
The technical realities of moving an Australian wellness, recovery or multi-modality clinic off Mindbody and onto Cliniko — what transfers cleanly, what doesn't, where the workarounds live, and what timeline to plan against.
simPRO API integrations: connecting AU trades to the stack
A practical view of the simPRO API surface — what it covers, where it stops, and the integration patterns Australian commercial trades operators use to build the layer simPRO doesn't ship natively.
Get started
Ready to wire up
Best Practice?
A 30-minute scoping call — no pitch deck, no hard sell. Tell us what you're trying to connect and we'll tell you straight whether it's a fit.