eHealth PHS

• C-DAC commented the server logs were examined for the issue and found that the issue is related to non-conformance of old records in UAT1 with the recently implemented input validation for data upload synchronization (for resolving security issues reported by CERT)
• C-DAC also commented that the issue may be arise with several data fields in house survey and member survey tables in UAT1 as input validation done in upload data synchronization APIs may not correctly pass for old records due to missing field values such as latitude, longitude, Ward IDs and data format mismatches in fields like contact number.
• eHealth commented that they will check the possibility of removing input validation to make implementations compatible for old records in live and will communicate after confirming with security team.

eHealth responds on 19.01.2023: Input validations will be required as recommended in the security report.

• In Family - member creation, Corresponding member ID completed status( ie All mandatory fields) should be checked ( null or P can be considered as Pending).
• In the same way , before Member creation house survey completion status can be checked (null or P can be considered as Pending).
• In House/Member deletion cases, Coalesce function can be used to handle null value fields as empty string before validation check.
• Data format issues for existing data need to allow formats matching with db field datatypes.