What is our primary use case?
Hyland OnBase serves as our main solution for centralizing and securing enterprise document management, primarily for digitizing, storing, and controlling user access permissions to patient and operational records, with integration across our healthcare system.
At the hospital, we needed to restrict access to sensitive patient health records strictly to authorized medical and administrative staff in compliance with LGPD data privacy regulations in my country. I configured specific user group permissions in Hyland OnBase, tested the access restrictions across different departments, and ensured that medical records were indexed correctly and restricted securely without exposing patient data to unauthorized personnel.
How has it helped my organization?
Hyland OnBase has positively impacted my organization by providing faster access to documents and information.
Improved access with Hyland OnBase has helped my organization greatly in terms of efficiency and compliance with regulatory requirements.
What is most valuable?
The best features that Hyland OnBase offers include intelligent document capture and indexing, process and workflow automation, seamless enterprise integration, and granular and secure access control and compliance.
Role-Based Access Control (RBAC) made the biggest difference for me among document indexing, workflow automation, integration, and access control. In a healthcare enterprise setting, RBAC allowed us to enforce strict data privacy requirements like LGPD by ensuring users could only access authorized records based on their role, while making user onboarding and permission management much faster and more reliable.
What needs improvement?
Hyland OnBase can be improved by providing a modern user interface, simplified deployment and admin overhead, API capabilities, and advanced AI.
I rated Hyland OnBase eight out of ten because the interface needs renewal.
For how long have I used the solution?
I have been using Hyland OnBase for approximately ten years during my previous technical roles, focusing on installation, environment setup, user access control, and testing.
What other advice do I have?
Regarding Hyland OnBase's AI capabilities, I believe its governance and security focus on data privacy, auditability, and human in the loop is essential.
I think about the accuracy and reliability of Hyland OnBase's AI output in terms of structured versus unstructured documents, the safety net it provides, and its continuous learning abilities.
In our enterprise environment, Hyland OnBase is often deployed in a hybrid on-premises architecture.
For the hybrid deployment of Hyland OnBase, we use Microsoft Azure and Amazon Web Services.
My top advice for anyone evaluating Hyland OnBase is to invest early in clean document taxonomy and Role-Based Access Control (RBAC).
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?