RC_Rx_Deactivate healthcare service (modified - EN)

Purpose

This WS is designed to deactivate healthcare service for division of legal entity.

Key points

1. Only authenticated and authorized user with appropriate scope can deactivate healthcare service.

2. Only active healthcare service can be deactivated.

3. Healthcare service can be deactivated for legal entities in ACTIVE or SUSPENDED statuses.

4. User can deactivate healthcare services only of its legal entity.

Specification

Apiary

Authorization

• Verify the validity of access token

  • in case of error - 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 = 'healthcare_service:write')

  • return 403 (“Your scope does not allow to access this resource. Missing allowances: healthcare_service:write”) in case of invalid scope(s)

Validations

Validate legal entity

• Extract legal entity id from access token. Check that legal entity is in ‘ACTIVE’ or ‘SUSPENDED’ status

  • in case of error - return 409 (“Invalid legal entity status”)

Validate healthcare service

• Get healthcare service by $.id. Check that healthcare service exists in PRM DB

  • in case of error - return 404 (“not_found”)

• Get healthcare service by $.id. Check that healthcare service belongs to legal entity id from access token

  • in case of error - return 403 (“forbidden”)

Validate transition

• Get healthcare service by $.id. Check that healthcare service status = ‘ACTIVE’

  • in case of error - return 409 (“healthcare_service.status healthcare service cannot be DEACTIVATED”), where healthcare_service.status = value of status of healthcare service from PRM DB

Service logic

1. Update healthcare service in healthcare_services table (PRM DB) with data from request and additional fields:

   1. status = 'INACTIVE';

   2. updated_at = now();

   3. updated_by = user_id from access token;