Bp Premier Spectra Release Notes

Bp Premier Spectra SP1 Release Notes

Download PDF

These release notes describe the changes made to Bp Premier since Spectra build 1.13.0.1061.

Release Date

25 March 2025

Release version

Bp Premier version Spectra SP1 1.13.1.1075.

Notes last updated

18 March 2025

Which version can I upgrade from?

You can upgrade to version Spectra SP1 (1.13.1.1075) 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 HelpAbout.

Which data update do I need?

You must install the October 2024 Data Update or later before you can upgrade to version 1.13.1.1075. 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 1.13.1.1075

You must have the October 2024 data update or later installed before you upgrade to Spectra SP1 1.13.1.1075.

  1. Back up your Bp Premier database before running the upgrade.
  2. Synchronise all workstations in remote database mode with the Bp Premier server before you upgrade.
  3. Download and run the latest Drug Update on your Bp Premier server computer.
  4. Log all users out of the server and all clients before you upgrade.
  5. Download and run the Spectra SP1 1.13.1.1075 update on your server and all clients.
  6. Log back in to Bp Premier and resume use.

Where do I find more information?

Select from the main screen of Bp Premier or select HelpOnline from Bp Premier to open the Knowledge Base from any main screen toolbar.

New Features

Enhancements to include Self-collection options for Cervical Screening

Cervical screening participants now have the choice to self-collect their own Cervical Screening Test sample. Enhancements have been implemented in Bp Premier version Spectra SP1 to accommodate the recording of results from tests where the patient themselves collected sample.

In Spectra SP1, the Cervical Screening Results screen has been enhanced to include a new check box, Self-collection, allowing clinicians to specify whether the patient has collected the sample themselves. A new option, Self-collected by patient, has been added to the Performed by field.

The recommended workflow for recording Self-collection in the Cervical Screening Results screen is as follows:

  • When the sample is Self-collected without the assistance of a Clinician, set the Performed by field to Self-collected by the patient and tick the Self-collection check box.
  • When the sample is Self-collected with the Clinician's assistance, update the value in Performed by to the Clinician and tick the Self-collection check box.

Enhancements to Database Searches for Cervical Screening

Enhancements have been implemented in the Database Search for Cervical Screening. The search criteria for Last Screening has been updated to incorporate a single drop down menu, Last Screening Test Over:, which allows searches for results from 1 year to 10 years.

The search criteria for additional parameters have been updated to the following:

  • HPV Test Only has been updated to HPV test/CST
  • When selecting HPV test/CST, the option for Cytology results will be replaced with LBC Results
  • A new search criterion, Risk Category, has been added
  • The search criteria for Performed By has been updated to include Self-collected by patient.

Email eScript tokens directly to the patient’s preferred pharmacy

Enhancements have been made to allow clinicians to send eScript tokens directly to the email address of the patient's preferred pharmacy.

If a patient consents to have their eScript token sent directly to their preferred pharmacy, the clinician can select Email (Pharmacy) from the Token menu in Current Rx. A new window, Send to Pharmacy, will appear, requiring the clinician to confirm that they have obtained consent from the patient for the eScript token to be sent to their preferred pharmacy. The clinician can manually enter the pharmacy email address or select a pharmacy contact with an email address on record.

eScript tokens sent via Email (Pharmacy) will include the patient's consent as an Action in Today's Notes. The action will detail the eScript delivery address (email address) and the corresponding drug and dosage information.

A contact note will be recorded for each eScript sent via SMS (default), SMS (Other), App, Email (default), Email (other), or Email (Pharmacy).

Email Investigation Reports as PDF from the Patient Record

Investigation Reports can be emailed directly to patients as a PDF file attachment, secured with a PIN, from the Investigation Reports screen within the Patient Record.

The document and image file formats listed below can be emailed directly from Patient Record > Investigation Reports:

  • Documents: PDF, RTF, DOC, DOCX 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 Investigation Reports sent via Email.

AIR Vaccination Encounter Reporting Changes

Reporting accurate vaccination information to the Australian Immunisation Register (AIR) allows the register to contain a complete and reliable dataset for monitoring immunisation coverage and administration. The Australian Immunisation Register (AIR) will establish new reporting requirements on 24 October 2025 to improve the data currently held.

Updates to Vaccine Type Reporting effective from 24 October 2025

The Australian Immunisation Register (AIR) is introducing changes to simplify the Vaccine Type field. In Spectra SP1, the following options will be available:

  • NIP/Commonwealth
  • Antenatal
  • Other

The options for Private and State Program have both been replaced by the new option 'Other'. Where you previously would have selected the Private or State Program option, you will now select 'Other'.

Other enhancements

Bp Function

Release Notes

Key

Australian Immunisation Register

The Add/Edit Immunisation screen has been updated to include the Vaccine Type changes mandated by the Australian Immunisation Register (AIR) that will take effect on 01 March 2025:

  • State Program and Private has been removed.
  • Other has been introduced and is to be used instead of State Program and Private.

78733

Australian Immunisation Register

The Australian Immunisation Register (AIR) has removed the requirement to specify the Serial Number when recording COVID-19 vaccination encounters. The Serial No: field has been removed from the Add/Edit Immunisation screen.

78735

Patient Record

The label for BSL (Blood sugar level) in the following screens has been updated to BGL (Blood glucose level).

  • Patient record > Clinical > Observations.
  • Patient record > Today's notes > General.
  • Patient record > Observations > Graph.
  • Patient record > Enhanced Primary Care > Diabetes cycle of care.

77870

Patient Demographics

English will now be positioned at the top of the Preferred Language list, followed by the top ten languages recorded by the Australian Bureau of Statistics, and then an alphabetical listing of all other languages.

77991

ePrescribing

A new option for eScript tokens, Email (Pharmacy), has been added to the Patient Demographics screen, allowing you to set the patient's preferred method for receiving their eScript Tokens.

77916

ePrescribing

A new option for eScript tokens, Email (Pharmacy), has been added to Current Rx to allow for the direct sending of eScript tokens to the patient's preferred pharmacy.

77917

ePrescribing

A new option for eScript tokens, Email (Pharmacy), has been added to the Resend or Reprint Token screen, allowing eScript tokens to be resent to the patient's preferred pharmacy.

77918

ePrescribing

eScript tokens sent via Email (Pharmacy) will include the patient's consent as an Action in Today's Notes. The action will detail the eScript delivery address (email address) and the corresponding drug and dosage information.

A contact note will be recorded for each eScript sent via Email (default), Email (other), or Email (Pharmacy).

75324

ePrescribing

Enhancements have been implemented on the Past Prescriptions screen to improve visibility on the method used for sending eScript tokens.

The eScript column in Past Prescriptions has been updated; Existing and historical prescriptions sent via eScript will now display the eScript token method used: SMS, SMS (Other), Paper, Email, Email (Other), MySL, or App, instead of the previous Yes/No format.

The eScript column in Past Prescriptions has been updated to display the eScript token method used for new or represcribed prescriptions sent via eScript: SMS, SMS (Other), Paper, Email, Email (Other), Email (Pharmacy), MySL, or App.

77920

ePrescribing

A new column, eScript address, has been added to the Past Prescriptions screen in the patient record to display the email address or mobile number to which new or represcribed eScript tokens were sent.

The eScript Address column will display the following:

  • The mobile phone number for eScript tokens sent via SMS and SMS (Other).
  • The email address for eScript tokens sent via Email, Email (Other), and Email (Pharmacy).

77921

Bp Email

Investigation Reports can now be emailed directly to patients as PDF file attachments from the Investigation Report screen in the Patient Record.

The following document and image file formats may be emailed directly from Patient Record > Investigation Reports:

  • Documents: PDF, RTF, DOC, DOCX and TXT.
  • Images: JPG, JPEG, TIF, PNG, GIF, BMP, TIFF and MTIF.

Investigation Reports will be delivered as a PDF attachment and secured with a PIN. The PIN is mandatory and cannot be removed.

Only one investigation report 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 Investigation Reports sent via Email.

78015

Cervical Screening

Enhancements have been introduced to the Cervical Screening Result screen in the patient record to accommodate the recording of results from Cervical Screening tests that were Self-collected by participants.

When adding a Cervical Screening result to the patient record by selecting Cervical Screening > Add, a new Self collection tick box will be available in the Cervical Screening Results window.

A new option, Self-collected by patient, has been added to the Performed by: drop down list.

77875

Cervical Screening

The Cervical Screening window in the patient record has been enhanced to include an additional column, Self-collection, that displays whether a cervical screening participant opted to collect their own Cervical Screening Test sample.

77876

Database Search

The Database Search for Cervical Screening has been updated to include the latest updates from the National Cervical Screening Program and the new enhancements for recording Self-collection in the Cervical Screening Results screen in Spectra SP1.

The search criteria for Last Screening has been updated to incorporate a single drop down menu, Last Screening Test Over:, which allows searches for results from 1 year to 10 years.

The search criteria for additional parameters have been updated to the following:

  • HPV Test Only has been updated to HPV test/CST
  • When selecting HPV test/CST, the option for Cytology results will be replaced with LBC Results
  • A new search criterion, Risk Category, has been added
  • The search criteria for Performed By has been updated to include Self-collected by patient.

77877

Bp Browser

Enhancements have been made in the Bp Browser to improve performance when opening and closing Bp Browser windows; memory is now deallocated more efficiently.

78201

Bug fixes

Bp Function

Release Notes

Key

Database Connections

A resolution has been implemented to improve the handling of errors that occur due to Network connectivity issues between a workstation and the Bp Premier database server.

Users will now be alerted when the following occurs:

  • 'The connection to the server has been lost! Check that the server is running and that your network connection is okay. Then press ‘Retry’ to attempt to re-establish the connection'. Users can press Retry to try to re-establish the connection to the Bp Premier database, or they can opt to Close Bp Premier.
  • 'A potential connection issue was detected, and some of your recent changes may not have been saved. If you close the application now, any unsaved data may be lost. Do you want to proceed?'. Users have the option to select No, go back & Retry to try to re-establish the connection to the Bp Premier database, or they can opt for Yes, Close Bp Premier.

79408

Database Connections

To further support the management of errors that arise from Network connectivity issues between a workstation and the Bp Premier database server, additional logging will be implemented for Auditing purposes.

  • When the client machine loses connection to the database server, the Error Handler window will display, and an entry will be logged in the database for auditing purposes.
  • When the client machine loses connection to the database on the server, the Error Handler window appears. Clicking the Retry, Cancel, or Close button in the Error Handler window results in an entry being recorded in the database.
  • When the client machine loses connection to the database server and the Retry button is clicked upon successful reconnection, an entry is logged in the database for auditing purposes.

79352

Patient Education Material

Resolved an issue where searching for leaflets in Patient Education Material would result in a fatal call stack error.

Callstack Indicator:

  • CTREEVIEW:EXPAND Line: 27
  • PATIENTEDUCATIONWINDOW:SEARCH Line: 47
  • PATIENTEDUCATIONWINDOW:FILE_SEARCH Line: 9

78720

Waiting Room

Resolved an issue where updating an Appointment status via the Legend in the Waiting Room resulted in the appointment being incorrectly moved and assigned to the wrong user.

78727

Known issues

Bp Function

Issue

Fixed In

Key

Suspect Databases

When a Suspect Database error occurs, and the Repair option is selected, a connection to the server error notification is displayed, and the Repair cannot be completed.

Workaround:

Contact Bp Premier Support at 1300 40 1111, options 1, 1, 5 if any errors occur.

Spectra SP1 Revision 1

79665

Remote Database

When selecting Clinical > Unchecked reports in the patient record from a Remote Database workstation, a non-fatal callstack error will occur.

Callstack Identifier:

  • CLEANUPORPHANEDINBOXRECORDS Line: 30
  • INBOXWINDOW:CLEANUP Line: 44
  • PATIENTINBOXWINDOW:LOADDATA Line: 7

Workaround:

Unchecked reports are not available in a remote database and should not be selected.

Not yet resolved.

79683

Remote Database

When a Remote Database workstation reconnects to the Bp Premier (BpInstance) database server instead of connecting to the BPSClient remote database, any patient information entered will not be saved.

Workaround:

Users must ensure their remote database workstation (BPSClient) has been disconnected from the Bp Premier server (BpInstance) network before entering patient information.

Not yet resolved.

79681

Bp Premier Spectra SP1 Revision 1 Release Notes

Download PDF

These release notes describe the changes made to Bp Premier since Spectra SP1 build 1.13.1.1075.

Release Date

28 May 2025

Release version

Bp Premier version Spectra SP1 Revision 1 1.13.1.1078.

Notes last updated

27 May 2025

Which version can I upgrade from?

You can upgrade to version Spectra SP1 Revision 1 (1.13.1.1078) 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 HelpAbout.

Which data update do I need?

You must install the April 2025 Data Update or later before you can upgrade to version 1.13.1.1078. 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 1 1.13.1.1078

You must have the April 2025 data update or later installed before you upgrade to Spectra SP1 Revision 1 1.13.1.1078.

  1. Back up your Bp Premier database before running the upgrade.
  2. Synchronise all workstations in remote database mode with the Bp Premier server before you upgrade.
  3. Download and run the latest Drug Update on your Bp Premier server computer.
  4. Log all users out of the server and all clients before you upgrade.
  5. Download and run the Spectra SP1 Revision 1 1.13.1.1078 update on your server and all clients.
  6. Log back in to Bp Premier and resume use.

Where do I find more information?

Select from the main screen of Bp Premier or select HelpOnline from Bp Premier to open the Knowledge Base from any main screen toolbar.

New Features

Date of Birth requirements on all Prescriptions in the ACT

The Australian Capital Territory (ACT) has amended the Medicines, Poisons, and Therapeutic Goods Act 2008 to mandate that the patient's Date of Birth appear on all Prescriptions issued, dispensed or administered in ACT from 13 June 2025.

In Spectra SP1 Revision 1, when a prescriber logs into a Location with a Postcode in the Australian Capital Territory (ACT), the patient's Date of Birth will be displayed on all Prescriptions, including those that are printed.

Other enhancements

Bp Function

Release Notes

Key

Current Rx

The Australian Capital Territory (ACT) has amended the Medicines, Poisons, and Therapeutic Goods Act 2008 to mandate that the patient's Date of Birth appear on all Prescriptions issued, dispensed or administered in ACT from 13 June 2025.

When a prescriber logs into a Location with a Postcode in the Australian Capital Territory (ACT), the patient's Date of Birth will be displayed on all Prescriptions, including those that are printed.

79864

Bp Comms

The ReceiptID value for Bp Comms SMS delivery reports and replies has been increased.

79869

Bug fixes

Bp Function

Release Notes

Key

Suspect Databases

Resolved an issue where if a Suspect Database error occurred, and the Repair option was selected, a connection to the server error notification was displayed, and the Repair could not be completed.

79665

Bank Accounts

Resolved an issue that prevented duplicate Provider/Practice Bank Accounts from appearing in the Setup > Configuration > Bank Accounts window when they had the same Account Number.

79994

Database Connections

Resolved an issue where if a call stack error occurs and is not closed, and a network connectivity error occurs, the application will not regain full connectivity with the server.

80075

Database Connections

Resolved an issue in which users were not warned when a network connectivity error occurred while accessing or using the Bp Premier Utilities.

80078

Known issues

Bp Function

Issue

Fixed In

Key

Database Connections

When a connection issue occurs, the Retry prompt appears prominently in front of the active window, preventing users from switching to other windows or using Bp Premier in the background. However, if the user opts to navigate to other windows using Shortcut keys, there is a risk of data loss.

Workaround:

To minimise the risk of data loss, users should avoid using Shortcut keys while Bp Premier is attempting to reconnect to the Bp Premier database server.

Not yet resolved.

80048

Bp Premier Spectra SP1 Revision 2 Release Notes

Download PDF

These release notes describe the changes made to Bp Premier since Spectra SP1 Revision 1 build 1.13.1.1078.

Release Date

14 August 2025

Release version

Bp Premier version Spectra SP1 Revision 2 1.13.1.1080.

Notes last updated

14 August 2025

Which version can I upgrade from?

You can upgrade to version Spectra SP1 Revision 2 (1.13.1.1080) from Bp Premier version Orchid 1.12.1.1023 or later. To check the current program version that you have installed, select HelpAbout.

Which data update do I need?

You must install the July 2025 Data Update or later before you can upgrade to version 1.13.1.1080. 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 2 1.13.1.1080

This release reflects our ongoing commitment to enhancing stability, resilience, and optimisation across Bp Premier, with particular attention to supporting the increasingly complex on-premise operating environments used by our customers.

Refer to the Technical Bulletin for more information on network disconnections.

You must have the July 2025 data update or later installed before you upgrade to Spectra SP1 Revision 2 1.13.1.1080.

  1. Back up your Bp Premier database before running the upgrade.
  2. Synchronise all workstations in remote database mode with the Bp Premier server before you upgrade.
  3. Download and run the latest Drug Update on your Bp Premier server computer.
  4. Log all users out of the server and all clients before you upgrade.
  5. Download and run the Spectra SP1 Revision 2 1.13.1.1080 update on your server and all client workstations and devices used in and out of the clinic.
  6. Log back in to Bp Premier and resume use.

Where do I find more information?

Select from the main screen of Bp Premier or select HelpOnline from Bp Premier to open the Knowledge Base from any main screen toolbar.

New Features

Antenatal Indicator added to the Add/Edit Immunisation screen

From 24 October 2025, new rules for the Australian Immunisation Register (AIR) will apply. The Department of Health, Disability and Ageing is introducing an Antenatal field to:

  • Report more easily and accurately if a patient is pregnant at the time a vaccine is administered
  • Improve the collection of antenatal data
  • Support monitoring of immunisation coverage.

Bp Premier version Spectra SP1 Revision 2 includes programmatic changes to comply with the new Antenatal reporting requirements for AIR vaccination encounters. An Antenatal check box has been added to the Add/Edit Immunisation screen with the following logic:

  • Automatically selected if the patient is recorded as pregnant and aged 10 to 65
  • A warning will display if selected manually outside of this age range.

To continue interacting with the AIR from within Bp Premier, and ensure compliance with the new mandatory reporting requirements, practices must update to Spectra SP1 Revision 2 before 24 October 2025. After this date, practices that have not upgraded will receive an error when uploading to or viewing the AIR.

Changing and correcting Vaccine Codes in an Updated Encounter Request

Services Australia has required Best Practice Software to add functionality which allows the changing and correcting of Vaccine Codes in an Updated Encounter Request.

When editing a vaccination encounter and selecting a new vaccine, if you have ticked Update and send to AIR, clicking Save will record the change in the Bp Premier data, an Action will be recorded in Today's notes showing the vaccine name change, and an updated encounter request will be sent to AIR with the revised details.

Other enhancements

Bp Function

Release Notes

Key

Database Connections

Enhancement to improve the handling of errors that occur due to network connectivity issues between a workstation and the Bp Premier database server.

If your practice IT infrastructure experiences network errors, the updated error management handling may result in additional callstack errors, to inform a user when a network connectivity error has occurred and:

  • The Retry option is not selected
  • A callstack error existed when a connectivity error occurred.

Independent investigation is advised to resolve any underlying cause of network connectivity errors.

80619

Australian Immunisation Register

The options for Route of Administration in the Add/Edit Immunisation screen have been updated to display the full text rather than the abbreviations.

Available options for Route of Administration:

  • Intramuscular
  • Subcutaneous
  • Oral
  • Intradermal.

79168

Australian Immunisation Register

Immunisations with a Vaccine Type of Antenatal that were recorded before installing Spectra SP1 Revision 2 will now display in the form of a check box labelled 'Antenatal' when being edited.

80599

Australian Immunisation Register

When adding or editing an Immunisation encounter for a patient outside the age range of 10 to 65 years and ticking the Antenatal check box, an error message will be displayed when clicking Save, informing the user that ‘antenatal value may not be valid for this individual’.

79087

Bug fixes

Bp Function

Release Notes

Key

Australian Immunisation Register

Resolved a callstack error that occurred when viewing Sent Vaccinations from the main screen of Bp Premier > Utilities > Australian Immunisation Register > View > Sent Vaccinations.

Callstack Indicator:

  • GETSENTIMMUNISATIONLOCATIONLISTBYDISEASE Line: 52
  • ACIRSENTWINDOW:GETDISPLAYDATA Line: 31

69289

Australian Immunisation Register

Resolved an issue that was occurring after editing and sending a previously sent immunisation record to the Australian Immunisation Register. The previously sent and newly edited immunisation record was not including the Antenatal indicator in the payload of the Update Encounter when being sent again.

If a user edits an immunisation and unchecks/checks the Antenatal checkbox, the Antenatal field in the payload is correctly set when sending an Update Encounter request to the Australian Immunisation Register.

79023

Executable Utilities

Resolved an issue that was preventing proper error handling when using some utilities such as the Bulk document importer, Billing Utility, eRx setup when a connection to the server is lost. The error handling will now follow protocol, ensuring that even in a disconnected state, the user can attempt to Retry the action instead of being prevented with the call stack only.

80078

Known issues

Bp Function

Issue

Fixed In

Key

Document Viewer

After emailing multiple investigation results via either Add Investigation or Results import and reopening a patient record, the Word Processor documents fail to render content.

The document viewer will either display a blank screen or trigger a TX Text Control error.

Workaround:

Closing and reopening Bp Premier will resolve the error.

Not yet resolved.

80077

Database Connections

If a network connectivity error occurs, i.e. a disruption between the client workstation and server, at the same time a patient record is being reopened and the "Do you want to continue adding to those notes" prompt is displayed, clicking yes can result in a visit being incorrectly linked to a Visit ID of 0, causing notes not to be saved or recoverable.

Workaround:

If a network connectivity error occurs when a patient record is being reopened and a Retry prompt is displayed, the patient record should be closed and reopened.

Not yet resolved.

80913

Bp Premier Spectra SP1 Revision 3 Release Notes

Download PDF

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

10 October 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 HelpAbout.

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.

  1. Back up your Bp Premier database before running the upgrade.
  2. Synchronise all workstations in remote database mode with the Bp Premier server before you upgrade.
  3. Download and run the latest Drug Update on your Bp Premier server computer.
  4. Log all users out of the server and all clients before you upgrade.
  5. Download and run the Spectra SP1 Revision 3 1.13.1.1096 update on your server and all clients.
  6. 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 HelpOnline 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, 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:

The BBPIP payments will be split 50/50 between the practice and the provider and paid by the government into the bank accounts recorded in HPOS. Existing Bulk Billing incentive benefits will remain as a direct payment to the GP.

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:

  • 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.

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:

  • Increasing fees for the existing LARC insertion and removal items (35503, 35506, 14206, 30062)
  • Introduction of new items for Nurse Practitioners for insertion and removal (82201, 82202, 82203)
  • Introduction of new loading items that will provide 40% of the fee of the relevant LARC administration item when bulk billed:
    1. 35501 for GPs and Specialists
    2. 82204 for Nurse Practitioners.

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:

  • If the patient has opted out of receiving electronic messages, Bp Premier will display a message advising: The patient has chosen to opt out of receiving any electronic messages.
  • If the patient has not opted out but has no consent options selected under Clinical Communication (e.g. Results, Clinical Messages), Bp Premier will display the following message: The ability to Send Clinical Communication messages must be enabled to perform this action.

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:

  • Documents: PDF, RTF, DOC, DOCX, HTML and TXT.
  • Images: JPG, JPEG, TIF, PNG, GIF, BMP, TIFF and MTIF.

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:

  • File Path: C:\Program Files\Best Practice Software\BPS\BPSupport\BP.ThirdPartyIntegrations.exe
  • Within Bp Premier: Select Setup > Configuration > Database > Setup Third Party Integrations.

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:

  • BPDOCUMENTVIEWER:TEXTCONTROLPAGEWIDTH:ASSIGN Line: 3
  • DOCUMENTVIEWER:SETPAGESIZE Line: 74

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