Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose

The logic for creating new employee must be changed so employee without tax_id will be able to register in E-health. If the employee doesn't have tax_id registration flow must be next:

  • input Passport Numberattach scan of Passport 

Passport number is stored in same field as tax_id, additionally for Party there is a boolean field 'no_tax_id'=[true, false]  

...

That will lead to changes described below:

  1. Create employee request (https://edenlab.atlassian.net/wiki/x/SKUO)  (apiary)
  2. Create/Update employee (https://edenlab.atlassian.net/wiki/x/VBYU
    • Search party_id by 'tax_id' (tax or passport id) and birth_date for deduplication Party
      1. If found, update object party - Update party WS
      2. If not found - Create object party
    • Update Party:

      1. The following fields can't be changed:

        1. document_id
        2. birth_date
  3. Sign Declaration (https://edenlab.atlassian.net/wiki/x/Y_oQ) Declaratio- drfo=[tax_id, passport_number]
  4. Create new party, Update Party (apiary)
  5. List Search for party (apiary)
  6. Get Party details (apiary)
  7. Get employee details (apiary)
  8. Fraud Black list Users - block users by adding to black list 'tax_id' (tax or passport id)
  9. Fraud replication - add field parties.no_tax_id

...

  1. For Employee Lists must be added parameter - no_tax_id: GET /employees?no_tax_id (apiary)
  2. NHS admin must be able to filter by parameter no_tax_id=true and see attached documents
  3. Get Party documents list Update Employee request list and Employee request by id (apiary)