Release 4.38 MDLP on February 27, 2021

Information about the content of the release in Russian can be found at this link.

Installed on Sandbox test environment: on 25/02/2021 from 4:00 PM until 8:00 PM, MSK

Installed on productive environment: on 27/02/2021 from 8:00 PM until 12:00 AM, MSK

XSD-schemes version: 1.36

Improvements

A new feature of repeated entering was added for the faulty goods 

Return of faulty goods (operation 391 with reason_return=2) is allowed for the medicines for which the following disposal operations have been previously registered:

• 511/10511 -> 391 (withdrawal_reason=9 - "Withdrawn from circulation as a result of retail sale");
• 521/10521 -> 391 (withdrawal_reason=4 - "Withdrawn from circulation as a result of discount prescription");
• 531/10531 -> 391 (withdrawal_reason=5 - "Withdrawn from circulation as a result of issue for healthcare delivery").

When returning faulty medicine, its status will change to "paused_circulation".

In case when reason_return value has not been indicated in the registered operation (in view of the fact that the field is optional), it will be filled in as =1 by default.

Re-introduction of good quality goods has been reconsidered

Return of good quality goods (operation 391 with reason_return=1) is allowed for the medicines for which the following disposal operations have been previously registered:

• 335 (custom_procedure_code=10 - "Export") -> 391 (withdrawal_reason=10 - "Withdrawn from circulation as a result of export"). 
  Medicine status will be changed to one, which has been before operation 335/10 - "arrived", "in_circulation";
• 335 (custom_procedure_code=31 - "Re-export") -> 391 (withdrawal_reason=2 - "Withdrawn from circulation as a result of re-export").
  Medicine status will be changed to one, which has been before operation 335/31 - "released_foreign";
• 441 -> 391 (withdrawal_reason=6 - "Withdrawn from circulation as a result of shipment to unregistered participant").
  Medicine status will be changed to one, which has been before operation 441 - "in_circultion";
• 461 -> 391 (withdrawal_reason=8 - "Withdrawn from circulation as a result of shipment to EEU").
  Medicine status will be changed to one, which has been before operation 461 - "in_circultion";
• 552 (withdrawal_type=13 - "Writing off without transfer for destruction") -> 391 (withdrawal_reason=1 - "Withdrawn from circulation as a result of writing off").
  Medicine status will be changed to one, which has been before operation 552 - "marked", "released_foreign";
• 552 (withdrawal_type=6 - "Sample control") -> 391 (withdrawal_reason=7 - "Withdrawn from circulation as a result of sample control").
  Medicine status will be changed to one, which has been before operation 552 - "marked", "released_foreign".

Feature of viewing the hierarchy for SSCC belonging to a participant has been added

When using “Search for SSCC” function in the user account, the feature of getting a full packages hierarchy for requested SSCC if it belongs to Participant has been added (Figure 1).

Modifications in the Registry of SGTINs awaiting for withdrawal (CRE or Document)

• New conditions have been added for getting into the awaiting registry. Now SGTINs withdrawn from circulation under scheme 512 will be also included into the awaiting registry. 
• Scheme “512 -Dispensing of medicine other than indicated in the register receipt“ will be also displayed in the "Operation Type" field.

Thus, the "Registry of sgtins awaiting for withdrawal (CRE or document)” now includes the medicines from the following documents:

• 10511 – Retail sale using cash register equipment;
• 10522 – Released by subsidized prescription using cash register equipment;
• 511 – Retail sale;
• 512 – Dispensing of medicine other than indicated in the register receipt.

Modifications in the contents of the financial reports provided to Participant

Modifications have been introduced into the section “Finance- Reports”.

“Reports about dates of service” is outdated, thus it has been removed. A report on this form is no longer available.

“Report on emitted and paid MCs” has been changed:

1. It has been renamed “Report on paid marking codes and dates of services” (Figure 2);
2. The following columns have been added:
   2.1. “Service date”;
   2.2. “Batch number”.
3. The following columns have been deleted:
   3.1. “Quantity of marking codes transferred to the Participant based on Participant's requests, pcs”;
   3.2. “Quantity of marking codes transferred to the Participant based on Participant's requests (with “upon emission” payment type), pcs”;
   3.3. “Quantity of marking codes transferred to the Participant based on Participant's requests (with “upon application” type of payment), pcs”.

Modification date has been added into the registry of business places and into the registry of responsible storages

To optimize the work and registries uploading, the date of the records modification has been added.

The possibility to filter by new attribute has been added into the user account (Figure 3).

New methods for getting a list of responsible storages and business places have been added into API.

Disposal registrars will support new statuses

New statuses have been added into the section “Registers and classifiers - Registry of loggers of disposal”:

1. “Decommissioned” status is assigned to the disposal registrar if it is not expected to continue to be used;
2. “Acceptance rejection” status is assigned to the disposal registrar after the participant has refused to accept the registrar.

Filtering by "Status" attribute supports these modifications (Figure 4).

New "Operations with batch of documents" right has been added

"Operations with batch of documents" right has been added into the section "Administration - Rights Management" in the "Documents” item (Figure 5). It applies to the possibility of calling the following API methods:

1. "Start processing a group of documents" - POST api/v1/documents/bulk;
2. "Checking the possibility of starting a group of documents" - POST api/v1/documents/bulk/check;
3. "Getting information about a group of documents" - GET api/v1/documents/bulk/{bulkId};
4. "Getting information about groups of documents" - POST api/v1/documents/bulk/filter.

Interface improvements

• In the participant’s user account, the "Export Selected” button will change its color if the row in the table is selected (Figure 6).

• Switch has been added for the information note in the “Registry of documents- Draft documents” section (Figure 7).

• In “Administrative” section, the feature of searching has been added when creating and editing rights (Figure 8).

Feature for viewing the SGTIN tracking has been added for the Manufacturers

New section - “Products - Viewing of SGTIN tracking”, where you can see the history of medicine movement between the goods circulation participants, has been added into the user account (Figure 9).

This feature is only available to the medicine manufacturers who have ordered and applied the marking codes. The “Viewing of SGTIN tracking” right is required to work with the tracking.

Also, information is available by calling a new method - “Getting a list of operations by ICM" - GET /api/v1/reestr/sgtin/events?sgtin={sgtin}. 

This feature has been already integrated into the production environment.

Recommendations on the errors occurred during the document processing have been added

"Description of error codes during processing of xml documents" document has been finalized:

• “Working with receipt” section was added;
• Recommendations to the following errors at the document level were added:
  "200 - Identical document was sent before";
  "3012 - Operation cannot be executed. Error in event history: the operation date is specified incorrectly".
• Recommendations to the following errors at the ICM level were added:
  "11 - Operation cannot be executed. Unacceptable switch to product supply chain";
  "19 - Operation cannot be executed. Error in event history: the operation date is specified incorrectly";
  "22 - ICM is held by another participant";
  "33 - Operation cannot be executed. Specified SGTIN / SSCC is in intermediate state";
  "34 - Operation cannot be executed. Data sender and SGTIN/SSCC owner do not correspond";
  "38 - Operation cannot be executed: the specified SGTIN / SSCC is not found in the system or is disaggregated";
  "52 - Operation cannot be executed. The indicated SGTIN/SSCC is not found in the system";
  "100 - Operation cannot be executed. Aggregation requirements are violated. Check aggregated items";
  "3012 - Operation cannot be executed. Error in event history: the operation date is specified incorrectly".

API modifications

1. More information on revision list can be found in documentation. To receive technical documents on API methods, please contact technical support at support@crpt.ru.