Since 2010

The software healthcare facilities have run on for sixteen years

Admissions, care records, staff scheduling, billing, mobile apps. A complete business system, being migrated screen by screen to modern technology without stopping the work.

Gextra
16 years

of continuous development and operation, by the same team

30

healthcare facilities using it every day

13

applications making up the system: admissions, scheduling, portals, mobile, coding

The context

Gextra runs healthcare facilities day to day: admissions, pre-admissions, care records, staff scheduling, billing, exchanges with patient referral platforms. It is not a tool you open on Monday morning; it is the one that stops the facility functioning when it goes down. It was written sixteen years ago, and its interface technology aged faster than its business rules — which are still correct, and often written down nowhere but in the code.

What we did

  • check_circleContinuous development of the business software since 2010: admissions, records, scheduling, billing, portals for families and doctors.
  • check_circleScreen-by-screen migration to a modern interface, with both versions living behind the same address. The old version is the reference: it serves as the oracle, oddities included, which are almost always a forgotten business rule.
  • check_circleIntegrations across the healthcare ecosystem: patient referral platforms, care software, exchanges with public bodies. Every feed logged, every interruption alerted.
  • check_circleMobile applications published on both stores, with tracking of the deadlines Apple and Google impose every year.
  • check_circleHosting, backups and monitoring, with the requirements specific to health data — the most demanding regime there is.
  • check_circleRegular access audits on API endpoints: what must be authenticated is, and the accepted exceptions are written down and dated rather than discovered by accident.

What changed

  • trending_upSixteen years of continuity, with no takeover by a supplier who would have had to relearn everything. The business rules were never lost.
  • trending_upThe migration advances without ever interrupting the work: teams move over screen by screen, and rollback stays possible at every step.
  • trending_upKnown compliance gaps are written in a dated register, with their deadline. A documented gap is defensible; a forgotten one is not.
  • trending_upThe facility has one point of contact for the software, the servers, the mobile apps and the integrations. Nobody passes the blame on an outage day.

Let's talk about your project

Thirty minutes is enough to tell whether we are the right fit. We reply within 48 hours, and we say no when it is not for us.