Collection of services

orchestration of services to deliver cloud native experience

EHR.Network is composed of a collection of independent services working together to deliver the complete functionality for an EHR solution. All these services are designed to work in isolation and manage their data independently. They are also designed to be used together to achieve functional requirements through multi-service call flows.

While the functional architecture of EHR.Network is designed along the principles of an EHR architecture (EHRA) envisaged in ISO/BIS 18308 standard, the technology architecture has been designed with the Cloud Native paradigm in focus. This services architecture also implements the privacy by design principle to achieve segregation of data for data privacy.

All the services expose REST APIs that are exposed to applications through the API Gateway.

The above architecture ensures that the platform, while maintaining privacy & security through segregation of data, also ensures standardized APIs and service level clustering for cloud scale performance.

As an EHR application developer, you can use a collection of these APIs to achieve the functionality envisaged for your application.

FHIR Server

FHIR R4 native service that provides the APIs required to manage Demographic data and Masters on EHR.Network

openEHR CDR

openEHR compliant Clinical Data Repository that makes the platform unique. Scheme extension can be modeled at runtime to manage any clinical requirement.

API gateway

A Gateway level security service that that protects and manages platform services APIs. API security that includes API keys, rate limiting, bot detection that ensures QOS

Auth Server

Authentication and authorization services that implement OAuth2.0 and OIDC

Terminology

Terminology available as a service for app developers. Covers SNOMED CT, drug list(generic & branded) and lookup to ICD 10