Skip to main content
GullySystem
Healthcare

Workflow and Approvals for Diagnostic centres

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A study moves from technician to radiologist to sign-off before the report is released. Addenda need a second approval. A report held for a missing prior film is shown as waiting.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
Diagnostic centres

How the business operates.

A centre with an X-ray room, two ultrasound rooms and a CT scanner handles walk-ins, booked scans, hospital referrals and health check packages through one front desk. That desk is the bottleneck.

Slot booking by machine and room

Book ultrasound, X-ray, CT and MRI slots against the room that does them, and send the preparation a scan needs with the booking.

Study status from scan to dispatch

Follow each study through booked, scanned, in draft, signed and delivered, with views by room and radiologist.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Patient registration and visits. Register each patient once, found by phone number or ID, with every visit, prescription, referrer and report on the same record.
  • Slot booking by machine. Book ultrasound, X-ray, CT, MRI and other rooms by slot. The preparation each scan needs is printed or sent at booking, so fasting and test values are asked for in advance.
  • Rate lists and health packages. Keep separate rate lists for walk-ins, hospitals, corporates and camps. Group scans and tests into health check packages.
  • Billing, dues and refunds. Bill each visit from the right rate list, take part payments, record every discount with the person who approved it, and refund a cancelled scan with the reason written down.

Operational bottlenecks to check

Every machine keeps its own diary

Ultrasound uses a register, CT uses a sheet, and the desk cannot see either while a caller waits on the line. Double bookings follow.

Preparation is missed

A patient arrives for an abdomen scan after breakfast, or for a contrast study without a recent creatinine value. The slot is lost.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Booking

    A patient or a referring doctor books by phone, on WhatsApp or at the desk. The slot goes on a machine and room, and the preparation instructions go with it.

  2. 2. Registration and billing

    The desk registers the patient, notes the referrer and the prescription, and bills from the rate list that applies. Cash, bank transfer, card or a credit account settles the visit.

  3. 3. Scan

    The technician sees the room’s worklist, checks preparation and consent, and marks the study scanned. Images go to the centre’s PACS or viewer.

  4. 4. Reporting

    The radiologist opens the study, writes findings from a template and signs. A critical finding is flagged so the referring doctor gets a call.

  5. 5. Delivery

    Signed reports are printed with films or a CD, or sent as a PDF. Messages go through the centre’s own WhatsApp Business account where that is set up.

  6. 6. Month end

    Credit visits roll into statements for each hospital and corporate. The owner sees studies by machine, modality and referrer.

Industry reports to connect with

  • Studies by modality, machine and day
  • Reports awaiting sign-off, by radiologist
  • Visits by referring doctor and hospital
  • Credit dues by hospital and corporate

Questions before implementation.

When should diagnostic centres consider workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements