Use Dedalus ORBIS with AI via MCP
In many hospitals across the German-speaking region, ORBIS is the central hub for documentation, medication and billing. Dedalus does not provide an MCP server for it, so the link to CompanyGPT is built as an integration project on HL7 v2, ISiK FHIR and IHE profiles.
What is Dedalus ORBIS?
ORBIS is the hospital information system of Dedalus HealthCare GmbH, based in Bonn, Germany, part of the Italian Dedalus Group and originally the Agfa HealthCare business. The system covers clinical documentation, medication processes, operating theatre planning, nursing and billing; ORBIS U is the modernized product generation. It is typically operated in the hospital’s own data centre.
A large share of a hospital’s operational knowledge therefore sits inside the HIS – and it is subject to strict legal requirements. For AI use, narrow access matters more than broad access: defined data slices for defined tasks in administration, medical controlling or quality management, with a documented legal basis and traceable permissions.
Connection at a Glance
- MCP server
- None available – individual integration
- Interfaces
- HL7 v2, FHIR/ISiK (Section 373 SGB V), IHE profiles incl. XDS
- Authentication
- Interface accounts inside the hospital network, project-specific
- Operating model
- On-premises (ORBIS U as the modernized generation)
- Permissions
- Fixed queries per tool, role-based control in CompanyGPT
How to Connect Dedalus ORBIS to CompanyGPT
Dedalus does not provide an MCP server for ORBIS. Using the system with CompanyGPT therefore does not rely on an off-the-shelf component but on an integration project built around the interfaces your hospital already runs.
In practice these are HL7 v2 messages via the communication server, FHIR resources from the ISiK interfaces that Section 373 SGB V makes mandatory for German hospitals, and IHE profiles such as XDS for document exchange. From these sources we model MCP tools with fixed, predefined queries: an agent reads exactly the fields intended for the approved use case, and nothing beyond that. Aggregated or pseudonymized views are often the more suitable basis than individual case records.
Interface accounts are issued and logged by your IT department. Inside CompanyGPT, your administrators additionally decide by role and group which departments may use the integration. We configure read-only access by default; any extension, in particular write access to ORBIS, requires explicit approval and coordination with your data protection and hospital management functions.
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 Dedalus ORBIS
Prepare quality reports
Quality management has key figures for internal reports and external quality assurance compiled, and gets pointers to gaps in the documentation.
Structure audit requests
For requests from the medical review service, the agent collects the relevant documentation of a case and prepares it for review by the responsible physician.
Keep track of theatre planning
Operating theatre management queries utilization, free capacity and rescheduling in chat instead of generating a new report for every follow-up question.
Frequently Asked Questions
Dedalus ORBIS and AI – the most important answers
Is there an MCP server for ORBIS?
No. Dedalus does not offer an MCP server for ORBIS. Access from CompanyGPT is built individually on the hospital interfaces already in place.
Which interfaces do you use instead?
HL7 v2 via the communication server, FHIR via the legally mandated ISiK interfaces under Section 373 SGB V, and IHE profiles for document exchange. We expose these calls to CompanyGPT as MCP tools.
Which data does an AI agent get to see?
Only the fields configured in the respective tool. Many analyses work with aggregated or pseudonymized data. You define the scope together with your data protection officer before the project starts.
How is the hospital network involved?
ORBIS stays in your network and CompanyGPT in your own cloud tenant. Both are joined by a dedicated, encrypted link that we set up together with your IT and network teams.
Can the AI create entries in ORBIS?
The interfaces make it technically possible, but we do not configure it by default. Write access to a hospital information system requires explicit approval, clear responsibilities and a documented review.
Dedalus ORBIS 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 Dedalus ORBIS – centrally managed, with roles and permissions. We set up the connection together with you.
Dedalus ORBIS is a trademark of its respective owner (Dedalus HealthCare GmbH (Dedalus Group)). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.