Frequently Asked Questions

Existing Partners may continue to integrate with on-premise Bp Premier software without using Halo Connect until January 2025. Partners will be required to use Halo Connect to access new features that will be developed and released over the next 18 months. These features will be communicated to Partners via Bp Partner Network email communications. Partners may also subscribe to Halo Connect updates here

No data is stored by Halo Connect and Halo Connect does not have access to medical practice data. Data is transferred via secure methods between Medical Practices and integrators (and vice versa).

Halo Connect uses industry-leading encryption technologies to protect data during transit. Halo Connect uses access control and audit records (among other security tools) to protect data during transportation. For more information, please visit the Halo Connect Trust Centre here

Expressions of interest are welcomed by members of the Bp Partner Network. To participate in beta testing of Halo Connect APIs, please contact hello@haloconnect.io.

The Halo Connect fee structure is usage based. We will charge you a small fee per query (up to 100kb). If your query and/or result exceeds the 100kb cap, then we will charge you for every additional 100kb of data transferred to and from the clinic server. For more information including detailed Beta pricing and discounts, please contact hello@haloconnect.io.

Use of Halo Connect's API requires a separate commercial agreement and is a separate cost to the Bp Partner Network, though we don't intend for there to be a significant commercial impact for you. Currently, integrators will be incurring either direct or indirect costs (or both) associated with their integrations. This may include data transfer fees, the cost and time lag of working with Practices’ IT providers to install their connector and the cost of providing support when the connection breaks for…reasons. We believe the Halo Connect usage-based pricing model provides a competitive alternative to these costs. It also gets cheaper per query the more clinics you integrate with, so it supports scaling, and there are additional discounts available for early adopters. For larger integrators with more than 500 practices, Halo Connect will work with you and the Bp Partnerships Team to find a suitable price point for your use case and usage.

Please contact the Bp Commercial Partnerships Team via partners@bpsoftware.net or by calling 1300 40 1111 Option 4. 

Only members of the Bp Partner Network may use Halo Connect to integrate with Best Practice Software. Please see Best Practice Software Partner Network | Bp Partner Network (bpsoftware.net) for more information.

The Halo Connect API public documentation can be found here. If you have any questions, or would like to speak to the Halo Connect technical team, please contact hello@haloconnect.io.

Halo Connect and Best Practice Software are independent companies with separate ownership and investment structures. Governed by separate Boards, Halo Connect and Best Practice Software operate with separate management and staff. 

Both companies were founded by Chris Smeed, however, Halo Connect and Cubiko are independent companies with separate ownership and investment structures. Governed by separate Boards, Halo Connect and Cubiko operate with separate management and staff.

Halo Connect is built on Microsoft Azure and hosted in Australia.

Halo Connect will play a pivotal role in Best Practice Software’s roadmap for interoperability. Endpoints developed for Best Practice Software’s API will work across on-premise and cloud products. Members of the Bp Partner Network will be required to use Halo Connect to integrate with Best Practice Cloud Products and with Best Practice Premier from January 2025.

Halo Connect is now available to all Bp Partners, and Halo Link, the local database connector, was included in the July Data Update for Bp Premier.

Some integrators are in the early stages of partnership and haven’t yet written SQL queries to read/write the data they require. The good news is we’re also building API endpoints beyond the SQL Passthrough that are designed so that you never need to write your own SQL. We’ve started with Appointments and Demographics, which you can read more about here. Over the course of the next 18 months, we’ll be building these out for more and more categories, such as Billing, Documents, Messaging, Pathology, Imaging, Clinical etc. In the interim, the Passthrough is available for you to send any SQL query you write that you have database access for.