client comments:
As discussed over phone, Consider following points given below.
• If a user have multiple ashablock assigned institutions, then an institution selection required before ashablock selection on the same ashablock selection screen.
• If only single ashablock assigned, institution selection will be auto populated.
• For the time being, you can proceed with ashablock selection only for piloting. Incorporate institution selection later along with PH supervisor handling changes.
• Role ID don't need to check for survey users as all have same functionalities apart from PH supervisor user role. But In services , role wise functionality access will be added.
• Institution transfer process -While reliving an employee in HMS , ashablock from user will be detached. So In app side detached ashablock wont be available for user.
________________________________
From: tharas@cdac.in
To: "BIYAS S" <biyas.ehk@kerala.gov.in>
Cc: "Anjaly Chandran" <anjalyc.ehk@kerala.gov.in>, "ANJU V.M" <anjuvm.ehk@kerala.gov.in>, "Aswathy R Nair" <aswathyrn.ehk@kerala.gov.in>, "VIVEK A. B." <vivekab.ehk@kerala.gov.in>, "Vinod Raj Varadarajan" <vinod.ehk@kerala.gov.in>, "rontgen ehk" <rontgen.ehk@kerala.gov.in>, "AKHILARAJ V J" <akhil.ehk@kerala.gov.in>, "Rajeshkumar N" <rajesh.ehk@kerala.gov.in>, "jiji pb" <jiji_pb@cdac.in>, chris@cdac.in, "aswathy mg" <aswathy.mg@cdac.in>, shameera@cdac.in, devanand@cdac.in, "sujithks ehk" <sujithks.ehk@kerala.gov.in>
Sent: Sunday, October 15, 2023 7:45:34 PM
Subject: RE: app release - testing
Dear Biyas,
In continuation with communication in Whatsapp, Please comment on whether we can have the following approach to check app access eligibility for a user (JPHN/JHI/MLSP) and ASHA Block listing
• ASHA Block assigned to the user is determined by referring the table ph_ashablock_assign (only user id used, institutions not considered, may be from multiple institutions)
• The role ID of the user from keycloak falls in one of the following
"JPHN": 3, "JHI": 6, "FWC JPHN": 10, "BS JHI": 41, "MLSP staff Nurse": 53.
ie. Only userid-ashablock mapping and user's role considered. The institution and institution type of the user is not considered here.
• If user has no ASHA Block assigned, message will be No ASHA Block assigned to the user.
• If role is not valid, the message will be User is not allowed to access the app.
With this, please share what will be the approach for handling institution transfer.