Product Update: Managing Organization Re-architecture
We are pleased to announce the release of the Managing Organization Re-architecture change in OmegaAI.
Purpose
This release eliminates the concept of the Master Organization and introduces the Managing Organization model. The Managing Organization becomes the top-level entity that owns patient records, while child organizations operate under it with limited configurations. This re-architecture simplifies organizational management, ensures consistency in patient data, and streamlines integration across all workflows.
Key Highlights
-
Managing Organization replaces Master Organization
-
All references to “Master Organization” are now updated to “Managing Organization.”
-
Managing Organization is the top-most entity in the hierarchy.
-
-
Unified Patient Management
-
Patient records are always created under the Managing Organization.
-
User Access Control (UAC) for patients is applied at the Managing Organization level, even for members of child organizations.
-
-
Child Organization Capabilities
-
Child organizations can manage users and may act as Imaging Organizations.
-
In single-location practices, all configurations remain within the Managing Organization.
-
-
Data Consistency & Migration
- All existing patient records from child organizations are to be migrated and merged into the Managing Organization to ensure consistency and avoid duplication.
-
How User Access Control (UAC) works ?
-
Patient UAC: Queries apply at the Managing Organization level and extend across all child organizations.
-
Study UAC: Remains based on the Imaging Organization for precision in access control.
-
Benefits
-
Simplified organizational hierarchy and reduced complexity.
-
Seamless patient and study management across workflows.
-
Standardized data governance for improved accuracy and reliability.
-
Clear separation between patient ownership (Managing Organization) and imaging responsibilities (Child Imaging Organization or Managing Organization in a single-location practice).