Properties of a REST API method document

...

...

Document type

...

Метод REST API

...

Document title

...

[Document status] REST API [Назва методу] [ID методу]

...

Guideline ID

...

GUI-0011

...

Author

...

@

...

Document version

...

1

...

Document status

...

DRAFT

...

Date of creation

...

ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD)

...

Date of update

...

ХХ.ХХ.ХХХХ (дата зміни версії)

...

Method API ID

...

API-005-007-002-0112

...

Microservices (namespace)

...

IL

...

Component

...

Employees

...

Component ID

...

COM-005-007

...

Link на API-специфікацію

...

https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/employee-requests/create-employee-request-v2

...

Resource

...

{{host}}//api.ehealth.gov.ua/api/patients/id/encounter_package

...

Scope

...

Protocol type

...

Request type

...

Sync/Async

...

Public/Private

Purpose

The method is used to register new employee or to update an existing one. There are two different flows of registration depending on whether the employee has tax_id or doesn't have one.

Logic

...

Configuration parameters

Description of the configuration parameters that are used when processing a request in the system

Dictionaries

• POSITION

• EMPLOYEE_TYPE

• GENDER

• +DOCUMENT_TYPE

• COUNTRY

• EDUCATION_DEGREE

• QUALIFICATION_TYPE

• PHONE_TYPE

• SPECIALITY_TYPE

• SPECIALITY_LEVEL

• SPEC_QUALIFICATION_TYPE

Input parameters

Description of input parameters

...

Input parameter

...

Mandatory

...

Type

...

Description

...

Example

...

composition_id

...

 M

...

String ($uuid) (path)

...

Composition object ID

...

 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59

...

Request structure

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

{
  "signed_content": "...",
  "signed_content_encoding": "base64"
}

Headers

...

Key

...

Value

...

Mandatory

...

Description

...

Example

...

Content-Type

...

application/json

...

M

...

Тип контенту

...

Content-Type:application/json

...

Authorization

...

Bearer c2778f3064753ea70de870a53795f5c9

...

M

...

Перевірка користувача

...

Authorization:Bearer c2778f3064753ea70de870a53795f5c9

...

Request data validation

Digital signature

Decode content that is encrypted in an electronic digital signature.
Use Digital signature WS. Method checks digital signature and returns result.

Validate DRFO

1. Check that DRFO in Certificate details exists and not empty

2. Check that DRFO in Certificate details is equal to DRFO of the user that creates employee_request in Party

   1. Get party.tax_id using user_id from employee request payload

   2. Compare DRFO in Certificate with party.tax_id

      1. Convert DRFO and TAX_ID to uppercase

      2. Compare DRFO and TAX_ID as Cyrillic letters

      3. Convert DRFO to Cyrillic and compare as Cyrillic letters

   3. In case validation fails - generate 422 error

Latin to Cyrillic mapping using legal table 

Validate request (JSON schema)

1. Validate request using JSON schema

   1. In case validation fails - generate 422 error

new_employee_request_schema.json

There is an object “<employee_type>” (“doctor”, “assistant”, “specialist”…) in the body of the “employee_request”; <employee_type> is the same as employee to be created (DOCTOR, ASSISTANT, SPECIALIST, etc). Required for the employees with mandatory medical education (“doctor”, “assistant”, “specialist”, “laborant”, “med_coordinator”, ”med_admin”, ”pharmasist”).

1. if employee_type == PHARMACY_EMPLOYEE_TYPES check division_id

   1. if division_id is absent - return error 422 "division_id should be specified"

Validate request (Logic)

...

Check employee_type: Employee configurable validation rules and dictionaries

...

If employee_id is passed in the payload:

1. search employees by employee_id

   1. if not found - return error 404

2. check that employee_type not in (OWNER, PHARMACY_OWNER)

   1. in case of error - return 409 “Forbidden to create <employee_type>“

3. check employee_type and tax_id (or passport_id, if no_tax_id: true)

   1. If dosn't match, return error 409 “<field> doesn't match"

4. check that employee is active (status = APPROVED and is_active = true)

   1. in case of error - return 409 “employee is <status>“

...

Check allowed employee types for legal_entity type: Legal_Entity_Type vs Employee_Type validation rules

1. if not found - return error 404

...

Validate legal entity type status for current legal entity: status should be active or suspended

Validate party

...

Properties of a REST API method document

Purpose

The method is used to register new employee or to update an existing one. There are two different flows of registration depending on whether the employee has tax_id or doesn't have one.

Logic

...

Configuration parameters

Description of the configuration parameters that are used when processing a request in the system

Dictionaries

• POSITION

• EMPLOYEE_TYPE

• GENDER

• +DOCUMENT_TYPE

• COUNTRY

• EDUCATION_DEGREE

• QUALIFICATION_TYPE

• PHONE_TYPE

• SPECIALITY_TYPE

• SPECIALITY_LEVEL

• SPEC_QUALIFICATION_TYPE

Input parameters

Description of input parameters

Request structure

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

{
  "signed_content": "...",
  "signed_content_encoding": "base64"
}

Headers

Request data validation

Digital signature

Decode content that is encrypted in an electronic digital signature.
Use Digital signature WS. Method checks digital signature and returns result.

Validate DRFO

1. Check that DRFO in Certificate details exists and not empty

2. Check that DRFO in Certificate details is equal to DRFO of the user that creates employee_request in Party

   1. Get party.tax_id using user_id from employee request payload

   2. Compare DRFO in Certificate with party.tax_id

      1. Convert DRFO and TAX_ID to uppercase

      2. Compare DRFO and TAX_ID as Cyrillic letters

      3. Convert DRFO to Cyrillic and compare as Cyrillic letters

   3. In case validation fails - generate 422 error

Latin to Cyrillic mapping using legal table 

Validate request (JSON schema)

1. Validate request using JSON schema

   1. In case validation fails - generate 422 error

new_employee_request_schema.json

There is an object “<employee_type>” (“doctor”, “assistant”, “specialist”…) in the body of the “employee_request”; <employee_type> is the same as employee to be created (DOCTOR, ASSISTANT, SPECIALIST, etc). Required for the employees with mandatory medical education (“doctor”, “assistant”, “specialist”, “laborant”, “med_coordinator”, ”med_admin”, ”pharmasist”).

1. if employee_type == PHARMACY_EMPLOYEE_TYPES check division_id

   1. if division_id is absent - return error 422 "division_id should be specified"

Validate request (Logic)

1. Check employee_type: Employee configurable validation rules and dictionaries

2. If employee_id is passed in the payload:

   1. search employees by employee_id

      1. if not found - return error 404

   2. check that employee_type not in (OWNER, PHARMACY_OWNER)

      1. in case of error - return 409 “Forbidden to create <employee_type>“

   3. check employee_type and tax_id (or passport_id, if no_tax_id: true)

      1. If dosn't match, return error 409 “<field> doesn't match"

   4. check that employee is active (status = APPROVED and is_active = true)

      1. in case of error - return 409 “employee is <status>“

3. Check allowed employee types for legal_entity type: Legal_Entity_Type vs Employee_Type validation rules

   1. if not found - return error 404

4. Validate legal entity type status for current legal entity: status should be active or suspended

5. Validate party

   1. first_name, last_name, second_name have the same validation pattern - `^(?!.*[ЫЪЭЁыъэё@%&$^#])[А-ЯҐЇІЄа-яґїіє’\\'\\- ]+$` 

      1. if doesn't match, return error 422 "string does not match pattern ..."

   2. validate birth_date

      1. birth_date > 1900-01-01 and birth_date < current date

         1. otherwise return error 422 "invalid birth_date value"

      2. birth_date has validation pattern - `^(\\d{4}(?!\\d{2}\\b))((-?)((0[1-9]|1[0-2])(\\3([12]\\d|0[1-9]|3[01]))?|W([0-4]\\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\\d|[12]\\d{2}|3([0-5]\\d|6[1-6])))?)?$`

         1. if doesn't match, return error 422 "expected 'birth_date' to be a valid ISO 8601 date"

   3. gender has one of the following values - "FEMALE", "MALE"

      1. otherwise return error 422 "value is not allowed in enum"

   4. validate tax_id

      1. tax_id has validation pattern - `^([0-9]{9,10}|[А-ЯЁЇIЄҐ]{2}\\d{6})$`

         1. if doesn't match, return error 422 "string does not match pattern ..."

   5. validate birth_date

      1. birth_date > 1900-01-01 and birth_date < current date

         1. otherwise return error 422 "invalid birth_date value"

      2. birth_date has validation pattern - `^(\\d{4}(?!\\d{2}\\b))((-?)((0[1-9]|1[0-2])(\\3([12]\\d|0[1-9]|3[01]))?|W([0-4]\\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\\d|[12]\\d{2}|3([0-5]\\d|6[1-6])))?)?$`

         1. if doesn't match, return error 422 "expected 'birth_date' to be a valid ISO 8601 date"

   6. gender has one of the following values - "FEMALE", "MALEemail has validation pattern - `^[\\w!#$%&'*+/=?`{|}~^-]+(?:\\.[\\w!#$%&'*+/=?`{|}~^-]+)*@(?:[A-Z0-9-]+\\.)+[A-Z]{2,6}$`

      1. if doesn't match, return error 422 "expected 'email' to be an email address"

   7. validate documents

      1. documents.type has one of the following values:

         1. "BIRTH_CERTIFICATE"

         2. "BIRTH_CERTIFICATE_FOREIGN"

         3. "COMPLEMENTARY_PROTECTION_CERTIFICATE"

         4. "NATIONAL_ID"

         5. "PASSPORT"

         6. "PERMANENT_RESIDENCE_PERMIT"

         7. "REFUGEE_CERTIFICATE"

         8. "TEMPORARY_CERTIFICATE"

         9. "TEMPORARY_PASSPORT"

            1. otherwise return error 422 "value is not allowed in enum"

      validate tax_id

      1. tax_id documents.number has validation pattern - `^([0-9]{9,10}|[А-ЯЁЇIЄҐ]{2}\\d{6})$`

         1. if doesn't match, return error 422 "string does not match pattern ..."

   8. email has validation pattern - `^[\\w!#$%&'*+/=?`{|}~^-]+(?:\\.[\\w!#$%&'*+/=?`{|}~^-]+)*@(?:[A-Z0-9-]+\\.)+[A-Z]{2,6}$`

      1. if doesn't match, return error 422 "expected 'email' to be an email address"

   9. validate documents

      1. documents.type has one of the following values:

         1. "BIRTH_CERTIFICATE"

         2. "BIRTH_CERTIFICATE_FOREIGN"

         3. "COMPLEMENTARY_PROTECTION_CERTIFICATE"

         4. "NATIONAL_ID"

         5. "PASSPORT"

         6. "PERMANENT_RESIDENCE_PERMIT"

         7. "REFUGEE_CERTIFICATE"

         8. "TEMPORARY_CERTIFICATE"

         9. "TEMPORARY_PASSPORT"

            1. otherwise return error 422 "value is not allowed in enum"

      2. documents.number has validation pattern according to documents.type

         1. BIRTH_CERTIFICATE - `^((?![ЫЪЭЁыъэё@%&$^#`~:,.*|}{?!])[A-ZА-ЯҐЇІЄ0-9№\\/()-]){2,25}$`

         2. COMPLEMENTARY_PROTECTION_CERTIFICATE - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         3. NATIONAL_ID - `^[0-9]{9}$`

         4. PASSPORT - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         5. PERMANENT_RESIDENCE_PERMIT - `^(((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{4,6}|[0-9]{9}|((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{5}\\/[0-9]{5})$`

         6. REFUGEE_CERTIFICATE - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         7. TEMPORARY_CERTIFICATE - `^(((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{4,6}|[0-9]{9}|((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{5}\\/[0-9]{5})$`

         8. TEMPORARY_PASSPORT - `^((?![ЫЪЭЁыъэё@%&$^#`~:,.*|}{?!])[A-ZА-ЯҐЇІЄ0-9№\\/()-]){2,25}$`

      3. validate documents.issued_at 

         1. documents.issued_at has validation pattern - `^(\\d{4}(?!\\d{2}\\b))((-?)((0[1-9]|1[0-2])(\\3([12]\\d|0[1-9]|3[01]))?|W([0-4]\\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\\d|[12]\\d{2}|3([0-5]\\d|6[1-6])))?)?$`

            1. if doesn't match, return error 422 "expected 'issued_at' to be a valid ISO 8601 date"

   10. validate phones

       1. phones.type has one of the following values - "LAND_LINE", "MOBILE"

          1. otherwise return error 422 "value is not allowed in enum"

       2. phones.number has validation pattern - `^\\+38[0-9]{10}$`

          1. if doesn't match, return error 422 "string does not match pattern ..."

          2.  

Alternative notation 2 of validation :

...

1. 1. 1. according to documents.type

         1. BIRTH_CERTIFICATE - `^((?![ЫЪЭЁыъэё@%&$^#`~:,.*|}{?!])[A-ZА-ЯҐЇІЄ0-9№\\/()-]){2,25}$`

         2. COMPLEMENTARY_PROTECTION_CERTIFICATE - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         3. NATIONAL_ID - `^[0-9]{9}$`

         4. PASSPORT - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         5. PERMANENT_RESIDENCE_PERMIT - `^(((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{4,6}|[0-9]{9}|((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{5}\\/[0-9]{5})$`

         6. REFUGEE_CERTIFICATE - `^((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{6}$`

         7. TEMPORARY_CERTIFICATE - `^(((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{4,6}|[0-9]{9}|((?![ЫЪЭЁ])([А-ЯҐЇІЄ])){2}[0-9]{5}\\/[0-9]{5})$`

         8. TEMPORARY_PASSPORT - `^((?![ЫЪЭЁыъэё@%&$^#`~:,.*|}{?!])[A-ZА-ЯҐЇІЄ0-9№\\/()-]){2,25}$`

      2. validate documents.issued_at 

         1. documents.issued_at has validation pattern - `^(\\d{4}(?!\\d{2}\\b))((-?)((0[1-9]|1[0-2])(\\3([12]\\d|0[1-9]|3[01]))?|W([0-4]\\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\\d|[12]\\d{2}|3([0-5]\\d|6[1-6])))?)?$`

            1. if doesn't match, return error 422 "expected 'issued_at' to be a valid ISO 8601 date"

   2. validate phones

      1. phones.type has one of the following values - "LAND_LINE", "MOBILE"

         1. otherwise return error 422 "value is not allowed in enum"

      2. phones.number has validation pattern - `^\\+38[0-9]{10}$`

         1. if doesn't match, return error 422 "string does not match pattern ..."

         2.  

Alternative notation 2 of validation :

if (employee_id is passed in the payload) {
	result=search employees by employee_id;
	if (result == false) {
		return error 404 }
	else { 
		result=check * employee_type and * tax_id
		if (result == false) {
			return error 409}
		else {
			if (employee is active) {
				if (employee_type = OWNER || employee_type = PHARMACY_OWNER) {
					set status = APPROVED
					set is_active = false}
				if (employee_type not OWNER && employee_type not PHARMACY_OWNER) {
					set status = DISMISSED
					set is_active = true}
				if (employee is active) {
					create employee request }
				else {
					return error 409 }
					}
				}
			}
		}
	}
}	
result=search employee_type_legal_entity_type_links by employee_type+legal_entity_type
if (result == false) {
			return error 409}
		else {
			if (employee is active) {
				if (employee_type = OWNER || employee_type = PHARMACY_OWNER) {
					set status = APPROVED
					set is_active = false}
				if (employee_type not OWNER && employee_type not PHARMACY_OWNER) {
					set status = DISMISSED
					set is_active = true}
				if (employee is active) {
					create employee request }
				else {
					return error 409 }
					}
				}
			}
		}
	}
}	
result=search employee_type_legal_entity_type_links by employee_type+legal_entity_type
if (result == false) {
		return error 404 }

Processing

Save signed declaration to media storage

Get url for declaration upload.
Use Request a Secret WS

Parameter

Source

action

'GET'

bucket

'EMPLOYEE_REQUESTS'

resource_id

: EMPLOYEE_REQUEST_ID

resource_name

: signed_employee_request

...

Upload signed declaration to media storage

Create employee request

Create employee request in IL_DB table - employee_request.

1.  

   1. generate GUID and writte in id column

   2. write JSON object with employee request details

Send activation link on email

1. Generate activation link, which contains Employee request GUID

2. Send activation URL on user email

   1. invoke service - Send message

Updating employee data

To update the data of an existing employee use the endpoint `Create Employee Request v2`.
It is necessary to transfer the same JSON as when creating employee request with the same id of an existing employee.

There are several rules when updating employee data:

1. position can not be changed

   1. in case of failure, return error 422 "employee position can not be changed"

2. Start_date can not be changed

   1. in case of failure, return error 422 "start_date doesn't match"

3. If specialities.speciality_officio:true, in this object value of speciality can not be changed (with several exceptions in the item b)

   1. in case of failure, return error 422 "main speciality can not be changed"

   2. there are following exceptions related to speciality changing for legal entity types “PRIMARY CARE” and “MSP“: 

...

Old speciality

...

New speciality

...

Status details for existing declarations

...

pediatrician

...

family_doctor

...

patient's declarations aged 0 to 18 remain status “active”

...

pediatrician

...

therapist

...

patient's declarations aged 0 to 18 change status to “terminated”

...

family_doctor

...

therapist

...

patient's declarations aged 18 and older remain status “active”

...

patient's declarations aged 0 to 18 change status to “terminated”

...

family_doctor

...

pediatrician

...

patient's declarations aged 0 to 18 remain status “active”

...

patient's declarations aged 18 and older change status to “terminated”

...

therapist

...

family_doctor

...

patient's declarations aged 18 and older remain status “active”

...

therapist

...

pediatrician

...

patient's declarations aged 18 and older change status to “terminated”

Response structure

Response structure examples

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API response structure, example

404 }

Processing

Save signed declaration to media storage

1. Get url for declaration upload.
   Use Request a Secret WS

   Parameter

   Source

   action

   'GET'

   bucket

   'EMPLOYEE_REQUESTS'

   resource_id

   : EMPLOYEE_REQUEST_ID

   resource_name

   : signed_employee_request

    

2. Upload signed declaration to media storage

Create employee request

Create employee request in IL_DB table - employee_request.

1.  

   1. generate GUID and writte in id column

   2. write JSON object with employee request details

Send activation link on email

1. Generate activation link, which contains Employee request GUID

2. Send activation URL on user email

   1. invoke service - Send message

Updating employee data

To update the data of an existing employee use the endpoint `Create Employee Request v2`.
It is necessary to transfer the same JSON as when creating employee request with the same id of an existing employee.

There are several rules when updating employee data:

1. position can not be changed

   1. in case of failure, return error 422 "employee position can not be changed"

2. Start_date can not be changed

   1. in case of failure, return error 422 "start_date doesn't match"

3. If specialities.speciality_officio:true, in this object value of speciality can not be changed (with several exceptions in the item b)

   1. in case of failure, return error 422 "main speciality can not be changed"

   2. there are following exceptions related to speciality changing for legal entity types “PRIMARY CARE” and “MSP“: 

Response structure

Response structure examples

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API response structure, example

{
  "meta": {
    "code": 201,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  },
  "data": {
    "division_id": "b075f148-7f93-4fc2-b2ec-2d81b19a9b7b",
    "legal_entity_id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
    "position": "P8",
    "start_date": "2017-03-02T10:45:16.000Z",
    "end_date": "2018-03-02T10:45:16.000Z",
    "status": "NEW",
    "employee_type": "DOCTOR",
    "party": {
      "first_name": "Петро",
      "last_name": "Іванов",
      "second_name": "Миколайович",
      "birth_date": "1991-08-19T00:00:00.000Z",
      "statusgender": "NEWMALE",
      "employeeno_tax_typeid": "DOCTOR"false,
      "party": {
      "first_nametax_id: 3126509816 (string, required) - if no_tax_id=true then passport number, otherwise tax_id": "Петро",
      "last_nameemail": "Івановemail@example.com",
      "second_namedocuments": "Миколайович", [
        {
          "birth_datetype": "1991-08-19T00:00:00.000ZPASSPORT",
          "gendernumber": "MALEАА120518",
          "noissued_tax_idby": false,
 "Рокитнянським РВ ГУ МВС Київської області",
    "tax_id: 3126509816 (string, required) - if no_tax_id=true then passport number, otherwise tax_id": "",
"issued_at": "2017-02-28"
        }
     "email": "email@example.com" ],
      "documentsphones": [
        {
          "type": "PASSPORTMOBILE",
          "number": "АА120518"+380503410870"
        }
      ],
      "working_experience": 10,
      "issuedabout_bymyself": "Рокитнянським РВ ГУ МВС Київської області"Закінчив всі можливі курси"
    },
    "doctor": {
      "issued_ateducations": "2017-02-28"[
        }{
      ],    "country": "UA",
 "phones": [         {"city": "Київ",
          "typeinstitution_name": "MOBILEАкадемія Богомольця",
          "numberissued_date": "+380503410870"2017-02-28",
        }
  "diploma_number": "DD123543",
     ],       "working_experiencedegree": 10,"MASTER",
          "about_myselfspeciality": "ЗакінчивПедіатр"
 всі можливі курси"     },
     "doctor": { ],
      "educationsqualifications": [
        {
          "countrytype": "UASPECIALIZATION",
          "cityinstitution_name": "КиївАкадемія Богомольця",
          "institution_namespeciality": "Академія БогомольцяПедіатр",
          "issued_date": "2017-02-28",
          "diplomacertificate_number": "DD1235432017",
          "degreevalid_to": "MASTER2017",
          "specialityadditional_info": "Педіатрдодаткова інофрмація"
        }
      ],
      "qualificationsspecialities": [
        {
          "typespeciality": "SPECIALIZATIONTHERAPIST",
          "institutionspeciality_nameofficio": "Академія Богомольця"true,
          "specialitylevel": "ПедіатрFIRST",
          "issuedqualification_datetype": "2017AWARDING",
          "certificateattestation_numbername": "2017Академія Богомольця",
          "validattestation_todate": "2017-02-28",
          "additionalvalid_to_infodate": "додаткова інофрмація"
2020-02-28",
       }
      ],       "specialitiescertificate_number": [ "AB/21331"
        }
  {    ],
      "specialityscience_degree": "THERAPIST",{
          "speciality_officiocountry": true"UA",
          "levelcity": "FIRSTКиїв",
 
        "qualification_typedegree": "AWARDING",

         "attestationinstitution_name": "Академія Богомольця",
 
        "attestationdiploma_datenumber": "2017-02-28DD123543",
          "valid_to_date"speciality": "2020-02-28Педіатр",
          "certificateissued_numberdate": "AB/213312017"
      }
 }   },
   ], "id": "b075f148-7f93-4fc2-b2ec-2d81b19a9b7b",
    "scienceinserted_degreeat": {
   "2017-05-05T14:09:59.232112",
    "countryupdated_at": "UA",2017-05-05T14:09:59.232112"
  }
   }HTTP  "city": "Київ",
        "degree": "",
        "institution_name": "Академія Богомольця",
        "diploma_number": "DD123543",
        "speciality": "Педіатр",
        "issued_date": "2017"
      }
    },
    "id": "b075f148-7f93-4fc2-b2ec-2d81b19a9b7b",
    "inserted_at": "2017-05-05T14:09:59.232112",
    "updated_at": "2017-05-05T14:09:59.232112"
  }
}HTTP status codes

...

Response code

...

HTTP Status code

...

Message

...

Internal name

...

Description

...

Базові

...

1000

...

404

...

Composition not found

...

COMPOSITION_NOT_FOUND_404

...

Не знайдено медичний висновок

...

401

...

Unauthorized

...

Помилка підтвердження

...

Специфічні

...

status codes

HTTP status codes

Post-processing processes

Description of actions performed on data after processing

Technical modules where the method is used

List of pages describing technical modules where the method is used

...