Sign-up failed when the NPI records were modified: the ‘gender’ field is now null while a new ‘sex’ field is introduced. Example:
{ "first_name": "Jane", "last_name": "Doe", "sex": "F" }
The issue appears to result from incomplete integration of new database schema changes. In my experience with similar updates, it is crucial to ensure that all dependent systems and processes are aware of the newly introduced field. The null value for ‘gender’ coupled with the creation of ‘sex’ suggests that older modules might not have been updated accordingly. It is advisable to review the backend logic for field mapping and adjust the sign-up process to properly capture or migrate existing data without causing registration errors.