User Acceptance Testing Environment (UAT)

Purpose and Characteristics

The UAT environment is where end users validate that the system meets clinical and operational needs before production deployment. OpenMRS maintains separate UAT environments for both Platform (http://uat-platform.openmrs.org ) and Reference Application (uat-refapp.openmrs.org) testing.

●      Key Features:

○      Contains only release-candidate code that has passed QA testing

○      Uses production-like data volumes and realistic clinical scenarios

○      Highly stable with controlled, scheduled updates

○      UAT Platform resets daily; UAT RefApp resets weekly

○      Configuration and performance closely mirror production

○      Changes require manual deployment through Bamboo CI

○      Serves as final staging area before production release

Deployment Process

UAT deployments are manual and controlled through the Bamboo deployment system. According to the OpenMRS Platform Release Process, after each platform release, the UAT environments must be updated to point to the new version.

Deployment steps include:

●      Creating deployment project in Bamboo CI

●      Configuring environment details (name, description, docker image tag)

●      Setting up deployment scripts with docker commands

●      Selecting specific build result for deployment

●      Executing deployment with appropriate docker image tags (e.g., :uat)

Testing Activities

●      Real-world clinical workflow validation by end users

●      Usability testing with actual healthcare providers

●      Training sessions on new features and functionality

●      Acceptance testing against defined business criteria

●      Sign-off procedures before production deployment

●      Key Users:

○      Clinical staff and healthcare providers

○      Administrators and data managers

○      Implementation team members

○      Business stakeholders for final approval