eHealth PHS

eHealth comments on 04.10.2023 changes in workflow
Current flow is incomplete-All the members transfering from app is
available for all institutions. Only member mapped to ashablock need to showing in corresponding institution ashablock for merge.Relation b/w ashablock mapping to transfered member get from table ph_ashablock_member_transfer(mapping via HMS application screen)
In app side:
Get members with status 'p' for ashablock based syncing for transfer members.
After merging the member ,update status to 'A',and add user id in approved_by and merged date in approved_date fields in ph_ashablock_member_transfer.
Also update transfer status as N ,house_id in member survey and this updates will synced to central DB

New workflow
Member Transfer: The transfer_status in ph_member_survey will be set to 'Y'.

The HMS server will do mapping of transferred members with a new ASHA Block and the table ph_ashablock_member_transfer will be inserted with a new row. (The script of the table from eHealth pending)

Based on logged in user's ASHA Block selection, the records from ph_ashablock_member_transfer to be download synched to device for the ASHA Block selected and with a status field 'p' (or 'P')

The records from ph_member_survey table also to consider the records from ph_ashablock_member_transfer?

The member merge screen to be populated from the local ph_ashablock_member_transfer.

The record for a member after merging to a house is updated for status field as 'A' and also approved_by and approved_date fields.
The table is upload synched to server side and records in server are updated.

Also to update transfer_status as N, house_id in member survey and upload synched to central DB

Further confirmation from eHealth

In the 'member_transfer' process transferred members mapped with ASHA block has been done in HMS only

- The mapped entries will be inserted in the table ph_ashablock_member_transfer with status 'p' initially (in this table HMS using small letters for status)

- While synching, the records from ph_member_survey table we have to consider the records from ph_ashablock_member_transfer also if the ASHA block is associated with that device/user

- The record for a member after merging to a house is updated for status field as 't' ( not 'A' ) and also update approved_by and approved_date fields in the table ph_ashablock_member_transfer

- The fields description

requested_by -  This field saves the 'id' of the user who transfer out the members. 

requested_date - the uploaded date for the transfer out members

approved_by -  This field saves the 'id' of the user who wants to transfer in the members to his/her device, most probably he/she will map the ASHA block to the those members in HMS. - to be updated from mobile

approved_date  -  the date at which the member transfer process completed. - to be updated from mobile

eHealth informs on 11.p10.2023 that member merge need not implement in app.