Page Comparison

...

1. Death registration

   • type (il.dictionary: name='DOCUMENT_TYPE')
   • number
   • death_date 
     • file example: person_example.csv

2. Termination by declaration_id

   • declaration_id
     • file example: declaration.csv

...

In case file structure = Death registration of patients

1. Validate that document $type one $document.type 
   1. one of from dictionary (name='DOCUMENT_TYPE') 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
      1. show the row with MPI_ID with status "not_found"
   3. in case MPI_ID was found, but could not be deactivated
      1. show row with MPI_ID with status "processed"
3. Validate death_date if exists
   
   1. in case death_date <> valid date ()
      1. show the row with MPI_ID with status "date_error"
   2. in case death_date does not exist
      1. show the row with MPI_ID with status "date_error"
   3. in case death_date year < 1900
      1. show the row with MPI_ID with status "date_error"

      2. Validate that $type one of from dictionary (name='REGISTER_TYPE'). If type is not as in dictionary show the 422 error 'Incorrect register type'

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

...

1. Validate headers – should be type,number
   1. in case headers are different return error 422, msg 'Incorrect headers in file' 
2. Validate that $type exists in dictionary (name='REGISTER_TYPE').
   1. In case error show the 422 error "value is not allowed in enum"
3. Validate declaration_id
   1. in case declaration_id was not find found in ops.declarations.id
      1. show the row with not found ID with status "not_found"
   2. in case $declaration_id.status <> active
      1. show the row with ID with status "processed"
   3. in case $declaration_id can not be deactivated
      1. show the row with declaration ID with status "error"
4. In case technical error happened, but declaration found
   1. show the row with not found ID with status "error"

...

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 = $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 

Backward compatibility

 is not possible for this kind of termination. In case the wrong declaration was terminated, the patient must sign the new one.

...