Atlas3 and WebAPI 3.0.0 Released
We are pleased to announce the release of Atlas3 3.0.0 and WebAPI 3.0.0. Together, these releases establish the next generation of the OHDSI Atlas application and service platform.
Atlas3 3.0.0 is the first release from the Atlas3 repository. It provides a modern Atlas experience for core observational research workflows, including cohorts, concept sets, characterizations, feature analyses, pathways, incidence rates, profiles, data-source reporting, and administration. Major analytics workflows are organized in a unified Analysis Hub, while concepts, configuration, and job monitoring have been streamlined into consolidated experiences.
WebAPI 3.0.0 is a major platform modernization. It upgrades the application to Java 21, Spring Boot 3.5, Spring MVC, Spring Batch 5, embedded Tomcat 10.1, and Jakarta EE-compatible dependencies. It also introduces external YAML configuration, updated database migration tooling, and a new authorization architecture based on Spring Security and entity-level access control.
Highlights
-
Atlas3 provides the new user interface for core cohort, vocabulary, concept-set, characterization, feature-analysis, pathway, incidence-rate, profile, and data-source workflows.
-
WebAPI 3.0 adds OAuth/OIDC capabilities, role mapping at sign-in, API keys, method-level authorization, ETag support, and administrator RunAs support.
-
WebAPI 3.0 replaces the legacy Shiro security framework with Spring Security and introduces resource-level permissions for major Atlas entities.
-
Pathway characterization, cohort characterization, feature analysis, incidence rates, and patient-profile services are available in the 3.0 platform.
-
Internationalization is no longer handled by WebAPI; it is a user-interface responsibility in the new platform.
Before Adopting 3.0
Atlas3 and WebAPI 3.0 are major-version releases. Before beginning an upgrade, ensure that backups of the existing 2.x deployment are current, complete, and independently verified.
-
Take up-to-date backups of the WebAPI database, including the schema, data, roles, and permissions required for recovery.
-
Preserve the current 2.x application configuration, authentication configuration, data-source configuration, and deployment artifacts.
-
Validate that backups can be restored in a non-production environment before running any 3.0 database migration or changing the production deployment.
-
Record the installed Atlas and WebAPI versions and confirm the migration and rollback process with the local operations team.
Migration Scope
The new release modernizes both the user interface and the server-side security and configuration model. Organizations should review their authentication integration, entity permissions, custom configuration, and site-specific workflows before production adoption.
Some Atlas 2.x functionality is not available in the 3.0 release, including population-level estimation, patient-level prediction, the custom Tool Registry, the Reusables manager, and the LDAP/Active Directory user-import workflow. Review the detailed Atlas3 3.0.0 release notes when planning migration.
Community Feedback
We welcome community feedback on Atlas 2.x capabilities that should be reconsidered for inclusion in a future Atlas 3.x release. Share missing-feature requests and use cases in the Atlas3 feature feedback discussion.
Deployment Information
The WebAPI setup guide has been updated with information for WebAPI 3.0.
Broadsea and Docker deployment information will be provided shortly.