Contact

Frequently Asked Questions

What exactly is dotbase?

What is dotbase and what does it do?

dotbase is a next-generation medical workspace designed to unify fragmented systems across specialties and settings. It centralizes structured documentation, patient views, dashboards, and patient reports for coordination and continuity of care. Built on a semantically interoperable data layer, it supports data-driven work while remaining flexible enough to adapt to complex medical processes.

Is it a full HIS replacement or a layer on top?

dotbase replaces fragmented HIS modules with a single, purpose-built platform for structured documentation, patient views, dashboards, and patient reports. It is designed to align and extend existing systems without requiring a rip-and-replace approach, bridging gaps between rigid legacy components and modern clinical needs and offering interoperability and customization where traditional HIS systems fall short. While integrating seamlessly today, we build with the vision of full replacement in the future, while keeping you in full control of your infrastructure.

Is it modular, and can we start small?

Yes. We even recommend to start with a single clinic and expand as needed. dotbase is modular and designed for phased rollout.

How is it different from a traditional HIS?

Traditional HIS systems are often rigid, department-bound, and expensive to customize. dotbase is flexible, fast to implement, and allows clinicians to build and update workflows themselves. Unlike conventional systems, dotbase maintains a syntactically and semantically interoperable data layer – ensuring data can be reused across settings, systems, and analytical tools.

What clinical workflows are supported today?

dotbase supports specialty-specific templates, structured documentation, PROMs/PREMs, patient management, interdisciplinary handoffs and more. New workflows can be added without coding knowledge from clinicians themselves.

Is dotbase secure and compliant?

Where is the data stored, and can we self-host?

On-Premise Deployment and custom cloud configurations are supported. For Cloud-based Deployment Data is hosted in Germany.

Is dotbase compliant with GDPR, MDR, DVG, etc.?

Yes. dotbase is built in accordance with GDPR and MDR. Born inside Germanys largest university clinic we are deeply familiar with data privacy and medical device regulations. The dotbase plattform is not an MDR-certified product, but dotbase adheres to MDR requirements and maintains strict regulatory compliance. Specific MDR-certified modules in dotbase will become available later.

Do you have an ISMS and/or ISO 27001 certification?

Yes, our server infrastructure is ISO 27001 certified and dotbase is implementing its internal ISMS aligned with international standards.

Is patient data encrypted and secure?

All data is transmitted encrypted and all storage is access-controlled.

Does it support role-based access and audit logs?

Yes. dotbase includes granular permissions, user-level logging, and full audit trails. Optionally we can set-up custom roles with specific permissions.

Who is behind dotbase?

Who founded dotbase and what is their background?

dotbase was founded by clinicians and engineers from Charité and Berlin's startup scene, combining deep medical understanding with product and data expertise.

Is dotbase already used in hospitals or outpatient clinics?

Yes. dotbase is live in many clinics and has continuously supported real-world patient care since 2022.

Do you work with clinicians or medical institutions?

Yes. All workflows and modules are co-developed with real clinical teams and validated in daily practice.

Does this work in my hospital setting?

How long does a typical implementation take?

Initial implementation can begin in under 4 weeks. Full rollout per clinic typically takes 1–6 months, depending on scope.

Can we run a pilot in one clinic first?

Yes. dotbase supports phased implementation. Most customers begin with a focused pilot.

Can clinical teams customize workflows without coding?

Yes. The no-code builder allows medical staff to create and adapt workflows independently.

What systems can you integrate with (lab, billing, etc.)?

dotbase integrates with lab systems, scheduling, billing, EHRs, and national infrastructures using FHIR, HL7v2, and custom APIs.

How do you support onboarding and change management?

We provide co-creation workshops, role-based training, and responsive support. Our team works closely with yours to ensure smooth adoption.

What does dotbase cost?

How is pricing structured (user, clinic, module, other)?

dotbase operates on a simple pricing model: a base installation fee depending on your needs, coupled with a per-user seat licensing. There are optional paid add-ons for custom APIs and advanced features like multi-site deployments. You only pay for what you use.

Do you offer pilot or phased pricing models?

Yes. We also offer tailored pricing for pilots and early-stage projects. Please check our plans for more details.

Is implementing dotbase worth its costs?

Implementers frequently see ROI through faster documentation, reduced administrative burden, and better alignment between teams and tools. By streamlining workflows and minimizing reliance on outdated modules, dotbase should offset its costs through time savings and operational efficiency within the first year. And that is without taking improvement of quality of care and workplace satisfaction into acccount.

How does the cost compare to legacy systems or alternatives?

dotbase is more cost-effective than traditional HIS extensions or fragmented toolchains, especially when scaling in- and outpatient care and across departments.

Architecture and Interoperability

Do you support open standards (FHIR, HL7v2, etc.)?

Yes. dotbase is built on FHIR and supports HL7v2 and custom integrations.

Can we freely access and export our data?

Yes. Data can be exported at any time, in structured formats e.g. FHIR-Bulk Export.

Are APIs available for integrations or extensions?

Yes. We provide secure APIs for third-party tools and custom modules.

Can dotbase integrate with our existing HIS/EHR systems?

Absolutely. dotbase can sync with existing systems, enabling hybrid models and smooth transitions.

What is working with dotbase like?

What’s the onboarding journey like?

We guide each team through onboarding with tailored workshops, e-learning, and live support.

How are updates managed and how often are they released?

dotbase follows a continuous deployment model with bimonthly updates. You do not need to anything to get these updates.

Do you provide support, SLAs, and user training?

Yes. All plans include responsive support, onboarding, training, and optional SLAs. Please check our plans for more details.

Can our team manage and evolve workflows themselves?

Yes. Clinical users can build and adapt processes using our no-code tools. dotbase allows highly specialty-specific workflows and documentation templates tailored to every field. We may also have some templates for your specialty in our library or network.

Practical Questions

Does dotbase support multiple languages?

Yes. You can create multilingual templates and patient forms without restrictions, or run clinics in parallel with localized interfaces. The platform itself currently supports German and English, please contact us for other languages.

How should I cite dotbase in a scientific publication?

If you’ve used dotbase in the context of research and would like to reference it in your publication, please use the following format:
In Methods section: Data collection and storage were conducted using dotbase, a digital medical workspace designed for clinical environments¹.‍
In Reference list: ¹ dotbase medical GmbH, Berlin, Germany. Available at: https://dotbase.org

What are the hardware or browser requirements?

For end users you just need devices such as PCs, laptops, iPads, or smartphones running Windows, macOS, iOS, or Linux.The platform itself is built on Docker Stack and can be deployed on standard hospital IT infrastructure (e.g., virtual servers) without requiring special hardware.If your use case includes local deployment of AI models, custom hardware might be needed. Contact us—we're happy to support you with specifications and guidance.

Do you have a public roadmap?

No, we have no dedicated department that could keep this up to date yet, but we are more than happy to share all upcoming features we are currently working on in a meeting.

Get in touch

Contact information:

“Having structured documentation and patient reports all in one system streamlines my workflow, improves communication with patients, and helps me focus on what really matters – delivering better care.”

2000+

> 99 %

“Embedding interoperable, structured documentation with patient reports into clinical workflows improves quality of care and unlocks real-world data for research by reducing data collection burden.”

0 min

95 %