What is EHRbase?
EHRbase is an open source software backend for clinical application systems and electronic health records.
It is mainly based on the openEHR specifications, an open platform architecture for developing flexible and interoperable eHealth systems. Applications based on openEHR share a common information architecture, i.e. they “speak” the same technical language to express clinical information. This enables interoperability between applications by design.
EHRbase is also part of the openEHR community, which aims to break down barriers for vendors, hospitals, regional and national eHealth programmes, researchers and others to adopt open standards and thereby foster the establishment of semantic interoperability. As an alternative to proprietary platform products or self-development, EHRbase aims to provide organisations with a modern, standards-compliant and rock-solid foundation for their next-generation eHealth solutions.
EHRbase is proudly developed by vitagroup, a leading German healthcare IT company with over 300 experts working on the future of healthcare IT, in close collaboration with MHH Hannover Medical School (Medizinische Hochschule Hannover) and HiGHmed. EHRbase is used in vitagroup’s enterprise offerings HIP EHRbase and HIP CDR. For any mission-critical solutions, environments, and deployments, vitagroup provides professional support, consulting services and advanced features.
Creating the right data environment for tomorrow
Why use EHRbase?
Features
The following is a non-exhaustive list of the various features provided by EHRbase. More will be added with each major release:
- openEHR Reference Model 1.0.4
- Transactions
- openEHR REST API
- EHR
- EHR_STATUS
- VERSIONED_EHR_STATUS
- COMPOSITION
- Flat Format
- Canonical XML
- Canonical JSON
- VERSIONED_COMPOSITION
- DIRECTORY
- CONTRIBUTION
- QUERY
- DEFINITIONS
- WebTemplate Format
- ADL 1.4 Template
- Stored Queries
- EHRbase Admin API
- SECURITY
- OAuth 2 Support
- Basic Auth Support
- SSL
- EHR (physical delete)
- COMPOSITION (physical delete)
- DIRECTORY (physical delete)
- TEMPLATE (physical delete, forced overwrite)
- SECURITY
- EHRbase Status API
- Metric and Monitoring Endpoints
- ATNA Logging
- EHR
- Composition
- Query
- User Login
- Attribute Based Access Control Connectivity
- Configurations for Cloud Deployment
- Data Validation
- Based on openEHR Template
- Based on FHIR Terminology Server
- Archetype Query Language
- Aggregation functions (count, max, min etc.)
- Contains operators AND, OR and nesting
- ORDER BY
- Partial Paths Queries
- Filter by name attributes
- Embedded FHIR Terminology Server calls
- Software Development Kit
- Auto-generated DTO Java classes from openEHR Templates
- (De-)Serialization from/to DTOs
- Queries based on DTOs classes
- AQL parser and serializer
Connect, share & learn
Join the openEHR forum
It’s people like you who have made EHRbase more than just code. This is your community. Here you can ask questions, join the discussion and share your knowledge with others.