Polyclinics

A specialty referral

END-TO-END WORKFLOW CASE

The case, from start to finish.

The next specialist receives the shared record and the documented referral context.

6connected steps

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

  1. Document the first consultation

    Treating clinician

    Record the assessment and the reason a specialist review is requested.

    Assessment · Referral reason
  2. Coordinate the referral

    Access & coordination

    Arrange the receiving specialty appointment against the existing patient identity.

    Referral · Specialty · Appointment
  3. Review the shared context

    Treating clinician

    Review the referring note and relevant available results before documenting the specialist encounter.

    Referring note · Results · Encounter
  4. Connect specialist requests

    Treating clinician

    Link the specialist’s orders and prescription to the receiving consultation.

    Specialist note · Orders · Prescription
  5. Return the care plan

    Treating clinician

    Document the specialist assessment and follow-up responsibility for the referring service.

    Assessment · Plan · Next service
  6. Review each service account

    Finance team

    Keep 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 clinician

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
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.

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 patient is referred from one specialty to another within a polyclinic. The receiving clinician needs the referral reason, previous notes and available results.

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

A referral with its clinical reason and receiving service. Specialist work adds to the shared patient record. Separate service accounts retain their encounter references. If the receiving service needs more information, record the missing referral context and return the task to the responsible service.

Explore the details
Explore all frequently asked questions