Short answer: Google is removing XSLT from Chrome, Edge and the WebView2 component Bp Premier uses to show documents, so XML documents such as discharge summaries now carry a warning. They still display for now. To keep them working after XSLT is switched off on 17 November 2026, your IT administrator can apply the temporary XSLTEnabled policy.
Two of our medical practice customers contacted us in the same week about a red warning banner. A practice in northern New South Wales saw it at the top of every hospital discharge summary in Bp Premier, on new documents and old ones in patient files. A Gold Coast practice saw the same message when opening a patient’s My Health Record. Both wanted to know if something was broken. The documents still displayed correctly underneath, but the banner is an early warning from the Chromium web engine that a feature these documents rely on, XSLT, is being switched off in November 2026. Here is what the warning means and the temporary setting that keeps the documents displaying while the software vendors update them.
Fixed by Emma Mitchell, Senior Engineer at GCIT. Written up by Elliot Munro, CISO.
Symptoms
A red banner appears across the top of documents opened in Bp Premier (for example hospital discharge summaries and investigation reports) or in My Health Record:
This site uses XSLT; that functionality is being removed from this browser very soon. When that happens, this page will likely no longer display correctly. You might be able to install a browser extension that allows you to continue viewing it. Otherwise, you should contact the maintainer of the site for further information.
The banner appears on every affected document, including older documents that displayed without it before. The document content below the banner is still readable. You might also hear it described as an “XSLT deprecation warning”, “XSLT is being removed” or “this page will likely no longer display correctly”.

Affected Software
- Application: Bp Premier (seen on version 1.14.1.1129), My Health Record documents, and any other clinical software that shows XML documents styled with XSLT
- Platform: Windows workstations and Remote Desktop servers
- Related Services: Microsoft Edge WebView2 Runtime, Microsoft Edge and Google Chrome
Cause
Many clinical documents, including hospital discharge summaries and My Health Record documents, are XML files. A stylesheet written in a language called XSLT turns that XML into the formatted page you read. The web browser does that conversion.
Google is removing XSLT from Chromium, the engine behind Google Chrome, Microsoft Edge and the Microsoft Edge WebView2 component. Bp Premier uses WebView2 to display documents inside the program, which is why the banner shows up in Bp Premier even if you never open a web browser. Google’s published timeline is:
- Chrome 158, 17 November 2026: XSLT stops working on the Stable release for everyone, except organisations using the temporary enterprise policy or a site-level trial.
- Chrome 176, 17 August 2027: the trial and the enterprise policy stop working, and XSLT is disabled for all users.
After XSLT is switched off, documents that depend on it will likely show as unformatted or blank. Nothing is wrong with your computers or your Bp Premier installation. The long-term fix has to come from the people who produce and display the documents, such as Best Practice Software and the Australian Digital Health Agency.
Resolution
Google and Microsoft provide a temporary policy called XSLTEnabled that keeps XSLT working after the November 2026 switch-off. These steps are for the practice’s IT administrator. Apply the setting to the place where the documents are actually displayed.
Step 1: Work out where the banner appears
- Inside Bp Premier (Correspondence In, investigation reports, discharge summaries): Bp Premier displays these with Microsoft Edge WebView2. Apply the WebView2 setting on every computer that runs Bp Premier. If staff use Bp Premier on a Remote Desktop server, apply it on that server.
- In Google Chrome or Microsoft Edge (for example My Health Record opened in a browser): apply the Chrome and Edge settings on each workstation.
- Not sure? Applying all three settings does no harm.
Step 2: Apply the XSLTEnabled setting
For one or two computers, set the registry values below from an administrator account. For a whole practice on a Windows domain, use Group Policy instead (Step 3).
| Where the banner appears | Registry key | Value |
|---|---|---|
| Bp Premier (WebView2) | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\WebView2 |
XSLTEnabled (DWORD) = 1 |
| Microsoft Edge | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge |
XSLTEnabled (DWORD) = 1 |
| Google Chrome | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome |
XSLTEnabled (DWORD) = 1 |
If a key does not exist yet, create it. To undo the change later, delete the XSLTEnabled value.
Step 3: Or deploy it with Group Policy
The same setting is called Control the availability of the XSLT feature in each product’s administrative templates:
- WebView2: Administrative Templates > Microsoft Edge WebView2 (MSEdgeWebView2.admx)
- Microsoft Edge: Administrative Templates > Microsoft Edge (MSEdge.admx)
- Google Chrome: the Google Chrome administrative templates
Set the policy to Enabled, link the Group Policy Object so it covers every computer that needs it, and name it clearly as temporary (for example “XSLTEnabled (temporary)”) so it is easy to find and remove later. Computers pick it up at their next policy refresh or restart.
Step 4: Check the setting has applied
- In Microsoft Edge, go to
edge://policy. In Google Chrome, go tochrome://policy. XSLTEnabled should be listed with a value of true. - For Bp Premier, ask staff to close Bp Premier completely (or sign out of the Remote Desktop session and back in), then reopen a document that showed the banner and confirm it still displays correctly.
Important Notes
- The banner may not go away. The policy keeps XSLT working. It is not documented to hide the warning. Staff can carry on using the documents as normal.
- This is a temporary workaround, not a permanent fix. Microsoft and Google both describe XSLTEnabled as a temporary policy. Google’s timeline and Chromium’s current policy definition both say the policy stops working at Chrome 176 (17 August 2027). The Chrome Enterprise policy page has said Chrome 164, so check it before relying on the later date.
- Ask your software vendors about their plans. Contact Best Practice Software support about how Bp Premier will display XSLT-based documents once the policy is retired. For My Health Record documents, the change has to come from the Australian Digital Health Agency and your clinical software vendor.
- Remove the setting when it is no longer needed. Once your vendors have updated their documents, delete the registry values or the Group Policy Object. Keeping old features switched on longer than necessary is not good security practice, and Google is removing XSLT partly because it has been a source of browser security problems.
- Do not install random browser extensions. The banner suggests a browser extension as an option. On computers that hold patient information, only install extensions your IT provider has approved.
If Bp Premier instead shows “Unable to initialise BP.DocumentViewer.Control” and the result inbox will not open, see Bp Premier “Unable to Initialise BP.DocumentViewer.Control”.
Related Resources
- Fix: NCSR Hub Not Working in Bp Premier (Bp FHIR Service)
- Setting up My Health Record (MHR) Access in Best Practice
- Fix: “The ability to send Clinical Communication messages must be enabled” in Best Practice
- Chrome for Developers: XSLT deprecation and removal timeline
- Microsoft Learn: Microsoft Edge WebView2 policies (XSLTEnabled)
- Microsoft Learn: Microsoft Edge browser policy XSLTEnabled
- Chrome Enterprise: XSLTEnabled policy
- Best Practice Software: Troubleshoot WebView2 in Bp Premier
Related troubleshooting
MMD report downloader shows an invalid JSON error. If the error is in the separate MMD report downloader rather than Bp Premier, check whether downloads succeed but updating their completion status fails.
If you need help keeping your practice’s clinical software running smoothly, get in touch with our team.