Oct 5, 2025
6
min read
Medically Reviewed
Share
The Fragmentation Problem in Australian Healthcare
The Australian healthcare technology market has evolved organically over decades, with different vendors building products for different segments of the market using different technology stacks, different data models and different approaches to interoperability. Best Practice, MedicalDirector, Halaxy, Cliniko and Nookal are the most widely used practice management systems in Australian primary care, and each was built independently with its own database schema, its own API architecture and its own approach to data exchange. A practice that uses one of these systems has access to a well-supported PMS platform, but the data in that system is largely inaccessible to other systems the practice might want to use for AI scribing, billing optimisation or practice analytics unless those systems have been specifically integrated with the practice’s particular PMS platform at a level of depth that supports real-time bidirectional data exchange.
The fragmentation extends beyond PMS platforms to the government systems that practices must interact with. Medicare claiming requires PRODA authentication and MBSonline submission. My Health Record integration requires conformity with the Australian Digital Health Agency’s interoperability specifications. Prescribing, immunisation recording and electronic referrals each have their own technical requirements and standards. A platform that cannot connect with these government systems forces the practice to manage them as separate workflows, logging into different portals and manually transferring data between the practice’s clinical systems and the government’s digital services.
The cost of this fragmentation is borne by practices in the form of staff time spent on manual data entry, errors introduced during data transfer between systems, and the opportunity cost of not having the integrated analytics and workflow automation that a connected platform can deliver. For the healthcare system as a whole, fragmentation means that the patient data that could drive population health insights, quality improvement and care coordination is locked in separate silos that cannot be combined to create the comprehensive picture of patient health that clinicians and policymakers need to make informed decisions about both individual care and system-level planning.
Interoperability as a Design Principle, Not an Afterthought
Most healthcare software platforms treat interoperability as a feature to be added after the core product is complete, usually in response to customer demand for integration with a specific PMS platform or government system. The platform is built around its own internal data model, and integration with external systems is handled through custom adapters that map the platform’s data structures to the external system’s API. This approach works for the initial integration but becomes increasingly difficult to maintain as the platform evolves, as the external systems update their APIs, and as the number of integrations grows. Each new integration requires a new custom adapter, each adapter must be maintained separately as both the platform and the external system change, and the quality of the integration depends on the depth of the vendor’s understanding of each external system’s data model and workflow patterns.
MediQo takes the opposite approach. Interoperability is a design principle that shapes every architectural decision, from the choice of FHIR and HL7 as the platform’s data model to the design of the API layer that exposes platform data to external systems. The platform does not have an internal data model that must be mapped to external standards through custom adapters; it uses FHIR as its native data model, so data that enters the platform is already structured in the standardised format that healthcare interoperability frameworks expect. When the platform connects with a PMS, a government system or a future digital health service, the data exchange is based on shared standards rather than custom mappings, reducing the complexity, maintenance burden and risk of data loss or misinterpretation at the integration boundary between the two systems.
The practical consequence of this approach is that MediQo’s integrations are deeper, more reliable and less expensive to maintain than integrations built on custom adapters. When a PMS platform updates its API or the Australian Digital Health Agency releases a new version of its interoperability specifications, MediQo’s compliance with the underlying standards means that the impact is usually limited to updating the standard implementation rather than redesigning a custom integration that was built around a specific version of a specific system’s proprietary data format that may have changed substantially between releases.
Expert Tips
"The vision for MediQo has always been bigger than any single module. We are building the infrastructure for a connected Australian healthcare system where data flows freely between practices, between the practice and the government, and between the practice and every other part of the patient's healthcare journey. That vision requires interoperability to be in the platform's DNA, not bolted on as an afterthought. Every integration we build makes the next one easier, and every practice that joins the platform strengthens the network for everyone else." — Arash Zohuri, CEO, MediQo
Deep Integration With Australian PMS Platforms
MediQo’s integration with Australian practice management systems is a direct expression of the interoperability-first philosophy. The platform connects with Best Practice, MedicalDirector, Halaxy, Cliniko and Nookal at a depth that goes beyond simple data exchange. Patient demographics, appointment details, clinical notes, billing information and recall data flow bidirectionally between MediQo and the practice’s PMS in real time, ensuring that both systems are always synchronised and that the practice staff always have access to the most current information regardless of which system they are working in at any given moment of the patient journey.
The integration depth is visible in the way data is handled. When CALLA books an appointment, the booking is written directly into the PMS schedule, not into a separate MediQo diary that a staff member must manually transfer. When the Clinical Assistant generates a consultation note, the note is written back to the PMS clinical record, not stored only in MediQo. When Smart MBS Billing submits a claim, the claim status is reflected in both MediQo and the PMS. The practice staff do not need to maintain two sets of records, check two systems for the same information, or reconcile data between MediQo and the PMS at the end of each day. The integration is invisible, automatic and comprehensive, and the practice experiences MediQo as an extension of its existing PMS rather than as a separate system that adds to the complexity of managing multiple tools across the full workflow.
The deep integration also means that practices can adopt MediQo without disrupting their existing PMS. Practice staff continue to use their familiar PMS for the functions it handles well, while MediQo adds AI capabilities that extend the PMS’s functionality without requiring a migration, data conversion or change to established workflows. This approach respects the investment practices have made in their existing systems and the institutional knowledge their staff have built around them, while still delivering the AI-powered automation, documentation and analytics that a modern practice needs to create capacity and improve its performance across every dimension of its operations.
Key Takeaways
A connected healthcare platform eliminates the data silos that fragment patient records across separate systems and vendors.
Deep integration with Australian PMS platforms ensures data flows in both directions in real time, not through scheduled synchronisation.
FHIR and HL7 provide the interoperability foundation that allows the platform to connect with the broader healthcare ecosystem.
Interoperability-first design ensures that MediQo can evolve as new PMS platforms and government digital health initiatives emerge.
Australian healthcare operates on a foundation of remarkable diversity in its technology landscape. General practices, specialist clinics, allied health providers, aged care facilities and hospitals each use different practice management systems, clinical software and administrative tools, many of which were designed to operate as standalone systems that were never intended to share data with each other. The result is a healthcare ecosystem that is rich in capability at the individual practice level but fragmented at the system level. Patient information that should flow seamlessly between a general practice and a specialist, between a practice and a hospital, or between a practice and the national My Health Record system instead moves through fax machines, secure messaging services that operate on incompatible standards, paper printouts sent by mail, and manual data entry that introduces errors, delays and gaps in the clinical record that can affect patient safety and the quality of care across transitions between different care settings and different providers.
An interoperability-first approach to platform design addresses this fragmentation by building connectivity into the platform's fundamental architecture rather than treating it as an integration project to be undertaken after the core product is complete. MediQo was designed from the outset as a connected platform that would exchange data bidirectionally with the practice management systems that Australian practices actually use, with the government systems that underpin Australian healthcare funding and regulation, and with the broader digital health ecosystem including My Health Record, secure messaging and emerging national infrastructure. The platform is built on FHIR and HL7, the interoperability frameworks that the Australian Digital Health Agency and the international healthcare standards community have adopted as the foundation for healthcare data exchange. Every integration, every data flow and every module is designed to be interoperable by default rather than requiring custom adaptation each time the platform needs to exchange data with a new external system or a new version of an existing system.
This article explains the vision behind MediQo's connected platform approach, the technical and strategic decisions that make it possible, and what this approach means for Australian practices that want to be part of a genuinely connected healthcare ecosystem rather than operating as an island of digital capability that cannot communicate effectively with the rest of the patient's care network.
Share