Extensions
Help reception support a clear next step.
Patient Access
Configure practitioner or location resources, session dates, opening hours and slot rules. Link services and approved booking permissions to the resource.
Identify the patient, review contact and identifier information and book the intended service. Preserve referral and payer details where the selected care and revenue workflow requires them.
Record arrival and queue information, open or link the encounter and direct the person to the responsible clinic or department. Confirm the next responsibility rather than leaving a booking without a care destination.
Record completion, cancellation or missed attendance, then arrange an appropriate follow-up. Apply the configured revisit and charging policy using the selected billing workflow.
Your configuration
Use the registered details of your organization. Do not enter patient records here.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Registered organization namelegal_name | Yes | text | Example Healthcare Organization |
Commercial registration numberregistration_number | Yes | text | EXAMPLE-CR-001 |
Countrycountry | Yes | SA / AE / BH / KW / QA / OM / EG / OTHER | SA |
Tax registration numbervat_number | Optional | text | — |
Add every facility included in your subscription. These become real, separate facilities in your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Your organization
| Column | Required | Format | Example |
|---|---|---|---|
Facility namename | Yes | text | Example Facility |
Facility typetype | Yes | hospital / clinic / polyclinic / laboratory / other | clinic |
Facility licenselicense_number | Yes | text | EXAMPLE-LICENSE-001 |
Addressaddress | Yes | text | Example training address |
Phonephone | Yes | text | +966500000000 |
Time zonetimezone | Yes | Asia/Riyadh / Asia/Dubai / Asia/Qatar / Africa/Cairo / UTC | Asia/Riyadh |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility number (starting at 1)facility | Yes | integer 1–1000 | 1 |
Department namename | Yes | text | Example Department |
Create departments, consultation rooms, wards and beds. You can add more inside your app.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
Load / review first: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Location namename | Yes | text | Example Room |
Typekind | Yes | room / ward / bed | room |
Inside location (optional)parent | Optional | text | — |
Your verified account becomes the facility administrator. Invite staff in the account portal; staff seats are enforced.
Upload in the matching account setup step, review the preview, apply the values and Save and continue. The tenant version may define different columns; download its template inside setup.
| Column | Required | Format | Example |
|---|---|---|---|
Namename | Yes | text | Example Staff |
Work emailemail | Yes | staff@example.invalid | |
Clinical rolerole | Yes | facility_admin / doctor / nurse / pharmacist / reception / billing / member | doctor |
Security roles and explicit permissions
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
| Column | Required | Format | Example |
|---|---|---|---|
Role namerole_name | Yes | text | Example scheduling role |
Permission identifierpermission_slug | Yes | text | can_list_schedule |
Facility organization memberships
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Planned team · Departments · Roles & permissions
| Column | Required | Format | Example |
|---|---|---|---|
Staff emailstaff_email | Yes | staff@example.invalid | |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Department namedepartment | Yes | text | Example Department |
Approved role namerole_name | Yes | text | Doctor |
User clinician profile and clinic affiliation
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Planned team · Departments · Rooms, wards and beds · Users & department access
| Column | Required | Format | Example |
|---|---|---|---|
Doctor emailstaff_email | Yes | staff@example.invalid | |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Clinic locationclinic_location | Yes | text | Example Room |
Qualificationqualification | Yes | text | TO-CONFIRM |
Practitioner licencelicense_number | Yes | text | EXAMPLE-LICENSE-001 |
Primary clinicprimary_clinic | Optional | checkbox | true |
Healthcare service directory
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Departments · Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Local service codeservice_code | Yes | text | EXAMPLE-SVC-001 |
English namename_en | Yes | text | Example service |
Arabic namename_ar | Yes | text | خدمة تدريبية |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Locationlocation | Yes | text | Example Room |
Service functioninternal_type | Yes | general / scheduling / lab / pharmacy / store | scheduling |
Practitioner schedules and availability
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Doctors & operational clinics · Services & department catalogue
| Column | Required | Format | Example |
|---|---|---|---|
Unique schedule codeschedule_code | Yes | text | EXAMPLE-SCH-001 |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Doctor emailstaff_email | Yes | staff@example.invalid | |
Departmentdepartment | Yes | text | Example Department |
Clinic locationclinic_location | Yes | text | Example Room |
Weekdayweekday | Yes | mon / tue / wed / thu / fri / sat / sun | sun |
Start timestart_time | Yes | HH:MM | 08:00 |
End timeend_time | Yes | HH:MM | 12:00 |
Slot durationslot_minutes | Yes | integer 5–240 | 15 |
Valid fromvalid_from | Yes | YYYY-MM-DD | 2026-10-09 |
Valid tovalid_to | Yes | YYYY-MM-DD | 2027-10-09 |
Registry function settings applied to native scheduling closures with readback
Upload in Your products · configuration data. Apply, then Save and continue checks cross-file references. Launch imports supported records in one transaction and reconciles counts. Function settings are validated against the supported registry, applied natively and read back; prices, catalogue mappings and hardware require approval before activation.
Load / review first: Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Selected feature IDfeature | Yes | scheduling | scheduling |
Function settingfunction_key | Yes | scheduling.closures | scheduling.closures |
Closure namename | Yes | text | Example closure |
First closed datevalid_from | Yes | YYYY-MM-DD | 2026-12-01 |
Last closed datevalid_to | Yes | YYYY-MM-DD | 2026-12-01 |
Closed fromstart_time | Yes | HH:MM | 08:00 |
Closed untilend_time | Yes | HH:MM | 17:00 |
Room (blank closes the whole facility)location | Optional | text | Example Room |
Freeze products, versions, facilities, delivery mode and acceptance scope.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
| Column | Required | Format | Example |
|---|---|---|---|
Catalogue product IDproduct_id | Yes | text | outpatient |
Agreed releaserelease | Yes | text | TO-CONFIRM |
Operating modemode | Yes | native / connected | native |
Facility scopefacility_scope | Yes | text | all |
Included in this projectincluded | Yes | true / false | true |
Accountable roleowner_role | Yes | text | Project owner |
Acceptance evidenceacceptance_test | Yes | text | Approved end-to-end test |
Approval referenceapproval_reference | Yes | text | EXAMPLE-REF-001 |
Map roles to permitted actions and verify access across facility boundaries.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Facilities · Planned team
| Column | Required | Format | Example |
|---|---|---|---|
Rolerole | Yes | text | doctor |
Facility scopefacility_scope | Yes | text | EXAMPLE-FACILITY-001 |
Resourceresource | Yes | text | Patient record |
Actionaction | Yes | text | read |
Allowedallowed | Yes | true / false | true |
Approverapprover_role | Yes | text | Security owner |
Test evidenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Record locally approved pathways, responsibilities and exception handling.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Departments · Access & approvals
| Column | Required | Format | Example |
|---|---|---|---|
Workflow IDworkflow_id | Yes | text | EXAMPLE-WF-001 |
Product IDproduct_id | Yes | text | outpatient |
Entry evententry_event | Yes | text | Patient arrival |
Responsible roleresponsible_role | Yes | text | Nurse |
Required informationrequired_information | Yes | text | Verified identity and visit context |
Next eventnext_event | Yes | text | Clinical consultation |
Handover ownerhandover_owner | Yes | text | Doctor |
Exception pathexception_path | Yes | text | Identity mismatch to review |
Workflow approvalapproval_reference | Yes | text | EXAMPLE-REF-001 |
Record complete positive, negative, boundary, access and failure tests per product.
Upload in Account setup → Implementation files & acceptance evidence. The data is saved in your account implementation records. Review with the named owner, record approval and attach the evidence. This register records decisions; it does not activate production configuration.
Load / review first: Project scope · Clinical workflow configuration
| Column | Required | Format | Example |
|---|---|---|---|
Test IDtest_id | Yes | text | UAT-001 |
Product IDproduct_id | Yes | text | outpatient |
Scenarioscenario | Yes | text | Visit from arrival to financial follow-up |
Preconditionspreconditions | Yes | text | Approved setup and synthetic data |
Exact actionsactions | Yes | text | TO-CONFIRM |
Expected resultexpected_result | Yes | text | TO-CONFIRM |
Actual resultactual_result | Yes | text | NOT-RUN |
Statusstatus | Yes | not_run / pass / fail / blocked | not_run |
Evidence referenceevidence_reference | Yes | text | EXAMPLE-REF-001 |
Approverapprover_role | Yes | text | Product owner |
Illustrative operating cases
Reception converts an available practitioner session into a patient visit.
Booking, arrival and encounter refer to the same patient and intended care resource.
A practitioner session changes and a returning patient needs rebooking under the accepted revisit rules.
The schedule change, original visit and new booking remain linked; the revisit charge decision is evidenced.
Worked operating scenarios
Review session dates, resource assignments and slot rules before publishing corrected availability.
Check the originating visit, valid period and applicable service charge; keep the decision linked to the booking.
Delivery boundary
Access links a person to a care service. Public booking channels, patient communications and external identity or insurance services require selected and accepted connections.
Registration, scheduling, encounter access and queues; patient portal and family communication scope is separately verified. Publish availability: Configure practitioner or location resources, session dates, opening hours and slot rules. Link services and approved booking permissions to the resource. Register & book: Identify the patient, review contact and identifier information and book the intended service. Preserve referral and payer details where the selected care and revenue workflow requires them. Arrive & route: Record arrival and queue information, open or link the encounter and direct the person to the responsible clinic or department. Confirm the next responsibility rather than leaving a booking without a care destination. Reschedule & follow up: Record completion, cancellation or missed attendance, then arrange an appropriate follow-up. Apply the configured revisit and charging policy using the selected billing workflow.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Departments (departments.csv); Rooms, wards and beds (locations.csv); Doctors & operational clinics (doctors.csv); Doctor schedules · every department (doctor_schedules.csv); Services & department catalogue (services.csv); Clinical workflow configuration (clinical_workflows.csv); Function settings · scheduling closures (product_settings.csv); Acceptance tests (uat_cases.csv). Each file’s field guide identifies whether it imports setup records or documents a migration/decision.
Explore the detailsOverlapping resource schedules Review session dates, resource assignments and slot rules before publishing corrected availability. Patient returns under a revisit rule Check the originating visit, valid period and applicable service charge; keep the decision linked to the booking.
Explore the detailsAccess links a person to a care service. Public booking channels, patient communications and external identity or insurance services require selected and accepted connections.
Explore the details