AI for healthcare: lighten the administration of practices and clinics
A saturated switchboard, appointments to fit in, letters to write, patients to call back: the administrative load eats into the time of carers and front desks. Your AI agent can absorb a large part of it — provided two lines are never crossed: absolute confidentiality of health data, and no involvement whatsoever in the act of care. Hosted in France — on local inference or an isolated resource — with the HDS requirement settled with you at scoping. The carers keep the lead.
Updated on
No medical question handled — those are held for the front desk.
⛓ Source · the practice's diary + reception arrangements
I am preparing a handover note for your approval.
✎ Action · handover ready — the front desk approves
In a medical practice or a clinic, Blue Lemon Agent offers an administrative supervisor: it opens and follows the case file for a request, sequences the steps between the selected specialised agents, consolidates their replies and documents into a single output submitted for human approval, and holds exceptions, follow-ups, escalations and closure. It delivers no business service on its own: replies to patients, letters, administrative documents, routing of requests and internal memory are carried by specialised agents billed separately, whose price is not included in the supervisor's — and the supervisor itself remains quote-only. Appointment booking remains an architected target, not orderable: no compliant, HDS-hosted and acceptance-tested health agent exists. And no journey handling health data can be sold until the HDS evidence matching the architecture being sold has been verified. It runs on local inference or on French hosting; medical acts and decisions remain the work of the care team.
Reference points describing our offer, not results measured at a client. The scale of the gain is confirmed by a pilot on your own scope.
Why AI matters to practices and clinics — and why they hesitate
Carers want to spend more time with patients and less on the phone or on letters. But the data involved is the most sensitive there is, and the line with the act of care must never be crossed.
! The issue
The practice or clinic is caught between a saturated switchboard, missed appointments and letters to produce — and a front desk whose time is mechanically squeezed. Yet most consumer AI solutions amount to entrusting health data, among the most protected there is, to a third party often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
AI is only of interest to a care organisation if it is sovereign, confidential and strictly administrative by design. Hosting in France or local inference, the HDS requirement settled at scoping, systematic human oversight, no involvement in the act of care: the time saved on administration is never paid for in lost confidentiality. The aim is not to replace the carer, but to give them back time for what a machine will never do — care and the human relationship.
Health data: HDS certification and confidentiality, an absolute requirement
Health data is among the most protected under the GDPR, and is covered by medical confidentiality. Here is how the architecture of our agents protects it.
Local inference
Where the use allows, the agent runs on a machine at the organisation: no data leaves the network, nothing passes through a cloud.
Health data: the HDS requirement
Otherwise, hosting for health data located in France, under French law — your data: processing and access within the European Union targeted by the architecture. In France, hosting health data on behalf of others is subject to HDS certification of the host: that requirement is settled with you at scoping, before any go-live.
Reduced extraterritorial exposure
Architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
One isolated resource per organisation
No pooling of health data: an environment strictly dedicated to your practice or clinic.
Medical confidentiality respected
Encryption in transit and at rest, role-based access, strong authentication and logging — medical confidentiality binds the whole chain.
Strictly administrative
No diagnosis, no medical triage, no clinical opinion; routing on purely administrative criteria, never medical ones.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
- Roles and permissions are configured and accepted for the identities and systems actually connected.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
See the agent at work
5 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.
A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.
· Dr Kane is away on Thursday 13/08. The absence was entered on the rota last night. 14 patients hold an appointment that day and none has been told.
· A record access request has been waiting six days. Mrs Sow filed it on 30/07; the eight-day limit expires the day after tomorrow.
· 7 reports are sitting in the shared inbox, five days old, attached to no patient record. I can see they are attached to nothing — I have not opened their content.
· Dr Mbaye's professional indemnity certificate expired on 31/07. No renewal is on the administrative file. morning-watch_4-flags.pdf4 flags · source of each
⛓ Source · rota, access-request register, shared inbox, administrative file
Moving a patient's appointment means deciding that their consultation can wait. Of these 14, I do not know which ones can, and knowing would mean reading a clinical reason that I do not read.
What I have done: the list of 14, each with how long ago the appointment was booked, whether it is a first appointment or a follow-up, and whether another practitioner in the practice has a free slot the same day. That is diary data, not health data.
Seven have an equivalent slot with Dr Diallo on the Thursday. For the other seven, the first free slot is 27/08.
The rescheduling message is ready, in two versions — moved within the same day, and moved by a fortnight. Neither goes out until someone has said who goes where. appointments-13-08_to-reschedule.pdf14 patients · substitute slots
✎ Support · rescheduling prepared — the clinical call stays with the practice
Routing follows your organisation: the absence and the rescheduling to the head of reception; the access request to her as well, because the limit is a legal one and she holds it; the unattached reports to the medical secretariat; the expired certificate to the practice manager, because that is not a reception matter.
With a chase: nothing done after 48 h, a reminder; after 72 h, the coordinating doctor. And a weekly summary: what was flagged, what was dealt with, what went unanswered. A state of the issues, not a ranking of people.
And I do not stop at the flag: whatever could be prepared is. The rescheduling for the day of absence is proposed patient by patient, two slots each, taken from actual availability; the access request is built with the documents to attach and the statutory time limit counted, day by day; the unattached reports come back with the identifying element each one is missing; and the certificate renewal is pre-filled. Over a week, that is half a day of reception time handed back.
What stays with a person, and it is what protects the patient: everything touching on care. I can see that a report is attached to nothing; I do not know what it says — clinical content is not opened to me, and that is an installation choice, not a setting. A rescheduling, an approval, an answer to a patient carry the name of whoever gives them.
And I read what you have opened to me, station by station, every access logged and withdrawable on a word: nothing leaves the practice.
✎ Proposal · watch and chases to be configured — you set the thresholds
Over the month: 1,260 administrative requests received, 1,118 closed at first contact. The remaining 142 are exceptions, sorted by what is blocking them:
· 58 are waiting on an administrative document — proof of entitlement, referral letter, funding approval;
· 41 are waiting on a practitioner or a room;
· 28 fall outside the protocol you wrote: a request from a third party, an unusual reason, a situation the standing instruction does not cover;
· 15 are postponements asked for by the patient.
Chasers go out on their own, on the dates you set: day 2 by message, day 5 by phone, day 9 a final reminder stating the consequence in plain words. Of the 58 missing documents, 47 came back by day 5, against 21 in a comparable month before.
Escalations go to a named person, never to a department: the 28 outside protocol go to the lead secretary with the exact reason they left the protocol; 9 went up to the practitioner, because they call for a clinical judgement — and those do not come back to me until he has answered.
Closure is traceable, and that is the part always neglected: a request is closed only with a reason picked from your list, the date, the author — me or a person — and the link to the document or message that closes it. Across 1,260, not one is closed without those four. That is what lets you answer in thirty seconds when a patient calls back a month later.
A figure that does not suit me: 11 requests slept for 14 days in the queue. All eleven had received a partial answer from the patient, and my rule treated any answer as a chaser satisfied. An answer that does not close the reason now chases again after 48 hours: nothing beyond 9 days for six weeks.
✎ Framework · exception queue, dated chasers, traced closure
The rise is not spread evenly. It sits almost entirely on slots before 9:30 am (24% no-show) and on appointments booked more than six weeks ahead (19%). The rest of the diary is stable.
One thing the figures do not settle: 41 of those absences were cancelled by the patient less than two hours ahead. Your software counts them as missed, even though the slot could have been reassigned. That is a configuration question, not patient behaviour. missed-appointments_quarter.pdf213 rows · reason and booking lead time
⛓ Source · practice diary, last 3 months
What this mechanism does not do: it does not overbook, it cancels nothing of its own accord, and it does not chase a patient who has already replied. The reminder rule is written with you at deployment — you set the threshold and the slots it covers.
And a weekly summary for the head of reception: what was reminded, what was released, what went unanswered.
One point remains yours to settle: the 41 late cancellations. Take them out of the count and your real rate falls from 11.6% to 9.4% — and the problem changes nature.
✎ Proposal · reminders to be configured with you — nothing goes out without your approval
The clinical section is left blank, marked "to be completed and signed by the practitioner". I do not write the medical content of a letter between clinicians.
Two things noted: the complementary cover on file expired on 31/12/2025 and has not been renewed; and the March discharge letter is not attached to the record — it is sitting in the shared inbox. referral_Faye_cardiology.pdfAdministrative section filled · clinical section to complete
⛓ Source · administrative record + practice referral template
The record holds eleven clinical documents over four years: I can list them, date them and attach each to the right episode, which saves you the search.
Selecting what is relevant to a cardiology opinion is a clinical judgement. It is yours, and I do not make it — not even as a suggestion, because a suggestion steers.
The chronological list is attached to the letter, as a separate sheet, for you to tick what you send.
One observation while I am here: three further referrals are due this week, all to the same department. The three records share the same administrative section, up to date or not. I can prepare all three envelopes tonight, leaving you only the clinical section to write. On your approval.
✎ Support · clinical selection stays with the practitioner
The discharge summary is covered by professional secrecy. An employer has no standing to request it, and the practice that hands it over commits the offence — not the party that asked.
What I can do, and have done: a standard reply to the employer stating that the request cannot be met and where to turn — the sick-leave certificate itself, sent by the employee, covers their need.
If it is the patient who wants his record, the route exists and I know it: written request from the patient himself, proof of identity, answer within eight days. standard-reply_employer-request.pdfReasoned refusal · redirection
⛓ Source · professional secrecy · art. L1111-7 French public health code
And the agreement would cover the wrong thing. The right of access belongs to the patient, not to a third party he names by phone: the record is handed to him, and what he then does with it is his business.
Form prepared: request for access to his own record, for Mr Ndiaye to sign, with the list of acceptable identity documents.
On timing the rule is strict: eight days from receipt of the request, two months where the information is more than five years old (art. L1111-7 French public health code). Two of the documents requested date from 2019 — the two-month limit applies to those.
A proposal: these requests reach the practice without being tracked, and the eight-day clock runs with nobody counting. I can keep that register — date received, documents requested, applicable limit, alert two days out — and flag to the head of reception what is coming due.
I would release nothing myself: I count the days, you hand over the record. record-access-request_form.pdfFor the patient to sign · time limits stated
✎ Action · form ready · the legal clock starts today
One warning, though: the note refers to a form in a version that has not been in circulation since 2025. The substance of the internal procedure still holds; the form reference needs checking before you apply it as written.
I will not go and fetch the current version from an outside site on my own initiative: it is not in your base, and I do not present as yours a rule you have not approved. patient-transport-procedure_v3.pdf5 steps · 1 reference to check
⛓ Source · practice document base · note v3 of 14/03/2024
Two deserve attention first, because they are the most consulted at reception: this one, and the note on care received abroad.
What I have prepared for the nine: a dated banner at the head of each — "reviewed 22 months ago; points to a form replaced in March 2025" — and, for the four citing something out of date, the current reference set beside the old one, with its source and date. Nine banners ready, none applied: they are waiting on the approval of whoever signed the note off.
Why a banner rather than a rewrite: an out-of-date note stays visible and stays marked as such — making it disappear would be worse than leaving it. And rewriting it without the person who approved it would be lending them a signature they never gave.
What I can do next, on your approval: flag every note past eighteen months without review to the person who approved it, chase once after a month if nothing moves, and send a monthly summary to the coordinating doctor — how many notes are overdue, which ones, since when. procedure-notes_to-review.pdf9 notes · last review date
✎ Proposal · review on a deadline — approval stays human
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
What the supervisor does itself, and what it coordinates
The supervisor delivers no business service on its own: it holds the case file, sequences the steps and hands back an output for approval. The business capabilities are carried by specialised agents, billed separately.
Shared administrative case file
Opening the case file for a request and following it end to end: a single thread, whatever the channel it arrived on, with its correlation identifier.
Sequencing the steps between agents
Sequencing the steps between the selected specialised agents, with bounded handoffs: what is passed on, to whom, and what is refused.
Consolidated output, submitted for human approval
Bringing replies, documents and actions together into a single output, handed to a competent person who approves it before anything is sent or filed.
Exceptions, follow-ups, escalations and traceable closure
Holding the exception queue, chasing what is overdue, escalating to a human whatever falls outside the protocol, and closing each request on the record.
AI agent for medical secretarial work
Answering patients' administrative questions, drafting standard letters, preparing certificates, forms and administrative papers, and directing a request to the right department on purely administrative criteria. These capabilities are carried under the same tariff identifier as the supervisor: they are included, with no separate billing.
Booking and managing appointments
No compliant, HDS-hosted and acceptance-tested agent carries health appointment booking today — the journey recorded for this page expressly forbids it until such an agent exists. The capability is architected, not deliverable: it is neither included in the supervisor, nor sold as a complementary agent.
Being architected — not orderable Be notified when it becomes available →Sovereign agent for regulated sectors (health / finance)
Hosting in France, the HDS requirement settled at scoping, a SecNumCloud option, reinforced security.
On quote View the agent page →AI knowledge base agent
Your practice's administrative reference material, made searchable: opening hours, documents to bring, referral routes, forms, published fees. The boundary is a narrow one — the supervisor passes on the question alone, rephrased with no patient identity, no contact details, no appointment slot, department or clinician, and nothing whatsoever about care; what comes back is an answer quoting the passage it relies on and its date, or a plain statement that no source answers. The agent reaches neither the patient record, nor the diary, nor the secure health messaging system, and it never addresses the patient: it answers authorised staff, through the supervisor. Even so, whatever this journey would carry arises in a care setting and serves a patient's care: on that ground it counts as health data. Paring it back lowers the risk; it does not change what the data is. That paring back is written into the journey and built into the acceptance tests, but those tests have yet to be run: until the HDS evidence has been verified, the capability stays architected — neither included in the supervisor, nor orderable from this page.
Available View the agent page →The specialised agents the supervisor coordinates
These specialised agents are billed separately: their price is not included in the supervisor's, which remains quote-only. And no journey handling health data can be sold until the HDS evidence matching the architecture being sold has been verified.
Phone reception
Answering calls, giving information on opening hours, access and arrangements, without saturating the switchboard — around the clock.
Voice agent (AI switchboard) from 856 € excl. VAT / month AI voice switchboard →Document processing
Documents arrive in piles — scans, PDFs, attachments — and the data they contain has to end up in your systems.
Document processing agent (OCR, extraction) from 700 € excl. VAT / month Discover the agent →In 15 minutes we identify the most relevant agent — without oversizing the project.
How much time can a front desk win back?
Phone reception and appointment management take up a large share of a front desk's time. By taking on the everyday calls and the reminders, the agent gives that time back to the patient in the room; the scale of the gain is confirmed by a pilot.
The stages of your AI agent project
Audit & scoping
15 minutes to target the use case with the best return.
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
Design
We design the agent and its guardrails.
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
Rollout
Going live and training your team.
Operation
Continuous supervision and improvement.
An administrative agent, two ways of running it
An administrative agent (reception, appointments, letters, routing), installed and operated for you, hosted in France; the HDS requirement is settled with you at scoping. Choose according to how you are organised. Prices exclude VAT — annual subscription, the time it takes for the gains to settle in.
Four guarantees that matter to a care organisation
Your questions, our answers
Does the AI make diagnoses or replace the doctor?
Is patients' health data protected?
Which tasks can AI really take off our hands?
Is AI suitable for a small practice?
Can the agent direct a patient according to their symptoms?
Does the agent state that it is an artificial intelligence?
How long does it take to deploy an agent?
Which tools can people use to talk to the agent?
Other professions with demanding confidentiality
Let us estimate the potential in your organisation
15 minutes to identify the most useful use case — hosted in France (HDS requirement settled at scoping), supervised, with no commitment, and never touching the act of care.