The main components are: a Vendor Neutral Archive, a REST API and an administrative Web Console. It provides everything that you need to store, query, retrieve, manage and audit clinical information securely, privately and in a standardzed way.
The CloudEHRServer enables the creation of many types of clinical applications for clinical data entry, clinical data visualization and clinical data analysis. Your clinical app backend is ready, so you can focus on your app features.
On the learn page you will find documentation and guides that will help you in the process of understanding how the CloudEHRServer woks and how to get the most out of it.
Also check the latest demo of the EHRServer:
The core of the CloudEHRServer is based on the openEHR specifications. Most of the capabilities and features offered by the CloudEHRServer are because of this.
The CloudEHRServer 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 CloudEHRServer, the data is indexed for querying. Of course, those documents should comply with their definitions (OPT). A manager will create data queries using the CloudEHRServer 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 CloudEHRServer. That's it, data in, data out, all standardized, without writing a single line of code.