Standards

Overview of how OpenCRVS uses best-practice technology standards

Because OpenCRVS is a core component of Digital Public Infrastructure, we are obsessed with conforming to good, existing standards.

CR Standards: Digital Convergence Initiativearrow-up-right

OpenCRVS are a Standards Committee Member arrow-up-rightof the Digital Convergence Initiative, CRVS and SP-MISarrow-up-right interfaces. We helped author these standards and interoperate with social protection systems such as OpenSPParrow-up-right.

Centre for Digital Public Infrastructurearrow-up-right - G2PConnectarrow-up-right

OpenCRVS has contributed to and conforms to the G2PConnect standardised APIarrow-up-right using the DCI payloads above.

Data

By using FHIRarrow-up-right as a standard for our NoSQL datastore, Heartharrow-up-right and the OpenHIEarrow-up-right standard interoperability layer OpenHIMarrow-up-right, OpenCRVS seamlessly connects civil registration to health services and other systems. We can receive birth and death notifications from the hospital setting and expose registration events to any other technical system, such as National ID, via our FHIR standard API gateways.

FHIRarrow-up-right was created by Health Level Seven International (HL7)arrow-up-right, a not-for-profit, ANSI-accredited, standards organization dedicated to providing a comprehensive framework and related standards for the exchange, integration, sharing and retrieval of electronic health information that supports clinical practice and the management, delivery and evaluation of health services.

We have extended FHIR's model to include custom codes and extensions that assist the Civil Registration context. To understand more about how and why we use FHIR, click here.

Interoperability

Systems can interoperate with OpenCRVS using FHIR or via Webhooks which follow WebSubarrow-up-right process and standards. Our friends at MOSIParrow-up-right have demonstrated ease of integration with OpenCRVSarrow-up-right using these methods.

I