Care workflows
Support continuity across visits and the people providing care.
Home & Palliative Care
Establish the person’s care context, consent and caregiver contacts. Define the service zone, multidisciplinary team and approved home or palliative-care plan with escalation responsibilities.
Assign the practitioner and visit time, accounting for service area and travel constraints. Confirm required equipment, medication and the information the visiting team needs.
Record the encounter, observations, symptom review and delivered care. Keep medication and service requests with the current plan and document the caregiver discussion and next responsibilities.
Plan the next visit or referral and hand over unresolved needs to the multidisciplinary team. Reconcile supplied items and delivered services through inventory and billing where selected.
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 |
Set working days, hours, patient identifiers and billing preferences. Your app starts with an empty patient database.
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 |
|---|---|---|---|
Working daysworking_days | Yes | sun-thu / mon-fri / every-day | sun-thu |
Opening time (HH:MM)opening_time | Yes | text | 08:00 |
Closing time (HH:MM)closing_time | Yes | text | 17:00 |
Appointment duration (minutes)slot_minutes | Yes | integer 5–240 | 15 |
Patient record prefixpatient_prefix | Optional | text | EXAMPLE |
Billing currencybilling_currency | Yes | SAR | SAR |
Default languagelanguage | Yes | ar / en | en |
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 |
Product knowledge catalogue
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: Facilities
| Column | Required | Format | Example |
|---|---|---|---|
Unique item codeitem_code | Yes | text | EXAMPLE-ITEM-001 |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Item namename | Yes | text | Training consumable |
Typeproduct_type | Yes | medication / consumable / nutritional_product | consumable |
UCUM unit codeunit_code | Yes | text | 1 |
Terminology systemcode_system | Optional | text | — |
External codeexternal_code | Optional | text | — |
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 |
Plan resource availability, overlap rules, closures and time zone 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: Operating preferences · Rooms, wards and beds · Planned team
| Column | Required | Format | Example |
|---|---|---|---|
Schedule IDschedule_id | Yes | text | EXAMPLE-SCH-001 |
Facility numberfacility_number | Yes | integer | 1 |
Departmentdepartment_name | Yes | text | Example Department |
Staff or roomresource_name | Yes | text | Example Room |
Weekdayweekday | Yes | sun / mon / tue / wed / thu / fri / sat | sun |
Start timestart_time | Yes | HH:MM | 08:00 |
End timeend_time | Yes | HH:MM | 17:00 |
Slot durationslot_minutes | Yes | integer minutes | 15 |
Time zonetimezone | Yes | IANA time zone | Asia/Riyadh |
Scheduling 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
A multidisciplinary team delivers a planned visit and updates the continuing care plan.
Visit notes, plan changes, resources and the next visit owner remain connected to the person.
A patient is unavailable for a visit and a later caregiver contact reports a change in symptoms.
Cancelled service, reported symptoms and subsequent clinical actions are recorded as distinct events.
Worked operating scenarios
Record the disposition, contact the care coordinator and review rescheduling and any time-sensitive care responsibility.
Use the approved clinical contact and referral pathway; document the assessment, advice and receiving service.
Delivery boundary
Home-care documentation, scheduling, stock and remote support are selected separately. Offline work, remote devices and route optimization must be explicitly confirmed for the chosen deployment.
Visits, care plans and multidisciplinary documentation with verified palliative workflows. Mobile, offline and family channels are distinct scope. Enroll & plan: Establish the person’s care context, consent and caregiver contacts. Define the service zone, multidisciplinary team and approved home or palliative-care plan with escalation responsibilities. Schedule the visit: Assign the practitioner and visit time, accounting for service area and travel constraints. Confirm required equipment, medication and the information the visiting team needs. Deliver & document: Record the encounter, observations, symptom review and delivered care. Keep medication and service requests with the current plan and document the caregiver discussion and next responsibilities. Continue care: Plan the next visit or referral and hand over unresolved needs to the multidisciplinary team. Reconcile supplied items and delivered services through inventory and billing where selected.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Doctors & operational clinics (doctors.csv); Scheduling configuration (scheduling.csv); Services & department catalogue (services.csv); Clinical workflow configuration (clinical_workflows.csv); Inventory & medication items (stock_items.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 detailsVisit cancelled or patient unavailable Record the disposition, contact the care coordinator and review rescheduling and any time-sensitive care responsibility. Symptoms require escalation Use the approved clinical contact and referral pathway; document the assessment, advice and receiving service.
Explore the detailsHome-care documentation, scheduling, stock and remote support are selected separately. Offline work, remote devices and route optimization must be explicitly confirmed for the chosen deployment.
Explore the details