This guide will help you understand how to store clinical data in the EHRServer, using the commit service, and diferent ways to test that service.
This guide will show how to work with Operational Templates (OPT) to generate and send data to the EHRServer. The main role of the EHRServer is clinica data storage, so the data commit service is one of the most important functionalities of the EHRServer, and it's key to know how it works in order to use the EHRServer successfully.
These resources will help you test the data commit to the EHRServer:
From the EHRs section you can manage existing EHRs and create new ones. It is recommended that the EHRs are created using the REST API, but to have full management abilities, we decided to provide a user interfaces in the Web Console to create EHRs manually.
On the EHR Details screen you can see all the Contributions to the EHR and access it's clinical documents. Don't worry, this information is 100% anonymous. Check our guide about this.
The Versions represent clinical documents that are versioned, so for the same clinical document (or Composition in the openEHR terminology), you can have more than one Version. On this section you can access all the Versions for Compositions of all the EHRs on the current Organization. This allows yo uto check which Composition where changed and under which circumstances, enabling full audit of the clinical information.
On this section you will find the logs of each change to each EHR of your Organization. This in combination with the Versions gives you full Audit abilities. So you have full control over what was added or changed, when, from where, by whom, etc.
The EHRServer gives you full access to all the information stored in the EHRs of each one of your organizations. This allow to develope apps that can use this information, without dealing with a lot of services and data formats.
From the Web Console, you can create queries to return clinical documents or just data points. Before saving the queries, you can test the queries with live data, and save the query when it returns what you need. When a query is saved, it can be executed form the REST API, so client apps will access the same data you saw when tesing que Query from the Web Console.
Queries are created for an Organization. If you want to allow Users from many Organizations to use the same Query, you can share the Query between your Organizations.
On this section you can manage the Operational Templates (OPT) of your Organization. An OPT is a clinical document definition, and is part or the openEHR specifications. OPTs are what makes the EHRServer so generic, and the base of the querying feature: data queries are created based on metadata contained in the OPTs.
On the openEHR fundamentals you can find more information about the tools needed to create OPTs. But don't worry, we provide a common set of OPTs to get you started, and we cna help you creating new ones, so you can extend your EHR capabilities.