OpenCRVS
v1.4
v1.4
  • 👋Welcome!
  • CRVS Systems
    • Understanding CRVS
    • Effective digital CRVS systems
    • OpenCRVS within a government systems architecture
    • OpenCRVS Value Proposition
  • Product Specifications
    • Functional Architecture
    • Workflow management
    • Status Flow Diagram
    • Users
      • Examples
    • Core functions
      • 1. Notify event
      • 2. Declare event
      • 3. Validate event
      • 4. Register event
      • 5. Print certificate
      • 6. Issue certificate
      • 7. Search for a record
      • 8. View record
      • 9. Correct record
      • 10. Verify record
      • 11. Archive record
      • 12. Vital statistics export
    • Support functions
      • 13. Login
      • 14. Audit
      • 15. Deduplication
      • 16. Performance management
      • 17. Payment
      • 18. Learning
      • 19. User support
      • 20. User onboarding
    • Admin functions
      • 21. User management
      • 22. Comms management
      • 23. Content management
      • 24. Config management
    • Data functions
      • 25. Legacy data import
      • 26. Legacy paper import
  • Technology
    • Architecture
      • Performance tests
    • Standards
      • FHIR Documents
        • Event Composition
        • Person
        • Registration Task
        • Event Observations
        • Locations
    • Security
    • Interoperability
      • Create a client
      • Authenticate a client
      • Event Notification clients
      • Record Search clients
      • Webhook clients
      • National ID client
      • FHIR Location REST API
      • Other ways to interoperate
  • Default configuration
    • Intro to Farajaland
    • Civil registration in Farajaland
    • OpenCRVS configuration in Farajaland
      • Application settings
      • User / role mapping
      • Declaration forms
      • Certificate templates
    • Business process flows in Farajaland
  • Setup
    • 1. Planning an OpenCRVS Implementation
    • 2. Establish project and team
    • 3. Gather requirements
      • 3.1 Mapping business processes
      • 3.2 Mapping offices and user types
      • 3.3 Define your application settings
      • 3.4 Designing event declaration forms
      • 3.5 Designing a certificate template
    • 4. Installation
      • 4.1 Set-up a local development environment
        • 4.1.1 Install the required dependencies
        • 4.1.2 Install OpenCRVS locally
        • 4.1.3 Starting and stopping OpenCRVS
        • 4.1.4 Log in to OpenCRVS locally
        • 4.1.5 Tooling
          • 4.1.5.1 WSL support
      • 4.2 Set-up your own, local, country configuration
        • 4.2.1 Fork your own country configuration repository
        • 4.2.2 Set up administrative address divisions
          • 4.2.2.1 Prepare source file for administrative structure
          • 4.2.2.2 Prepare source file for statistics
        • 4.2.3 Set up CR offices and Health facilities
          • 4.2.3.1 Prepare source file for CRVS Office facilities
          • 4.2.3.2 Prepare source file for health facilities
        • 4.2.4 Set up employees & roles for testing or production
          • 4.2.3.1 Prepare source file for employees
          • 4.2.3.2 Configure role titles
        • 4.2.5 Set up application settings
          • 4.2.5.1 Managing language content
            • 4.2.5.1.1 Informant and staff notifications
          • 4.2.5.2 Configuring Metabase Dashboards
        • 4.2.6 Configure certificate templates
        • 4.2.7 Configure declaration forms
          • 4.2.7.1 Configuring an event form
        • 4.2.8 Seeding & clearing your local databases
        • 4.2.9 Countryconfig API endpoints explained
      • 4.3 Set-up a server-hosted environment
        • 4.3.1 Verify servers & create a "provision" user
        • 4.3.2 HTTPS & Networking
        • 4.3.3 Create a Github environment
          • 4.3.3.1 Environment secrets and variables explained
        • 4.3.4 Provision environments
          • 4.3.4.1 Building, pushing & releasing your countryconfig code
        • 4.3.5 Deploy
    • 5. Functional configuration
      • 5.1 Configure application settings
      • 5.2 Configure registration periods and fees
      • 5.3 Managing system users
    • 6. Quality assurance testing
    • 7. Go-live
      • 7.1 Pre-Deployment Checklist
    • 8. Operational Support
    • 9. Monitoring
      • 9.1 Application logs
      • 9.2 Infrastructure health
      • 9.3 Routine monitoring checklist
      • 9.4 Setting up alerts
      • 9.5 Managing a Docker Swarm
  • General
    • Community
    • Contributing
    • Releases
      • v1.4.1: Release notes
      • v1.4.0 to v1.4.1 Migration notes
      • v1.4.0 Release notes
      • v1.3.* to v1.4.* Migration notes
      • v1.3.5: Release notes
      • v1.3.4: Release notes
      • v1.3.3: Release notes
      • v1.3.1: Release notes
      • v1.3.* to v1.3.* Migration notes
      • v1.3.0: Release notes
      • v1.2.* to v1.3.* Migration notes
        • v1.2 to v1.3: Form migration
      • v1.2.1: Release notes
      • Patch: Elasticsearch 7.10.2
      • v1.2.0: Release notes
      • v1.1.* to v1.2.* Migration notes
      • v.1.1.2: Release notes
      • v.1.1.1: Release notes
      • v1.1.0: Release notes
    • Interoperability roadmap
    • Product roadmap
Powered by GitBook
On this page
  1. Setup
  2. 4. Installation
  3. 4.2 Set-up your own, local, country configuration
  4. 4.2.2 Set up administrative address divisions

4.2.2.2 Prepare source file for statistics

Previous4.2.2.1 Prepare source file for administrative structureNext4.2.3 Set up CR offices and Health facilities

Last updated 1 year ago

Next you need to prepare your statistics source file. This is a file for the statistical parameters that are used to calculate performance metrics and . You can import and create csv files in Excel or Google Drive. Using our as an example, download and create a new csv file with the statistical information for your country.\

adminPcode
name
male_population_2008
female_population_2008
population_2008
crude_birth_rate_2008
male_population_2009
female_population_2009
population_2009
crude_birth_rate_2009
male_population_2010
female_population_2010
population_2010
crude_birth_rate_2010
male_population_2010
female_population_2010
population_2010
crude_birth_rate_2010
male_population_2012
female_population_2012
population_2012
crude_birth_rate_2012
male_population_2013
female_population_2013
population_2013
crude_birth_rate_2013
male_population_2014
female_population_2014
population_2014
crude_birth_rate_2014
male_population_2015
female_population_2015
population_2015
crude_birth_rate_2015
male_population_2016
female_population_2016
population_2016
crude_birth_rate_2016
male_population_2017
female_population_2017
population_2017
crude_birth_rate_2017
male_population_2018
female_population_2018
population_2018
crude_birth_rate_2018
male_population_2019
female_population_2019
population_2019
crude_birth_rate_2019
male_population_2020
female_population_2020
population_2020
crude_birth_rate_2020
male_population_2021
female_population_2021
population_2021
crude_birth_rate_2021
male_population_2022
female_population_2022
population_2022
crude_birth_rate_2022

AWn3s2RqgAN

Central

177555

170774

348377

19.4

181676

175555

357291

19.6

188087

181116

369261

18.8

189251

182171

371480

17.6

191308

183928

375281

16.6

197533

190359

387958

17.9

143825

141233

285059

17.6

145664

142059

287723

19.3

149012

146810

295822

17.7

151786

149045

300831

16.6

152859

150197

303057

18.2

155068

139186

294255

16.9

152874

144456

297331

17.3

163391

148928

312320

17.6

387162

299071

686233

6.99

KozcEjeTyuD

Sulaka

201028

186018

387046

19

201079

187184

388263

21.1

205044

189817

394861

17.6

207035

192464

399499

18.6

213349

199019

412368

20.3

213774

197747

411521

19

187272

180532

367806

18

175569

173179

348750

18.7

305507

306748

612257

19.7

309110

309404

618515

21.6

292729

289899

582630

20.1

303743

320864

624608

20

347497

306895

654393

18.1

365242

330116

695358

16.7

356247

297534

653781

17.9

B1u1bVtIA92

Pualula

245834

229646

475481

21

245920

228128

474048

22.7

252761

234940

487701

19

253865

236282

490147

19.5

260700

241754

502454

19.2

264423

245103

509534

18

267310

259051

526363

18.8

261220

257310

518530

19.4

280519

275429

555948

18.8

284831

280377

565210

20.1

278730

273515

552247

17.6

285236

269631

554868

17.2

300896

285807

586704

15.1

269712

303358

573070

15.3

260244

308373

568617

16.1

Each row will represent a unique set of statistics for an administrative division in your country.

Notice that the adminPcode and name columns are identical to applicable levels created in the csv file in the previous step.

The next 4 columns are repeated for however many years you are able to source data from your statistical department. Each year MUST contain a minimum of 4 columns:

  • male_population_<year>

  • female_population_<year>

  • population_<year>

  • crude_birth_rate_<year>

Be careful when adding extra years to not have any spaces in your headers between the name of the header and the year key.

You can remove year blocks of 4 columns if you do not have this data, but make sure the available years that you do have run consecutively without any time gaps.

You can add statistical data to a location every year using the .

Note: crude death rate is applied globally in the step later in this documentation.

Note: At this stage, there is not too much point in you entering data more than 5 years back in time as OpenCRVS can only calculate completeness rates based on the registration information it has available. In future versions, we plan to introduce legacy data import to include historical registrations. At that point, a history of population data becomes really powerful.

Do not change or re-format the header row as the seeding process requires these names to be precise in order to parse the csv. Do not use commas in any cell and do not have any empty rows.

csv
completeness rates
statistics.csv
FHIR Location API
3.2.5 Set up Application Settings