Structure & Versioning of the Standards
Last updated
Last updated
It is distinguished whether some standards can be reused and are valid across mutiple interfaces (which would be stored in the common space/main page that you are looking at) or only for their own respective interface (which would be stored in the respective space of their interface linked on the left, e.g. for CRVS-specific in CRVS with SP-MIS Standards)
For instance, a name may be defined always in the same manner for multiple different workstreams which would classify it for common, whereas a Person could be slightly defined differently depending on the use case (Payment, CRVS, Social Registry, etc.) hence it would fall under interface-specific standards and be stored there.
Each standard is split up into three main parts:
The overall standards are versioned directly in the GitBook via the naming of the space. Hence CRVS v1.0 would be the first version of the CRVS with SP-MIS Standards.
The versioning of the API's is explained in the Design Principles section.
You can find all previous versions of the standards in the respective "Previous Versions" Page at the very end of each space. For instance, this is the page of the CRVS with SP-MIS Standards.
Process
Standards serve as a Proof of Concept of the implemented data and API interface-specific standards. Hence, if the standards would be implemented for some social protection use cases - how would the process flow look like? These process flows serve as examples that have been considered one of the most relevant, but are of course not exhaustive.
Data
API
Standards contain the different specifications per interface that are needed for information exchange. Valid across all interfaces are considerations regarding Design Principles, including Security and Versioning.
Standards to ensure a shared language and format for data used across diverse systems and organizations. They are further divded into the like e.g. a Person (containing attributes like first name, sex, etc.),(containing a list of possible values for an attribute like marital status) and (e.g. is this a String or a decimal and for some types, e.g. String how to format them, e.g. a date).