Bp Premier Orchid SP1 Revision 1 Release Notes

These release notes describe the changes made to Bp Premier since Orchid SP1 build 1.12.1.1018.

Release Date	08 January 2024
Release version	Bp Premier version Orchid SP1 Revision 1 1.12.1.1023
Notes last updated	04 January 2024
What is in this release?	This release includes clinical enhancements described in Bp Premier Orchid SP1 Revision 1 Release Notes.
Which version can I upgrade from?	You can upgrade to version Orchid SP1 Revision 1 from Bp Premier version Saffron SP3 (1.11.3.968/1.11.3.974) 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 December 2023 Data Update or later before you can upgrade to version 1.12.1.1023. 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 or higher is supported. Microsoft Windows Server 2012 and higher is supported. Microsoft SQL Server 2014 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 Orchid SP1 Revision 1 1.12.1.1023

You must have the December 2023 data update or later installed before you upgrade to 1.12.1.1023.

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 1.12.1.1023 update on your server and all clients.
Log back in to Bp Premier and resume use.

Upgrade notes

Security Enhancements to BP Browser SQL Logins

Orchid Service Pack 1 Revision 1 includes security enhancements to mitigate the risk of unauthorised access to the Bp Premier database without limiting functionality for your practice to access your own data.

These enhancements are:

The 'BP Browser' SQL Logins, BPSRawData and BPSViewer will be removed.
The method that the Bp Premier application uses to connect to the Bp Premier Database has been altered to improve security.

These changes will impact your practice if you currently connect any third-party applications to the Bp Premier database using either the BPSRawData, or BPSViewer SQL Logins. A common use-case for these accounts is to use tools such as Microsoft SQL Management Studio or Microsoft Power BI to generate reports or query your practice's data.

See Use the BP Browser utility to browse the database for more information.

New send to AIR immunisation error codes

By reporting precise vaccination data to AIR, the register can contain a complete and reliable dataset for monitoring immunisation coverage and administration. AIR will implement additional mandatory reporting requirements from 1st March 2024, to improve the data already held.

Vaccination providers may encounter the following error codes when sending vaccination encounters to AIR from March 1, 2024; they should be aware of what the error codes are and why they occur.

Alert	Description
AIR-E-1084	Invalid code for Vaccine funding type.
AIR-E-1085	Invalid code for Route of administration.
AIR-E-1086	The values supplied for Vaccine funding type and Vaccine code are not compatible.
AIR-E-1087	The values supplied for Route of administration and Vaccine code are not compatible.
AIR-E-1088	[0] is required for {1} vaccines: [0] = field name [1] = supplied vaccine code

Where do I find more information?

Selectfrom 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

Mandatory AIR Vaccination Encounter Reporting Changes from 1 March 2024

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 mandatory reporting requirements on 1 March 2024 to improve the data currently held.

Where a vaccination provider is both the immunisation and information provider and the vaccine was administered on or after 1 March 2024, the following information will be required to upload an encounter to AIR from 1 March 2024:

Route of Administration will be mandatory for selected vaccines.
Selecting the Vaccine Type will be mandatory for selected vaccines.
Recording Batch Numbers will be mandatory for selected vaccines.

Document the patient's MyMedicare registration status

To assist in capturing patients who have registered with the practice for MyMedicare, the patient demographic window has been updated to include the following new fields:

Registered for MyMedicare allows you to mark that a patient has registered for MyMedicare with your practice.
MyMedicare Registration Date allows you to set a date from which the MyMedicare registration is effective.
Registered Location allows you to record the patient's preferred MyMedicare practice location.

Once the patient's MyMedicare registration has been recorded in Bp Premier, their MyMedicare status will be displayed in the appointment book workflow, when creating an invoice and in the patient demographic area of the clinical record.

Record the MyMedicare Site ID for each Practice Location

A new field, MyMedicare Site ID, has been added to the Location Details window in Setup > Practice Details > Add/Edit.

The Organisation Site ID should be entered into the MyMedicare Site ID field for single and multi-location practices, ensuring that the Organisation Site ID matches the correct practice location in Bp Premier. To obtain the Organisation Site ID for your practice location, log on to PRODA > HPOS > Organisation Register.

In Orchid SP1 Revision 1, the MyMedicare Site ID will be used in conjunction with the patient's Registered Location to ensure that the correct MyMedicare incentive is applied for the invoicing location.

Improvements to support Level E Consultation Item Numbers

Bp Premier will estimate the MBS item number required for a consult based on the visit length for providers with the billing preference Calculate the MBS item in the Finalise window selected in Setup > Preferences.

The previous billing logic would always estimate a Level D consultation item number where the visit length was 40 minutes or longer. Improvements have been made to correctly estimate Level E consultation item numbers where the visit length is 60 minutes or longer.

Updates to BP Browser Access and Third-party backups

In Setup > Configuration > Database, the Third-party backup button replaces the database browser button, and this is where you will configure the password for third-party database backups. By assigning a password to this account, database backups can be conducted with the BPSBackup login.

Access to the BP Browser has been updated, and you can now log in using your Bp Premier user name and password. To provide more control over who can access the BP Browser, we've added a new permission type called BP Browser Access; by default, this permission will be set to No Access.

Other enhancements

Bp Function	Release Notes	Key
Australian Immunisation Register	To support the mandatory AIR 1st March 2024 changes, a new drop down labelled 'Vaccine Type' has been added to the Add/Edit Immunisation window, where the provider must specify the funding type of a vaccine depending on the patient's eligibility in the NIP. The following funding options will be available for selection: Antenatal NIP/Commonwealth Private State Program	73998
Australian Immunisation Register	To accommodate the mandatory AIR Vaccination Encounter reporting changes that take effect on 1 March 2024, the View AIR > History tab has been updated to include the Route of Administration and the Vaccine Type.	73378
Australian Immunisation Register	The View AIR > History tab has been updated to correctly map the return codes to descriptions for Individual Immunisation History Details. The 'Route' column will display the full text for the Route of Administration. The 'Vaccine Type' column displays the full text for the Vaccine Funding Type.	74185
Billing	Bp Premier will estimate the MBS item number required for a consult based on the visit length for providers with the billing preference Calculate the MBS item in the Finalise window selected in Setup > Preferences. The logic in Bp Premier has been updated to correctly estimate the new Level E consultation item numbers where the visit length is 60 minutes or longer.	73977 / 74071
MyMedicare	To capture patients who have registered with the Practice for MyMedicare, a new check box Registered for MyMedicare has been added to the patient demographics window along with the ability to set a date from which the registration is effective.	74020
MyMedicare	After a patient is marked as Registered for MyMedicare, their MyMedicare status will be shown when creating an invoice and in the patient demographic area of the clinical record.	74022
MyMedicare	After a patient is marked as Registered for MyMedicare, their MyMedicare status will be displayed throughout the appointment book workflow.	74021
MyMedicare	The Registered Location for MyMedicare can be recorded in the patient demographic details. The Organisation Site ID can be recorded in the MyMedicare Site ID field in the Location Details window in Setup > Practice Details > Add/Edit for each practice location.	74045
MyMedicare	The billing logic in Bp Premier has been updated to accommodate MyMedicare MBS item numbers and to automatically apply bulk billing incentives item numbers. When billing MyMedicare specific telehealth video MBS item numbers (91801, 91802, 91920, 91804, 91805, 91923, 91807, 91808, 91926), the correct incentive is automatically added to the invoice. When adding the MyMedicare specific telehealth phone MBS item numbers (91900, 91910, 91903, 91913, 91906, 91916), the correct MyMedicare incentive is automatically added to the invoice. Based on the item billed and whether the Location's MyMedicare Site ID matches the MyMedicare Registered Location in the patient demographics, Bp Premier will apply the most appropriate incentive item numbers to the invoice.	74056
MyMedicare	MyMedicare incentives will be prevented from being manually added to invoices in Bp Premier versions Orchid SP1 Revision and later.	74338
Finalise Visit	Bp Premier will estimate the MBS item number required for a consult based on the visit length for providers with the billing preference 'Calculate the MBS item in the Finalise' window selected in Setup > Preferences. The billing logic has been updated to correctly estimate a Level E consultation item number where the visit length is 60 minutes or longer.	73977 / 74071
Configuration	The database browser password and button have been deprecated and replaced by Third-Party Backups. Setting a database backup password allows database backups to be performed using the BPSBackup login.	74053
Configuration	Access to the BP Browser has been updated, and you can now log in using your Bp Premier user name and password. To control who can access the BP Browser, a new permission type, BP Browser Access; by default, this permission will be set to No Access.	74052
Active Script List	Prescriptions created prior to upgrading to Saffron will not have any Consent to upload to ASL options recorded and will not be visible in MySL when represcribed. In Orchid SP1 Revision 1, providers will be offered the opportunity to provide Consent to Upload to ASL when represcribing prescriptions created prior to upgrading to Saffron.	73992
Third Party	When installing the Orchid SP1 revision program update or the full ISO installer, Halo Link will not be installed if the InstallHalo registry value is 0. If the InstallHalo flag does not exist or is not equal to 0, Halo Link will be installed silently.	73092

Bug fixes

Bp Function	Release Notes	Key
Active Script List	Resolved an issue where, when selecting the View MySL button, the eScript token drop down supplied the user contact details instead of the patient's details.	74024
ePrescribing	Resolved an issue where practices that have upgraded to Orchid SP1 and completed eRx registration and configuration experienced the following issues when sending SMS eScript tokens: SMS is not displayed as a delivery method for eScript Tokens if Bp Comms is not enabled for the practice. If Bp Comms is configured or was previously configured for your practice, but no Bp Comms credits remain, a Bp Comms credit error message is displayed when sending an eScript via SMS. Bp Premier no longer requires a Bp Comms SMS user name or Bp Comms credits to be available in the database to send SMS eScript tokens.	74023
Prescribing	Resolved an issue where editing the Current RX dose did not populate the medication and previous dose in Today's Notes.	73379
Prescribing	Resolved an issue where deleting an ingredient from a custom preparation was permanent, regardless of whether the preparation was saved or not. Ingredients that have been deleted or edited will only be saved to the database when the user clicks the Save button in the Custom Preparation window.	41216
MediSecure	When MediSecure Detector is run, the BP_Premier password is updated and no longer reverts to the deprecated BP_Administrator Password.	73513
Australian Immunisation Register	Resolved an issue where the dhs-subjectId header value displayed the incorrect patient date of birth when updating an immunisation encounter.	74320

Known issues

Bp Function	Issue	Fixed In	Key
Remote Databases	Client-side remote database instances initially created before upgrading to Orchid SP1 Revision 1 will encounter a callstack error when attempting to synchronise the remote database with the live Bp Premier Database Server. Client-side remote database instances created in Orchid SP1 or below are incompatible with version Orchid SP1 Revision 1 or later due to enhancements made to the Bp Premier database. The following issues may be encountered: Inability to synchronise with the Bp Premier Database Server Unable to download a Patient Group Unable to operate in remote database mode. The provider must manually enter visit information that has not been synced to the Bp Premier database. Callstack Indicator: MAKEJADELOGINCHANGES Line: 41 CBPREMOTE:TRANSFERDATA Line: 19 Workaround: IMPORTANT Before uninstalling Bp Premier, the visit information must be manually copied from the client remote database to the live Bp Premier database; failure to do so will result in the permanent loss of visit information. The client installation of Bp Premier and the local client installation of Microsoft SQL will need to be completely uninstalled. Bp Premier should be reinstalled as a client from an Orchid ISO file, followed by an upgrade to Orchid SP1 Revision 1 or later. Once the Bp Premier client installation has been updated to Orchid SP1 Revision 1 or later, a new remote database instance can be created.	Orchid SP2	74873

Bp Function

Issue

Fixed In

Key

Remote Databases

Client-side remote database instances initially created before upgrading to Orchid SP1 Revision 1 will encounter a callstack error when attempting to synchronise the remote database with the live Bp Premier Database Server.

Client-side remote database instances created in Orchid SP1 or below are incompatible with version Orchid SP1 Revision 1 or later due to enhancements made to the Bp Premier database. The following issues may be encountered:

Inability to synchronise with the Bp Premier Database Server
Unable to download a Patient Group
Unable to operate in remote database mode.

The provider must manually enter visit information that has not been synced to the Bp Premier database.

Callstack Indicator:

MAKEJADELOGINCHANGES Line: 41
CBPREMOTE:TRANSFERDATA Line: 19

Workaround:

IMPORTANT Before uninstalling Bp Premier, the visit information must be manually copied from the client remote database to the live Bp Premier database; failure to do so will result in the permanent loss of visit information.

The client installation of Bp Premier and the local client installation of Microsoft SQL will need to be completely uninstalled. Bp Premier should be reinstalled as a client from an Orchid ISO file, followed by an upgrade to Orchid SP1 Revision 1 or later.

Once the Bp Premier client installation has been updated to Orchid SP1 Revision 1 or later, a new remote database instance can be created.

Orchid SP2

74873