1/7/2025 - Active (solved) - Nothing happens when clicking on the BPDerm icon in the patient file.
Last month's issue seems to have reappeared with the latest BPData update released this morning.
We have released a new version of BPDerm to resolve the issue permanently so this does not happen each month. This new release does not access the BP database at all, only using UI elements from the BP Patient window to retreive the required information for the patient. We have also removed site licensing requirements to simplify the use of the application going forward.
After installing this new version, please log off the windows user and log back in again for BPDerm.exe to run. Please see the section below titled “Installation of BPDerm” for more information about the installation process.
Old note from Scott Smart, 5/6/2025 @ 10.32am AEST:
BP have just provided a working solution to the problem! Here are the instructions to solve the issue:
3. Run the downloaded BP Script Runner, load the fix script downloaded in step 2 then click Run.
4. You should see something like “Statement executed without errors. 3 records affected”. Click Close.
Next we need to disable the ThinkSmart Health partner login and re-enable it for the fix to take effect (this process can't be skipped):
1. Log in to Best Practice (as a user with enough permissions to adjust settings), go to the Setup menu then to Configuration.
2. Click on the Database icon on the left side.
3. Click on the Setup third-party integrations button.
4. Untick ThinkSmart Health then click Save, then Save again on the Configuration window.
6. Go back into the Setup menu then to Configuration.
7. Click on the Database icon on the left side.
8. Click on the Setup third-party integrations button.
8. Tick ThinkSmart Health then click Save, then Save again on the Configuration window.
The problem should now be solved! Please email us on contact@thinksmarthealth.com or call 300 822 667 if further assistance is required.
Old note from Scott Smart, 5/6/2025 @ 9.43am AEST:
We had been alerted to issues with the BPDerm app on 4th June 2025 and found the cause on the same afternoon. The problem is widespread and we are working towards a solution ASAP and will post any fixes here on this wiki page.
BP had released the June BP Data Update which removed our ability to query the patient table for basic patient info for all partner logins including ours. This update automatically installed for all BP sites. BP's aim was to stop third parties from doing IHI number lookups for patients, though BPDerm had never used that information anyway.
I have been working with the BP Partner Support team and our developers and there are now two things happening behind the scenes:
BP are working on a script we can apply to onsite BP databases to allow our app's query to work as it had done, for our partner login, just for now. I am not sure when they will have something for us, though I have already tested 2 scripts they have made. These scripts have not yet solved the issue.
We are developing an updated BPDerm application that obtains the required patient information in another way that doesn’t use the current back-end database access (bringing forward our planned mechanism to work in a post Halo Connect BP).
I’m hoping to have one or both done ASAP and will let you know what we come up with as it happens. We’re already in full swing sorting this out. Thank you for your patience!
Workaround for Heine Cube users: You will need to browse directly to the Heine Cube's web interface. The address to use in your web browser will be in the format http://heine-cube-network-address-here/
To find the web address for your Heine Cube, you can use the BPDerm icon's setting button. To do this:
1. When in the patient file in Best Practice, click on the settings icon:
2. Note the Cube Server address then click Save.
3. Open a web browser, then type in http://heine-cube-network-address-here/ In the example above, this would be http://192.168.1.135/
4. Then log in to the Heine Cube interface as per normal.
Workaround for Microderm users: Please open the Microderm application directly from the desktop and use the software without BP integration.
The only difference is that patient information will not automatically come across from BP. We are yet to provide information on how to link them back to BP once this issue is resolved; we aim to post that information here too as soon as possible.
This step will install BPDerm on your computer. This only needs to be installed on the computers that need to open the BPCube interface and could include a doctor or nurse’s computer or a Remote Desktop server if this technology is used for delivering user desktops.
2. Open the downloaded file. Note: You may be prompted to elevate privileges via User Account Control. Please allow this operation to proceed (click Yes).
3. Click the Run link in the lower right corner of the setup window.
4. Put the dot next to BP Cube (for Heine Cube) or Microderm (for Visiomed Microderm) installations.
IMPORTANT:
Older versions required the entry/selection of site licensing information. This new version has been simplified and no longer requires any of this to be entered.
5. After installation, click the OK button then the Finish link. After this, you will need to log off your Windows user account then log back in for BPDerm to start for the first time. A reboot would also work here though it is not easy to achieve a reboot on a Remote Desktop server during the day. Alternatively, you can manually start the BPDerm application and avoid logging off/on and rebooting by opening the C:\Program Files\BPDerm folder then double-clicking on BPDerm.exe.
¶ REDUNDANT - BP Login configuration for BP Saffron, Orchid and Spectra
This step was formerly required for BPDerm though is no longer needed. This information has been left here only for those still running an older version of BPDerm. This process is done only once per site during the first installation of BPDerm and involves enabling access to this third-party integration. As this setting will be effective on all PCs, skip to the next section if already completed.
1. Log in to Best Practice (as a user with enough permissions to adjust settings), go to the Setup menu then to Configuration.
2. Click on the Database icon on the left side.
3. Click on the Setup third-party integrations button.
2. Click on the settings button on the Heine icon that appears on the screen.
3. This step not needed with latest release of BPDerm: Click on the Site Verification button and enter the details for your site you will receive via email when the site registration information is verified. Then click Save.
4. Enter the Cube Server IP address (or computer name), the Share Name, Cube Username and Cube Password. Click the Test Access button to ensure the connection to the Cube works.
¶ BPDerm Visiomed License and Settings Configuration
1. Open Best Practice then open any patient file.
2. Click on the settings button on the Visiomed icon that appears on the screen.
3. This step not needed with latest release of BPDerm: Click on the Site Verification button and enter the details for your site you will receive via email when the site registration information is verified. Then click Save.
¶ BPDerm settings file corrupt or contains invalid entries
Fig.1: An item with the same key has already been added
1. Use the Windows Task Manager to close BPDerm.exe
2. Open the following folder: %localappdata%\BPDerm e.g. C:\Users\WindowsUser\AppData\Local\BPDerm
3. Rename Settings.txt to OldSettings.txt
4. Open the following folder: C:\ProgramData\BPDerm
5. Rename Settings.txt to OldSettings.txt
6. Reinstall BPDerm application
7. Open the following folder: C:\Program Files\BPDerm
8. Double click to run BPDerm.exe and check if the icon appears in Best Practice again.
¶ BPDerm icon does not appear when in a patient file in Best Practice
There are a number of reasons why the BPDerm icon may not appear when a patient file is open. The two most common solutions are as follows.
Ensure Best Practice is not set to run as Administrator when launching as running an application in this way (with UAC elevation) will cause the application to run in a different context to that of a program that is not running with UAC elevation.
1. Right click on Best Practice desktop icon and click on Properties
2. Click on the Compatibility tab
3. Click on the Change settings for all users button at the bottom of the window
4. Untick Run this program as Administrator then click OK button.
5. Run BP again; it should now start without Admin privileges.
¶ REDUNDANT - Login failed for user ‘BPP-33’ error - BP Jade, Saffron and Orchid
This step was formerly required for BPDerm though is no longer needed. This information has been left here only for those still running an older version of BPDerm. You may receive the following error when attempting to open BPDerm.
The problem is usually caused by BP resetting third party integration permissions during a BP Data or program update. This can happen with any of the other third party integrator permissions and the solution is the same.
These steps need only be done once per site and it should solve the problem for all users on the same network. If the problem reappears, simply follow the steps again.
1. Log in to Best Practice (as a user with enough permissions to adjust settings), go to the Setup menu then to Configuration.
2. Click on the Database icon on the left side.
3. Click on the Setup third-party integrations button.
4. Note down all of the ticked third party integrations in this list as we need to tick them again later in this process.
5. Untick any items already ticked in the list then click Save, then Save again on the Configuration window.
6. Go back into the Setup menu then to Configuration.
7. Click on the Database icon on the left side.
8. Click on the Setup third-party integrations button.
8. Tick ThinkSmart Health and all of the other items noted in step 4, then click Save, then Save again on the Configuration window.
If you receive the following error when trying to use BPDerm or ealier versions of BPCube, you may see the following error:
Cannot access BP Database
Sorry, we couldn't access the BP database!
Instance: [SERVERNAME]\BPSINSTANCE
Username: BPSRawData
This could have happened if the database password was wrong, if
Clinical database access is turned off in BP settings, if the database
password does not meet SQL Server;s complexity requirements, or due
to an unknown cause.
The rror message is as follows:
Login failed for user 'BPSClinical'.
Would you like to try re-entering the password?
[OK] [Cancel]
This is due to a change in the way BP allows database access behind the scenes and has been resolved in newer versions of BPDerm. Please update to a newer version of BPDerm as mentioned in this wiki article under “Installation of BPDerm”.
Need Help? LEMR customers can get help by contacting LEMR Support.
