Connection
Connectors link basebox to your systems.
The AI finds answers where your data lives, with the permissions of the person asking.
For specialists: Our connectors use MCP (Model Context Protocol), the open standard for connecting AI applications to data and tools.
All connectors from our library are included in your licence.
Your administrator switches them on; new ones are added all the time at no extra cost.
Clinical

Communication servers
Council information




Document management and e-files



Tickets and requests
Geodata
Finance

For all sectors
Documents and knowledge

Email and calendar
Projects and contacts
Tools
One connection, many systems.
Many hospitals already bring their data together: through a communication server or a data platform based on openEHR or FHIR. basebox can connect to either and then reaches what already flows together there, read-only by default.
Many administrations link their specialist applications through an integration platform. basebox can connect to it and then reaches the systems already connected there, read-only by default.
We assess the effort free of charge. The price follows the price list.
If your system is missing, we build the connector.
If a system has an interface, we connect it. The concept is free of charge; after that you get a fixed price. The connector is usually ready within five working days. If we build a new connector and it may go into our library, you pay half, and it is then available to all customers.
| Connector | Price | May go into the libraryiApplies to newly built connectors. If we may add it to our library, you pay half. Only the technical connection goes into the library, never your configuration, credentials or data. |
|---|---|---|
| Already in our library | €0 | – |
| Vendor provides a connector | €1,900 | – |
| New, with a documented interface | €6,900 | €3,450 |
| Complex systems, such as SAP or HIS | €13,800 | €6,900 |
One-off, list prices, net plus VAT.
Every access runs with the permissions of the person asking.
Your software uses basebox.
Through an OpenAI-compatible interface, without the user interface.
Frequently asked questions
Connectors from the basebox library are included in every licence, including all new ones. Costs arise only if we build a new connector for your system: once, according to the table above. If a newly built connector may then go into the library, you pay half.
If your system has an interface, basebox builds the connector. The concept is free of charge; you get a fixed price between €1,900 and €13,800. It is usually ready within five working days; for complex systems we state the duration together with the fixed price. If we build it new and it may go into our library, you pay half.
Your administrator switches a connector on for your organisation in basebox. After that, each person signs in with their own account and sees only what they are allowed to see there anyway. If the system offers OAuth, basebox receives an authorisation for this, not a password.
Yes. Our FHIR connector (FHIR R4) is built on the ISiK specification of gematik, the German interoperability standard for hospitals, and we adapt it to any ISiK stage. What it can read in your hospital is determined by your system: which ISiK stage and which modules the vendor has implemented, and what your hospital releases. In a data integration centre, the core data set of the German Medical Informatics Initiative applies instead of ISiK, plus vendor profiles. So we clarify in advance with you and the vendor which data your system provides, which data basebox may read and how it signs in, and adapt the connector to your system. “basebox supports FHIR” therefore does not mean basebox is already connected to your hospital information system. The adaptation counts as a complex connector: fixed price €13,800, half if the connector may then go into our library. The concept is free of charge.
HL7 is the organisation that publishes FHIR, and also the name of its older messaging standard HL7 v2. Via HL7 v2, the hospital information system reports events such as an admission or a finding, and the communication server distributes them to laboratory, radiology or billing. These messages are not meant for targeted queries. basebox therefore reaches this data through a query your communication server provides, for example via its FHIR interface, or through the FHIR interface of the hospital information system.
Yes, basebox connects such data platforms through their interfaces. These platforms store clinical data according to the open standard openEHR, some also according to FHIR, and offer queries through a REST interface, with openEHR using the query language AQL. As with the FHIR connector, we set up the connection for your hospital: which data basebox may read and how it signs in, agreed with you and the provider. We build the connector at a fixed price according to the price list; the concept is free of charge.
basebox uses network drives differently from connectors: we connect network drives to basebox during setup, with one account for the whole organisation and read-only; several drives are possible. Network drives are only available when basebox runs on your server, not in the cloud. A drive is used in an app: whoever builds the app chooses a folder under Files, optionally only certain file types such as PDF. basebox takes the files into the app and syncs them daily, weekly or manually; deleted files also disappear from the app. The permissions on the drive do not apply per person: anyone allowed to use the app gets answers from all files taken in. So you decide who sees what by sharing the app. Anyone allowed to build apps sees all connected drives. The OrbisF1 help pages work the same way.
Not by default; basebox only reads. We agree write access with you and enable it selectively.
Last updated: