ЕСОЗ - публічна документація

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Version compatibility

#TestPreconditionsInputExpected resultActual resultRealised in Postman
1Create Legal Entity (LE) with api v1






req.edrpou != prm.legal_entities.edrpouValid data for v1
req.type = MSP		200200Create LE / v1 / PUT MSP type v1
2req.edrpou != prm.legal_entities.edrpouValid data for v1
req.type = PHARMACY		200200
Create LE /v1 / PUT PHARMACY type v1
3req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type=MSP		422422
Create LE /v1 / MSP type v2 payload format - validation failed
4req.edrpou != prm.legal_entities.edrpouValid data for v1
req.type = PRIMARY_CARE		422422
Create LE /v1 / PRIMARY_CARE type v1 - invalid type
4.1req.edrpou != prm.legal_entities.edrpouValid data for v1
req.type = MSP_PHARMACY		422422Create LE /v1 / MSP_PHARMACY type v1 - invalid type
5

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within EDRPOU property

Valid data for v1

req.edr-data-id.edrpou != req.edrpou

req.type = MSP

422200Create LE /v1 / MSP3 type v1 - edrpou differs from EDR data
6

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within legal form  property

Valid data for v1

req.edr-data-id.olf_code != req.legal_form

req.type = MSP

422422Create LE /v1 / MSP3 type v1 - legal form differs from EDR data
7

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within name  property

Valid req v1
edr-data-id.names.display != req.public_name

req.type = MSP

422422Create LE /v1 / MSP3 type v1 - name differs from EDR data
8

Information about company is absent in EDR

Valid req v1
edr-data-id is absent
edr-data-list is absent

422500Create LE /v1 / MSP type v1 - EDR data is absent
9Create LE api v2




req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type = MSP		409
Create LE /v2 / PUT MSP type v2 - invalid type
10req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type = PHARMACY		200200
Create LE /v2 / PUT PHARMACY type v2
11req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type = PRIMARY_CARE		200200
Create LE /v2 / PUT PRIMARY_CARE type v2
12req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type = OUTPATIENT		200200
Create LE /v2 / PUT OUTPATIENT type v2
13req.edrpou != prm.legal_entities.edrpouValid data for v1422
Create LE /v2 / MSP type v1 payload format - validation failed
14req.edrpou != prm.legal_entities.edrpouValid data for v2
req.type = MSP_PHARMACY		409
Create LE /v2 / MSP_PHARMACY type v2 - invalid type
15

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within EDRPOU property

Valid data for v2

req.edr-data-id.edrpou != req.edrpou

req.type = PRIMARY_CARE

409

16

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within legal form  property

Valid data for v2

req.edr-data-id.olf_code != req.legal_form

req.type = PRIMARY_CARE

409

17

req.edrpou != prm.legal_entities.edrpou

req.data doesn`t correspond to EDR data within name  property

Valid data for v2

req.edr-data-id.name != req.name

req.type = PRIMARY_CARE

409

18

req.edrpou != prm.legal_entities.edrpou

EDR identifier exists in eHealth and linked to another LE

Valid data for v1

req.edr_data.id = prm.edr_data.id

409


req.edrpou != prm.legal_entities.edrpou

req.type = PRIMARY_CARE

req.license.type = PHARMACY422


req.edrpou != prm.legal_entities.edrpou

req.type = PHARMACY

eq.license.type = MSP422


req.edrpou != prm.legal_entities.edrpou

req.type = PRIMARY_CARE

req.license is empty422

19Update LE api v1

req.edrpou = prm.legal_entities.edrpou

prm.legal_entity.type=MSP and created with v1 api

Valid data for v1.
req.type = MSP		200
Update LE /v1 / MSP type v1
20

req.edrpou = prm.legal_entities.edrpou

prm.legal_entity.type=MSP and created with v1 api

Valid req for v1
req.type = PRIMARY_CARE		422
Update LE /v1 / MSP1 to PRIMARY_CARE v1  - invalid type

req.edrpou = prm.legal_entities.edrpou
EDR data exists in eHealth but not in EDR

Valid data for v1

req.edr-data-id.id is absent
req.edrpou = prm.legal_entities.edrpou

422
Update LE /v1 / MSP type v1 - EDR is absent
21Update LE api v2

req.edrpou = prm.legal_entities.edrpou

prm.legal_entity.type=MSP created with v1

Valid req for v2
req.type = PRIMARY_CARE		200
Update LE /v2 / MSP2 to PRIMARY_CARE2 v2
22

req.edrpou = prm.legal_entities.edrpou

prm.legal_entity.type=PRIMARY_CARE created with v2

Valid data for v2
req.type = PRIMARY_CARE		200
Update LE /v2 / PRIMARY_CARE type v2
23

req.edrpou = prm.legal_entities.edrpou

prm.legal_entity.type=MSP created with v2

Valid data for v2
req.type = MSP		409
Update LE /v2 / MSP type v2 - incorrect type
24

req.edrpou = prm.legal_entities.edrpou

LE has already assigned licenses.type=MSP

req.license id is empty
req.license.type=MSP		409
Update LE /v2 / PRIMARY_CARE type v2 - license type duplication
25

req.edrpou = prm.legal_entities.edrpou

LE updates another LE license.
prm.license.id exists in eHealth

req.license id != prm.license.id409
Update LE /v2 / PRIMARY_CARE type v2 - license id from another LE
26Find LE with api v1prm.legal_entity created with v1edrpou200
One LE v1 was found
Find LE /v1 / LE v1 by edrpou
27prm.legal_entity created with v1
prm.legal_entity created with v2		settlement_id &&
type &&
status &&
nhs_verified		200
Result set includes LE v1 and v2
Find LE/v1 / LE v1 and v2 by params
28Find LE with api v2prm.legal_entity created with v2edrpou200
One LE v1 was found
Find LE/v2 / LE v1 by edrpou
29prm.legal_entity created with v1
prm.legal_entity created with v2		settlement_id &&
type &&
status &&
nhs_verified		200
Result set includes LE v1 and v2
Find LE/v2 / LE v1 and v2 by params
30Get LE with api v1prm.legal_entity created with v1legal_entity_id200
One LE v1 was returned
Get LE/v1 / LE v1
31prm.legal_entity created with v2legal_entity_id200
One LE v2 was returned
Get LE/v1 / LE v2
32Get LE with api v2prm.legal_entity created with v1legal_entity_id200
One LE v1 was returned
Get LE/v2 / LE v1
33prm.legal_entity created with v2legal_entity_id200
One LE v2 was returned
Get LE/v2 / LE v2
34Verify LE by MIS  with api v1prm.legal_entity created with v1
prm.legal_entity.mis_verified=NOT_VERIFIED		legal_entity_id200 OK
LE updated with mis_verified=VERIFIED
Verify LE by MIS / not verified MSP v1
35prm.legal_entity created with v1
prm.legal_entity.mis_verified=VERIFIED		legal_entity_id409
LE wasn`t updated
Verify LE by MIS / verified MSP v1
36prm.legal_entity created with v2
prm.legal_entity.mis_verified=NOT_VERIFIED		legal_entity_id405
Verify LE by MIS / not verified MSP v2
37Verify LE by NHS with api v1prm.legal_entity created with v1
prm.legal_entity.nhs_verified=false
prm.legal_entity.status=ACTIVE		legal_entity_id200 OK
LE updated with nhs_verified=true
Virify by NHS / not verified MSP v1
38prm.legal_entity created with v1
prm.legal_entity.nhs_verified=true
prm.legal_entity.status=ACTIVE		legal_entity_id409
LE not updated
Virify by NHS / verified MSP v1
39prm.legal_entity created with v2
prm.legal_entity.nhs_verified=false
prm.legal_entity.status=ACTIVE		legal_entity_id200 OK
LE updated with nhs_verified=true
Virify by NHS / not verified MSP v2

40

Create Division with api v1Owner`s employee already exists.
prm.legal_entity.type=MSP created with v1		req.type=CLINIC200
Division was created
Create divisions \ CLINIC for MSP v1
41Owner`s access token is valid.
prm.legal_entity.type=PRIMARY_CARE created with v2		req.type=FAP200
Division was created
Create divisions \ FAP for PRIMARY_CARE v2
42Owner`s access token is valid.
prm.legal_entity.type=PRIMARY_CARE created with v2		req.type=DRUGSTORE

422

Division wasn`t created


Create divisions \ DRUGSTORE for PRIMARY_CARE v2 - invalid division type
43Create Employee Request api v1Owner`s employee already exists.
prm.legal_entity.type=MSP created with v1		req.type=DOCTOR200 OK
Employee request was created, status=new
Create Employee /v1 / DOCTOR for MSP v1
44Owner`s employee already exists.
prm.legal_entity.type=PRIMARY_CARE created with v2		req.type=PHARMACIST

404

Employee request wasn`t created


Create Employee /v1 /PHARMACIST for PRIMARY_CARE v2 - invalid employee type
45Owner`s access token is valid.
prm.legal_entity.type=PRIMARY_CARE created with v2		req.type=DOCTOR200 OK
Employee request was created, status=new
Create Employee /v1 / DOCTOR for PRIMARY_CARE v2
46Owner`s employee already exists.
prm.legal_entity.type=PRIMARY_CARE created with v2		req.type = DOCTOR
req.doctor.specialities.speciality = PHARMACIST (only)		409
Create Employee /v1 / DOCTOR for PRIMARY_CARE v2 - wrong speciality PHARMACIST
47Approve Employee api v1Employee req created for LE v1
Emplotee request exists in status=new		employee_requests.id
200 OK
employee_requests.status=APPROVED, employee created, user created, party created,

Approve Employee / DOCTOR of MSP v1
48Employee req created for LE v2
Emplotee request exists in status=new		employee_requests.id
200 OK
employee_requests.status=APPROVED, employee created, user created, party created,

Approve Employee / DOCTOR of PRIMARY_CARE v2
49Create Contract api v1LE created with api v1Valid req data200
Create contract request/ Create contract request - MSP v1
50LE created with api v2Valid req data200
Create contract request/ Create contract request - MSP v2
51Create Declaration RequestLE created with api v1Valid data200
Create and Approve Declaration / Create Declaration Request Auth OTP v2 - for MSP v1
52LE created with api v2Valid data200
Create and Approve Declaration / Create Declaration Request Auth OTP v2 - for PRIMARY_CARE v2
53Approve Declaration RequestLE created with api v1Valid data200
Create and Approve Declaration / Approve declaration request - for MSP v1
55LE created with api v2Valid data200
Create and Approve Declaration / Approve declaration request - for PRIMARY_CARE v2
55Sign Declaration RequestLE created with api v1Valid data200
Create and Approve Declaration / Sign declaration request - MSP v1
56LE created with api v2Valid data200
Create and Approve Declaration / Sign declaration request - PRIMARY_CARE v2
57Create Medication Request RequestLE created with api v1Valid data200
Create and approve Medication request / Create Medication_request_request - MSP v1
58LE created with api v2Valid data200
Create and approve Medication request / Create Medication_request_request - PRIMARY_CARE v2
59Sign Medication Request RequestLE created with api v1Valid data200
Create and approve Medication request / Medication_request_request Sign - MSP v1
60LE created with api v2Valid data200
Create and approve Medication request / Medication_request_request Sign - PRIMARY_CARE v2
61Deactivate LE api v1LE created with api v1.
prm.legal_entity.is_active = true & prm.legal_entity.status = (ACTIVE or SUSPENDED)
LE has active employees		req.legal_entity_id
200 OK
prm.legal_entity.status=CLOSED & is_active=false,
related owner has is_active = false,
related other employees has status=DISMISSED,
related contracts has is_suspended=true & status=TERMINATED & reason=auto_deactivation_legal_entity
related contract requests has status=TERMINATED & reason=auto_deactivation_legal_entity

Deactivate LE / MSP v1
62LE created with api v2.
prm.legal_entity.is_active = true & prm.legal_entity.status = (ACTIVE or SUSPENDED)
LE has active employees		req.legal_entity_id
200 OK
prm.legal_entity.status=CLOSED & is_active=false,
related owner has is_active = false,
related other employees has status=DISMISSED,
related contracts has is_suspended=true & status=TERMINATED & reason=auto_deactivation_legal_entity
related contract requests has status=TERMINATED & reason=auto_deactivation_legal_entity

Deactivate LE / PRIMARY_CARE v2
  • No labels

ЕСОЗ - публічна документація