Organization structure

Group, legal entity, facility and department. Roles and users are assigned to these nodes.

Acceptance criteria

US-44 Org Hierarchy as Configured Data HIGHEST NEW SCREEN

As an administrator, I want organization entities (group, legal entity, facility, department) available as records, so that roles and users can be associated with the right part of the organization.

Org entities (group, legal entity, facility, department) exist as records roles can reference.
Shallow/flat structure sufficient for BETA (for inheritance engine see US-44b).
Seed the demo org tree for client presentations.

US-44b Org Hierarchy Deep Engine HIGHEST NEW SCREEN

As an administrator, I want a full organizational hierarchy with inheritance (Group→Legal Entity→Facility→Department), so that roles and permissions can be assigned and inherited across the org structure.

Full model with inheritance.
Departments extensible (X-ray, consultation/doctors, ER/examination, operation, lab, nurse station…).
Roles can be assigned at any level, inheriting downward.

US-52a Data-Scoping Design + Org-Node Stamping HIGHEST NEW SCREEN

As the system, I want every record stamped with its originating org-node and a data-scoping model designed, so that row-level isolation can be enforced later without a data retrofit.

Design the row-level scoping model (deferred enforcement to US-52b).
Every record stamped with its originating org-node from now on.

Wireframe state

BasicDeep

Read only. You are an Auditor: read only. You can read and export this page. Changes need an administrator.

OrganizationStructureReporting groups Data scope

Basic structure. Facilities are the lowest level for now. Departments and inheritance arrive with the full hierarchy.

Inheritance is on. A role given at a node also applies to everything under it. A claims officer assigned to Facility A works in all 6 of its departments, and nowhere else.

Al Raneem Group

Add node

Al Raneem GroupGroup2 legal entities, 3 facilities

Al Raneem Medical CompanyLegal entityCR 1010456789

Facility A: Al Raneem Hospital, RiyadhFacility11 users, 4 roles

Consultation clinicsDepartment14 users Inherits Facility A roles

Emergency and examinationDepartment9 users Inherits Facility A roles

LaboratoryDepartment4 users Inherits Facility A roles

RadiologyDepartment3 users Inherits Facility A roles

Operation theatreDepartment5 users Inherits Facility A roles

Nurse stationDepartment6 users Inherits Facility A roles

Facility B: Al Raneem Clinics, JeddahFacility6 users, 3 roles

Consultation clinicsDepartment4 users Inherits Facility A roles

LaboratoryDepartment2 users Inherits Facility A roles

Al Raneem Dental CompanyLegal entityCR 1010987654

Facility C: Al Raneem Dental, RiyadhFacility3 users, 2 roles

Group Legal entity Facility Department

Selected: Facility A

Rename

Type: Facility
Parent: Al Raneem Medical Company
NPHIES provider ID: NPHIES-10-0457
Certificate: Valid until 14 Mar 2027
License: ORG-LIC-24817
Departments: 6Not tracked yet
Users: 11

Roles assigned here

Edit scope

Claims officer2 users
Receptionist3 users
Insurance approval officer2 users
A/R1 user
A/P1 user

Add nodeMoveRemove

Every new record is stamped with the node it was created in. See Data scope.

NPHIES identity per facility

Facility	NPHIES provider ID	License	Certificate
Facility ARiyadh	NPHIES-10-0457	ORG-LIC-24817	Valid until 14 Mar 2027
Facility BJeddah	NPHIES-10-0458	ORG-LIC-25102	Expires in 21 days
Facility CDammam	NPHIES-10-0473	ORG-LIC-26340	Valid until 2 Aug 2027

Each facility signs and sends as itself, so it needs its own provider ID and certificate. A node below a facility uses its parent's.