CLARENDIS
CLARENDIS
Healthcare & Medical

University Hospital

A university hospital bills tens of thousands of stays and consultations a year — to insurers, to patients, to institutions — under negotiated tariffs and evolving rules. Billing is not a peripheral administrative function: it is a continuous flow touching every department and every procedure.

Project Patient billing and public websitesSector Healthcare & Medical

Context

Clinical and administrative data lived in the establishment’s internal system, sole legitimate holder of the patient record. Any application needing it — to bill a stay, to publish public health information — faced the same choice: duplicate the data, or read it. Duplication created as many competing sources of truth as applications, and every divergence became a billing dispute or erroneous health information. Exchanges with insurers followed their own formats, unlinked to the record justifying them.

Challenge

Billing a medical procedure requires cross-referencing the stay, applicable tariff, patient coverage and insurer rules — without ever blocking a care record for an administrative reason. Care comes before the invoice, and the system must account for that. Sector exchange protocols impose their own framework.

Objectives

  • Build patient billing on internal system data, with no intermediate database.
  • Deliver two public sites, one on vaccination and travel-related risks.
  • Connect all three applications to the internal system in read mode.
  • Guarantee no billing rule interrupts a care pathway.
  • Comply with sector exchange standards for insurer flows.

Billing and both sites read the establishment’s internal system. Clinical and administrative data stay where they belong, and applications draw on them rather than holding a copy. A billed stay and a care record can no longer diverge.

Areas of expertise

Clinical Systems Interoperability
Billing, Quoting & Configurators
Websites, Content & Communities

Similar project in mind?

Our digital directors are at your disposal to discuss your specific challenges.

Get in touch
Share this case study
Skip to main content