Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requesting and approving a correction request #3601

Open
jpye-finch opened this issue Jun 28, 2022 · 0 comments
Open

Requesting and approving a correction request #3601

jpye-finch opened this issue Jun 28, 2022 · 0 comments
Assignees
Labels
Milestone

Comments

@jpye-finch
Copy link
Collaborator

jpye-finch commented Jun 28, 2022

Problem statement

Different countries have different processes for correcting a record. Most of the time an agent makes the correction sends it for approval by the Registrar. Currently OpenCRVS only supports the option for a Reigstrar to directly make the correction.

Proposed work

  • All corrections by Registration Agents must be sent for approval
  • Reg Agent: Completes correction flow and ‘Sends for approval’
  • Request is sent to Registrar(s) in the same Office
  • New record status: Pending correction
  • Correction request appear in Registrar’s Ready for Review workqueue?
  • Correction request can not be updated. Just approved or rejected
  • Approved correction status changed to Registered
  • Email/SMS notification of decision to Submitter
  • Registrar: Can find a record and ‘Correct record’ (as they can to day)

https://www.figma.com/file/O6PevbBv0lApmXWYotR8sf/OpenCRVS-Design-Specifications-v2?type=design&node-id=7088%3A3797&mode=design&t=9J8DZFeliKIr5Gz7-1

User stories

(How the product should work for various user types)

Future work

  • Correction approval is dependent on what field is being corrected eg. date of birth requires approval
  • Correction approval is done by someone from another office
  • Flagging record corrections to external systems (eg. national ID system)

Research

  • Insights from Kenya:
  1. When one registrar makes a correction, a different registrar reviews and approves (not the same guy who amends approves the correction). Used for accountability. They also have an internal tracker (Received by; Recorded by; Correction done by; etc)
  2. Registrations and corrections of vital records are decentralised. Happen within a district (sub-county) and are independent of other registry offices. The highest type of approver for corrections is the head of the sub-county/district office. Other officers above district level are not involved in registrations.
  3. They consider any change a correction. Corrections / Changes follow the law; court order (interprets what a change is); for example, Correction on the basis of error, correcting an entry in a record which shouldn't be there, for example, if the DNA test proves the father is a different person from the one listed),

Findings from the product council:

  1. Some fields require higher level approval other than the registrar
  2. Registration Agents can make correction requests for approval by the registrar
  3. Some fields must not be editable after registration (for example place of birth)
  4. Need to add configuration settings to toggle on/off questions in the form that require a higher level of approval
  5. Need to create a higher level of approval role in the system? Will this affect work queues? Will tag the record "correction " to separate it from other records in the work queue requiring approval?
@jpye-finch jpye-finch removed the Epic label Feb 27, 2023
@jpye-finch jpye-finch changed the title Correct record v2 Correct record v2 (requesting and validating a correction request) Aug 10, 2023
@github-project-automation github-project-automation bot moved this to In Design in OpenCRVS Core Nov 21, 2023
@jpye-finch jpye-finch added this to the v1.4.0 milestone Nov 21, 2023
@jpye-finch jpye-finch changed the title Correct record v2 (requesting and validating a correction request) Requesting and approving a correction request Nov 21, 2023
@jpye-finch jpye-finch moved this from In Design to Completed in OpenCRVS Core Nov 21, 2023
@jpye-finch jpye-finch changed the title Requesting and approving a correction request feat: requesting and approving a correction request Nov 22, 2023
@jpye-finch jpye-finch changed the title feat: requesting and approving a correction request Requesting and approving a correction request Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants