A clear financial story behind every episode of care.
Connect services, charges, invoices and reconciliation without losing the context of the patient's journey.
Explore the story
Planned core Medrella workflows, to be built from scratch using Schedula as the foundation. Availability requires development and demonstrated acceptance.
What this workflow connects.
The scope below guides discovery and demonstration. The adopted version and local configuration determine availability.
- 01
Service catalogues, prices and patient invoices
- 02
Clinical activity and charge capture
- 03
Receipts, adjustments, refunds and review
- 04
Packages and payer-specific commercial rules
- 05
Receivables and reconciliation with accounts
Revenue work begins before the invoice
The final bill is the visible result of many earlier decisions: patient category, service selection, package rules, payer arrangements and the recording of completed work. When those inputs are disconnected, billing teams become the last line of manual reconciliation.
Medrella's financial direction is to develop connected hospital activity and financial records so that services and transactions can be understood together. The aim is a dependable account of what happened and how it was charged. It is not a promise of automatic revenue improvement or a replacement for the hospital's financial policies.
Separate clinical events from financial events
An order, a completed service, an invoice and a payment are different events.
Treating them as one creates confusion when care changes. A cancelled test may need no charge, a reversed charge or a refund depending on the stage reached. A package may include some services and exclude others. These rules need to be explicit and approved by the appropriate owners. The implementation should map the events that create financial entries and the evidence used to reconcile them. Staff should be able to explain a charge without reconstructing the entire patient journey from paper.
Make exceptions manageable for the team
Deposits, credit arrangements, split payment responsibilities, discounts and returns are part of routine hospital finance. A useful workflow records who authorised an adjustment and why, while keeping the original transaction traceable.
Patient-facing explanations should be understandable and consistent with the approved tariff. Reception, billing, finance and clinical staff need different views of the same episode. Giving every user unrestricted access is not a solution to coordination. Design the permissions and escalation route alongside the transaction flow, including how the team handles an unresolved discrepancy when the patient is preparing to leave.
Connect receivables to operational reality
An outstanding balance may represent patient payment, insurer settlement or a contractual adjustment still under review. Those categories should not be mixed into a single number without context.
Financial reporting needs agreed definitions, posting rules and reconciliation with the ledger. Integration with external payment or insurer systems requires explicit handling of delayed responses, duplicates and failed updates. The first rollout should prove a bounded billing journey before adding complex packages or advanced revenue analytics. Planned AI may help identify incomplete documentation or prepare summaries, but authoritative amounts and approvals remain deterministic business processes.
Evaluate the cases that create rework
Bring a normal outpatient invoice, an inpatient discharge, a package exception, a refund and an insurance-related balance into the demonstration. Trace each from the underlying service through approval and reconciliation.
Ask whether the responsible person can explain the state without relying on a private spreadsheet. Review audit history and the handling of corrected transactions. Define measures such as unresolved billing items and reconciliation time from your own baseline. The foundation provides accounting and transaction capabilities; hospital-specific tariffs, integrations and policies require configuration and acceptance testing before they are represented as ready for daily use.
Connected thinking.
What would more time
for care make possible?
Let's explore it together