The following information should be considered or noted when you upgrade DeficiencyPop deployments. Read this information prior to upgrading your version of OnBase.
- Server Machine Considerations
-
The following should be considered with regard to server machines:
-
When upgrading from OnBase 16 or later, back up the DeficiencyPop Web.config file. The backup copy can be referenced when updating specific settings for the new version of OnBase.
-
Note the authentication settings for the DeficiencyPop Web application in IIS.
-
Note the settings for the DeficiencyPop application pool in IIS.
-
As of OnBase Foundation EP1, if DeficiencyPop is embedded in another application or an iframe, then the cookieSameSite attribute in the DeficiencyPop web.config file must be set to None. It is set to Lax by default.
-
As of OnBase Foundation EP1, if DeficiencyPop is integrated with Epic, then Epic encryption settings must be configured in OnBase Configuration as described in the Integration for Epic module reference guide. The PopChecksumKey and EpicAuthenticationType web.config settings are no longer used.
-
As of OnBase 18, DeficiencyPop requires a 64-bit application pool. When upgrading to OnBase 18 or later, ensure the Enable 32-Bit Applications setting is False for the DeficiencyPop application pool (Advanced Settings).
-
As of OnBase 16, DeficiencyPop requires the OnBase Application Server in order to communicate with the database and retrieve documents from Disk Groups.
-
As of OnBase 16, DeficiencyPop uses the OnBase Patient Window to provide a comprehensive view of a patient record when a physician is looking for additional information to satisfy a deficiency. DeficiencyPop no longer uses the legacy ChartPop, LongitudinalPop, or MRNPop integrations.
- End-User Workstation Considerations
-
The following should be considered with regard to end-user workstations:
-
Delete the browsing history on end-user machines.
-
Delete the Temporary Internet Files cache for Internet Explorer.
-
When upgrading from a version of OnBase prior to OnBase 16, you should uninstall existing ActiveX controls from users' workstations. DeficiencyPop no longer uses ActiveX controls as of OnBase 16.
- Query String Considerations
-
If you are upgrading from a prior version of OnBase, you may need to update the query strings configured for existing DeficiencyPop links.
-
As of OnBase Foundation EP1, query strings that include Epic authentication parameters must also include the epicTimestamp parameter.
-
As of OnBase 18, the assigningauthority parameter is no longer supported. To provide an assigning authority for a patient identifier, see the section on creating DeficiencyPop URLs in the DeficiencyPop module reference guide.
-
As of OnBase 16, the following query string parameters are not supported:
-
viewMRMMode
-
customEvaluationName
-
newwindow(Replaced by the isembedded parameter.)
-
-
As of OnBase 16, the newwindow parameter has been replaced by the isembedded parameter. If existing links contain the newwindow parameter, be sure to update them to use the isembedded parameter.
-
As of OnBase 16, valid values for the external parameter are true and false. The external parameter no longer accepts yes and no values. If existing links contain the external parameter, be sure to update them to use the new values.
- General Deployment Considerations
-
In addition to the previous considerations, the following should be considered with regard to general deployments:
-
As of OnBase 17, the EnablePatientContextSync setting has been moved from the DeficiencyPop Web.config file to OnBase Configuration. If EnablePatientContextSync was true in Web.config, then you need to select the Enable Patient Context Syncing setting in OnBase Configuration under Medical | User Interface Settings | DeficiencyPop | Settings.
-
As of OnBase 16, DeficiencyPop is a different Web application from previous versions. As a result, you cannot use an automated installer to upgrade DeficiencyPop from a version of OnBase prior to OnBase 16. If you are upgrading from a version of OnBase prior to OnBase 16, be sure to uninstall the old version of DeficiencyPop before installing the new version.
-
As of OnBase 16, the deficiency autoplay feature is not available in DeficiencyPop. This functionality remains available in the Medical Records Unity Client.
-
As of OnBase 16, the option to cc other physicians on an editable transcription is not available in DeficiencyPop. This functionality remains available in the Medical Records Unity Client.
-
As of OnBase 16, correction tasks cannot be completed in DeficiencyPop; they can only be submitted through the Analysis window. Correction task completion remains available in the Medical Records Unity Client. Workflow-based correction tasks remain available in the OnBase Patient Window, which can be accessed from DeficiencyPop.
-
As of OnBase 16, internal mail is not available in DeficiencyPop. This functionality remains available in the Medical Records Unity Client.
-
As of OnBase 16, meaning statements are not available for Edit Transcription deficiencies. When a physician signs an Edit Transcription deficiency, the physician will not be prompted to provide a meaning statement, even if a meaning statement is configured for the Document Type of the transcription. Meaning statements remain available in the Medical Records Unity Client.
-
As of OnBase 16, proxy users cannot log on to DeficiencyPop to work on a physician's deficiencies. Only users configured as physicians can log on to DeficiencyPop. Support for proxy users remains available in the Medical Records Unity Client.
-
As of OnBase 16, the view secondary signer reports feature is not available. A primary signer can view only the pending Dual Edit Transcription deficiencies that are currently available for the primary signer to address. If the deficiency is not yet available due to the Secondary Signer Duration To Complete Transcription Deficiencies setting, the primary signer must wait for the configured period to elapse before the deficiency becomes available in the primary signer's queue.