Patient records and findings
Health data is special-category data under Art. 9 GDPR, and medical confidentiality applies to everyone, including an AI provider. What patients entrust to you belongs in no outside data center.
LOKI runs completely locally on your hardware, behind the practice’s firewall. It finds findings, logs, QM documents and inboxes with a single question. Every answer comes with its source.
Thursday’s the inspection. Where do I find the device inventory, the last STK for the ECG and the autoclave batches?
The device inventory required by the German Medical Devices Operator Ordinance (MPBetreibV) is up to date, last amended in May [1]. The safety inspection (STK) of the ECG took place in March, the record is on file [2]. The autoclave’s batch documentation is complete with no gaps, including the validation report from 2025 [3].
Next week’s the haematology EQA. What stood out last time, and what did we change afterwards?
In autumn, one parameter sat at the edge of the tolerance range [1]. The corrective action: calibration brought forward and the control rule tightened, documented together with the effectiveness check [2]. Since then, all internal controls have been unremarkable [3].
How does the DMP enrolment work here again? And which forms do I need?
The procedure is a work instruction in the QM manual, last reviewed in January [1]. The forms, including a guide to filling them in, are in the templates folder [2]. And the team minutes from March record the agreement on who handles the follow-up documentation [3].
From family-run businesses to DAX corporations. Machine building, chemicals, and the public sector.
Patients entrust it to you under the protection of medical confidentiality.
Health data is special-category data under Art. 9 GDPR, and medical confidentiality applies to everyone, including an AI provider. What patients entrust to you belongs in no outside data center.
External quality assessment (EQA) under the German Medical Association’s lab-quality directive (RiliBÄK), control records, standard operating procedures: accreditation under DIN EN ISO 15189 checks whether you measure correctly, and just as much whether you can prove it without gaps. That chain must belong to you.
Billing code chains, quarterly figures, audit queries from the KV, the regional Association of Statutory Health Insurance Physicians: whoever reads them knows the financial position of the practice. None of it is anyone’s business outside the building.
Treatment documentation must be retained for ten years under Section 630f BGB. Add the medical device log and the device inventory under the MPBetreibV, deadlines for safety and metrological checks (STK, MTK), and the batch and validation documentation of reprocessing. Keeping it all works. Finding it again is what costs.
The public health office inspects hygiene, the KV spot-checks your QM against the directive of the G-BA, Germany’s Federal Joint Committee, and in the lab the DAkkS, Germany’s national accreditation body, watches over the accreditation. And the RiliBÄK requires external quality assessment at fixed intervals. Anyone who first has to search for evidence loses days.
Medical assistants (MFA) have been on the Federal Employment Agency’s shortage list for years. The knowledge of your workflows lives in heads and sticky notes: who expects which preparation, how enrolment works, where the template sits. With every departure, part of it walks out the door.
eAU, eRezept, ePA, KIM: the channels go digital, the filing stays scattered: chart entry in the PVS, findings in the lab system, letter in the KIM inbox, fax as a scan, the rest in the paper archive. None of these systems can search the others.
The knowledge is in the building. It just sits in the PVS, the lab system, the QM folder, the KIM inbox and the paper archive all at once.
Your knowledge lives in four worlds that don’t know each other: chart entries in the PVS, findings and controls in the lab system, work instructions in the QM folder, letters and faxes in the inbox. LOKI lays one search across all four, with role-based access: whoever may not see patient data does not see it.
Chart entry, lab findings, QM document, mail thread.
LOKI opens up all four, following your role-based access.
No system knowledge, no file names, no folder hunting.
Every statement carries the source it came from.
One question. Four systems. One answer that tells you where it knows it from.
Tuesday, 7:50 a.m. The public health office has announced the hygiene inspection, for Thursday.
Thursday’s the inspection. Where do I find the device inventory, the last STK for the ECG and the autoclave batches?
The device inventory required by the German Medical Devices Operator Ordinance (MPBetreibV) is up to date, last amended in May [1]. The safety inspection (STK) of the ECG took place in March, the record is on file [2]. The autoclave’s batch documentation is complete with no gaps, including the validation report from 2025 [3].
The evidence is gathered before consultation hours begin.
Your team wants to work with the best models, and does so anyway, if need be around the official toolbox. LOKI turns that into an official path: you connect external models, and every request passes through a check first. Names, order numbers, part identifiers and amounts are detected and redacted before the prompt leaves the building.
Doctor’s letter to cardiology for H. Berger[PATIENT], born 12.03.1958[DATE OF BIRTH], status post myocardial infarction[DIAGNOSIS], for co-treatment.
Protokoll11:24 · Dr. Sommer · Claude Opus 4.8 · 3 findings redacted · sent
Name recognition and configurable patterns find what must not go out.
The user sees in the chat what was found and chooses: send anonymized, send unchanged, or cancel.
Every call is in the log, with user, model, time and the result of the check. Including the cancelled ones.
And this is what the switch looks like in the product: choose a cloud model and it tells you right above the input field.
That’s the difference between a ban that gets bypassed and a path you’re allowed to take.
We don’t have to vouch for the architecture ourselves. The conference of Germany’s data-protection authorities (DSK) described it before we built it.
The DSK’s guidance on AI and data protection states that technically closed systems are preferable from a data-protection perspective: in open systems, the input data leaves the users’ protected environment. With LOKI it doesn’t.
Inside a language model itself there is no way to control who may see which information; the supervisory authorities state this explicitly. In the knowledge system in front of it, tenant separation and role-based access do work. That’s why LOKI is built this way. And that’s why individual entries can be deleted deliberately instead of disappearing into a model.
Health data is special-category data, and medical confidentiality allows no exception for AI tools. A system that runs entirely inside the practice keeps patient data where it belongs, and at the same time opens up the evidence chains that the QM directive, the Medical Devices Operator Ordinance and the RiliBÄK demand. Who may see which record is decided by role-based access rather than by chance.
The regulators call this a mitigating measure, not a blanket solution, and name open questions around transparency and data-subject rights. We put it exactly the same way.
Without you changing your system landscape.
LOKI replaces neither the PVS nor the lab system; they stay in charge. LOKI makes findable what lies between them. Who may see patient data is decided by role-based access.
LOKI compiles the hygiene plan, validation reports, batch documentation and the team’s training records, every document with its source.
The inspection cannot see whether you work cleanly. It can see whether you can prove it.
Standard operating procedures, device histories, EQA results, staff qualifications: LOKI finds the status of every record and shows the gaps before the audit.
Accreditation hangs on the chain of evidence rather than on the measurement technology.
How practice supplies are ordered, which preparation each physician expects, how consent for self-pay services (IGeL) is documented: LOKI finds the work instruction, the team minutes and the email where it was last clarified.
Onboarding from the records instead of from memory.
Also: answering KV audit queries with the quarter’s supporting notes · keeping STK and MTK deadlines in view · keeping the QM manual current and documenting changes · onboarding new colleagues · making contracts and KV circulars searchable
With our locally installed AI assistant from IGNAITE, our employees can access company knowledge much faster. For example, information from past projects. This enables higher productivity and, above all, more comprehensive knowledge sharing.
In our collaboration with IGNAITE, we built a practical, high-performance computer-vision solution that has sustainably improved our incoming-materials processes. What particularly convinced us was the structured approach, the deep process understanding, and the ability to translate complex requirements into pragmatic solutions.
LOKI opens up what was written down. But much of what happens in practice and lab never makes it into a document: the temperature of the vaccine fridge, the room climate in the storage area, device runtimes. MINERVA captures them, with its own boards on your own network, and turns them into sources LOKI can cite. The fridge temperature curve becomes evidence with a source.
Extendable with MINERVABoth products follow the same principles: sovereign, source-based, local. You start with one and add the other when you need it.
From signing to productive operation in under four weeks — without touching the PVS or lab system.
We look at where your records live (PVS, lab system, QM folders, inboxes) and tell you honestly what LOKI can open up from them.
The hardware goes behind your firewall. We connect archives, exports and inboxes, without touching the PVS or lab system. Role-based access is set up together before launch.
We hand over only once it runs production-ready. The EU AI Act has required you since February 2025 to train your staff in the competent use of AI; we deliver that training.
With a cloud AI, that is exactly the right concern: health data enjoys special protection, and medical confidentiality also applies to service providers. That is why LOKI runs entirely on your hardware: no upload, no API call to OpenAI, Anthropic or Google, no training by third parties. And role-based access governs who may see which record.
We open up the relevant content: document archives, letters, forms, GDT and LDT exports, and PDF collections including scans. We make no attempt to replace the PVS; the aim is to answer the question “Where does it say that?” in seconds. What is concretely possible in your landscape is something we clarify before installation.
No. LOKI only shows sources the person asking is authorized for: billing sees no findings, the lab sees no charts. Role-based access is set up together with you before the rollout.
No. Scanned documents are processed with text recognition. With handwritten entries the hit rate drops. We tell you that up front instead of promising otherwise.
LOKI answers from sources and names the document behind every statement, checkable before anything goes into a letter or a record. And we draw one line deliberately: LOKI is a knowledge assistant for administration, QM and research. It is not a medical device. It finds; diagnosis and treatment decisions stay with you.
It helps with the part that costs time: keeping evidence findable. Standard operating procedures, device histories, EQA results, training records: LOKI finds the current status and its location. Your QM system stays in charge; LOKI changes nothing about it, it makes it searchable.
A fixed monthly price plus a one-time setup fee that includes the server hardware. The license covers unlimited users. There are three packages that differ in hardware sizing. Operation, maintenance, updates and support are included. We’ll give you the specific price in the intro call.
The industry pages show LOKI in the everyday work of individual industries. If yours is missing, that only means we haven’t written it up yet.
30 minutes, an honest assessment. No slides, no sales pressure. We’ll also tell you if LOKI isn’t the right step for your data situation yet.