Bundle requirements from all sources
The agent reads requirements specifications, tickets and minutes and merges identical requirements. It sets contradictions between departments side by side.
312 requirements from 3 sources, 47 duplicates mergedThe core system is end-of-life and the date is set. The requirements are scattered across the departments.
Supports the re-tendering of the hospital information system: requirements, procedure type, deadlines.
Public administration
Four processes that take up the most time today
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
Sovereign hosting in Germany, single-tenant from the first user.
Legal, tax and compliance expertise for legally sound deployment.
Advisory and implementation for the public sector, starting with the AI readiness assessment.
The requirements exist, just not in one place.
Every department has written down its wishes at some point: in the old requirements specification, in a ticket, in the minutes of the system meeting. For the procurement documents this has to become one consistent list, and in parallel the procedure type and its deadlines have to be fixed. Together they make up the lead time that has to fit before the end-of-life date.
14departmentsEach brings its own requirements for the future hospital information system.
3legacy sourcesRequirements specification, ticketing system and minutes describe the same thing in their own language.
1procedure typeDeadlines, the notice and the entire timeline hang on it.
9 monthslead timeThat is how long preparation takes up to the notice, before the deadline starts to bite.
If the requirements from all sources are bundled and the timeline is anchored to the procedure type, preparation time falls by 40%.
The 40% is this agent's headline figure. Fourteen departments and nine months of lead time describe a typical procurement for a hospital information system; they are not a measured value.
Three steps through the process.
The agent presents requirements, procedure variants and timeline in one bundle; the procurement office chooses the procedure.
Compare procedure variants with their deadlines
The agent sets the eligible procedure types side by side with their deadlines. For every deadline it names the reference in the procurement rules.
Comparison of 2 variants, 7 weeks' difference in deadlinesPresent the timeline for agreement
The agent plans the milestones backwards from the end-of-life date. The procurement office chooses the procedure type.
zeitplan_kis_vergabe_2026.xlsx, 11 milestones, 6 weeks' bufferWhat the agent does not do.
It does not choose the procedure type.
It compares the variants with their deadlines and references. The procurement office makes the choice.
It does not evaluate bids.
It prepares the requirements and the timeline. Evaluation and award rest with procurement management.
It publishes nothing.
The notice stays a draft in the case. The procurement office triggers it.
Connected systems
- Procurement management
- IT ticketing system
- document management
Operations
- Deployment modelEU cloud, private cloud or on-premises
- Data processingGDPR-compliant, no model training on your data
- Responsible teamsIT Management, Procurement Office, Executive Management
The questions that come up before the first meeting.
How quickly is the Hospital Information System Tender Agent ready to use?
A pilot typically runs on your own data within 4 to 6 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.
Where is the data processed?
EU cloud, private cloud or on-premises. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.
Where does the figure “40% less preparation time” come from?
It is based on experience from comparable projects and process benchmarks, not a commitment. We work out the realistic effect for your organisation during the assessment before the pilot.
Related agents.
- Hospital Digital Obligations Agent45%less evidence effortIT management, medical controlling, executive management
- Hybrid DRG Routing Agent50%less revenue leakageMedical controlling, billing
- AI Regulation Agent50%less review effortCompliance, Data Protection, IT Governance
- NIS2 Classification Agent50%less review effortInformation security, IT management
- KRITIS and NIS2 Agent50%less evidence effortInformation security, IT management, compliance
- MD Review and Coding Agent50%less review effortMedical controlling, clinical coders