A specialty referral
The next specialist receives the shared record and the documented referral context.
Polyclinics
Every specialty. One connected polyclinic.
Bring specialist visits, diagnostics, medication and revenue together without losing the patient’s context.
22Capabilities in the starting scope
4Workflow case studies
360° SOLUTION COVERAGE
Reception & scheduling
Keep each specialty visit connected to registration and encounter access.
MANSOQ IN PRACTICE
See the whole journey at work.
Four complete operational cases. Read each one here.
END-TO-END WORKFLOW CASE
A specialty referral
The next specialist receives the shared record and the documented referral context.
The situation
A patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.
What MANSOQ connects
Different specialties should add to one patient story.
The people involvedTreating clinicianAccess & coordinationFinance teamDepartment teamRevenue team
The complete journey
Document the first consultation
Treating clinicianRecord the assessment and the reason a specialist review is requested.
Assessment · Referral reasonCoordinate the referral
Access & coordinationArrange the receiving specialty appointment against the existing patient identity.
Referral · Specialty · AppointmentReview the shared context
Treating clinicianReview the referring note and relevant available results before documenting the specialist encounter.
Referring note · Results · EncounterConnect specialist requests
Treating clinicianLink the specialist’s orders and prescription to the receiving consultation.
Specialist note · Orders · PrescriptionReturn the care plan
Treating clinicianDocument the specialist assessment and follow-up responsibility for the referring service.
Assessment · Plan · Next serviceReview each service account
Finance teamKeep each encounter’s services and billing distinct while retaining the shared patient context.
Encounter charges · Patient account
The factors that make it work
Starting information
Assessment · Referral reason
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
The referral needs clarification
If the receiving service needs more information, record the missing referral context and return the task to the responsible service.
Responsible team · Treating clinicianAn incomplete referral or department request
Return the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamA charge or payer response needs correction
Review the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Diagnostic work in the care journey
The laboratory handles the order and specimen before the result returns to the clinician.
The situation
A specialty clinic requests a laboratory test. The laboratory processes the work, returns the result and the clinician documents its review.
What MANSOQ connects
The result must return to the patient and the consultation that requested it.
The people involvedTreating clinicianLaboratory teamRevenue teamDepartment team
The complete journey
Create the clinical request
Treating clinicianRecord the requested laboratory service in the correct specialty encounter.
Order · Encounter · Requested serviceReceive the laboratory work
Laboratory teamConfirm the patient, request and supported specimen workflow before processing.
Patient · Request · SpecimenProcess and document
Laboratory teamComplete the selected native laboratory work or agreed LIS exchange.
Laboratory activity · Source systemReturn the available result
Laboratory teamAttach the documented result to its request and patient encounter.
Result · Request referenceRecord clinical review
Treating clinicianReview the result professionally and document the next care action.
Review note · Care actionClose the service loop
Revenue teamReview the delivered service charge while retaining any remaining clinical follow-up.
Service charge · Follow-up
The factors that make it work
Starting information
Order · Encounter · Requested service
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
A specimen needs review
A rejected or incomplete specimen stays connected to the original request, with the laboratory’s documented reason and next responsibility.
Responsible team · Laboratory teamAn incomplete referral or department request
Return the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamA charge or payer response needs correction
Review the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
LaboratoryNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Medication, from request to dispensing
Clinical prescribing connects to pharmacy operation and stock responsibilities.
The situation
A patient leaves a specialist consultation with a prescription. The polyclinic pharmacy reviews, dispenses and records the selected medication work.
What MANSOQ connects
Prescribing, dispensing and stock movement need distinct responsibilities in one connected path.
The people involvedTreating clinicianPharmacy teamDepartment teamFinance teamRevenue team
The complete journey
Document the prescription
Treating clinicianRecord the clinician’s prescription against the specialty encounter.
Prescription · Clinician · EncounterReceive the pharmacy work
Pharmacy teamVerify the patient and prescription context within the selected pharmacy scope.
Patient · Prescription referenceReview the medication request
Pharmacy teamDocument the pharmacist’s review and any clarification needed from the prescriber.
Pharmacy review · ClarificationRecord the dispensing step
Pharmacy teamRecord the agreed dispensing activity against the prescription and patient.
Dispensing record · PrescriptionConnect stock responsibility
Department teamLink recorded dispensing to inventory responsibilities where inventory is included.
Dispensing · Stock movementComplete the account and follow-up
Finance teamReview medication charges and preserve documented follow-up for the care team.
Medication charge · Care follow-up
The factors that make it work
Starting information
Prescription · Clinician · Encounter
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
An unavailable item or unclear prescription
An unavailable item or unclear prescription returns to the responsible pharmacist and prescriber; the software does not choose a substitute treatment.
Responsible team · Pharmacy teamAn incomplete referral or department request
Return the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamA charge or payer response needs correction
Review the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
PharmacyNative operationConfirm deployment scope
InventoryNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
END-TO-END WORKFLOW CASE
Eligibility to reconciliation
Revenue teams follow the visit’s insurance and financial work through the payer response.
The situation
An insured specialty visit includes diagnostics and medication. The revenue team follows coverage, approvals, claims and payment allocation across those services.
What MANSOQ connects
Several departments can contribute to one claim without losing the origin of each service.
The people involvedAccess & coordinationRevenue teamDepartment teamFinance team
The complete journey
Verify coverage
Access & coordinationRecord eligibility and the relevant coverage context for the visit.
Eligibility · Coverage · EncounterFollow service approvals
Revenue teamConnect required preauthorization requests and payer decisions to the requested services.
Service · Authorization · ResponseCapture delivered services
Department teamRecord consultation, diagnostic and pharmacy activity with its encounter reference.
Department activity · Charge referenceReview and submit the claim
Revenue teamReview the claim work items and use the agreed, activated exchange channel.
Claim · Submission · Exchange traceResolve payer responses
Revenue teamAssign rejection reasons for correction, review and documented resubmission where needed.
Response · Reason · ResubmissionReconcile the remittance
Finance teamMatch payer remittance to claim records and assign remaining financial differences.
Remittance · Claim · Difference
The factors that make it work
Starting information
Eligibility · Coverage · Encounter
Responsibility at every step
Each stage identifies the team, the action and the record carried forward.
An agreed operating scope
Confirm the selected capabilities, required companions and external connections during configuration.
Exceptions. A clear next responsibility.
A partially paid claim
A partially paid claim keeps the paid allocation and unresolved lines separate, with a documented reason and follow-up owner.
Responsible team · Finance teamAn incomplete referral or department request
Return the missing information to the referring or requesting team while retaining the original patient and encounter references.
Responsible team · Department teamA charge or payer response needs correction
Review the reason against the delivered service and agreed contract scope. Record the correction and next financial owner.
Responsible team · Revenue teamScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Revenue Cycle ManagementNative operation · Agreed connectionConfirm deployment scope
EligibilityNative operation · Agreed connectionConfirm deployment scope
ClaimsNative operation · Agreed connectionConfirm deployment scope
ReconciliationNative operation · Agreed connectionConfirm deployment scope
PreauthorizationNative operation · Agreed connectionConfirm deployment scope
Charge CaptureNative operation · Agreed connectionConfirm deployment scope
Denials & ResubmissionNative operation · Agreed connectionConfirm deployment scope
RemittanceNative operation · Agreed connectionConfirm deployment scope
Payer ContractsNative operation · Agreed connectionConfirm deployment scope
NetworksNative operation · Agreed connectionConfirm deployment scope
Benefits & Cost SharingNative operation · Agreed connectionConfirm deployment scope
Tariffs & Price ListsNative operation · Agreed connectionConfirm deployment scope
RCM ReportingNative operation · Agreed connectionConfirm deployment scope
External systems, device connections, catalogue licenses and national exchanges are activated only within their agreed delivery scope. The professionals retain clinical decisions.
Make it your polyclinic.
Your solution is already selected. Adjust the services and review your proposal.
SOFTWARE + MANAGED OPERATIONS
A clear plan for every stage.
More capacity. More support. Choose how your care team grows.
Yearly prepayment · 10% off base software only
All prices are SAR before VAT. The setup and migration budget range is indicative; the final price follows the statement of work. Bespoke additions are quoted separately.
Select a feature or capacity label to learn more.
Essential
The essentials to run daily care.
SAR 2,490/ monthYearly: 10% off base software only; managed operations are not discounted.
50
1 site included
Your care foundation
Premium
For growthConnect your team and automate more.
SAR 4,990/ monthYearly: 10% off base software only; managed operations are not discounted.
150
1 site included
Everything in Essential, plus
Diamond
More controlManaged follow-through. Your data, your choice.
SAR 8,990/ monthYearly: 10% off base software only; managed operations are not discounted.
250
1 site included
Everything in Premium, plus
Enterprise
Built around your organisation.
Tailored to youA proposal from our sales team
550+
Custom capacity & sites
Everything in Diamond, plus
Diamond & Enterprise: keep the database and files in your own cloud, Spaces or server-hosted storage. Deployment and recovery are verified before launch.
RCM RaaS is additional to your subscription and is billed on approved eligible cleared collections. Enterprise requires an approved exact rate within its published range.
Included in every plan
Care workflows · secure access · audit trails · backups · patient and family communication · required NPHIES and ZATCA workflows · onboarding and support
Required NPHIES and ZATCA workflows are included in every plan. Live transmission is activated after your organisation’s NPHIES and ZATCA credentials and external acceptance.
Compare service scope, fees & additions
| Included / additional | Essential | Premium | Diamond | Enterprise |
|---|---|---|---|---|
| Base software / month | SAR 1,490 | SAR 2,790 | SAR 4,490 | Agreed with sales |
| Managed operations / month | SAR 1,000 | SAR 2,200 | SAR 4,500 | Agreed with sales |
| Extra care unit / month | SAR 150 | SAR 200 | SAR 250 | Agreed with sales |
| Extra site / month | SAR 1,500 | SAR 2,000 | SAR 3,000 | Agreed with sales |
| Extra managed hour | SAR 180 | SAR 180 | SAR 180 | Agreed with sales |
| Setup & migration budget (indicative) | SAR 5,000–SAR 10,000 | SAR 8,000–SAR 18,000 | SAR 15,000–SAR 30,000 | Agreed with sales |
| Your own database & storage | MANSOQ-managed storage | MANSOQ-managed storage | Available · scope agreed | Available · scope agreed |
VAT is additional where applicable. Annual prepayment discounts base software only. Customer infrastructure and bespoke integrations follow an agreed statement of work. The setup and migration budget range is indicative; the final price follows the statement of work.
Optional additions · quoted to your scope
AI documentation assistant
Opt-in; clinician review, consent, intended-use and supplier review required.
Branded patient / family app
Branding, distribution and app maintenance scoped separately.
Additional or bespoke interfaces
Each connector has an acceptance specification and supplier cost.
Devices, telepresence & connectivity
Customer-owned devices or separately quoted hardware, carrier and vendor fees.
On-site training
Travel, delivery days and attendance agreed in advance.
Dedicated hosting & continuity design
Architecture, recovery objectives and infrastructure require an Enterprise proposal.
RCM RaaS managed revenue service
The selected plan’s configured percentage of eligible cleared collections, additional to the package subscription. Enterprise requires an approved exact rate within its configured range and an accepted operating scope.
Messaging & video usage
Third-party usage budget and consent agreed; no unlimited carrier charges.
Responsibility and service boundaries
Customer supplies licensed clinicians, clinical decisions, escalation coverage, medical governance and source-system permissions. MANSOQ supplies the contracted technology and non-clinical operations.
Routine service window and commissioning
Routine managed operations: Sunday–Thursday, 08:00–18:00 Arabia Standard Time, excluding agreed holidays. Critical technical incident cover is separately commissioned; operational hours are not 24/7 clinical coverage.
Included hours cover configuration, specialist review and agreed queue work; recorded in 15-minute increments. Review preparation counts. Additional care units and sites do not increase the included hours or interfaces. No rollover unless agreed. Notify at 80% / 100%; obtain approval before extra work. Product defects and critical support do not consume this allowance. Standard maintained interfaces exclude applicable national foundation connectors; bespoke connector build and vendor fees are separately scoped.
Prices describe the commercial scope. Before clinical launch, agree the statement of work, hosting / data terms, accepted interfaces, migration reconciliation, trained users, downtime and escalation tests, and commissioned support SLA. Availability and response targets require signed acceptance.