Admin: Automated edit (via update-page on MediaWiki MCP Server)

2026-07-06T04:02:59Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 09:32, 6 July 2026
Line 94:		Line 94:
	\| Facility Admin, Administrator		\| Facility Admin, Administrator
	\|}		\|}

			{{Navbox access governance}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:42:58Z

OHC identity seed

New page

{{Doc header
|type=concept
|domain=access-governance
|title=Facility Organization
|order=3
|introduced=3.0
|concept=Concepts/Location
|reference=References/Organization
}}

A '''facility organization''' is a department, team, or group inside a single facility — Cardiology, the Emergency Ward, the night-shift nursing team. It is how one facility is divided internally so that staff, patients, and resources can be grouped, and so that access can be granted to a ''part'' of the facility rather than the whole of it.

== What it represents ==

A facility organization is the facility-scoped form of the [[Concepts/Organization|organization]] primitive (<code>FacilityOrganization</code>). It carries a name and description, a place in the facility's internal tree, a type, and a list of member users — each with the role they hold.

The distinction from an instance-wide organization is one of scope. An instance organization is a deployment-level grouping — a hospital network, a governance body, a user group — that lives above any single facility. A facility organization exists only inside one facility and is deleted with it. Think of the instance organization as "who operates across the system" and the facility organization as "how one building is divided up inside."

== Types ==

A facility organization's type describes the kind of unit it is within the facility.

{| class="wikitable"
|-
! Type
! What it is
|-
| <code>root</code>
| The system-generated top node, one per facility, created with the facility; cannot be edited or deleted
|-
| <code>dept</code>
| A department — a major functional division such as Cardiology or Radiology
|-
| <code>team</code>
| A working team within the facility, often nested under a department
|-
| <code>role</code>
| A facility-scoped user group, used to grant a shared role to a set of staff
|-
| <code>other</code>
| Any grouping that does not fit the categories above
|}

<code>dept</code> and <code>team</code> carry the everyday structure of a hospital; <code>role</code> provides facility-level user groups (the facility-scoped counterpart of an instance [[Concepts/Organization|role organization]]).

== How it is structured ==

Facility organizations form a tree. Every facility is created with a single '''root''', and departments, teams, and groups hang beneath it as nested children — a department can itself contain sub-teams, several levels deep.

<syntaxhighlight lang="text">Facility root → Department (dept) → Team (team)</syntaxhighlight>
A unit's name must be unique among its siblings — the units sharing its parent — but the same name can be reused in a different branch of the tree.

The tree is what makes access manageable: a permission granted high in the tree reaches every unit nested under it without being re-granted at each level. Equally, a department "sees" only its own caseload, because patients and resources are attached at or below that department's node — never above it.

== How it connects ==

* '''Facility''' — every facility organization belongs to exactly one [[Concepts/Facility|facility]] and shares its lifetime.
* '''Encounters''' — an [[Concepts/Encounter|encounter]] is scoped to one or more responsible facility organizations. This is the link that decides who can reach a patient's encounter: a clinician's role in a responsible department (or any unit above it) is what grants access to that encounter and the clinical data recorded in it.
* '''Users & roles''' — staff are added as members with a role, which is how Care decides what each person may do within that unit and the units beneath it.
* '''Locations''' — physical [[Concepts/Location|locations]] such as wards and beds are modelled separately; a facility organization groups people and access, not rooms (though an encounter's current location also contributes to who can reach it).

== Permissions ==

Access to facility organizations is governed by the permissions below. The roles listed are the system (default) roles that carry each permission; a deployment may bind these to its own roles. Because the tree cascades downward, a permission held on a parent unit applies to every unit nested under it.

{| class="wikitable"
|-
! Permission
! Description
! System Roles
|-
| <code>can_create_facility_organization</code>
| Create a new department or team beneath an existing unit
| Facility Admin
|-
| <code>can_view_facility_organization</code>
| See a facility's organizations and where they sit in the tree
| Facility Admin, Admin, Staff, Doctor, Administrator, Nurse, Volunteer
|-
| <code>can_manage_facility_organization</code>
| Change a unit's name, description, metadata, and similar details
| Facility Admin, Administrator
|-
| <code>can_delete_facility_organization</code>
| Remove a facility organization
| Facility Admin
|-
| <code>can_list_facility_organization_users</code>
| See who belongs to a facility organization
| Facility Admin, Admin, Staff, Doctor, Administrator, Nurse
|-
| <code>can_manage_facility_organization_users</code>
| Add, remove, and assign roles to users in a facility organization
| Facility Admin, Administrator
|}

{{Related}}

Concepts/Facility Organization - Revision history

Admin: Automated edit (via update-page on MediaWiki MCP Server)

Admin: OHC identity seed