Hospitals

Care delivered. Revenue followed.

END-TO-END WORKFLOW CASE

The case, from start to finish.

Revenue teams follow service activity through billing, payer responses and reconciliation.

6connected steps

The situation

A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.

What MANSOQ connects

Revenue follow-up starts with the services actually recorded in the encounter.

The people involvedAccess & coordinationDepartment teamRevenue teamFinance teamNursing team

The complete journey

  1. Establish financial responsibility

    Access & coordination

    Record the patient, encounter and payer or self-pay context before financial follow-up.

    Encounter · Payer · Patient account
  2. Capture delivered activity

    Department team

    Link recorded departmental and care services to accountable encounter charges.

    Service activity · Charge reference
  3. Review prices and contribution

    Revenue team

    Check the agreed tariffs and patient contribution against the recorded services and coverage.

    Tariff · Coverage · Contribution
  4. Issue the invoice

    Finance team

    Review the invoice and use the selected ZATCA exchange scope where configured and activated.

    Invoice · E-invoice response
  5. Allocate payments

    Finance team

    Match recorded payments or payer financial responses to the relevant account and invoice.

    Payment · Allocation · Balance
  6. Resolve the remaining balance

    Revenue team

    Assign unresolved differences for review and record the reconciliation decision and next action.

    Difference · Owner · Reconciliation

The factors that make it work

Starting information

Encounter · Payer · Patient account

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 disputed charge

A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.

Responsible team · Finance team

An incomplete handover

Keep missing notes or results attached to the encounter. The receiving team identifies the responsible service and records the follow-up.

Responsible team · Nursing team

A service or account discrepancy

Return the disputed item to its source activity. Review the charge or record correction with the responsible team before financial closure.

Responsible team · Finance team

Scope and delivery boundaries

MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
Revenue Cycle ManagementNative operation · Agreed connectionConfirm deployment scope
Billing & FinanceNative operation · Agreed connectionConfirm deployment scope
ClaimsNative operation · Agreed connectionConfirm deployment scope
ReconciliationNative operation · Agreed connectionConfirm deployment scope
Tariffs & Price ListsNative operation · Agreed connectionConfirm deployment scope
Benefits & Cost SharingNative operation · Agreed connectionConfirm deployment scope
Charge CaptureNative operation · Agreed connectionConfirm deployment scope
ZATCA E-invoicingNative operation · Agreed connectionConfirm deployment scope
EligibilityNative operation · Agreed connectionConfirm deployment scope
PreauthorizationNative operation · Agreed connectionConfirm deployment scope
Payer ContractsNative operation · Agreed connectionConfirm deployment scope
NetworksNative operation · Agreed connectionConfirm deployment scope
Denials & ResubmissionNative operation · Agreed connectionConfirm deployment scope
RemittanceNative 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.

Operational illustration based on documented capabilities; not a named customer deployment or measured outcome.

Configure this solution

Your questions, answered.

Is this a customer result or an operational illustration?

This is an illustrative hospitals workflow, not a named deployment or a measured outcome. A hospital encounter includes ward care, departmental services and patient payments. Finance needs to explain every charge and remaining balance.

Explore the details
What must be complete before this journey is accepted?

Every reviewed charge has a care-activity reference. Payments and outstanding balances have clear allocation. Financial differences have a responsible next action. A disputed charge returns to its service reference for review; a corrected financial record keeps the original encounter trace.

Explore the details
Explore all frequently asked questions