Purpose

This WS allows to update current verification status of specified party. Now updating of DRACS death stream verification status is allowed.

Specification

Apiary

Authorization

• Verify the validity of access token

  • Return (401, 'Invalid access token') in case of validation fails

• Verify that token is not expired

  • in case of error - return (401, 'Invalid access token')

• Check user scopes in order to perform this action (scope = 'party_verification:write')

  • Return (403, 'Your scope does not allow to access this resource. Missing allowances: party_verification:write') in case of invalid scope(s)

• Ensure that requested party has Employee that relate to the legal entity from token:

  • Return 403 ('Access denied') in case of error

...

• Set party DRACS verification status to prm.party_verifications table:

  • party.dracs_death_verification_status = $.dracs_death.verification_status

  • party..dracs_death_verification_reason = $.dracs_death.verification_reason

  • party..dracs_death_verification_comment = $.dracs_death.verification_comment

• Calculate cumulative verification status based on persons verification status in each stream:
  DRFO registry verification, DRACS death acts registry verification according to logic described at https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1804841790617820254221/Party+verification+status+model#Cumulative-verification-status :

  • Set calculated status to prm.party_verifications field

  • Create StatusChangeEvent in event manager with new verification status if it was changed

• Render a response according to specification