Cloud EHRServer (beta) EN | ES

Get started

Currently we are only accepting sign-ups for the Beta Partners Program. Soon we will launch our service plans for general usage.

Enrollment process

To sign-up send a request to participate in the Beta Partners Program from here. After your request is approved, you'll need to confirm your account and start using the CloudEHRServer.

Trying out CloudEHRServer

We have two staging servers that we use for testing and demos, that are publicly accessible. You can create a test account directly on those servers. Consider that those are small servers, with that we mean that are really sloooow, and might not have the latest version of the EHRServer installed, but we try to keep them up to date. Also the service might not be available 100% of the time.

Usage and Management

In our Learn section you will find documentation and guides that will help you in the process of understanding how the EHRServer woks and how to get the most out of it.

Also check the latest demo of the EHRServer:

How does it work?

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.

Simple as:

  1. Create a clinical document definition
  2. Upload the definition to the EHRServer
  3. Create data queries based on document definitions
  4. Integrate the EHRServer API in your apps
  5. Commit some data
  6. Query and display your data

Main features:

  1. Web Console for simple management
  2. Full audit access for traceability
  3. Versioned clinical documents
  4. Service Oriented / REST API
  5. Supports XML and JSON formats
  6. Query Builder from the Web Console
  7. Supports any structure of clinical document
  8. Multitenant
  9. Open Source
  10. Compliant with the openEHR standard

Continue learning