Polyclinics

From a service record to a traceable coding decision.

END-TO-END WORKFLOW CASE

The case, from start to finish.

Connect supported SBS mapping, provider services and separate payer tariff responsibilities.

6connected steps

The situation

A polyclinic introduces a service into its billing catalogue. Coding and revenue teams must agree the supported code mapping and its payer price rules.

What MANSOQ connects

A service code and a payer tariff answer different questions.

The people involvedDepartment teamRevenue teamFinance team

The complete journey

  1. Identify the provider service

    Department team

    Document the service description and operational department.

    Service · Description · Department
  2. Confirm the catalogue scope

    Revenue team

    Confirm the supported SBS release and permitted catalogue usage.

    Release · Catalogue scope · Rights
  3. Review the service mapping

    Revenue team

    Review the proposed provider-to-code mapping and record the responsible decision.

    Provider service · Code · Review
  4. Define payer tariff context

    Finance team

    Record the separate contract price and tariff rules for the service.

    Contract · Tariff · Price
  5. Validate an encounter example

    Revenue team

    Review a selected service charge against its mapping and agreed tariff.

    Charge · Mapping · Tariff version
  6. Record approved use and changes

    Revenue team

    Retain the reviewed mapping and assign responsibility for later catalogue changes.

    Approved mapping · Change responsibility

The factors that make it work

Starting information

Service · Description · Department

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 code mapping is uncertain

An uncertain mapping is held for responsible coding review. Catalogue tooling does not grant licensing rights or define payer reimbursement automatically.

Responsible team · Revenue team

An 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 team

A 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 team

Scope and delivery boundaries

MANSOQ CoreNative operation · Agreed connectionConfirm deployment scope
SBS Specific Mapping ToolingNative operation · Agreed connectionConfirm deployment scope
Full Supported SBS Catalogue ToolingNative operation · Agreed connectionConfirm deployment scope
Tariffs & Price ListsNative operation · Agreed connectionConfirm deployment scope
Revenue Cycle ManagementNative 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
Benefits & Cost SharingNative operation · Agreed connectionConfirm deployment scope
Charge CaptureNative operation · Agreed connectionConfirm deployment scope
ClaimsNative operation · Agreed connectionConfirm deployment scope
Denials & ResubmissionNative operation · Agreed connectionConfirm deployment scope
RemittanceNative operation · Agreed connectionConfirm deployment scope
ReconciliationNative 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 polyclinics workflow, not a named deployment or a measured outcome. A polyclinic introduces a service into its billing catalogue. Coding and revenue teams must agree the supported code mapping and its payer price rules.

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

Service-to-code mapping has a recorded review decision. Payer prices remain distinct from service classification. Later changes have a catalogue and tariff reference. An uncertain mapping is held for responsible coding review. Catalogue tooling does not grant licensing rights or define payer reimbursement automatically.

Explore the details
Explore all frequently asked questions