Sample

Early Childhood development product requirement document draft



Version 1.0
Prepared by
Piramal Swasthya Management Research Institute
&
Wipro Limited
Health Care Delivery Unit

This document is an intellectual property. Unauthorized copying, reproduction or distribution of this document, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law.







Document Management Information
Document Title: Early childhood development Product requirement draft
Document Owner: Piramal Swasthya Management Research Institute & Wipro Ltd.
Document Classification: Confidential
This document is a confidential document of Wipro Ltd. and Piramal Swasthya Management Research Institute. Reproduction, translation, transformation to any medium requires prior written approval of the Wipro Ltd./ PSMRI. This document includes confidential information related to Wipro Ltd. and PSMRI and shall not be distributed to any persons other than those mentioned in the distribution list without the consent of both the parties.
Document Identification

Document Title

Version

Author (s)

Remarks

Early childhood development PRD draft

1.0

Piramal Swasthya Management Research Institute
&
Wipro Limited

 



Document Distribution List

Sr. No.

Name & Company

Title

1

PSMRI

Author

2

Wipro Limited

Author








Contents
1. Business Process
2. Actors-Outbound
3. System Use Case-Outbound
3.1. Helpline-ECD-0001: User Login
3.2. Helpline-ECD-0002: Supervisor – Upload ECD Data into Application
3.3. Helpline-ECD-003: System – Generate unique ID
3.4. Helpline-ECD-0004: System – Identify duplicate data during next data upload into the System
3.5. Helpline-ECD-00005: System– Self & Other Phone numbers- Logic
3.6. Helpline-ECD-00006: System– Estimated Delivery Date Calculation
3.7. Helpline-ECD-0008: Supervisor – Allocate Calls to Agent
3.8. Helpline-ECD-00010: Agent/Associate -Outbound Call worklist
3.9. Helpline-ECD-00011: Agent-Outbound Call worklist – High Risk Patient
3.10. Helpline-ECD-00012: Outbound Call – View Call & History Details
3.11. Helpline-ECD-00013: Outbound Call – Call Documentation- Self / Other Phone number
3.12. Helpline-ECD-00016: Move beneficiary to MO worklist – for High-Risk Patient
3.13. Helpline-ECD-00017: SMS feature for MO to send any Advice
3.14. Helpline-ECD-0018: System – Retain Beneficiary data into the system as per the defined rule and Auto Schedule for next ECD call
3.15. Helpline-ECD-0019: System – Stop Scheduling for further calls for a Selected Beneficiary
3.16. Helpline-ECD-0025: Allocation of agent to their respective Quality Auditor
3.17. Helpline-ECD-0025: Quality Auditor Activities- Listening the call and rating the call of ANM/MO
3.18. Helpline-ECD-0021: Quality Auditor Activities- Call Audit Details
3.19. Helpline-ECD-0022: ANM/MO Activity – Agent to rebuttal if he is not satisfied with the Audit report/Remarks
3.20. Helpline-ECD-0023: Dashboard requirement for Quality supervisor
3.21. Helpline-ECD-00034: System – User should be Navigated to Homepage/Dashboard when Agent clicks on Break
3.22. Helpline-ECD-00035: System – IVRS Recording- When Agent has kept Beneficiary on Hold
3.23. Helpline-ECD-00026: System – SMS Alerts to Beneficiary
3.24. Helpline-ECD-00027: System – Capture Congenital Anomalies during PNC Calls
3.25. Helpline-ECD-00028: System –Report- Congenital Anomalies
3.26. Helpline-ECD-00029: System –Sticky Agent
3.27. Helpline-ECD-00030: ECD No of Calls Configuration Screen:
3.28. Helpline-ECD-00031: ECD Content data for each ECD Calls Upload Screen:
3.29. Helpline-ECD-00032A: Supervisor- Dashboard
3.30. Helpline-ECD-00032B: Supervisor- Reports
3.31. Helpline-ECD-0033-System-Auto- Preview dialling
3.32. Helpline-ECD-0034-System-Capture CSAT Score through Manual/IVRS/SMS Services



  1. Revision History

    Version

    Date of Revision

    Description of Change

    Reason for Change

    Affected use case

    Approved By (Name, Email Id)

    V 0.1

    18.07.2022

    Initial Draft

    Product Requirement-ECD

     

     

    Business Process

Actors-Outbound

Following are the actors who will be interacting with the Application

  1. Ancillary Nurse Midwife – ANM
  2. MO (Medical Officer - MO
  3. Supervisor
  4. Associate / Agent
  5. Quality Auditor


Following are the actors who will be interacting with the Beneficiary

  1. Ancillary Nurse Midwife - ANM
  2. MO (Medical Officer) – MO
  3. Agent


3. System Use Case-Outbound


3.1. Helpline-ECD-0001: User Login


ID

Helpline-ECD-0001

Requirement No

N/A

Type

Product specific

Requirement Description

User can login to ECD application.

Solution Description

Login with user name – Staff can login with username and password. After login, system asks for role selection.

Actor(s)

Agent, ANM (Ancillary Nurse Midwife), Medical Officer, Supervisor, Quality Auditor

Pre-Conditions

  • Respective user is created in the system and roles have been assigned by admin

Basic Flow

  • Enter username & password
  • Select the required role (if user is having more than one role)
  • System opens the respective 'Module'/ 'Screen'/Homepage
  • User will see their home page (suggest to include previous "Call History").
  • Suggest to include values for selection "Ported Out" in drop down list in case call is not answered.

Alternative Flow

None

Business Rules

For whole session, screen displays username, Login Date & Time

Post-Conditions

User has logged into ECD application

Change Impact

N/A

Exception(s)

  1. If user id and password do not match. System displays an error message.
  2. If password id incorrect. System to provide 5 attempts after which user will get locked/deactivated. Reactivation of which can be done by Admin.
  3. User can reset the password using a set of security questions. These security questions are to be defined at the time of first log in.

Extension Points

N/A

Data Elements

Data Field

Input Type

Validation

Behaviour

Login Id

Entry

Username should have login created

 

Password

Entry

Mandatory, should have minimum 8 characters with alpha numeric with at least one uppercase

 

Current Date and Time

Display

Format: DD-MM-YYYY and HH:MM: SS

 

 

Variants

N/A

Assumptions

N/A

Not in Scope

N/A


3.2. Helpline-ECD-0002: Supervisor – Upload ECD Data into Application


ID

Helpline-ECD-0002

Requirement No

N/A

Type

Product specific

Requirement Description

ECD data, which is received from RCH, should be uploaded into the system via a manual upload from Supervisor role.

Solution Description

Supervisor should be able to upload the clean ECD data into the application via manual upload process

Actor(s)

Supervisor

Pre-Conditions

  • Data received from RCH
  • Data cleansing done as per the requirement
  • Different states where ECD program is operational needs to be defined in the System
  • Upload needs to be done against to that specific state from data upload master screen.
  • Mother Data & Child Data files needs to be uploaded separately.
  • Rules defined to prevent duplicate data upload.

Basic Flow

  • Supervisor logs into the ECD application
  • Download the required template and populate the data.
  • Click on data upload master
  • Select Mother Data/Child Data option to upload
  • Select the file/Browse the file from the system and
  • Click on Upload.
  • Data will be up loaded against the specific state under selected Mother/Child Data.
  • Supervisor will allocate calls to Associate/Agents.

Alternative Flow

None

Business Rules

None

Post-Conditions

  • Mother data and child data uploaded into the system
  • Uploaded data available for system/Supervisor to allocate to the agents.
  • System should capture record uploaded date in the System.

Change Impact

N/A

Exception(s)

  • System to identify invalid contact numbers based on number of digits.
  • System needs to check the availability of mother id/child id in the DB at the time of subsequent data uploads. Mother ID need not to be uploaded if it already exists in the DB.

Extension Points

 

Data Elements

Data Field

Input Type

Validation

Behaviour

Supervisor> Data Upload Master>

Selection

 

 

Mother Data

Selection

 

Radio Button

Child Data

Selection

 

Radio Button

Browse File

Selection

 

Browse button

Upload

Selection

 

Button

 

Variants

 

Assumptions

 

Not in Scope

 

3.3. Helpline-ECD-003: System – Generate unique ID


ID

Helpline-ECD-0003

Requirement No

N/A

Type

Product specific

Requirement Description

System to generate unique AMRIT ID for every unique beneficiary.

Solution Description

Agent/associate should generate a unique AMRIT ID for new Beneficiaries for identification of the beneficiary across platform.

Actor(s)

Agent/Associate

Pre-Conditions

  • Beneficiary data is new, and the same data/beneficiary is not register in AMRIT platform earlier.
  • AMRIT Unique ID Generation Rule/Logic is defined at AMRIT Platform level.

Basic Flow

  • When ECD data is being uploaded into the system,
  • System should check the availability of same beneficiary in the System
  • If data is not found, system will upload the beneficiary details
  • If same details of beneficiary are found, system will not upload the data.
  • Duplicate beneficiary report should be generated which could be accessed by supervisor.

Alternative Flow

None.

Business Rules

  • Agent should generate unique ID for each Beneficiary in the system.
  • If same beneficiary data is provided with different Mother ID, system will create new record to provide ANC/PNC service, however history of the beneficiary will be available and no new Unique Beneficiary Id will be created (This will depend on Mother Name, Husband Name, Phone number criteria, if none of the above is matched it is considered as new entry and create a Unique ID).

Post-Conditions

Unique Beneficiary/AMRIT ID is generated in the system.

Change Impact

N/A

Exception(s)

N/A

Extension Points

N/A

Variants

 

Assumptions

 

Not in Scope

 



3.4. Helpline-ECD-0004: System – Identify duplicate data during next data upload into the System


ID

Helpline-ECD-00004

Requirement No

N/A

Type

Product specific

Requirement Description

Every time when ECD data is being provided by govt there are lot of records, which are duplicate.
With the present system once, the beneficiary data is in the system, it will continue to be active in the ECD program till the last ANC/PNC call is completed as per the program guidelines.
So, system should identify the duplicate records during upload and should not overwrite on the existing data.
During upload system should search the data in the system and when no matches is found, it should upload the data and generate a report for duplicate records.

Solution Description

When ECD data is provided to PSMRI, most of the time there will be lot of duplicate records, which has been provided earlier.
System must identify those duplicate and should not upload the same and generate a report for those Mother ID/Child ID.
System should consider only new records for subsequent upload.

Actor(s)

System

Pre-Conditions

Previous data is available in the system and when new data is being uploaded into the system, system should validate for duplicates

Basic Flow

  • First time data is uploaded into the system.
  • Based on the ECD calls rules it would be scheduled for ANC/PNC calls accordingly (which is bases on LMP/EDD and DOB)
  • Next time when there is new date/additional data provided to PSMRI from RCH, the same is uploaded into the System by supervisor
  • During upload, System should validate if there are duplicate records (which is based on same Mother ID/Child ID), filter them out, and allow uploading only new/unique records.

Alternative Flow

when a beneficiary becomes pregnant for the second time, RCH will generate a separate Mother ID, in that case system should identify such cases and append previous calls history of the mother to this new mother id as historical record.

Business Rules

  • System should generate unique ID for each Beneficiary in the system
  • If same beneficiary data is provided with different Mother ID, system will create new record to provide ANC/PNC service, however history of the beneficiary will be available and no new Unique Beneficiary Id will be created (this will depend on Mother Name, Husband Name, Phone number criteria, if none of the above is matched it Is considered as new entry and create a Unique ID)
  • If more than one match is found, system should create a new record in the system.

Post-Conditions

Unique Beneficiary is generated in the system.

Change Impact

N/A

Exception(s)

Phone number will not be considered to identify duplicates, because many beneficiaries will not have mobile number and there ASHA worker number is provided. So, it is excluded in duplicate identification logic

Extension Points

N/A

Data Elements

Data Field

Input Type

Validation

Behaviour

Mother ID

Display

 

Numeric

Mother Name

Display

 

Text field

Husband's Name

Display

 

Text field

District Name

Display

 

Text field

Health Block

Display

 

Text field

PHC Name

Display

 

Text field

Sub Facility/Subcentres

Display

 

Text field

GP Village

Display

 

Text field

Address

Display

 

Text field

ASHA name

Display

 

Text field

ASHA mobile number

Display

 

Text field

ANM Name

Display

 

Text field

ANM mobile number

Display

 

Text field

Child ID

Display

 

Numeric

Child Name

Display

 

Text field

 

Variants

 

Assumptions

 

Not in Scope

 

Last modified Date

 

Last modified by

 



3.5. Helpline-ECD-00005: System– Self & Other Phone numbers- Logic


ID

Helpline-ECD-00005

Requirement No

N/A

Type

Product specific

Requirement Description

ECD data has both mother & Child Data- In most of the cases Beneficiary phone number (Self Number) are not provided, they might have entered ANM's or other persons phone number (Other Number) when data is provided for outbound call.
System should identify them at the time of data upload and segregate it in Self and Other number buckets separately for a supervisor to assign calls to agents respectively.

Solution Description

Once data is uploaded into the system, it should segregate mother & Child data with Self & Other numbers separately in different buckets for a supervisor to assign calls to agents manually.
This is applicable only if Manual allocation of calls is configured in the system.

Actor(s)

System, Supervisor (Based on configuration)

Pre-Conditions

  • Mother & Child ECD data uploaded into the system

Basic Flow

  • Once Data is uploaded into the system (Refer use Case: Helpline-ECD-0008
  • System will validate Duplicate data (Refer use Case: Helpline-ECD-00010)
  • Generate unique Beneficiary ID (Refer use Case: Helpline-ECD-0003)
  • Check/Validate 'Self or Other' Phone number
  • Segregate them into different buckets
  • Supervisor will be able to see the number of records in each bucket
  • Manually Allocate the number of call (Self or Other) to an agent/MO/ANM.

Alternative Flow

  • None

Business Rules

Once data is uploaded into the system, it should segregate mother & Child data with Self & Other numbers separately in different buckets for a supervisor to assign calls to agents manually.

Post-Conditions

  • Allocated calls will be visible in Agent's work list.

Change Impact

N/A

Exception(s)

N/A

Extension Points

N/A

Variants

 

Assumptions

 

Not in Scope

 



3.6. Helpline-ECD-00006: System– Estimated Delivery Date Calculation


ID

Helpline-ECD-00006

Requirement No

N/A

Type

Product specific

Requirement Description

When the data is uploaded into the system, ECD data will have LMP (Last Menstruation Period) & EDD (Estimated Delivery Date).
Sometime the EDD data entry is not correct with respect to last LMP.
So, System must calculate the EDD based on the LMP Provided or modified by an Agent/ANM/MO during the outbound call.
Note: EDD should not be editable. Associate/Agent alone has the privilege to edit LMP.

Solution Description

System should calculate/re-calculate and populate the EDD based on LMP

Actor(s)

System, Agent, ANM, MO

Pre-Conditions

  • LMP is provided by ECD data
  • Agent/ANM/MO modifies the LMP as per beneficiary mentioned LMP

Basic Flow

  • ECD data when uploaded into the system
  • System to verify the LMP and validate the correct EDD is populating
  • System should consider 280 days after LMP as the estimated delivery date and populate the EDD filed accordingly.

Alternative Flow

  • During call Agent, verify the correct LMP from the mother.
  • If mother mentions the correct LMP which is different in the system Agent will modify the LMP accordingly
  • System should re-calculate the EDD and populate the same accordingly.

Business Rules

280 days from LMP should be the EDD

Post-Conditions

Based on the LMP and EDD should auto schedule ECD call (ANC/PNC) according to the ECD program guidelines, which are state specific.

Change Impact

N/A

Exception(s)

N/A

Extension Points

N/A

Variants

 

Assumptions

 

Not in Scope

 



3.7. Helpline-ECD-0008: Supervisor – Allocate Calls to Agent



ID

Helpline-ECD-00008

Requirement No

N/A

Type

Product specific

Requirement Description

When new ECD data is uploaded into the System, Supervisor will be able to allocate the records to the respective agents to make outbound call.
This feature should be enabled only if call allocation is configured in Admin/Configuration module/Call Allocation Type

Solution Description

When data is uploaded in the System, Data needs to be allocated to agents to make outbound call to Beneficiary (may be either "Husband" or 'Wife).

Actor(s)

Supervisor.

Pre-Conditions

  • Manual Call allocation is enabled in Admin/Configuration module/Call Allocation Rule

Basic Flow

  • ECD Data uploaded into the system
  • Supervisor navigates to Allocate calls feature from menu.
  • Select the list ID (Mother Data or Child Data)
  • Filter the Date Range (this date range is the date between which the data was uploaded).
  • If no Date range is selected, System will show all the records which are pending for allocation.
  • After selecting date range, clicks on 'Submit' Button,
  • System will show all the pending records to be allocated.
  • Select the agent
  • Allocate the number of Records.
  • Click on 'Allocate' Button'

Alternative Flow

N/A

Business Rules

  • First introductory call to be allocated only to Associate/Agent
  • HRP calls are identified by ANM only during the service call not introductory call by agents. Post introductory call by Agent, filtered beneficiary data who are interested to get the ECD services are allocated for ECD service call to ANM.
  • High Risk Pregnancy/Infant high-risk calls will be allocated only to MO
  • Low risk/non allocated t calls to be allocated only to ANM

Post-Conditions

  • Allocated calls will be displayed in Agent's worklist to make outbound call.

Change Impact

N/A

Exception(s)

N/A

Extension Points

N/A

Data Elements

Data Field

Input Type

Validation

Behaviour

List ID:

Selection

Mother Data or Child Data

Dropdown

Phone number Type

Selection

Self or Other

Dropdown

From Date

Date Entry

 

Date Format

To Date

Date Entry

 

Date Format

Submit Button

Selection

 

Button

Total New Records

Display

Self or Other

Numeric Display

Allocate to

Selection

 

Dropdown list

Allocate No of Records

Numeric Entry

 

Numeric

Allocate

Selection

 

Button

 

Variants

 

Assumptions

 

Not in Scope

 

Last modified Date

 

Last modified by

 

3.8. Helpline-ECD-00010: Agent/Associate -Outbound Call worklist


ID

Helpline-ECD-00010

Requirement No

N/A

Type

Product specific

Requirement Description

Agent to view their Outbound Call worklist which has been assigned to them.

Solution Description

Agent to view their Outbound Call worklist which has been assigned to them.

Actor(s)

Agent, ANM (Ancillary Nurse Midwife), Medical Officer

Pre-Conditions

  • Respective user is created in the system and roles (Agent/ANM/MO) have been assigned by admin

Basic Flow

  • Enter username & password
  • Select the required role (if user is having more than one role)
  • System opens the respective 'Module'/ 'Screen'/Homepage
  • User will see their home page.
  • Click on call link/ Menu select outbound call worklist
  • User can see the allocated calls in their worklist
  • Worklist will have all the calls allocated to them with this details like: Sl.No, Mother ID, Child ID, Phone Number, lapse time(difference of call allocated and current date), self/others phone number, ECD call type, call attempt number, status of call, Record upload date, View Button.
  • Invalid/wrong number and if the beneficiary does not give the consent, should be marked as no further call required. Reason should be mentioned as invalid number/Not interested respectively.

Alternative Flow

None

Business Rules

For whole session, screen displays username, Login Date & Time.
Users can see the allocated calls/task in their worklist (allocation can be System allocated or Supervisor Manually allocated)

Post-Conditions

User can see the allocated calls in their worklist.

Change Impact

N/A

Exception(s)

If no calls are allocated, there will not be any data in the worklist

Extension Points

N/A

Data Elements

Data Field

Input Type

Validation

Behaviour

S. No

Display

 

Numeric

Phone Number

Display

 

Numeric

Mother ID

Display

 

Numeric

Child ID

Display

 

Numeric

Action

  • View

Selection

 

Button

Lapse time

 

Auto populate

 

Whom phone number

 

Auto populate

 

Call Attempt Number

 

Auto populate

 

Call status

 

 

 

Record upload date

 

 

 

ECD Call type

 

Auto populate

 

 

Variants

N/A

Assumptions

N/A

Not in Scope

N/A

Last modified Date

 

Last modified by

 



3.9. Helpline-ECD-00011: Agent-Outbound Call worklist – High Risk Patient


ID

Helpline-ECD-00011

Requirement No

N/A

Type

Product specific

Requirement Description

High risk calls will be transferred to MO.

Solution Description

High Risk Pregnancy calls will be handled with MO, Agent will verify all the High-Risk Pregnancy calls and transfer the list to supervisor for allocation to MO.

Actor(s)

Agent, Medical Officer, Supervisor, System

Pre-Conditions

  • Respective user is created in the system and roles have been assigned by admin

Basic Flow

  • Enter username & password
  • Select the required role (if user is having more than one role)
  • System opens the respective 'Module'/ 'Screen'/Homepage
  • User will see their home page.
  • Click on call link/ Menu select outbound call worklist
  • Worklist will have all the calls allocated to them with these details like S. No, Mother ID, Child ID, and Phone Number, lapse time(difference of call allocated and current date), ECD call type, call status, call record upload date, View Button.

Alternative Flow

  • During an ANM outbound call to beneficiary, if ANM finds out that beneficiary condition falls under high risk, she will mark/select High Risk Flag.
  • Upon flagging, ANM can move the beneficiary to supervisor for allocation of the call to MO.

Business Rules

System should identify the data as high-risk pregnancy and auto segregate data based on the below identification criteria:
High risk Indicators-

IDENTIFICATION OF HIGH RISK PREGNANCY

 

 

S.NO

HISTORY TAKING

HIGH RISK PREGNANCY IDENTIFIER

1

Age of the patient

Age < 18 years and age > 35years

2

LMP

not known, > 40weeks ( postdatism)

3

Obstetric history

recurrent abortions, no living issue, cong anamoly, still birth, LBW or > 4.5kg, previous caesarean delivery, history of PPH, failure of lactation, Grand multipara(> 4 live births)

4

Personal history

Heart disease, DM or HT, any surgical history, drug allergy, hypothyroidism, any medication on

5

Height

< 145cm

6

Stature

Any spinal deformity

7

Pallor

<7 gm%

8

Bp, Oedema

>140/90mmHg

9

Blood Group

Rh Negative

10

HIV, HbsAg, VDRL

Positive

11

USG/ Examination

Abnormal Lie( breech, transverse etc), multiple pregnancy

12

Present Pregnancy

High priority fetus(infertility treatment), Bleeding P/V( abortions, placenta praevia), GDM, PIH

13

Others