Products
HealthFireKit™
Real-time data processing in healthcare – reliable, traceable, interoperable.
Edge-native. 100% FHIR®-compliant. Efficient, auditable, and flexible.
HealthFireKit™ processes health data where it originates – in real time, securely, and transparently.
New speed at the point of care – for privacy, interoperability, and minimal latency.
💡 No lock-in, no workarounds: FHIR® on 100% web technology – enhanced by MCP for context-driven, explainable agents directly on site.
Where data arises, intelligence arises.
Edge with TypeScript. FHIR® without compromises. Real-time capable. Trustworthy.
In the past: “As long as it works.”
Today it’s clear: architecture and tech stack define scalability, security, and connectivity.
— The atollee team builds the technological foundation —
- HealthFireKit™ provides a reliable, modular foundation for demanding environments – so teams can focus on what matters: real use cases.
- Event Sourcing, CQRS, and Domain-Driven Design create sustainably maintainable structures – avoiding technical debt.
- Stack: next-generation web technology, edge-first, end-to-end TypeScript – from backend to frontend. Fully FHIR®-compliant, modular, and without platform lock-in.
- Extensions via auditable plugins for agents, apps, and business logic – standardized, FHIR®-compliant, and MCP-oriented.
💡 A foundation for scalable, transparent, and future-proof solutions.
Consistently FHIR® – without interpretation.
No workarounds.
Many implementations call themselves FHIR®-compliant but remain fragmented. They create FHIR facades for static use cases – extensions become complex and costly.
— HealthFireKit™ is different —
Every deviation from the FHIR® specification is treated as a bug – and fixed. Development is test-driven against community specifications with atollee’s detailed test kits. Custom business logic can be implemented quickly, resource-efficiently, and traceably – reliably and predictably.
Test-driven. Standardized. Predictable.
No surprises in operation. No interpretation in code.
HealthFireKit™ is developed test-driven – based on extensive test kits from the FHIR® community specification and beyond. All components, interfaces, and extensions are continuously tested automatically.
— FHIR® and MCP are structurally anchored: reproducible, verifiable, consistent —
atollee’s test kits cover thousands of precise scenarios – from structural and terminology checks to complex data flows.
For agent systems, full compliance is critical – it forms the basis for context-sensitive, traceable, and rule-based actions.
Model Context Protocol – Context, Control, Clarity.
No black-box AI. No shadow logic.
Many AI integrations look impressive – but are hard to explain, poorly controllable, and loosely embedded.
— HealthFireKit™ does it differently —
With Model Context Protocol (MCP), interactions are transparent and rule-based. Agents don’t access raw data but clearly defined contexts – with structured permissions, full logging, and standardized release. Actions happen where they matter: close to the process, embedded in clear rules.
Agents capture context, follow rules, and act efficiently.
They work in the background – so professionals can act in the foreground.
One backend, one language. No friction.
TypeScript at the edge.
A unified codebase enables seamless development – no barriers between backend and frontend.
- TypeScript end-to-end reduces complexity and maintenance.
- Clear responsibilities – aligned directly with users, without unnecessary handoffs.
- Modern web technology for high-performance, scalable applications.
💡 A unified stack for more speed and efficiency.
Real-time. Truly secure.
- No cloud latency – data is processed instantly.
- Data minimization & privacy-by-design – sensitive data stays where it is needed.
- Zero-trust security – encrypted, traceable, strictly authorized.
- Cloud, EHRs, and hospital systems as single source of truth – intelligent, secure synchronization while maintaining data sovereignty.
💡 More speed, more security, more control.
What makes HealthFireKit™ stand out
100% FHIR®-compliant
Consistent implementation of the specification for maximum interoperability and future security. Deviations are treated as bugs.
FHIR Release 6 ready
Architecture and tooling prepared for current and upcoming FHIR versions.
Edge-optimized & high-performance
Processing directly at the point of care – minimal latency, maximum efficiency.
Modular & flexible
Plugin-based extensibility enables tailored solutions without lock-in.
Auditable plugins for agents & logic
Agents, apps, and business logic integrated in a standardized and traceable way – with direct MCP integration.
MCP for context-driven AI
LLMs and agents access approved, context-related data – secure, auditable, rule-based.
Terminology service
Supports SNOMED CT, LOINC, ICD-10 and more for precise, interoperable data.
Validator service
High-performance validation according to specification incl. profiles and terminologies.
Test-driven development
Standardized test environment with atollee test kits for automated, continuous validation.
Event Sourcing, CQRS & DDD
Clear separation of concerns, robust history, and sustainable extensibility.
Zero-trust architecture
Strict access controls, data minimization, and full auditability.
OAuth 2.0 / SMART on FHIR®
Standards-based authentication and authorization for FHIR resources.
RBAC/ABAC & identity integration
Fine-grained permissions, prepared plugins (e.g., Keycloak, Ory).
Decentralized processing, centralized consistency
Real-time locally, intelligent synchronization to central systems (SSoT).
EHR connectivity
Planned standardized integration into electronic patient records.
Monitoring & developer tools
Live metrics, audit logs, and plug-&-play integration (e.g., Grafana®).
💡 The full FHIR specification brought to an edge-native, modular architecture – standards-compliant, scalable, and flexibly configurable via plugins.
HealthFireKit™ in action: Deterministic vs. explorative tasks
Deterministic – reliable, structured data and process-oriented workflows with FHIR
Everything that can be clearly defined, standardized, and secured with structured FHIR data. Processes are traceably documented and audit-proof – crucial for privacy, billing, clinical documentation, regulatory communication, and quality assurance.
- Structured medical reports are generated automatically – in a uniform, reusable format.
- Every change is stored – tamper-proof and fully traceable (audit trail).
- Access rights are context-based: only authorized persons see specific information.
- Patient data is clearly linked – even in mobile or distributed use.
- Diagnoses and lab results are coded uniformly (e.g., SNOMED, LOINC) – machine-readable & interoperable.
- Legal requirements (e.g., for DiGA or research) are technically enforced – not just organizationally.
- Digital consents can be granted selectively – e.g., for specific providers or research purposes.
- Registries, studies, or QA receive automatically validated data – standards-based & seamless.
- Second opinions are automatically supported – full records, selectively restricted access.
- Hospitals, practices & systems can be connected in a legally compliant way – without proprietary solutions.
- Medications are documented in structured form – incl. interaction detection.
- Billing data can be exported automatically – for insurers or authorities.
- Interfaces to public reporting systems (e.g., infectious disease control) are standardized.
- Devices deliver automatically readable data – no manual transfer.
- Data from devices or apps is captured and used in a controlled way.
- Protection of sensitive content (e.g., HIV, abortion) is rule-based.
- Version control for all documents – clear history and recoverability.
- Offline use possible – e.g., during outages, disasters, or mobile deployments.
- Decentralized, rule-compliant processing – independent of a central data center.
- Planned: integration with national or private EHRs – structured, secure, standardized.
Explorative – context-aware intelligence & adaptive AI with MCP
This is where AI and agents unfold their potential – based on structured data in the right context. It’s about understanding, suggesting, learning, and supporting – rule-based, transparent, and traceable. The link: the Model Context Protocol (MCP).
- Suggestions for diagnoses or billing codes – context- and patient-specific.
- Individual consent texts are generated appropriately – understandable & legally compliant.
- Medical terminology is explained to patients automatically – clear and trust-building.
- Early detection of risks – e.g., cardiovascular or metabolic.
- Identification of care gaps – e.g., missing follow-ups or duplicate tests.
- Smart appointment suggestions – incl. availability & travel.
- Prioritization of important info – e.g., abnormal findings or critical changes.
- Warnings of possible complications – e.g., delirium, sepsis, overdoses.
- Therapy recommendations based on evidence and individual data.
- Learning from workflows – hints for process improvements.
- Contextual questions (“What’s missing here?”) – clear answers.
- Comparison with similar cases – what worked there?
- Suggestions for suitable studies – incl. inclusion/exclusion criteria.
- More efficient routines – e.g., nursing or ward rounds.
- Assistance with OR/round documentation – saves time & ensures quality.
- Integration of external context data – e.g., weather for asthma/migraines.
- Detection of technical errors or security patterns in logs.
- Why-explanations (explainable AI) for suggestions.
- Improved triage – e.g., ER with context data.
- Offline use – e.g., in disaster response or blackouts.