The first visit
Reception, the clinician and the billing team share one encounter from arrival to payment.
Clinics
Your clinic. Every visit connected.
From the first appointment to follow-up and payment, bring the whole visit into one clinical and financial context.
19Capabilities in the starting scope
4Workflow case studies
360° SOLUTION COVERAGE
Appointments & arrival
Connect scheduling, registration, queues and the encounter.
MANSOQ IN PRACTICE
See the whole journey at work.
Four complete operational cases. Read each one here.
END-TO-END WORKFLOW CASE
The first visit
Reception, the clinician and the billing team share one encounter from arrival to payment.
The situation
A new patient books a consultation, arrives at the clinic, receives a documented care plan and completes the visit’s financial steps.
What MANSOQ connects
Reception, consultation and payment should describe the same visit.
The people involvedAccess & coordinationTreating clinicianFinance team
The complete journey
Arrange the appointment
Access & coordinationConnect the appointment to the selected service and patient identity.
Appointment · Service · IdentityRegister the arrival
Access & coordinationConfirm the shared patient record and establish the outpatient encounter and financial context.
Patient record · Encounter · PayerDocument the consultation
Treating clinicianReview the available history and record the assessment and agreed care plan.
History · Clinical note · Care planConnect requests and medication
Treating clinicianAttach the clinician’s orders and prescriptions to the consultation context.
Orders · Prescription · EncounterComplete visit billing
Finance teamReview recorded services, patient contribution and payment against the encounter.
Services · Invoice · PaymentArrange the next visit
Access & coordinationRecord the next appointment or follow-up responsibility with the consultation’s care context.
Follow-up · Responsible service
The factors that make it work
Starting information
Appointment · Service · Identity
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 existing patient record
If the patient already has a record, verify the identity before continuing so the new encounter follows the correct history.
Responsible team · Access & coordinationMissing history or pending results
Identify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianA changed appointment or service
Update the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Patient AccessNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
Orders, Results & MedicationNative 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
A follow-up with context
A returning patient’s previous notes and relevant results inform the next consultation.
The situation
A returning patient has a follow-up consultation after earlier testing. The clinician needs the prior plan and available results beside today’s record.
What MANSOQ connects
A follow-up should build on the previous visit instead of restarting the story.
The people involvedAccess & coordinationTreating clinicianFinance team
The complete journey
Identify the returning patient
Access & coordinationConfirm the patient and connect the new appointment to the existing record.
Identity · Appointment · Prior encountersReview the earlier plan
Treating clinicianReview the prior consultation and its recorded follow-up reason.
Previous note · Follow-up reasonReview available results
Treating clinicianReview relevant available results and record their interpretation in today’s consultation.
Results · Review noteUpdate the care plan
Treating clinicianDocument the current assessment and the clinician’s changes to orders or medication.
Assessment · Updated plan · OrdersComplete the encounter account
Finance teamLink today’s recorded service and payment responsibility to the follow-up encounter.
Follow-up service · AccountSet the next responsibility
Access & coordinationRecord the next appointment, referral or documented follow-up action.
Next appointment · Referral · Owner
The factors that make it work
Starting information
Identity · Appointment · Prior encounters
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 result has not arrived
When a result has not arrived, record the pending item and the responsible follow-up; do not present it as reviewed.
Responsible team · Treating clinicianMissing history or pending results
Identify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianA changed appointment or service
Update the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm 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
From order to review
The care team links a clinical order and the available result back to the encounter.
The situation
During a consultation, a clinician requests a test and prescribes medication. Each request needs an owner and a return path to the visit.
What MANSOQ connects
A request is useful when the result or medication step returns to the care context.
The people involvedTreating clinicianDepartment teamFinance teamIntegration & IT teamAccess & coordination
The complete journey
Open the consultation context
Treating clinicianReview the patient record and the current consultation before creating a request.
Patient · ConsultationRecord the diagnostic order
Treating clinicianConnect the requested service and documented clinical context to the encounter.
Order · Service · Clinical contextRecord the prescription
Treating clinicianDocument the clinician’s prescription and its encounter reference.
Prescription · Encounter referenceRoute the departmental work
Department teamUse the selected native department or agreed external connection to carry the request.
Request · Department or interfaceReview the returned information
Treating clinicianReview available results in the encounter and document the next clinical action.
Result · Review · Next actionComplete follow-up and billing
Finance teamReview delivered service charges while the care team records remaining follow-up responsibilities.
Charges · Pending work · Follow-up
The factors that make it work
Starting information
Patient · Consultation
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 request crosses a system boundary
External diagnostics and dispensing require an agreed interface or documented handover; an order alone does not imply a native laboratory or pharmacy.
Responsible team · Integration & IT teamMissing history or pending results
Identify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianA changed appointment or service
Update the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationScope and delivery boundaries
MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Outpatient CareNative operationConfirm deployment scope
Orders, Results & MedicationNative operationConfirm deployment scope
Clinical Documentation & Care PlanningNative operationConfirm deployment scope
System & Device InterfacesNative operation · Agreed connectionConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm 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
An insured visit, followed through
The revenue team traces coverage and approvals through the claim and payer response.
The situation
An insured patient attends a clinic. Reception verifies coverage, the revenue team follows the required approval and the claim is reconciled after the visit.
What MANSOQ connects
Care activity, payer decisions and the patient’s contribution must remain traceable together.
The people involvedAccess & coordinationRevenue teamTreating clinicianFinance team
The complete journey
Verify eligibility
Access & coordinationCheck coverage and retain the response with the patient and encounter context.
Coverage · Eligibility responseFollow the required approval
Revenue teamRecord the preauthorization request, payer response and next responsibility where required.
Request · Approval status · OwnerDocument the delivered consultation
Treating clinicianRecord the consultation and services in the same outpatient encounter.
Clinical note · Service recordReview charge and contribution
Revenue teamApply the agreed contract and tariff context to reviewed charges and patient liability.
Tariff · Charge · Patient contributionFollow the claim response
Revenue teamReview the claim work queue and payer response, assigning any correction to its owner.
Claim · Response · CorrectionReconcile the financial response
Finance teamMatch remittance and payments to the claim and encounter; identify unresolved differences.
Remittance · Allocation · Reconciliation
The factors that make it work
Starting information
Coverage · Eligibility response
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 rejected claim
A rejection remains a work item with its reason, correction and resubmission history. NPHIES exchange is used only in the selected, activated scope.
Responsible team · Revenue teamMissing history or pending results
Identify the missing source and record who follows it up. The clinician decides how the available context affects the consultation.
Responsible team · Treating clinicianA changed appointment or service
Update the encounter and next appointment responsibility; review any affected service charges against the documented activity.
Responsible team · Access & coordinationScope 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
Payer ContractsNative operation · Agreed connectionConfirm deployment scope
Tariffs & Price ListsNative operation · Agreed connectionConfirm deployment scope
Denials & ResubmissionNative operation · Agreed connectionConfirm deployment scope
RemittanceNative operation · Agreed connectionConfirm deployment scope
NetworksNative operation · Agreed connectionConfirm deployment scope
Benefits & Cost SharingNative operation · Agreed connectionConfirm deployment scope
Charge CaptureNative 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 clinic.
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 990/ 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 1,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 3,490/ 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 690 | SAR 1,090 | SAR 1,690 | Agreed with sales |
| Managed operations / month | SAR 300 | SAR 900 | SAR 1,800 | Agreed with sales |
| Extra care unit / month | SAR 150 | SAR 200 | SAR 250 | Agreed with sales |
| Extra site / month | SAR 400 | SAR 600 | SAR 900 | Agreed with sales |
| Extra managed hour | SAR 180 | SAR 180 | SAR 180 | Agreed with sales |
| Setup & migration budget (indicative) | SAR 1,500–SAR 3,000 | SAR 2,500–SAR 5,000 | SAR 4,000–SAR 8,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.