Facility administration

Apply shared workflows in a clinic

Use the canonical Clinic 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 clinic

Choose Clinic in Facility Type. The current canonical native code is 12. The historical version-1 Clinic code was 3, so retain the setup contract version in any migration or import mapping.

2. Set up the care team and service list

Create the relevant department and link authorized users with their assigned roles. Configure the healthcare service/activity definitions and active questionnaires required for the clinic’s actual care scope.

3. Validate the outpatient path

Use patient search and registration, then book an available resource slot or start the appropriate configured encounter. Ambulatory is one supported encounter type; confirm it is enabled and appropriate rather than assuming the Clinic label forces this selection.

4. Complete clinical and follow-up work

Use the shared allergy, diagnosis, forms, medications and service-request workflows as permitted. Check results and prescriptions in the patient’s correct encounter and arrange a further appointment through the scheduling workflow when needed.

5. Validate financial and print outputs

Review the patient account, invoice and payment workflow used by your clinic. Use approved prescription and report templates, checking patient identity and content before printing.

Specialist SOP boundary

A specialty-specific consultation template, referral protocol, diagnostic package or clinical decision rule is not supplied by the Clinic classification. Each must be configured and reviewed for the actual service.

Classification evidence

The English label is Clinic 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.