Healthcare

Less time on documentation. Patient data stays in house. In your own server room.

Clinicians spend a large part of their time on administration. AI can help, but patient data does not belong in a consumer tool. werqly runs AI on a node in your own server room, with roles per department, safeguards on national ID and patient numbers, and an audit log that records who used which data and when.

Only the domain of your email address is used to look up your organisation.

  • Node in your own server room
  • Roles per department and function
  • Logging per user and per source
werqly NODE AI CONTROL GPU 1 GPU 2

Running in your server room

Role: Clinician

  • Mistral Large
  • Llama 70B
  • Qwen 32B

Safeguards active

Insight: anonymous (default)

  • National ID detection
  • Patient numbers blocked

werqly Node — dedicated AI node, in your server room or in our European datacentres

The risk

Where it goes wrong in healthcare.

Reports in consumer tools

Under time pressure, a report containing patient data gets pasted into a chatbot to tidy it up. No processing agreement, no logging, no idea where the data ends up.

A ban that does not work

Banning AI does not remove the administrative burden. It only makes the use invisible to the data protection officer.

Requirements you must evidence

Health data comes with national security and hosting requirements that must be demonstrable. A standalone AI tool without logging does not fit them.

Use cases

What healthcare providers use it for.

Automations are built per organisation, usually following from the TIMA Scan. Always supportive: the clinician checks and decides.

Draft reports and notes

A first version of a report, which the clinician checks and completes.

Summaries for handover

The relevant information from a record, gathered for a handover or referral.

Letters to referrers

Draft letters to the GP or referring physician, based on the report.

Searchable protocols

Your organisation’s guidelines, protocols and work instructions searchable, with sources.

Analysing incident reports

Recurring themes in complaints and incident reports made visible for quality management.

Administration and registration

Preparing registration and billing work, checked by the administration.

Regulation

What the rules look for.

werqly does not make processing patient data lawful by itself. It does give your organisation an environment that fits into your information security.

FrameworkWhat it asksHow werqly fits
National health-data hosting rulesSeveral EU countries set specific requirements: HDS certification for hosting health data in France, a C5 attestation for cloud use in Germany, NEN 7510 compliance in the Netherlands.A node in your own server room keeps health data within your organisation. werqly holds neither HDS nor C5, and its NEN 7510 certification is in progress.
Medical confidentialityPatient data only for those directly involved in the patient’s care.Roles per department and function determine which sources and automations someone may use.
GDPR: health data (Art. 9) and DPIA (Art. 35)Health data is a special category of personal data. Large-scale processing usually requires a data protection impact assessment.Processing on a dedicated node in your server room, without transfer to third parties, makes the DPIA more manageable.
Medical Device Regulation (EU 2017/745)Software intended for diagnosis or treatment can be a medical device.werqly is not a medical device. Use it for administration and support, not for diagnostic or treatment decisions.

This page is not legal advice. Always assess the use of AI with your own data protection officer, compliance function or professional body.

Recommended setup

Which setup fits a healthcare provider.

For patient data we recommend your own server room: the data then never leaves your organisation. With werqly Pro management, werqly operates the node remotely as a processor; when self-managed, your IT department does so.

  • Node in your own server room or datacentre
  • Connection to your electronic health record read-only and per role, as a project with your EHR vendor
  • werqly Cloud only for work without patient data

Calculator

Calculate your private AI costs.

Enter your work email. Our AI looks up the size of your organisation and works out four setups for you: in the cloud or in your own server room, self-managed or with werqly Pro management.

  1. 1Enter your work email
  2. 2AI estimates your headcount
  3. 3Compare four proposals and request a quote straight away

Only the domain of your email address is used to look up your organisation.

FAQ

Questions from healthcare providers.

May patient data be processed in werqly?

That depends on your own assessment: the legal basis, a DPIA, and how werqly fits your national security and hosting requirements. The setup in your own server room, without transfer to third parties, is built for it. Involve your data protection officer from the start.

Is werqly a medical device?

No. werqly supports administration and documentation. The clinician checks the output and makes the decisions. Applications intended for diagnosis or treatment fall under the Medical Device Regulation.

Can werqly connect to our electronic health record?

Yes, as a project with your EHR vendor. Such a connection is read-only, scoped per role and part of the DPIA. Expect it to be the part that needs the most preparation.

What does werqly see of patient data?

Prompts, documents and output are processed on the node in your server room. The management link carries configuration, updates and only the insights you release. With werqly Pro management, werqly is a processor and maintenance is covered by the processing agreement.