Use NEXUS / KIS with AI via MCP
NEXUS / KIS combines clinical workflows and departmental modules from radiology to psychiatry in one system. NEXUS AG does not provide an MCP server, so use with CompanyGPT is implemented individually via HL7 v2, the legally mandated ISiK FHIR interfaces and IHE profiles.
What is NEXUS / KIS?
NEXUS / KIS is the hospital information system of NEXUS AG, headquartered in Donaueschingen, Germany. Its defining characteristic is a modular structure: alongside the HIS core for patient administration and clinical documentation, there are departmental solutions for radiology, pathology, psychiatry and rehabilitation, among others. The NEXUS group reports more than 235,000 users and around 1,800 employees, with dedicated country organizations in Germany, Austria and Switzerland.
That modularity shapes the AI perspective as well: relevant information rarely sits in a single store but is spread across specialist modules and documentation layers. An AI assistant is therefore most useful where information from several modules has to be brought together – while the data release stays narrow, because this is health data under Article 9 GDPR.
Connection at a Glance
- MCP server
- None available – individual integration
- Interfaces
- HL7 v2, FHIR/ISiK (Section 373 SGB V), IHE, NEXUS module interfaces
- Authentication
- Internal interface accounts, project-specific
- Operating model
- On-premises; NEXUS / CLOUD IT available as an operating option
- Permissions
- Tool-level data scope, role-based control in CompanyGPT
How to Connect NEXUS / KIS to CompanyGPT
There is no MCP server for NEXUS / KIS – neither from the vendor nor as an established community project. We therefore plan and build the CompanyGPT connection individually, tailored to the modules you actually run.
The technical basis is the set of clinical standard interfaces: HL7 v2 via the communication server, FHIR via the ISiK interfaces mandated by Section 373 SGB V, IHE profiles for document exchange, and the module-specific NEXUS interfaces. We translate the required queries into MCP tools with a fixed scope and document, for each tool, which fields it returns and which purpose it serves. If you run NEXUS via NEXUS / CLOUD IT, the same interfaces apply – only the network path differs.
Approvals and interface accounts stay with your IT department, and every call can be logged. In CompanyGPT, your administrators use roles and groups to define which departments work with the integration. We recommend starting with a read-only, clearly bounded use case and expanding the scope only after the data protection assessment.
Note for on-premises operation: CompanyGPT runs in your own Azure tenant – so your on-premises network can be connected directly: via a site-to-site VPN (Azure VPN Gateway) or ExpressRoute between your corporate network and the virtual network of your CompanyGPT environment. The system does not need to be publicly reachable; we set up the connection together with your IT team.
Typical Use Cases
How AI agents in CompanyGPT work with NEXUS / KIS
Relieve clinical departments
Radiology or pathology query report status, workload and open documentation steps in chat instead of collecting them module by module.
Check documentation quality
Quality management has cases with missing mandatory entries listed and gets an overview of where follow-up documentation is due.
Self-service for administration
Admissions, department offices and billing clarify questions about cases, responsibilities and appointments without requesting a report from IT.
Frequently Asked Questions
NEXUS / KIS and AI – the most important answers
Does NEXUS AG offer an MCP server?
No. No vendor MCP server is available for NEXUS / KIS. The connection to CompanyGPT is built as an individual integration on the existing interfaces.
Does an AI connection work anyway?
Yes. Hospital systems have well-established standard interfaces – HL7 v2, FHIR following ISiK and IHE. We wrap those queries as MCP tools that CompanyGPT can call in a targeted way.
How do you ensure only approved data is processed?
Each tool has a fixed data scope that is documented and signed off during the project. In addition, roles and groups in CompanyGPT control who may invoke the integration at all.
What changes when running on NEXUS / CLOUD IT?
The functional interfaces stay the same. What differs is the network connection between your CompanyGPT environment and the hosted system, which we coordinate with your IT team and the operator.
How should such a project start?
With one narrowly scoped use case from administration, controlling or quality management. On that basis, value, effort and data protection requirements can be assessed reliably before further modules follow.
NEXUS / KIS and Your AI – GDPR-Compliant with CompanyGPT
CompanyGPT is the enterprise AI assistant in your own cloud tenant: all relevant AI models, your company data and integrations like NEXUS / KIS – centrally managed, with roles and permissions. We set up the connection together with you.
NEXUS / KIS is a trademark of its respective owner (NEXUS AG). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.