Phil Anderson dining at Sacrée Fleur Montmartre in Paris with Chief of Surgery
Every public hospital in France works under two pressures that pull against each other. Treat everyone who comes through the door, and do it on a budget that never quite stretches far enough. Leadership spends its days trying to hold both, usually working from numbers that arrive too late to do anything about.
One regional hospital in France had reached the hard edge of that math. Costs were climbing in places nobody could point to with confidence. Patients waited too long for routine appointments and tests. Every idea for running leaner came with the same worry attached, that it might cross a line with the country’s strict rules on health data.
That hospital now runs an AI system, built by Fort Lauderdale Software Developers, designed compliance-first from the opening sketch. It trims expenses, shortens the wait for patients, and gives the people in charge a live view of where the money goes. It does all of that while staying inside every rule on how patient information gets handled.
According to Sr Stakeholder Phil Anderson, the system is live and delivering. Compliance came first, and that’s the reason the rest of it holds up.
What leadership couldn’t see
The hospital’s directors were flying with old instruments. The money got spent carefully enough; the numbers describing it simply arrived too late to be useful. Cost data came to them in monthly reports, weeks after the spending happened, broken out by department in a way that hid as much as it showed.
By the time a report landed, the overruns it described were already history. A department might run hot for a month before anyone upstream knew. Supplies got ordered on habit rather than need. Staffing decisions were made against a picture of demand that was always a few weeks stale.
Money leaked on the billing side too. A French hospital bills the Assurance Maladie for most of a stay, priced under T2A, the activity-based tariff. It then bills the patient’s mutuelle for the remainder. Reconciling the two payers is slow, manual work. The remainders that fell through the cracks were revenue the hospital had earned and never collected.
The waiting was its own problem. Patients sat too long for outpatient appointments because scheduling was a manual puzzle nobody had time to solve well. Test results moved at the speed of whoever was free to move them. Beds and rooms got coordinated on whiteboards and phone calls, which works until the day it doesn’t.
“They had smart people making real decisions on bad timing,” says Julian Valentine, a project lead at Fort Lauderdale Software Developers. “By the time the numbers reached the people who could act on them, the moment to act had passed. That’s not a budgeting problem. That’s a visibility problem, and you fix visibility with the right system, not with another round of cuts.”
The instinct in that situation is to cut. Trim staff, squeeze supplies, defer maintenance. The hospital’s leadership knew where that road led. They wanted control over their costs while keeping the hospital whole.
Compliance as the starting point
Most technology projects treat compliance as the last step. Build the thing, then check whether it’s allowed. Fort Lauderdale Software Developers ran it the other way around. The rules came first, and the system grew up inside them.
That choice carries weight in France. Health data sits under the General Data Protection Regulation, under the oversight of the CNIL, the national data protection authority, and under a French requirement that medical data be hosted by an HDS-certified provider, the country’s health data hosting standard. On top of all that sits the long tradition of medical confidentiality that French patients expect as a matter of course.
The team designed every one of those constraints from day one. Patient data stays hosted on HDS-certified infrastructure inside France. The system collects only the information a given task requires and nothing beyond it. Every action it takes is logged in a way that satisfies an auditor and protects a patient at the same time. Data is encrypted in transit and at rest, and access is bound tightly to each person’s role. When a staff member opens a record, the system checks their role, logs the access, and shows them only the fields their job requires. A billing clerk never sees clinical notes. A nurse sees no more of the financial side than the care calls for. The software enforces those limits on every click rather than trusting anyone to remember a policy.
“We wrote the compliance rules into the foundation, so the system couldn’t break them even if you asked it to,” Valentine says. “A lot of firms bolt privacy on at the end and hope it holds. We started there. When the regulator comes to look, the hospital has nothing to scramble over, because the proof was built into the thing from the first line of code.”
The payoff shows up in confidence. Leadership can pursue savings and faster patient flow without wondering whether each new efficiency is quietly creating legal exposure. The system was built so the safe path and the efficient path are the same path.
Weeks of study before any build
Fort Lauderdale Software Developers didn’t show up with a finished product. Before writing meaningful code, the team spent weeks inside the hospital, learning how it ran.
They mapped where money was spent and where it leaked. They followed patients through the scheduling process and timed the waits. They traced how a supply order became an expense and how that expense eventually surfaced in a report. They followed a patient’s bill through both payers, the Assurance Maladie share under T2A and the remainder owed to the mutuelle, and saw how often that second half slipped away uncollected. They learned which existing systems held which data, where those systems connected, and where the rules drew hard lines around what could move and how. They sat with the finance team and the floor staff both, because the costs and the care turned out to be tangled together in ways no single department could see on its own.
That groundwork ran about 5 weeks before the design firmed up. By the end, the team understood the hospital as an operation rather than an org chart, including the cost drivers leadership had never been able to isolate.
“You can’t save a hospital money by guessing,” Valentine says. “We spent weeks with spreadsheets and stopwatches before we proposed anything, because the savings live in the details. Once you can see exactly where the time and money go, the fixes pick themselves. Skip that part and you’re just installing software and praying.”
The depth of that discovery is the reason the system fit. It works with the hospital’s real processes and its real constraints, rather than forcing the staff to reshape their work around a generic tool.
What the system does
With the work understood, the build aimed at three things. Bring the costs into view, shorten the waits, and keep a human in charge of every decision that matters.
On scheduling, the system reads demand across the hospital and arranges appointments and resources to match. Outpatient waits that ran around 90 minutes now sit under 35. Appointments that once took days to book often get booked the same day. The puzzle that nobody had time to solve by hand gets solved continuously, in the background.
On information flow, the system moves test results and records to the right people without the manual relay that used to slow everything down. A result reaches the clinician who ordered it in a fraction of the time it took before. Urgent findings get pushed forward for immediate human attention.
On the floor, the system tracks beds, rooms, and equipment as they free up and fill. The coordination that used to live on a whiteboard and a string of phone calls now updates on its own. Staff see what’s open without chasing it down, so a patient moves to the next step sooner.
On billing, the system reconciles the two payers without the manual chase. It prepares the Assurance Maladie claim with the right T2A coding, generates the mutuelle claim for the remainder, and flags any case where a Carte Vitale record or a coverage detail doesn’t line up. Remainders that used to slip away get billed and collected. Claim rejections fell, because the coding is right before anything leaves the building.
On the money, the system tracks spending as it happens. Supply use, staffing, and department costs feed into one current picture rather than a report written weeks after the fact. The hospital stopped ordering on habit and started ordering on need, because for the first time the need was visible in real time.
“The hospital was carrying a lot of cost it didn’t need to carry, and most of it was hiding in plain sight,” Valentine says. “Once you can see the whole operation at once, the waste has nowhere to hide. We found the savings in the slack the old reporting couldn’t show, with nothing taken out of care.”
Control that leadership can hold
The piece the directors value most is the one that gives them their hands back on the wheel.
Leadership now works from a live view of the hospital’s costs and capacity, updated through the day rather than written up once a month. When a department starts running hot, they see it while there’s still time to respond. When demand shifts, the picture shifts with it. Forecasts rest on current data instead of last month’s guess. If overtime spikes in one unit on a Tuesday, the picture shows it that afternoon, not in a report three weeks later. A director can ask why, get an answer the same day, and decide whether it’s a problem worth solving or a one-off worth leaving alone.
That changes the job from reacting to steering. A director can test a decision against a real picture before making it, watch the effect, and adjust. The hospital can defend its spending to the bodies it answers to with numbers that are current and backed by a full record.
“We handed leadership a steering wheel and a windshield,” Valentine says. “Before, they were driving by looking in the mirror. Now they see what’s coming and they can do something about it. The point was simple. Give them what they needed to make those decisions well.”
Every part of that runs on the compliance foundation underneath it. The live cost view draws on operational data, kept separate from patient records and governed by the same strict rules. Visibility for leadership never comes at the expense of privacy for patients.
The human stays in charge
The system handles volume and surfaces what matters. It doesn’t make the calls that belong to people.
Clinicians review what the system routes before it drives care. Leadership decides what to do with the cost picture the system shows them; the software informs the choice and never makes it. Where the system is unsure, it flags the question for a person rather than guessing its way past it.
That line matters more in a hospital than almost anywhere else. A system optimizing for cost alone, with no human judgment over it, would eventually trade away something that shouldn’t be traded. Fort Lauderdale Software Developers built the hospital’s people into the center of the system, where their judgment governs the machine rather than the other way around.
“Software should give good people better tools, full reach over the decision, and nothing less,” Valentine says. “The day a hospital lets an algorithm quietly run the place to save a few euros is the day it loses something it can’t buy back. We made sure that day never comes here. The machine serves the staff. The staff run the hospital.”
What changed
The figures tell a clear story. Operating costs down by roughly 18% in the first year of full operation. Administrative overhead down by close to a third. Outpatient waits cut from around 90 minutes to under 35. Test results reaching clinicians in a fraction of the old time. A data protection review passed with no major findings. Claim rejections to the Assurance Maladie down sharply. Mutuelle remainders that used to go uncollected now billed as routine.
The rest of the change is harder to put in a number. Leadership stopped bracing for the monthly report and started working from a picture they trust. The finance team moved from explaining overruns after the fact to heading them off. Patients spent less of their day in a waiting room. Nurses spent less of theirs hunting for an open bed. Supply orders started matching real demand, so the storerooms stopped swinging between shortage and overstock. The hospital found room in its budget without taking anything away from care.
The savings hold because they came from removing waste rather than cutting muscle. And the whole system rests on a compliance base solid enough that none of it has to be unwound when the auditors come to look.
Why it worked
Fort Lauderdale Software Developers is a boutique firm that builds custom software and stays close to its clients, including on-site work when a project calls for it. This one called for it. The team was in the building, learning the hospital, long before the code was written.
That approach shows in the parts of the project that rarely make a brochure. It shows in the weeks of study before the build. It shows in the decision to make compliance the foundation rather than the finish. It shows in the choice to give leadership control instead of taking decisions out of human hands. It shows in a billing engine that handles T2A coding and the Assurance Maladie and mutuelle split the way a French hospital does, built by a team that learned the French system rather than assuming it matched their own.
A generic platform could have been installed faster. It would have missed the hospital’s real cost drivers, frustrated the staff, and risked the data rules that carry real penalties in France. The hospital needed a system shaped to how it works and built to satisfy the law from the ground up. That takes a partner willing to learn the work before building the tool.
“Anyone can promise a hospital savings,” Valentine says. “Far fewer will sit with the staff for weeks, build every rule into the foundation, and hand the people in charge more control instead of less. That’s the difference between software that survives its first audit and software that becomes a problem the moment a regulator asks a hard question.”
The hospital that couldn’t see its own costs can see them now, in real time, with a system that follows every rule it’s bound by. The waits are shorter. The budget is under control, and leadership can prove it with a full record. At every point where a decision touches a patient or a euro that matters, a person is still the one who makes it.
