Facility administration

Create a facility through its governance organization

Use the actual governance and Add Facility screens, review defaults, resolve required fields and verify a new synthetic Clinic.

Current source · Actual application UI observed under a local synthetic superuser on the audited source version. Saved operations were independently read through normal product APIs. This does not qualify the full role, facility or clinical workflow matrix. · 6 min read

Before you begin

Use an authorized system or geographic administrator with permission to create a facility at the approved geographic leaf. The captured account was a local synthetic superuser.
Obtain the approved facility type, name, timezone, contacts, address and directory visibility decision before beginning. Training values are not production recommendations.

1. Open the governance organization

From the home dashboard, select Governance and choose the approved geographic organization. Follow its existing child organizations to the intended geographic leaf. The example uses an already configured Saudi country → Riyadh region → Riyadh city training hierarchy. Geographic organizations are separate from operational facility departments.

Open governance organizations from the home dashboard. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Open governance organizations from the home dashboard · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

Trace the configured governance hierarchy to a city organization. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Trace the configured governance hierarchy to a city organization · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

2. Open Facilities at the correct leaf

Check the breadcrumb, select Facilities and choose Add Facility. The displayed list belongs to that geographic organization. Existing geographic configuration was reused; this walkthrough does not demonstrate creating a country, region or city.

Add Facility at an approved geographic leaf organization. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Add Facility at an approved geographic leaf organization · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

3. Complete identity and resolve required fields

Enter the approved facility type, name and description. Required-field feedback appears when an empty form is submitted. This demonstration selected Clinic and a clearly synthetic name. The five canonical current setup types are Hospital, Clinic, Polyclinic, Laboratory and Other; changing the label does not provision clinical modules.

New facility requires classification, identity and contact fields. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — New facility requires classification, identity and contact fields · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

Prepare canonical facility identity and local business timezone. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Prepare canonical facility identity and local business timezone · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

4. Choose the business timezone and approved contact/address

Set the facility’s IANA business timezone explicitly; the example uses Asia/Riyadh. Review the country prefix on the phone field and the selected geographic names. The captured local form repeats State labels for hierarchical selectors and enforces a six-digit PIN Code. Have deployment localization resolved for the actual address; do not copy 111111 or the synthetic contact/address. Map lookup was restricted and was not tested.

Review facility contact, geographic leaf and synthetic address. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Review facility contact, geographic leaf and synthetic address · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

5. Review directory visibility and create

Scroll to Visibility Settings. Inspect Make this facility public explicitly: in this actual new-facility form it was checked by default. The demonstration unchecked it before selecting Create Facility. This is platform facility-directory discoverability, separate from knowledge-site access.

Choose facility directory visibility before creation. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Choose facility directory visibility before creation · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

6. Find and verify the created facility

After the sheet closes, filter the facility list by the chosen name and confirm the Clinic badge. View Facility opens the saved facility. An independent normal facility GET returned 200 and confirmed its exact name, Clinic classification, Asia/Riyadh, private visibility, geographic leaf, empty features and generated Administration root. The synthetic fixture contains no patients.

Synthetic Clinic created and found in the organization facility list. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — Synthetic Clinic created and found in the organization facility list · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

New facility settings and workforce navigation. Actual MANSOQ application in an isolated synthetic training estate; no real patient, staff or financial data. — New facility settings and workforce navigation · 2026-10-18. Current audited-source local training capture; synthetic superuser session, not a role-specific production qualification. Source f6e9f05f. Address and six-digit PIN configuration require deployment localization; external map requests are restricted.

Qualification stops at setup

The captured UI operation created one synthetic Clinic. Hospital, Polyclinic, Laboratory and Other have separate setup examples, but this exact creation UI was not exercised under every type or administrator boundary. Appointments, clinical catalogues, beds, RCM, finance, integrations and operational responsibilities need their own configuration and end-to-end verification.

Troubleshooting

Required fields are red or creation fails

Read each message, correct the actual invalid field and check the approved geographic leaf. Do not bypass product validation or substitute fictional production values.

The real postcode does not fit the form

The observed form currently requires six digits. Ask the deployment owner to resolve localization before production setup; the synthetic fixture value is not a valid-address recommendation.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.