Facility administration

Apply shared workflows in a polyclinic

Use the canonical Polyclinic 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. Use the explicit classification

Choose Polyclinic in the current Facility Type list. The version-2 native code is 13. The backend version-1 setup contract has no polyclinic entry; do not send a polyclinic kind to a version-1 setup import.

2. Represent departments explicitly

Create the clinical departments needed by the facility, respecting the configured nesting and total-department limits. Add authorized users to the relevant groups. The department configuration and role links determine actual responsibilities, not the Polyclinic label.

3. Connect encounters with responsible departments

At encounter creation, select the relevant department or departments. Use the encounter-department and care-team workflows for shared care. Verify the access effects when another department joins the care episode.

4. Configure appointments and service catalogues

Create schedules for the actual schedulable resources and active activity definitions for the offered tests or procedures. Validate a booking and a service order with the intended staff roles.

5. Check shared patient and financial records

Search the existing patient before registration, work in the correct encounter and facility account, and use the shared billing and reporting workflows. Do not assume the classification creates automatic inter-specialty referrals or cross-facility access.

Specialist SOP boundary

A specialist referral worklist, department-to-department acceptance protocol, linked episode billing policy and complete multi-specialty SOP were not established by this classification audit.

Classification evidence

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