Use Case: Fast Prototyping and Proof of Concept

There are many scenarios in which the EHRServer will help to build a functional prototype or MVP fast, adapting it to your scpecific requirements without writing a line of code for the backend.

1. Your company/organization wants to build apps for health care, that will be used on multiple platforms (mobile iOS & Android, web, desktop, etc.)
2. Your company is a software factory and needs to show a working prototype to a potential new client or an investor
3. You are planning a live demo of your apps and need a way to share clinical data between them

EHRServer is the perfect complement to allow your ideas come to life. Instead of worrying about the backend, how data will be stored, how it will be shared between platforms and devices, and learning how to implement the openEHR standard, just delegate that to the EHRServer, use it as a backend service, and focus on delivering features to your customers and end users. Either way, they won't see the effort you invested on building a backend, an will focus on what they see and how your apps can be used.

Get it done fast!

To adapt the EHRServer to your needs, just follow these steps:

1. Define the contents of your records: go to the openEHR Clinical Knowledge Manager and pick the content (openEHR Archetypes) that will be part of your app.
2. Aggregate the content into records / documents: create a document definition (Operational Template or OPT) with the content you selected from the CKM. You can use free tools to do that, like the Template Designer. We can help you with this, let us know!
3. Load your OPTs into the EHRServer: go to the Templates section on the EHRServer Web Console and upload the OPT. Now the EHRServer is able to receive data that follows your clinical document definition!
4. Generate some test data: use our openEHR-OPT project to generate sample XML instances that follow the structure in your OPTs. Check the README.
5. Load some sample data: use our Insomnia REST Client tests to commit some generated documents to the EHRServer. This will help you understand how the REST API works to start committing data from your own apps. Here you can find the test script.
6. Use the generated documents in your app: allow your app to generate clinical documents, or to inject data using the ones you generated as data templates. You can fill the data in the XML from data users enter in you app UI.
7. Use integrate the commit API in your app: you can generate an API Key from the EHRServer Web Console (from your organization's view), and use that key to authenticate your requests to the REST API, then just send the clinical documents generated from your app, to the commit service.
8. Get your data out!: you will be able to create any number of data queries to get data from the EHRServer and display it in your apps, even on a different app than the one that generated the data. This is key to support many platforms and devices and the base for data sharing between apps. Queries are created from the EHRServer Web Console, just go to the Queries section on the EHRServer, and create a new query. Then queries can be executed from the REST API, you just need the query UID.

That's it!, data in, data out. Adapted to your specific needs, using a simple REST API, being compliant with the openEHR standard, and without writing a line of code for the backend.

For more details, check the latest demo of the EHRServer.