Versions Compared

Old Version 7

changes.mady.by.user Yuliia Mazur (UA SoE eHealth)

Saved on

compared with

New Version 8

changes.mady.by.user Yuliia Mazur (UA SoE eHealth)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

Page Properties
idAPI_Specification

Link

-

Посилання на Apiary або Swagger

Resource

/graphql

Посилання на ресурс, наприклад: /api/persons/create

Scope

person:verify

Scope для доступу

Components

Patient registry

Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription

Microservices

mpi/api

il/api (rpc)

fe/admin-web

Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC

Protocol type

GraphQL

Тип протоколу, який використовується запитом, наприклад: SOAP | REST

Request type

POST

Тип запиту API, наприклад: GET, POST, PATCH…

Sync/Async

Sync

Метод є синхронним чи асинхронним?

Public/Private/Internal

Private

Потрібно зазначити тип методу за ступенем доступності

Expand
titleindex.graphql
Code Block
languagegraphql
 "Updates manual rules verification status for a single `Person` by NHS using its globally unique ID."
  updatePersonManualRulesVerificationStatus(
    input: UpdatePersonManualRulesVerificationStatusInput!
  ): UpdatePersonManualRulesVerificationStatusPayload

...

  • if verification_status = NOT_VERIFIED

    • in case of error - return 409 ('verification status comment is required')

Service logic

  1. Set fields person_verifications table (mpi database):

    1. nhs_verification_status = $.verification_status

    2. nhs_verification_comment = $.verification_comment

    3. nhs_verification_reason = MANUAL

    4. updated_by = user_id (from token)

    5. updated_at = current timestamp

  2. Calculate cumulative verification status based on persons verification status in each stream:
    Manual NHS verification, DRFO registry verification, DRACS death acts registry verification according to logic described at https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17250582534/Person + verification + status + model_EN#Cumulative-verification-statusEN:

    • Set calculated status to persons.verification_status field

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

  3. Create StatusChangeEvent in event manager with verification_status

Processing

API paragraph not found

...