HEALTHCARE

Meeting reports for Healthcare

Tumour boards, ward rounds, committees, patient interviews: Recapro captures and structures your meetings without ever letting health data leave your perimeter. Deployed on-premise in your data center, or at the HDS-certified host of your choice (France’s certified health-data hosting).

Start Now

0

health record on a US cloud

On-Premise

or the HDS host of your choice

The time spent writing up tumour-board reports, discharge letters and interview summaries is time taken away from care.

What

What exposes your health data

Medical confidentiality is not negotiable

Confidentiality covers everything the professional learns. Handing the recording and transcription of a clinical exchange to a third-party service means losing control of it.

Health data, the strictest regime

GDPR classifies health data as a special category (Article 9). Its hosting requires the host to be HDS-certified (Article L.1111-8 of the French public health code).

Tumour boards and ward rounds rely on scattered notes

Collegial decisions, therapeutic trade-offs, handovers: the exchanges that drive patient care are rarely captured in a usable, reusable form.

Consumer note-takers have no place here

Most cloud meeting assistants offer neither on-premise deployment nor HDS hosting. Data transits outside your perimeter, sometimes outside the European Union.

A poorly handled medical report puts more at stake than compliance: the patient’s medical confidentiality itself.

Recapro.ai

What Recapro brings

The tumour board becomes a structured report

The team runs its multidisciplinary meeting, Recapro produces a usable report: cases discussed, therapeutic decisions, proposals retained, next steps.

On-premise or the HDS host of your choice

A server installed in your data center, or deployment at the HDS-certified host you selected. HDS certification stays with your host; Recapro’s architecture conforms to it.

100% local inference

Transcription and summarisation are produced by models running on your infrastructure. No meeting excerpt is sent to a third-party language model, whatever the deployment mode.

Retention and traceability under your control

Every recording, transcript and report follows your retention policy. You attach the record to the patient file and archive it under your own rules.

Compatible with your tools

Recapro integrates with your hospital information system

Dedalus Maincare Softway Medical MIPIH EMED Doctolib Maiia Google Calendar Outlook Teams

What Recapro handles concretely

We do not replace caregivers. We give them back time to devote to patients.

Multidisciplinary team meeting

Case presentation, collegial discussion, therapeutic decision. The tumour-board report is structured and ready to be filed in the record.

Ward staff meeting and handovers

Daily briefing, handovers between teams, follow-up of inpatients. Knowledge no longer rests on the memory of a single handover.

Interview and disclosure consultation

The exchange with the patient is captured and restored. The professional stays present in the relationship rather than bent over their notes.

Committee and morbidity-mortality review

Ethics committee, M&M review, feedback session: sensitive exchanges are captured in a usable form, without leaving your perimeter.

For whom

If you handle personal health data on a daily basis

Healthcare institutions

Hospitals, clinics, hospital groups: standardise your tumour-board and ward reports while keeping health data in your data center or at your HDS host.

Practices, health homes and health centres

Physicians, specialists and health centres: document your interviews and internal meetings without exposing your patients to a third-party cloud.

Medico-social and clinical research

Care homes, medico-social structures, laboratories and research teams: the sensitive-data regime requires infrastructure you control.

Need deployment support?

For optimal Recapro integration in your organization, our partners NoBullshit Conseil support document process auditing, deployment and team training.

Discover the full journey

CLOUD ACT — HEALTH DATA AT RISK

The guarantee no US cloud can give you

As soon as a clinical meeting is recorded and transcribed through a US-law service, the health data it contains falls under an extraterritorial legal obligation, whatever its stated location.

« No, I cannot guarantee it »

Microsoft France’s answer to whether data hosted in Europe is beyond the reach of US law, before the French Senate commission of inquiry, 10 June 2025.

An “EU” location does not protect you

Keeping data in Europe is a contractual guarantee, not a legal one: the US legal obligation overrides the technical measure, as Microsoft acknowledged before the Senate.

Confidentiality and HDS require control

Medical confidentiality and the HDS hosting obligation assume you know who technically has access to the content while it is processed. A third-party cloud does not guarantee that.

A health-data leak is irreversible

Exposed health data cannot be taken back. The risk is not only regulatory: it directly affects the patient’s privacy and trust.

Sources

Understand the sovereignty of AI inference

THE VOCABULARY, IN PLAIN ENGLISH

Sovereign, on-premise, air-gapped: what they actually mean

These three words show up in every tender and every vendor brochure. They do not describe the same thing, and the distance between them decides who can technically read what is said in your consultations.

Sovereign governed by your own law, not another country’s: Sovereign software processes your data inside your own legal space: for a European organisation, under EU and national law. No foreign authority can compel it to be handed over.; What to ask a vendor: where the AI models actually run, and which country’s law governs the company operating them. Not only where the files are stored.
On-premise literally “on your own premises”: The server that transcribes your consultations sits in your own building, or with a hosting provider you contract with directly. It lives in your server room, like your electronic health record system.; Recording, transcription and drafting all happen on that machine. The opposite model, called SaaS, sends the audio to the vendor, who sends the text back.
Air-gapped literally “separated by air”: The machine has no physical link to the internet. No automatic updates, no telemetry, no remote backup. What goes onto that server cannot leave it over a network.; This is the level expected in sensitive clinical research and in classified environments. Updates are applied by hand, from physical media.

The three models, side by side

What you check	Cloud SaaS	On-premise	Air-gapped
Where the AI runs	On the vendor’s servers	On your site, or at your hosting provider	On your site, off every network
Can the vendor technically reach the content	Yes, during processing	No	No
Internet connection needed to process	Yes	No	None
What is left for you to verify	Which country’s law governs the vendor	Who administers the machine	The update procedure

In the SaaS model the processing infrastructure belongs to the vendor, which therefore holds, by construction, the technical means of reaching the content while it is being processed, subject to the contractual and technical measures each vendor puts in place. France’s HDS certification for health-data hosting, for its part, is an obligation that bears on where data is stored. It says nothing about where the AI performs the processing, and an HDS-certified service can perfectly well call a model operated somewhere else. The same gap exists under HIPAA: a business associate agreement allocates responsibility, it does not tell you which machine runs the model.

The questions you are about to ask us

01

Does an AI-drafted consultation note still respect medical confidentiality?

Medical confidentiality starts with controlling who can reach what the patient confides. With Recapro deployed on-premise, or at the certified health-data host you contract with, the audio and the text stay inside your infrastructure, and in this configuration no third party, Recapro included, has technical access to the content. That control over the place of processing removes one of the risks attached to using a third-party tool. It does not exempt you from telling the patient that the exchange is recorded and transcribed by an AI, nor from obtaining their agreement: both remain your responsibility.

02

What does an on-premise deployment actually look like for a practice or a hospital?

A server installed in your own building, or at the hosting provider you contract with, running the entire processing chain. You administer it the way you administer your electronic health record server. Nothing is sent to an outside service to be transcribed or summarised.

03

What does air-gapped mean, and who genuinely needs it?

An air-gapped machine has no internet connection at all. That mode belongs to sensitive clinical research, trials and environments under classification. For an outpatient practice, on-premise is enough in almost every case.

04

Do we still need a certified health-data host if the server sits inside our own organisation?

Health-data hosting certifications, of which France’s HDS is the best-known example, target the hosting of health data on behalf of a third party. An organisation hosting its own data on its own infrastructure is a different situation. As soon as you hand hosting to a provider, including a Recapro cloud offer, that provider’s certification and the regime that applies where you operate become the thing to check. Recapro is not itself certified for health-data hosting.

05

Do the recordings go to OpenAI, Anthropic or another US model?

No. Recapro runs its own transcription and drafting models on the machine you deploy. No call is made to a third-party vendor’s API, and no data feeds the training of a model.

06

Does Recapro work without an internet connection?

Yes, in on-premise and air-gapped deployments: transcription and drafting run locally. The connection only serves updates, so it becomes optional, and it disappears entirely in an air-gapped configuration.

07

Is this reserved for hospitals, or can a private practice use it?

Both, but not in the same way. As soon as patient data is involved, deploy on-premise in your own building or with the certified health-data host you contract with. Recapro is not itself HDS-certified, so its France-hosted offer must not be used to process personal health data. A private practitioner can use that offer for internal meetings that carry no patient data, then move to a dedicated server or a certified host as soon as a consultation is involved.

08

Do we have to inform the patient, or obtain their agreement, before recording a consultation?

Yes. The GDPR (article 13) requires the data subject to be informed of the processing of their data, including when the legal basis for care rests on article 9(2)(h). For the audio recording itself, professional good practice is to obtain the patient’s spoken agreement before starting it, and to let them refuse without any consequence for their care. Recapro supplies the technical tool; informing the patient and collecting that agreement remain the responsibility of the practitioner or the organisation.

09

Does Recapro fall under the obligations of the AI Act?

Recapro is not a medical device and makes no diagnosis, so it does not fall into the high-risk categories of annex III of regulation (EU) 2024/1689 on AI. The transparency obligation of its article 50, which requires a person to know they are interacting with an AI system, meets the information owed to the patient under the GDPR mentioned above.

10

How is Recapro different from a SaaS medical scribe?

A SaaS scribe sends the consultation audio to its vendor’s infrastructure, which returns the text. The guarantees then rest on contractual commitments. Recapro moves the processing to you: the guarantee becomes technical, because the data does not travel.

Dig deeper

Infrastructure questions surface fast once health data is involved. Here is where we treat them in detail.