The following information should be considered or noted when upgrading Release of Information Unity deployments. Read this information prior to upgrading your version of OnBase.
- Server Machine Considerations
-
The following should be considered with regard to server machines:
-
Ensure the version and build of the Medical Records Unity Client match the version and build of the OnBase Application Server.
- End-User Workstation Considerations
-
The following should be considered with regard to end-user workstations:
-
Ensure the proper compatible third party applications are installed (e.g., Adobe Acrobat, Microsoft Office).
-
Ensure the directory where the Medical Records Unity Client is installed is added to the virus scanner white list.
-
Make note of any settings in the Medical Records Unity Client configuration file that have been modified from their default values.
-
Ensure that the Application Server URL is correct in the ServicePath field of the Medical Records Unity Client configuration file and can be accessed from a web browser. Verify the user does not receive certificate errors and is not prompted for authentication credentials.
- ClickOnce Deployment Considerations
-
The following should be considered with regard to ClickOnce deployments:
-
Ensure the environment in which the Medical Records Unity Client will be deployed is not a Terminal Services environment.
-
Ensure the workstation environment can allow ClickOnce deployments to be installed.
-
Ensure any upgrades are made to existing deployments.
- General Deployment Considerations
-
In addition to the previous considerations, the following should be considered with regard to general deployments:
-
As of OnBase Foundation 22.1, changes to User Group rights and permissions will not be reflected within the Medical Records Unity Client until the Application Server's cache is reset. If you change User Group rights to include permissions to Release of Information, you will need to reset the Application Server's cache before those permissions will take effect.
You may reset the Application Server's cache using the Reset Cache option in OnBase Configuration or the Reset Server Cache option in OnBase Studio. For more information about the Reset Cache option in OnBase Configuration, see the System Administration documentation. For more information about the Reset Server Cache option in OnBase Studio, see the Studio documentation.
-
As of OnBase 18, the following XML path is no longer supported in Document Composition templates: //ROIRequest/Inventory/MedicalRecords/MedicalRecord/MRNWithAssigningAuthority
Prior to OnBase 18, this XML path was used to display the assigning authority for a patient's MRN. If your solution uses overlapping patient identifiers, make sure Document Composition templates provide sufficient information to distinguish patients who may have matching identifiers.
-
Beginning in OnBase 18, the Group by Patient option is available in Request Type configuration. This option is selected by default for all Request Types. It applies only to requests where multiple patients are attached and the Separate by Chart option is not selected on the release order screen. If a system is upgraded from a version prior to OnBase 18, the release order for documents attached to existing requests is not changed upon upgrade. The Group by Patient option takes effect on a day-forward basis.
-
Beginning in OnBase 17, packet generation is handled using the Unity Scheduler. It is no longer handled using the ROI Packet Generator and its prerequisites. If you are upgrading from a version prior to OnBase 17, uninstall the previous packet generation components before installing the Unity Scheduler components.
-
If you are upgrading from a version prior to OnBase 17, you must upgrade all ROI-related components, and all users must be on the same version. In OnBase 17 and later, Release of Information cannot be run in parallel with a version prior to OnBase 17.
-
If you are upgrading from a version prior to OnBase 17, ensure there are no requests with a status of Pending Packet. The Unity Scheduler service will not generate packets for requests that became ready for packet generation prior to OnBase 17.
-
If you are upgrading from a version prior to OnBase 17, Document Composition templates that use the //ROIRequest/Patient node must be modified to use the //ROIRequest/Inventory/MasterPatientIndexes node or the //ROIRequest/Inventory/MedicalRecords node to access the attached patients' data. Patient data will not be populated for placeholders using the //ROIRequest/Patient node.
-
If you are upgrading from a version prior to OnBase 17 and your solution uses overlapping MPIs or MRNs, then you must cancel in-progress requests and re-create them after the upgrade. Otherwise, placeholders on composed documents might not be populated for the in-progress requests.