Store and organize any type of clinical record generated by any number of applications, and integrate everything in the unique Electronic Health Record of each patient.
Create data queries using the EHRServer Query Builder and make them instantly available from the EHRServer REST API, without writing a single line of code.
Hassle free clinical data storage and retrieval. Manage EHRs and access all the clinical information in a standardized way, from any system or application, when you need to.
EHRServer solves a very specific challenge all clinical information systems have to tackle: to build a clinical data repository.
Clinical data is complex, heterogeneous and highly hierarchic. These characteristics make it very difficult to develop repositories that are: 1. generic (can handle different types of data structures), 2. maintainable in the long term, 3. performant, 4. scalable and 5. integrable into different apps.
At CaboLabs, it took us years of research and development, trial and error, to create a solution that complies with all of those requirements.
The goal of the EHRServer is to save time and money to companies that are building their EHR/EMR/PHR systems, and try to solve the same problem again and again, with custom solutions.
With EHRServer your company can start working on apps right away, focusing on the value and features you will offer to your customers, reducing time to market, and avoiding time-wasting tasks related to solving complex problems that are already solved.
Install your own self-managed instance of the EHRServer or use EHRServer Cloud. Even if you want to develop your own CDR backend later on, using EHRServer will help you create an MVP and test your idea without investing on building a backend.
The core of EHRServer is based on the openEHR specifications. Most of the capabilities and features offered by the EHRServer are because of this.
The EHRServer should be fed with clinical document definitions called Operational Templates, or OPT for short. The OPTs define the semantics, data structures, constraints and terminology associated with each clinical document. It is basically an XML with metadata.
When client apps commit clinical documents to the EHRServer, the data is indexed for querying. Of course, those documents should comply with their definitions (OPT). A manager will create data queries using the EHRServer Query Builder, and those queries are defined using only information from the OPTs, that is all clinical concepts like Blood Pressure, Diagnosis, Physical Examination, Glasgow Coma Scale, etc.
To create queries there is no need of writing any SQL or source code. Once queries are saved, a client system can executed them using the REST API, pulling clincial data out from the EHRServer. That's it, data in, data out, all standardized, without writing a single line of code.