Page Comparison

Use Case Step

Use Case: PostPartum and Infant Care, Step: Registration (provide link to UC when complete)

Preconditions

(list of conditions that MUST be met in order to be able to successfully execute this process)

•  The government-accredited health worker has successfully logged into the MCTS government portal(Registration BB) and has the necessary authorization to complete the registration process of the mother and child into the postpartum care program.

• Data sharing agreement between Registration BB and respective registries where information is queried from has been signed (contract) and respective REST API services in Information Mediator has been opened to Registration BB.

• The mother and newborn have already been registered in a national identification system (ID BB).

• The mother has her identity proof (card, QR code, ID number, etc) available together with the required credentials for the MCC that can be verified and authenticated with the national ID system.

Data inputs

1. Name of the mother

2. National ID number of the mother

3. National ID number of the newborn

4. Name of the newborn baby

5. Place of birth (explain the rationale behind this field)

6. Time of birth

7. Location of birth

Actors

(the people, organizations, computer systems - hardware and software, and building blocks that participate in the activity)

Human: Government-accredited health worker, A woman who has delivered her first baby

System:

• MCTS/ MCC application (Registration BB)

• Digital Registries BB

• Identity BB

• Consent BB

• Messaging BB

• Information Mediator BB

• National Population Registry (Digital Registries BB or Identity BB)

• MCC Membership Registry (Digital Registries BB)

Normal Course (what happens if the event is triggered and the preconditions have been met)

The registration form screen for the MCC application provides a list of initial details required to proceed with the registration (eligibility verification, required documents, required fees).

Step 1: The health worker enters the required initial details, including, but not limited to the following:

1. Mother’s and newborn baby’s National ID number

2. Name of the newborn child

3. Date of Birth

4. Place of Birth (such as home, clinic, etc.)

5. Time of Birth

6. Location of Birth

7. The health worker (MCC Application) suggests the Mother an option to retrieve additional data from the Population Registry and asks for a consent to do so.

Feature: Get Consent Agreement
Scenario: MCC Application retrieves Consent Agreement for Mother
  Given an Agreement for MCC user registration exists in Consent BB
    And MCC Application has MCC application has Mother's <ID> and authentication token for the registration session
  When MCC application fetches a Consent Agreement for MCC user registration
  Then MCC application gets a valid Draft Consent Agreement associated with Mother's ID

3. Step 2: The health worker (via MCC Application) introduces to the Mother the Consent Agreement for fetching the relevant details from the Population registry for verification and appropriate use with the MCC and captures signature to the Consent Agreement from the Mother.

Feature: Sign Consent Record

Background:
  Given MCC Application has the Draft Consent Agreement associated with Mother's ID
    And MCC application has Mother's <ID> and authentication token for the registration session 
    And Mother has read the Draft Consent Agreement
    And Mother approves to sign the Draft Consent Agreement associated with Mother's ID

Scenario: Sign Consent Record on Paper
  Given MCC application has captured the consent in a digital form (for example: scan of a paper form)
  When MCC sends digital Consent Record payload to Consent BB
  Then Consent BB digitally signs Consent Record
    And Consent BB confirms to MCC Application that Consent Record for Mother has been successfully signed
    
Scenario: Sign Consent Record Digitally
  Given Mother has capability to sign Consent Record digitally
  When MCC sends the Draft Consent Agreement to Consent BB
  Then Consent BB creates a paired ConsentRecord and Signature object 
    And Consent BB digitally signes Consent Record
    And Consent BB confirms to MCC Application that Consent Record for Mother has been successfully signed

Step 3: The MCC application form submits the

verified national ID number to the Population registry hosted in the IDBB/Digital Registries BB seeking relevant details of the mother, by invoking the API “Data read value” on the Govstack Digital Registries BB.

This scenario uses a set of features:

• Verify Consent Record by Consent BB

• Import data from a registry by Registry BB

Feature: Verify Consent Record
MCC Application verifies if Mother has signed Consent Record to fetch the needed personal data from Population registry for MCC user registration

Scenario: Retrieve valid Consent Record 
Given Mother has Signed Consent Record stored in Consent BB 
When MCC Application makes the request to population registry API to fetch Mother's personal data   
Then MCC Application makes prior request to Consent BB API to retrieve Mother's Signed Consent Record    
  And Consent BB sends the signed Consent Record to MCC Application

Feature: Imports client personal data from a registry
Import Mother's pesonal information from Population Registry to the e-service form

Given Mother has entered <ID> in the Registration e-service registration form, national ID number field
    And MCC Application has received Signed Consent Record from Consent BB
   When the MCC Application user pushes a button "Import Mothers's information"
   Then the MCC Application makes a request to Population Registry API
    And Population Registry returns requested data to MCC Application
    And MCC Application fills the form on the screen with Mothers data <ID>,<first>, <last>, <birth> 
  Examples:
    |ID|first|last|birth|
    |53|Sowmya|Krishnamurti|2022-11-01|