Departments
Connect medication requests, dispensing and stock.
Pharmacy
Create the medication request with the encounter, product, dose, route, frequency and duration. Keep allergy and current medication context available for professional review.
Review the prescription in the pharmacy queue, confirm the item and quantity and choose the appropriate stock lot. Record any substitution through the authorized process rather than silently changing the prescription.
Record prepared and handed-over medication, quantity, days supply and instructions. Link the dispense record to the patient, location, authorizing request and applicable charge.
Review outstanding prescriptions, completed dispensing and inventory movements. Handle returns and corrections through the approved stock and finance processes; inpatient administration remains a separate clinical record.
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 |
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 | — |
Products, lots and location inventory balances
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: Inventory & medication items · Rooms, wards and beds
| Column | Required | Format | Example |
|---|---|---|---|
Facility numberfacility | Yes | integer 1–1000 | 1 |
Item codeitem_code | Yes | text | EXAMPLE-ITEM-001 |
Storage locationlocation | Yes | text | Example Room |
Lot numberlot_number | Yes | text | EXAMPLE-LOT-001 |
Expiry dateexpiry_date | Yes | YYYY-MM-DD | 2027-10-09 |
Opening quantityquantity | Yes | text | 10 |
Unit purchase pricepurchase_price | Yes | text | 1.50 |
Device register, location and department assignment
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 |
|---|---|---|---|
Unique asset codeasset_code | Yes | text | EXAMPLE-LAB-001 |
Facility numberfacility | Yes | integer 1–1000 | 1 |
Departmentdepartment | Yes | text | Example Department |
Locationlocation | Yes | text | Example Room |
Device namename | Yes | text | Training laboratory analyser |
Manufacturermanufacturer | Yes | text | Example manufacturer |
Modelmodel | Yes | text | EXAMPLE-MODEL |
Serial numberserial_number | Yes | text | EXAMPLE-SERIAL |
Product / department purposecare_type | Yes | text | laboratory |
Interface protocol and versionprotocol | Optional | text | TO-CONFIRM |
Maintenance duemaintenance_due | Optional | 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 |
Define services and approved code mappings before orders, tariffs and interfaces.
Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.
Load / review first: Departments
| 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 | خدمة تدريبية |
Department codedepartment_code | Yes | text | EXAMPLE-DEPT-001 |
Unit of serviceunit | Yes | text | TO-CONFIRM |
Code systemcode_system | Yes | text | TO-CONFIRM |
Catalogue releaserelease | Yes | text | TO-CONFIRM |
Approved external mappingexternal_code | Yes | text | TO-CONFIRM |
Effective fromeffective_from | Yes | YYYY-MM-DD | 2026-10-09 |
Pharmacy-approved catalogue. Example records are for training and contain no dose advice.
Upload this preparation file in Account setup → Implementation files & acceptance evidence. It is saved in your account records. Use the secure migration workspace for actual clinical data. Approve the source-to-target mapping and import adapter for the selected release before any load. Run a dry run, reconcile counts and retain the result log.
Load / review first: Service catalogue
| Column | Required | Format | Example |
|---|---|---|---|
Item codeitem_code | Yes | text | EXAMPLE-MED-001 |
Display namename | Yes | text | Training medication only |
Code systemcode_system | Yes | text | TO-CONFIRM |
Approved codecode | Yes | text | TO-CONFIRM |
Strength with unitstrength | Yes | text | TO-CONFIRM |
Dosage formform | Yes | text | TO-CONFIRM |
Stock unitstock_unit | Yes | text | TO-CONFIRM |
Dispense unitdispense_unit | Yes | text | TO-CONFIRM |
Approved unit conversionconversion_factor | Yes | decimal | 1 |
Terminology releaserelease | Yes | text | TO-CONFIRM |
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
A clinician prescribes a medication and the patient receives the reviewed quantity from pharmacy.
The authorized request, dispensed lot, handed-over quantity and stock movement are traceable.
Only part of a prescribed quantity is available and a later return needs stock and financial review.
Requested, dispensed, outstanding and returned quantities remain distinguishable.
Worked operating scenarios
Record the quantity actually dispensed, retain the remaining prescription responsibility and apply approved substitution or replenishment rules.
Follow the quarantine and return policy; reconcile the inventory movement and financial effect without deleting the dispense history.
Delivery boundary
Prescribing, dispensing, administration and stock are linked but separate records. Formulary rules, unit conversions, payer coverage and external dispensers need their own accepted configuration.
Medication requests, dispensing and stock operation beyond prescribing or viewing a medication list. Prescribe: Create the medication request with the encounter, product, dose, route, frequency and duration. Keep allergy and current medication context available for professional review. Verify & prepare: Review the prescription in the pharmacy queue, confirm the item and quantity and choose the appropriate stock lot. Record any substitution through the authorized process rather than silently changing the prescription. Dispense & hand over: Record prepared and handed-over medication, quantity, days supply and instructions. Link the dispense record to the patient, location, authorizing request and applicable charge. Track & reconcile: Review outstanding prescriptions, completed dispensing and inventory movements. Handle returns and corrections through the approved stock and finance processes; inpatient administration remains a separate clinical record.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Inventory & medication items (stock_items.csv); Stock lots & opening quantities (stock_balances.csv); Medication catalogue (medication_catalogue.csv); Clinical workflow configuration (clinical_workflows.csv); Assets, devices & hardware (assets_devices.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 detailsPartial quantity or unavailable stock Record the quantity actually dispensed, retain the remaining prescription responsibility and apply approved substitution or replenishment rules. Expired lot or returned medication Follow the quarantine and return policy; reconcile the inventory movement and financial effect without deleting the dispense history.
Explore the detailsPrescribing, dispensing, administration and stock are linked but separate records. Formulary rules, unit conversions, payer coverage and external dispensers need their own accepted configuration.
Explore the details