Healthcare
Software for the Healthcare – with data that stays in the house
Specialist applications, evaluation and AI for clinics, practice groups, nursing facilities and service providers in the healthcare sector. On-premise operable, GDPR compliant – and without patient data leaving the house.
on-premise operableno data transfer to third parties
Where a request runs
And where it stays
1
Concerns come in
By phone, mail, fax or portal – often all four in parallel.
2
Assignment by hand
Someone decides where it belongs. This is where waiting time and errors arise.
3
Processing in the specialist system
The information is collected again because the systems are not connected.
4
Feedback and filing
Documentation is created separately from the actual processing.
Schematic. The marked step is the one where the most processing time can be saved in practice – without anyone having to work faster.
What facilities come to us with
Six starting points that occur again and again in the healthcare sector – regardless of size and discipline.
Systems that do not talk to each other
Between primary system, subsystems and administration is transferred by hand. Each transmission takes time and is a possible source of error.
Knowledge is in documents
Guidance, procedures, findings and endorsements are available but cannot be found. The answer exists, the search only takes too long.
Evaluations are made by hand
Key figures for management, quality management or cost carriers are compiled every time, instead of being set up cleanly.
Administrative burden binds specialists
People with medical education spend hours on appointments, forms, and queries that an application could handle.
AI should be used, but legally secure
The expectation is there, the legal situation is complex and the question is open which data a system is allowed to see at all.
Nothing should leave the house
From data protection, from confidentiality or from a requirement of the provider: Operation in your own data center is a condition, not a wish.
The framework that applies here
Health data belongs to the special categories of personal data. This shapes every architectural decision – from the beginning, not when it comes to acceptance.
Special categories according to GDPR
Health data is subject to a narrower framework than ordinary personal data. Legal basis, purpose limitation, erasure concept and logging therefore belong in the architecture.
Medical confidentiality
The obligation of confidentiality has an effect beyond data protection and also covers service providers. Access must be technically limited and traceable, not only contractually regulated.
Order processing neatly regulated
Anyone who deals with such data as a service provider needs a reliable contract and technical measures that suit him. Both must fit together, not just exist.
NIS2 covers the health sector
Facilities above a certain size fall under the new security obligations – with registration, reporting periods and proof obligations.
EU AI Act for AI projects
Health applications quickly fall into higher risk classes. What this means for documentation and supervision, we clarify before the implementation.
Connection to existing standards
Where data flows between systems, we stick to the established exchange paths instead of inventing our own – otherwise you disconnect.
What we do – and what we do not
This distinction is important to us because it has regulatory consequences in the health sector.
This is what we're building
- Specialised applications for administrative and organisational processes
- Evaluations and key figures on own stocks
- Knowledge systems that make documents findable
- Interfaces between existing systems
- AI applications that run entirely in-house
- Operation and maintenance of the structure
We're not building that
- Medical device software according to MDR
- Applications that diagnose or suggest therapies
- Certified primary systems such as CIS or PVS
We develop no medical device software. As soon as an application has a medical purpose, the MDR uses its own conformity procedure – this requires a manufacturer with a corresponding quality management system. Our field is everything before and against: organization, evaluation, knowledge access and the connection of the systems you already have.
Your contact person in Stuttgart
Our office is located in Stuttgart-Wangen. For an inventory, we come to your house.
Discussion of projects
- Initial consultation free of charge and without obligation
- On request with assessment of data protection and operating model
- Also suitable if only what is allowed is to be clarified
Frequent questions
No. As soon as an application has a medical purpose – i.e. serves for diagnosis, monitoring or treatment – it is a medical device and falls under the MDR. This requires a conformity procedure and a manufacturer with a suitable quality management system. We work before and after: organization, evaluation, knowledge access, interfaces.
If you will, yes – completely. Our solutions run in your own data center or in your private cloud. This also applies explicitly to AI parts: language models can be operated locally, so that no content goes to external providers. In the health sector, this is usually the only viable variant.
Yes, and that is the rule. We bring in the technical side, the legal assessment remains with your data protection officer or your legal department. This division of labor is much faster than if one side tries to do both.
This depends on which ways your system offers to the outside world. Many primary systems have interfaces or at least defined exports. At the beginning, therefore, there is an inventory, not a commitment – only then do both sides know what is possible.
Most likely where knowledge is in documents: guidelines, procedures, internal standards. A system that provides verifiable answers with a source indication saves search time immediately. We advise against applications that evaluate medically – this is a medical product and another procedure.
The health sector is one of the areas covered; What matters is the combination of sector and size. Legal assessment is part of legal advice. As far as technical implementation is concerned, we have described this on a separate page.
With a narrowly defined step: an evaluation that is created by hand today, or a process that binds too many specialists. This results in something usable in a few weeks. This is less risky than a major project and quickly shows both sides whether cooperation is beneficial.
Related benefits
AI consulting and RAG systemsProofable answers from own documents.Find out more ›NIS2 advisory servicesTechnically implement security obligations.Find out more ›AI Governance & EU AI ActClarify risk classes and documentation.Find out more ›Custom Software DevelopmentSpecialist applications for own processes.Find out more ›
Unclear what is allowed?
This is the norm in health care and a good reason for a conversation. We classify what is technically possible, what the framework provides and what can be started with.