Facility administration

Apply shared workflows in a hospital

Use the canonical Hospital classification with the verified shared configuration and care workflows; identify specialist requirements that still need validation.

Current source · source reviewed · 3 min read

Before you begin

Your organization has approved the facility classification and clinical scope.
An authorized administrator can create or update the facility and its related configuration.

1. Classify the hospital

Choose Hospital in the Facility Type list. The version-2 canonical native code is 11. Complete the facility identity and business timezone; the type selection alone does not create wards or clinical services.

2. Build accountable departments and locations

Create the clinical departments that will own encounters and locations. Build the location hierarchy and beds with the intended location forms. Link departments to locations where required. An encounter can then use the configured location-stay workflow for bed assignment or transfer.

3. Validate the encounter types

The shared encounter form supports configured Inpatient, Ambulatory, Observation, Emergency, Virtual and Home Health choices. Verify which choices your hospital instance enables. Start an encounter with at least one department, then assign the responsible care team and location.

4. Connect clinical services

Configure the activity catalogue, observation definitions, specimen requirements and active forms used by your hospital. Validate the doctor, nurse, laboratory and pharmacy role permissions against the patient-to-order-to-result or dispense workflow.

5. Finish the episode

Use the separate discharge, location-stay and encounter-completion workflows. Discharge does not immediately release the bed or close the encounter; the documented stay or completion action performs that work.

Specialist SOP boundary

Specialist operating-theatre lists, anesthesia documentation, ICU device escalation, neonatal care and maternity SOPs were not established by this facility-type audit. A feature label is not a validated specialist implementation.

Classification evidence

The English label is Hospital and the Arabic label is مستشفى. This is one of the five canonical setup contract types. The catalogue does not define a separate clinical workflow implementation for this type.

Local address limitation

The audited FacilityForm uses a required six-digit numeric PIN Code validator. This is a known local-address limitation for deployments that require a different postcode format. Do not invent a postcode to bypass validation; have the deployment owner resolve the address configuration.

Troubleshooting

The expected clinical service is missing after choosing the type

Review the configured departments, activity definitions, forms, resource schedules, user roles and enabled encounter classes. The facility classification alone does not establish those records.

Source evidence

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