Page Comparison

...

1. Death registration

   • type (il.dictionary: name='PERSONS_DEACTIVATION_IDENTITIES')
   • number
   • deathDate death_date 
     • file example: person_example.csv
     • file example with person_id: PERSON_D.csv

2. Termination by declaration_id

   • declaration_id
     • file example: declaration.csv

3. Reset authentication method

   • person_id
     • file example: reset_auth.csv

...

1. Validate that $document.type 
   1. one of from dictionary (name='PERSONS_DEACTIVATION_IDENTITIES') or is MPI_ID. If type is not as in dictionary or not MPI_ID show the row in the errors field.
2. Validate MPI_ID
   1.  in case MPI_ID is not UUID ("^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$")
      1. show the row with not found MPI_ID with status "error"
   2. in case MPI_ID was not found in mpi.persons.id OR medical_data.patients
      1. show the row with MPI_ID with status "not_found"
   3. in case MPI_ID was found in mpi.persons, but could not be deactivated
      1. show row with MPI_ID with status "processed"
   4. in case MPI_ID wasn't found in mpi.persons, but was found in medical_data.patients (preperson was found)
      1. show row with MPI_ID with status "processed"
3. Validate deathDate Validate death_date if exists
   
   1. in case deathDate case death_date <> valid date ()
      1. show the row with MPI_ID with status "date_error"
   2. in case deathDate death_date does not exist
      1. show the row with MPI_ID with status "date_error"
   3. in case deathDate death_date year < 1900
      1. show the row with MPI_ID with status "date_error"
   4. in case deathDate death_date < birth_date
      1. show the row with MPI_ID with status "date_error"

...

      3. Validate headers in file: type, number, deathDatedeath_date. In case of error show the 422 error 'Incorrect headers in file' 

...

The data from file must be stored to il.register_entries. In case some rows had errors those entries will be shown in filed "errors" and won't be processed.

After the file was processed the field "qty" from table il.registers must be updated.

...

If the person was matched then

1. update declarations.status to `terminated`
2. update persons.status='INACTIVE'
3. change declarations.reason to $"auto_"||type
4. update il.registers.status='matched'
5. update mpi.persons.death_date = $deathDate$death_date

If the person was found, but declaration not in status "active" - il.registers.status='matched'

...

If declaration_id was matched

1. update ops.declarations.status to `terminated`
2. update ops.declaration.updated_at = now()
3. update ops.declaration.updated_by = $user_id
4. change declarations.reason to $"auto_"||type
5. update il.registers.status='matched'
6. involve Event Manager for changed status 

Reset authentication method

If the person was matched then

1. update mpi.person_authentication_methods.type to `NA`
2. update mpi.person_authentication_methods.phone_number to `null`
3. update mpi.person_authentication_methods.updated_at to `now`
4. update il.registers.status='matched'

...

If the person was found, but declaration doesn't exist - il.registers.status='matched'

...

matched

...

update medical_data.patients.status='inactive'

...

update il.registers.status='matched'

...

update medical_data.patients.death_date = $death_date

...

update medication requests related to preperson if status is NEW. Set status = 'REJECTED'.

...

update medication request request related to preperson if status is ACTIVE. Set status = 'REJECTED'.

...

'

...

1. servece request has ACTIVE status

2. service program status is empty or in (NEW, IN QUEUE)

If the person

...

was not matched then

1. update il.registers.status='not_found'

...