These release notes describe the changes made to Bp Premier since Spectra SP1 Revision 2 build 1.13.1.1080.
Release Date |
30 September 2025 |
Release version |
Bp Premier version Spectra SP1 Revision 3 1.13.1.1096. |
Notes last updated |
26 September 2025 |
Which version can I upgrade from? |
You can upgrade to version Spectra SP1 Revision 3 (1.13.1.1096) from Bp Premier version Orchid SP1 Revision 1 (1.12.1.1023) or later. To check the current program version that you have installed, select Help > About. |
Which data update do I need? |
You must install the September 2025 Data Update or later before you can upgrade to version 1.13.1.1096. However, Best Practice Software recommend making sure you have the most recent Data Update installed before you run a program upgrade. |
Which database and operating system versions are supported? |
Windows operating system Windows 10 Pro or higher is supported. Microsoft Windows Server 2016 and higher is supported. Microsoft SQL Server 2016 and higher is supported. |
When should I upgrade? |
Best Practice Software recommend running the program upgrade outside of business hours. |
How do I upgrade? |
Brief upgrade instructions are included in this document. |
Upgrade to Spectra SP1 Revision 3 1.13.1.1096
You must have the September 2025 data update or later installed before you upgrade to Spectra SP1 Revision 3 1.13.1.1096.
- Back up your Bp Premier database before running the upgrade.
- Synchronise all workstations in remote database mode with the Bp Premier server before you upgrade.
- Download and run the latest Drug Update on your Bp Premier server computer.
- Log all users out of the server and all clients before you upgrade.
- Download and run the Spectra SP1 Revision 3 1.13.1.1096 update on your server and all clients.
- Log back in to Bp Premier and resume use.
Windows 10 end of support
Windows 10 will reach its end of support on 14 October 2025. After this date, Microsoft will no longer provide software updates, security fixes or technical support. Your PC will continue to function, but will become increasingly vulnerable to viruses and malware without regular security updates.
Best Practice recommends upgrading to Windows 11 as soon as possible if your PC is eligible.
Where do I find more information?
Select from the main screen of Bp Premier or select Help > Online from Bp Premier to open the Knowledge Base from any main screen toolbar.
New Features
Allow Bulk Billing Practice Incentive Program for all Patients
From 1 November 2025, expanded eligibility for Medicare bulk billing incentives, known as the Bulk Billing Practice Incentive Program (BBPIP) will come into place. Practices participating in this optional initiative will receive an additional quarterly 12.5% incentive payment on every $1 of MBS benefit paid from eligible services, split 50/50 between the provider and the practice, if they:
- Bulk Bill all eligible services for all Medicare-eligible patients
- Advertise their participation in BBPIP
- Register to participate in MyMedicare (or already are registered with MyMedicare)
- Register to participate in the BBPIP via the Orginisation Register.
In Spectra SP1 Revision 3, for participating practices, when adding an MBS item to a direct billed invoice that has an invoice date prior to November 1 2025, existing incentive rules are used. For MBS items added to a direct billed invoice with a date on or after November 1 2025, BBPIP incentives are added for all eligible patients.
See the BBPIP Frequently Asked Questions article to learn more.
Enhancements to the Claiming Logic for Chronic Condition Management MBS Items
As part of the ongoing support for the Chronic Condition Management (CCM) changes introduced on 1 July 2025, Bp Premier has introduced new claiming logic to improve the handling of relevant MBS item numbers across the finalise visit and invoicing workflows.
MBS Items in the Finalise Visit screen
Bp Premier will now suggest appropriate CCM item numbers when a user Finalises a Visit involving the preparation or review of a GPCCMP. Bp Premier will determine the correct item based on provider type (VR or Non-VR) and visit type (face-to-face or telehealth):
Vocationally Registered (VR) GPs:
- Face-to-face: 965 (creation), 967 (review).
- Telehealth (video): 92029 (creation), 92030 (review).
Non-Vocationally Registered (Non-VR) GPs:
- Face-to-face: 392 (creation), 393 (review).
- Telehealth (video): 92060 (creation), 92061 (review).
Co-Claiming Logic
Bp Premier will now enforce co-claiming restrictions when CCM items are added during the finalise visit or invoicing workflows. These restrictions reflect current Medicare billing rules and are supported by system prompts where applicable. The following co-claiming rules are applied:
- 965 / 392 cannot be billed with any other attendance item number
- 967/393 cannot be billed within a 3-month period unless there are extenuating circumstances
- 92029/92060 (telehealth creation) cannot be billed with any other attendance item number
- 92030/92061 (telehealth review) cannot be billed within a 3-month period unless there are extenuating circumstances.
Email Correspondence In as a PDF from the patient record
Items of Correspondence can be emailed directly to patients as a PDF file attachment, secured with a PIN, from the Correspondence In screen within the Patient Record.
The document and image file formats listed below can be emailed directly from Patient Record > Correspondence In:
- Documents: PDF, RTF, DOC, DOCX, HTML and TXT
- Images: JPG , JPEG, TIF, PNG, GIF, BMP, TIFF and MTIF.
An Action will be created in Today's notes to show that the Email has been sent, and a Contact Note will be generated for all items of Correspondence sent via Email.
Improvements to Setup Third Party Integrations
All Third Party Integrations and Partners will be making changes to the way they connect to your Bp Premier database, using Halo Connect, by 31st December, 2025. These enhancements are designed to strengthen data security, improve transparency, and make it easier for your practice to control access to your data.
Standalone Integration Management Window
The Setup Third Party Integrations window has been transitioned to a standalone utility. This change allows practices to manage integrations with third-party integrations more efficiently and with greater visibility.
Introduction of Secure Pairing Codes for Bp Partners
To support secure data access, most third-party integrations will now require a Pairing Code to be enabled. When a Bp Partner requires a pairing code, a prompt will appear, allowing a secure code to be generated. Pairing codes are:
- Automatically generated in a secure format
- Unique to your practice
- Visible and manageable through the Setup Third-Party Integrations screen.
Existing integrations that do not require pairing codes will continue to function without interruption.
Improved Integration Controls
The Setup third party integrations screen now includes enhanced prompts and safeguards when enabling or disabling partners:
- Confirmation prompts are displayed before applying changes
- Disabling a partner immediately revokes access and updates system permissions
- Existing pairing codes can be manually closed or regenerated when required.
These updates provide practices with improved visibility and tighter control over third-party data access.
Other enhancements
Bp Function |
Release Notes |
Key |
---|---|---|
Billing |
As part of the ongoing support for the Chronic Condition Management (CCM) changes introduced on 1 July 2025, Bp Premier has introduced new claiming logic to improve the handling of relevant MBS item numbers across the finalise visit and invoicing workflows. MBS Items in the Finalise Visit screen Bp Premier will now suggest appropriate CCM item numbers when a user Finalises a Visit involving the preparation or review of a GPCCMP. Bp Premier will determine the correct item based on provider type (VR or Non-VR) and visit type (face-to-face or telehealth): Vocationally Registered (VR) GPs:
Non-Vocationally Registered (Non-VR) GPs:
Co-Claiming Logic Bp Premier will now enforce co-claiming restrictions when CCM items are added during the finalise visit or invoicing workflows. These restrictions reflect current Medicare billing rules and are supported by system prompts where applicable. The following co-claiming rules are applied:
|
77952 |
Billing |
From November 1 2025, as part of the new incentive program, changes will be made to bulk billed long-acting reversible contraceptive services (LARCs). These changes include:
For the loading item to be payable, the patient cannot be charged any out-of-pocket costs for any MBS items claimed in the LARC insertion or removal appointment, including any co-claimed items relating to provision of the LARC service. Best Practice has added new tables where required in the database to record loading items and their applicable percentage. Learn more about these changes from the complete article. |
80589 |
Bp Comms |
When a user selects a document from Correspondence In or Investigations and clicks the Email copy to patient button, Bp Premier now performs an automatic check against the patient’s Bp Comms Consent Settings. Users will be alerted in the following scenarios:
These consent checks occur automatically when attempting to email a document and are designed to ensure that practices are alerted to missing or incomplete consent settings before sending electronic communications. |
79661 |
Bp Email |
HTML documents can now be emailed directly from Patient Record > Investigations. |
79235 |
Bp Email |
Correspondence items can be emailed directly to patients as PDF file attachments from the Correspondence In screen in the Patient Record. The following document and image file formats may be emailed directly from Patient Record > Correspondence In:
Correspondence items will be delivered as a PDF attachment and secured with a PIN. The PIN is mandatory and cannot be removed. Only one item of Correspondence can be emailed to the patient at a time. An Action will be created in Today's notes to show that the email has been sent, and a Contact Note will be generated for all Correspondence In items sent via Email. |
79151 |
Database Integrations |
The Setup Third Party Integrations window has been transitioned to a standalone utility. The utility can be launched from the following locations:
When launching the Setup Third-Party Integration Utility from the file path, users will be prompted to enter their login details. Only users with User Permissions to access the Configuration will be able to proceed. When launching the Setup Third-Party Integration Utility from within Bp Premier, the utility will open without prompting the user to log in. |
79250 |
Bug fixes
Bp Function |
Release Notes |
Key |
---|---|---|
Bp Email |
Resolved an issue that resulted in TX Control and Document Viewer errors when sending multiple Investigation Reports to patients as a PDF file attachment in the Patient Record. Callstack Indicator:
|
80077 |
Observations |
Resolved an issue that was occurring when adding in Observations for Assessments where the Observation time would be incorrectly recorded as 0:00 am. |
80736 |
Patient Record |
Resolved an issue in the patient record where clicking Print on HTML document types in Investigation Reports, Correspondence In, or Correspondence Out would result in the HTML document not being printed. |
81023 |
Third-party integrations |
Resolved an issue in which SQL logins and application roles were not restored in BPSDrugs when restoring a backup or after running a full drug replacement. |
81046 |
Known issues
Bp Function |
Issue |
Fixed In |
Key |
---|---|---|---|
Payment Integrations |
After upgrading to Spectra SP1 Rev 3, sites using CommBank Smart Health as their payment provider may encounter a configuration error with the Bp Payments Utility. This issue may prevent invoice viewing or payment processing. Workaround: CommBank Smart Health customers will need to reconfigure the integration by entering the API key again after the upgrade. |
Not yet resolved. |
80522 |