Architecture
Last updated
Last updated
OpenCRVS technical architecture is designed using modular, event-driven . Each micro service and every OpenCRVS component is configurable, scalable and protects data sovereignty by being provisionable in on-premise private tier 2/3 data centres using included configurations.
To learn about the server hosting & network architecture required for hosting OpenCRVS visit
OpenCRVS provides:
Easy country configuration via a dedicated config microservice, simple csv files and a configuration UI.
Standards-based multi-language content management.
An automated continuous integration, delivery and testing suite.
SMS 2-Factor Authentication with well defined user role authorization privileges
Many countries may be located far from a high-quality data-centre above Tier 2.
Many countries may not legally support international data storage of citizen data on a public cloud. Getting the legal approval for external storage of citizen data requires regulatory change which can take a considerable amount of time.
Because some countries may not be able to maintain complex software independently, we are considering a SaaS solution, provided enough countries get regulatory approval. Over time, this situation appears to be slowly evolving and we are monitoring it closely.
Previously unskilled system administrators can quickly up-skill in the techniques of private cloud infrastructure management using Docker Swarm. We wanted to democratise containerisation benefits for all countries.
De-duplication management to ensure data integrity is essential to any civil registration system. A fast search engine lowers operational costs and improves the user experience for frontline staff.
The OpenCRVS microservice architecture enables continuous evolution of its business requirements.
OpenHIM is built in NodeJS and is designed to ease interoperability between OpenCRVS and external healthcare systems. It provides external access to the system via secure APIs. OpenHIM is fully compatible with OpenCRVS and can be optionally included in the stack.
A market-leading, powerful search, audit and de-duplication engine powered by .
Real-time performance analytics powered by the time-series database .
An Amazon S3 compatible object store for storing supporting documentation attachments powered by .
Increased performance by the use of , reducing HTTP requests between client and server.
A single JS, codebase for backend, desktop and mobile using for offline and low-connectivity access.
External server and application health monitoring using
Automatic SSL configuration
OpenCRVS is a full-stack that is designed to give you the lowest possible .
Our international development teams work in an Agile way, in tandem with local development resources and human-centred designers, following the methodology, to rapidly design, build, deploy, test and maintain OpenCRVS releases.
The following dependencies are automatically provisioned alongside the OpenCRVS Core in containers in a Docker Swarm on Ubuntu.
was chosen by our architects in 2018 for it's lack of requirement of other essential dependencies, it's close alignment with Docker and it's simplicity in terms of installation and monitoring on a , on bare metal servers with headless . Why not use AWS, public cloud SaaS or serverless you might be thinking?
We are working on a migration now that Kubernetes has become a more mature, easier to use and configure solution, thanks to dependencies like Helm and other plugins increasing popularity since 2018. In the meantime, Docker Swarm makes it easy to commence containerised microservice package distribution privately, automatically configures a "round robin" load balanced cluster, and provides Service Discovery out-the-box.
The OpenCRVS data layer is . FHIR is a global standard for exchanging electronic health records.
In order to support configuration for limitless country scale, OpenCRVS was designed for , built on , and aligned to a globally recognised healthcare standard.
Massively scalable and extensible, is an OpenSource NoSQL database server originally built by the OpenCRVS founding member , using interoperable v4 ( Accredited, Fast Healthcare Interoperability Resources) as standard.
We extended to support the civil registration context. Our civil registration FHIR standard is described .
OpenCRVS uses , an industry standard, NoSQL document orientated, real-time de-duplication & search engine. Lightning fast, intelligent civil registration record returns are possible, even with imprecise “fuzzy” search parameters.
ElasticSearch is also used with for application and server health monitoring.
The hyper-efficient "time series database" is used in our stack for "big data" performance insights. Millisecond level query times facilitate civil registration statistical queries over years of data, disaggregated by gender, location and configurable operational and statistical parameters.
The core of OpenCRVS is a monorepo organised using . Each package represents a single microservice. Each microservice has over 80% unit test coverage in . Following the , 1 service per container model, every package is independently scalable in a single container.
\
The microservices are written in (a strictly typed superset of JavaScript that compiles to JavaScript) and NodeJS using the framework.
Each microservice in OpenCRVS has no knowledge of other services or business requirements in the application, and each exposes it’s capabilities via secured APIs.
The microservice API Gateway uses . allows OpenCRVS to perform much faster and more responsively in remote areas by drastically reducing the number of HTTP requests that are required in order to render a view in the presentation layer. The OpenCRVS GraphQL Gateway is a JWT protected server that requests and resolves resources from into GraphQL, for easy interoperability or client consumption.
Client applications are built using and technology. This means that we can take advantage of offline functionality and native mobile features using , without the overhead of maintaining multiple web and mobile codebases and respective App/Play Store releases.
In remote areas, registrars can save a configurable number of registrations offline on their mobile phone, using .
The is the interoperability layer of choice in the and interoperates natively using .
