Known issues

Lyrebird Health

After clicking block on the pop-up, users cannot modify their browser permissions for microphone access.

Workaround:

To modify the browser permissions to allow microphone access:

1. Close Bp Premier.
2. In the File Explorer, navigate to the following location:
C:\Users\%userprofile%\AppData\Local\Best Practice\EBWebView\Default



3. Locate and delete the Preferences file.
4. When launching Lyrebird in Bp Premier, a pop-up will appear requesting microphone access; click Allow.

Not yet resolved

77786

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

My Health Record

When uploading a Shared Health Summary to My Health Record, an error message will be displayed if a Medical History item with no recorded date is selected.

Error: An error occurred sending the Shared Health Summary! Data at the root level is invalid. Line 1, position 1.

Workaround: To be included on a Shared Health Summary, a Medical History item must include an estimated or actual date when the problem or diagnosis began, as indicated or identified by the clinician.

1. To add a date to a Medical History item, go to the Past History section of the Patient Record, right-click the Condition, and select Edit. The Past History screen will appear.
2. Enter the Date and click Save.

Orchid SP2

73912

My Health Record

When uploading an Advance Care Planning document to My Health Record, if you click to view the attachment when previewing the document, Bp Premier will display an error indicating that the document cannot be found. This issue only affects Terminal Server Environments and only impacts viewing the attachment; the Advance Care Planning document and attachment will upload to My Health Record correctly.

Orchid SP2

73135

My Health Record

An issue has been identified when attempting to display My Health Record documents in the Patient Clinical record. The below My Health Record document types may not display correctly and appear blank:

• Medicine View
• Pathology Overview
• Diagnostic Imaging Overview

A recent Microsoft update has enforced an XML document attribute where, if this is missing, the documents will not be rendered correctly.

This is impacting Bp Premier’s web browser and other Chromium browsers.

The Australian Digital Health Agency will also address this issue at their end and ensure that documents generated from My Health Record can be rendered correctly in Bp Premier.

Workaround: Users can access and view the impacted documents directly from the My Health Record portal. Alternatively, users can save, export, and view these outside of Bp Premier:

1. Select the impacted document from the My Health Record document list and click Save.
2. In Correspondence In, right-click the document you have saved.
3. Click Export.
4. Open the file in your chosen destination and double-click on the PDF or HTML document to view it.

The issue has been resolved by an external update to Microsoft WebView2. WebView2 will automatically update, and no action is required.

74188

eOrdering

Laboratories configured for legacy eOrdering that have been merged with enhanced eOrdering contacts, do not retain their laboratory code.

Workaround: Best Practice Software recommend noting the Laboratory Code prior to merging legacy eOrdering contacts with enhanced eOrdering contacts, as it will need to be entered again once the merge is complete.

-

70882

ePrescribing

For practices using eRx, when resending eScripts from past prescriptions via SMS, the tokens are not sent successfully, and no warning is provided.

Workaround: Electronic prescriptions can continue to be resent via Email, the Best Health App, or the token can be printed.

Orchid SP2

73882

ePrescribing

Practices that have upgraded to Orchid SP1 and completed eRx registration and configuration. The following issues impacting a limited number of practices have been identified:

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

Workaround: Best Practice Software have provided a script that practices who have upgraded to Orchid SP1 can download and run to resolve this issue. See Known Issue: National Prescription Delivery Service and eScript SMS Tokens for more information.

Orchid SP1 Revision 1

73780 / 74023

Active Script List (MySL)

The Consent to upload to ASL check box was added in Bp Premier version Saffron. The check box is set to opt-in by default; therefore, to prevent the drug from being uploaded to ASL, the user must untick this check box.

An issue has been identified when represcribing drugs from the Current RX that were created before the upgrade to Bp Premier version Saffron. These drugs are not being uploaded to ASL when the script is printed or sent by eScript.

Workaround:

Before represcribing the drug in Current Rx:

1. Right-click the drug's name and select Change Quantity/Repeats.
2. Untick the Consent to upload to ASL check box and click Save if the drug is not to be uploaded to the patient's ASL.
3. Leave the Consent to upload to the ASL check box as ticked and click Save if the drug is to be uploaded to the patient's ASL.

This will update the ASLConsent field to indicate whether the provider consented to upload to ASL. When represcribing the drug, the correct ASL Consent flag will be applied to all future repeats from this drug record.

Orchid SP1 Revision 1

73992

HealthLink Online Forms

Issue 1:

When a Healthlink Online Form link embedded in a viewable document (such as an investigation report) is opened via the Incoming reports or Inbox windows, the Healthlink Online Forms window will continue to re-open every minute. When attempting to close the windows, a fatal callstack error will occur.

Callstack Indicator:

• Error Code 50 – Access Violation

CAPP:EXEC Line:21

CBPSAAP:START Line:486

Issue 2:

When you open a Healthlink Online Form link embedded in a viewable document (such as an investigation report) via the investigation reports section of the patient clinical record, the Healthlink forms window will display; however, once you close the window, the Healthlink Online Forms window will automatically re-open after a minute and will continue to do so every time the Healthlink Online Forms window is closed until the patient clinical record is closed.

Not yet resolved.

74412

My Health Record

When uploading a Shared Health Summary to My Health Record, an error message will be displayed if a Medical History item with no recorded date is selected.

Error: An error occurred sending the Shared Health Summary! Data at the root level is invalid. Line 1, position 1.

Workaround: To be included on a Shared Health Summary, a Medical History item must include an estimated or actual date when the problem or diagnosis began, as indicated or identified by the clinician.

1. To add a date to a Medical History item, go to the Past History section of the Patient Record, right-click the Condition, and select Edit. The Past History screen will appear.
2. Enter the Date and click Save.

Orchid SP2

73912

TX Control

When trying to view a corrupted document type, the TX Control may encounter a rare fatal error, which prevents it from being displayed in Bp Premier.

Callstack indicator: BPDOCUMENTVIEWER:VIEWFILEONDISK Line: 16

Workaround: If you encounter this issue, right-click the file and select Export to save the file outside of Bp Premier, You can then view the file externally using an appropriate application such as Microsoft Word or Adobe PDF Reader.

Orchid SP1

70873

Online Claiming

Where there has been an underpayment from Medicare as a result of a derived fee calculation, batches may reconcile with payment records created; however, the services are left in a Sent (not paid) status.

Workaround: If you encounter this issue, right-click on the reconciled batch where there are services are marked as Not paid and select get processing report. This will reset the batch and place it in a Received status, allowing you to reconcile with Accept fee of.

Not yet resolved

71109

Legacy eOrdering

Pathology eOrders created for legacy Douglass Hanly Moir eOrdering contacts will no longer have the DHM prefix on ORM files after upgrading from a previous version to Orchid.

Workaround: We recommend merging legacy eOrdering contacts on the Setup > eOrdering > Existing eOrder Contacts Detected screen to prevent this issue. See Set up Pathology eOrdering for more information.

Orchid SP1

-

Bp Email

Invoices and receipts sent via email from a Terminal Server with TLS disabled may appear blank.

Orchid SP1

71621

Custom preparations

Deleting an ingredient from a custom preparation is permanent, regardless of whether or not the preparation was saved. This will affect custom preparations sent by eScript; the Patient will receive a script without identifying information on the drug, rendering it invalid. Also occurs in Jade and Saffron.

Workaround: If you encounter this issue, you must add the missing ingredients to the custom preparation.

Orchid SP1 Revision 1

41216