MANSOQ Core
One person. Shared context. Care and revenue, connected.
CONNECTED ACROSS TEAMS
Recognize the person
Understand the context
Carry the next step
Connect financial follow-up
Illustrative journey across your selected care and revenue capabilities.
YOUR PLATFORM, CONNECTED
Add the workflows, departments and extensions your teams need.
Core provides the foundation. A complete care service adds its care workflow and required clinical components, within your agreed data and deployment scope.
MANSOQ Core
Register the person with the identifiers your organization uses. Review a possible duplicate before creating another patient; preserve the original identifiers when a source system is retained.
Define legal organizations, facilities, departments and locations. Assign each operational record to its facility and keep cross-site sharing within the approved boundary.
Assign named users to roles and facilities, then verify their read, create and update permissions. Test a restricted user as well as an administrator before accepting the setup.
Link encounters, notes, observations, requests and attachments to the correct person. Departmental and revenue modules use this context through their selected capabilities and permissions.
Review record changes and responsible users, maintain shared configuration and confirm release-specific retention, backup and support arrangements. Re-test affected permissions when adding a site or module.
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 |
Choose a unique address. Eligible packages can attach a domain after ownership and secure connection checks.
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 |
|---|---|---|---|
App address, for example: my-clinicslug | Yes | text | example-clinic |
Custom domain (optional)custom_domain | Optional | text | — |
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 |
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
A registered patient visits a clinic and then needs laboratory work at the same facility.
The patient and encounter references remain consistent across the request, specimen and report; role-access checks pass.
An organization adds another site while keeping local administration and approved sharing boundaries.
Both allowed and denied access are evidenced, and each record retains its owning facility.
Worked operating scenarios
Compare source identifiers and demographics; route the match to an authorized reviewer. Approve any correction or merge through the supported workflow.
Review the old and new assignments, remove obsolete access and test both allowed and denied actions.
Delivery boundary
Core supplies shared identity and context. Cross-tenant data exchange, external patient matching and enterprise sharing require a separately accepted interface and governance scope.
Shared patient identity and record, administrative and clinical context, access, audit and common configuration within an agreed data boundary. Identify: Register the person with the identifiers your organization uses. Review a possible duplicate before creating another patient; preserve the original identifiers when a source system is retained. Organize: Define legal organizations, facilities, departments and locations. Assign each operational record to its facility and keep cross-site sharing within the approved boundary. Authorize: Assign named users to roles and facilities, then verify their read, create and update permissions. Test a restricted user as well as an administrator before accepting the setup. Connect context: Link encounters, notes, observations, requests and attachments to the correct person. Departmental and revenue modules use this context through their selected capabilities and permissions. Review & maintain: Review record changes and responsible users, maintain shared configuration and confirm release-specific retention, backup and support arrangements. Re-test affected permissions when adding a site or module.
Explore the detailsConfigure the selected release using the account templates, then validate references and preview before import. Required planning and setup files include Your organization (organization.csv); Facilities (facilities.csv); Departments (departments.csv); Rooms, wards and beds (locations.csv); Planned team (staff.csv); Roles & permissions (roles.csv); Users & department access (user_access.csv); Operating preferences (operations.csv); Your app address (domain.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 detailsPossible duplicate patient Compare source identifiers and demographics; route the match to an authorized reviewer. Approve any correction or merge through the supported workflow. User moves to another facility Review the old and new assignments, remove obsolete access and test both allowed and denied actions.
Explore the detailsCore supplies shared identity and context. Cross-tenant data exchange, external patient matching and enterprise sharing require a separately accepted interface and governance scope.
Explore the details