×

"Approved"

Order No. 2 dated 31 March 2023.

Acting Director of "Siroka Technology" Ltd.

Bozhokoyev E.Zh.


 

Regulations on rendering technical support services

Siroka Technology LLC
 

1. GENERAL PROVISIONS


 

1.1 This Regulation establishes the procedure for providing technical support services to Customers, users of software and services of Siroka Technology LLC (hereinafter referred to as the Company).


 

1.2 Technical support is provided by the Company's Technical Support Department.


 

1.3 Technical support services are provided exclusively to the Company's Clients on the basis of valid Licence or Sublicence agreements.


 

1.4 Issues that cannot be solved using the existing functionality are transferred to the development department, where a decision is made on the possibility of releasing a corresponding update. The terms of the update release are determined in the process of problem diagnostics and in accordance with the general development plan.


 

1.5 The technical support service cannot guarantee the time of problem resolution, as the time of problem resolution may be influenced by various factors, for example, timeliness of user response, necessity of bench testing and software revision.


 

1.6 The response time is determined by the total workload of technical support specialists and may be shorter than the terms stated in the regulations. In some cases, issues may be resolved immediately after receiving additional information from users.


 

1.7 Technical support provides for different levels of service (clause 2 of these Regulations).


 

1.8 The Company has the right to unilaterally make changes to these Regulations with obligatory notification of users by publishing the new Regulations on the official website of the Company https://siroca.com/ .


 

2. PROCEDURE FOR SUBMISSION AND PROCESSING OF REQUESTS TO THE TECHNICAL SUPPORT DEPARTMENT


 

2.1 The basis for performance of works on technical support is the following

Customer's request. Appeal is considered:

- appeal by phone: +996 755 97 98 05 or +996 312 97 98 05;

- an e-mail sent to the e-mail address: support@siroca.com;

- appeal to the Company's Telegram bot: @Siroca_Technology_bot

- filling out an application on the official website www.siroca.com in the "Technical Support" section.


 

2.2 Technical support is not provided by other means (WhatsApp, Skype and other messaging services), as well as by e-mail addresses other than those specified in these Regulations. Such means of communication shall be considered only as means of communication and general consultations.

Questions and appeals from other channels are not official appeals and are not registered in the Help Desk system.


 

2.3 Requests to the Technical Support Department are accepted 24/7 and are executed in the order of their receipt. Addresses with a higher level of criticality that require emergency intervention or consultation of the Technical Support Department specialists can be executed out of turn.


 

2.4 The appeals with criticality level No. 1 and No. 2 are executed 24 hours a day, 7 days a week, 24/7. Appeals with criticality level № 3 and № 4 - on working days (Monday - Friday) from 9 a.m. to 6 p.m. Bishkek time.


 

2.5 Determining the level of criticality of the problem

Upon registration of a request, employees of the Company's Technical Support Department determine the degree of influence of the indicated problem on software operability, taking into account also the number of Software Users affected by the incident, and then assign the appropriate level of criticality to it.

Level 1 (critical) is assigned to:

- an incident that stops the Customer's critical business processes: an emergency situation in which the Software is completely inoperable or the majority of the Software functions are not executed.

Level #2 (high) is assigned to:

- an incident that reduces the functionality of the Customer's critical business processes: an emergency situation in which the Software functions partially or with low performance;

Level #3 (medium) is assigned to:

- an incident that causes a minor software operation error, but does not prohibit user access to the system: the Software is functional, Technical Consultation is required.

Level #4 (low) is assigned to:

- An incident that is essentially a request for a change, adjustment, or reporting in the Software. The software is not functioning properly, and the reporting functionality needs to be expanded

If there is more than one request at the same time, the requests with a higher level of criticality are considered first.


 

2.6 Response and reaction time to requests.

The average response time to the Appeal to the Technical Support Department from the moment of its receipt is 15 minutes.


 

Maximum time to resolve an incident according to the established level of criticality:

- Problem Resolution Time / Critical 1 hour

- Problem resolution time / High up to 8 hours

- Problem resolution time / Medium up to 2 working days

- Issue Resolution Time / Low up to 5 working days

In some cases, issues may be resolved almost immediately upon receipt of questions or additional information from the Customer. The reaction of the Technical Support Department staff to the receipt of additional information may be longer, but not longer than the maximum reaction time defined for the assigned (given) criticality level.

2.7 Software Updates

In case of detection of problems or emergencies, the solution of which requires immediate unscheduled software update, the Technical Support Department shall send a notification to the Customer's authorised persons.


 


 


 

3. PROCEDURE FOR PROCESSING REQUESTS TO THE TECHNICAL SUPPORT SERVICE


 

3.1 The basis for providing technical support is an application of the User of the Company's software and services via the communication channels specified in these Regulations.

Technical support over the phone does not guarantee the solution of the problem at the moment of request (here and now), the User is consulted over the phone or the request is registered.


 

3.2 In the appeal must be accurately and competently formulated questions that require clarification, and describe the problems that require a solution. For more operative solution of questions, the appeal should include the following information:

- a description of the problem and a step-by-step description of actions to reproduce the problem (in as much detail as possible so that the Technical Support Department can reproduce it in a test environment);

- when creating an appeal or sending an appeal by e-mail, it is necessary to attach screenshots and graphical explanations that may help in solving the problem. Screenshots should be prepared in the following formats: JPG, GIF, PNG, PDF;

- frequency of the problem occurrence;

- contact details, including phone number, e-mail address and full name of the responsible person of the User.


 

3.3 Communication between the User and an employee of the Technical Support Department must be correct, conforming to the generally accepted norms of etiquette and speech culture. Insults and obscene expressions are not allowed. In case of violation of this paragraph by an employee of the Technical Support Department, the User has the right to report the incident directly to the Head of the Technical Support Department.


 

3.4 The solution of the appeal issues may be delayed or even impossible for the following main reasons:


 

- The User cannot provide enough information to solve the problem.


 

- The issue requires detailed diagnostics, functional improvement and/or release of a software update.

software update.


 

- The user performs actions in violation of the technical requirements for using the system.


 

- The issue is beyond the scope of technical support.


 

3.5 If in the process of working on the request the Technical Support Department finds out that the problem is related to the product of a third-party manufacturer or supplier, the User is recommended to contact the technical support of the corresponding manufacturer or supplier.


 

3.6 Criteria for the end of processing of a technical support request.

Each case of processing a request sent to the Technical Support Department, depending on the level of complexity, ends with one of the following actions:

- The User is provided with information allowing to resolve the problem or describing possible ways of solving the problem;

- The User is informed that the problem is not related to the functioning of both client and server parts of the Software;

- The User is informed that the problem will be resolved in a future software update;

- The User fails to respond to repeated requests of the Technical Support Department within three working days; in this case the request is closed and no work is done on it.


 

3.7 A request is considered closed if:

After providing a comprehensive answer and/or performing the relevant work, the appeal is considered closed, and is in this state until receiving confirmation from the Customer about the solution of the problem, performance of other work. In case of the Client's reasoned disagreement with the completion of the request, the execution of work on the request continues.

A completed request is switched to the closed state after the Technical Support Department receives a confirmation from the Customer that the problem or issue has been resolved. In case of absence of response from the Customer with confirmation of problem or issue resolution within 24 hours, the request is considered closed.

Interaction with LIS

Who this document is for


The Integration Service provides an interface for generating and ordering laboratory results, as well as receiving results.

This document describes the integration for developers. All requests are SOAP requests.


Prerequisite


Developers of the integration module must complete the following steps:

  1. Obtain the test API from SIROCA Technology.
  2. Approve the authorisation type.
  3. Obtain login, password, client_id (application identifier of Siroca system), MisID (MIS identifier in Siroca system) to work with the API.
  4. Get contracts for work.
  5. Realise interaction with API.
  6. Carry out testing.

Surroundings

API address

Test

http://{host}/LisService.svc

Receiving a token

/GetToken

You need to pass the following parameters:
Parameters for obtaining a token

Parameter

Data type

Mandatory

login

String

True

password

String

True

client_id

String

True

An AccessToken model must be included in the response:

Field

Data Type

Description

access_token

String

Access token

message

String

Message

manager_id

Int

Not used

life_time_seconds

Int

Lifetime in seconds

Example of requesting and receiving a token

To get a token, you need to make a SOAP request to a method

http://tempuri.org/ILisService/GetToken

In Body, the model should have a similar structure:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/">
    <soapenv:Header/>
    <soapenv:Body>
        <tem:GetToken>
            <tem:login>LOGIN</tem:login>
            <tem:password>PASSWORD</tem:password>
            <tem:client_id>APPLICATION SENDER ID</tem:client_id>
        </tem:GetToken>
    </soapenv:Body>
</soapenv:Envelope>

Response:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:Body>
        <GetTokenResponse xmlns="http://tempuri.org/">
            <GetTokenResult xmlns:a="http://schemas.datacontract.org/2004/07/Ais.Business" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
                <a:access_token>d20iddf83jvh837py14t</a:access_token>
                <a:life_time_seconds>86400</a:life_time_seconds>
                <a:manager_id>0</a:manager_id>
                <a:message/>
            </GetTokenResult>
        </GetTokenResponse>
    </s:Body>
</s:Envelope>

Creating an order

POST /CreateOrder2

The method accepts the following parameters: :

Order Creation Parameters

Parameter

Data type

Mandatory

Order

OrderCreateRequest

True

Token

String

True

Models used when creating the order:

Property

Data type

Mandatory

Description

OrderNumber

String

True

Order number from external system

Person

Person

True

Client

Sender

String

True

Sender system code

MisID

Long

True

Identifier of the external service in LIS

FinanceSourceCode

String

False

Funding source

Researches

List<OrderRequestResearch>

True


List of studies, must be at least 1 service

Materials

List<Material>

False

Materials in the referral

IsCito

Bool

True

Indication of urgency

Comment

String

False

Doctor's comment

IdRecievePunkt

Int

False

Point of collection

SenderFuncStructureID

Long

False

Code of the sender's functional unit

Nurse

Person

True, если в заказе есть услуги COVID

Nurse who collected the BM

IsResident

Bool

False

Whether the client is a resident of the country (default is True)

HasCovidSimptoms

Bool

False

Whether COVID symptoms are present

MessageType

MessageType

True

Message type

Person

Property

Data type

Mandatory

Description

MisID

String

True

Not used

Code

String

True

Client's IIN. If it is set, it searches for an existing client, otherwise a client is created

LastName

String

True

LastName

FirstName

String

True

FirstName

SecondName

String

False

Patronymic

BirthDate

DateTime

True

Date of birth

SexID

SexType

True

Gender

IsUnknownPerson

bool

True

Not used

Telephone

String

False

Phone

Email

String

False

Mail

Address

String

False

Address

JobInfo

String

False

Information about place of work

Еnum

Title

Significance

Description

Female

2

Woman

Male

3

Man

MessageType - enum

Title

Value

Description

CreateOrderRequest

0

Request to create an order

CreateOrderResponse

1

Response to the request to create an order

RemoveOrderRequest

2

Request for order cancellation

RemoveOrderResponse

3

Response to order cancellation request

OrderStatusRequest

4

Request order status

OrderStatusResponse

5

Response to order status request

OrderResultsRequest

6

Order result request

OrderResultsResponse

7

Response to order results request

OrderNextResultRequest

8

Request to receive the next finished order

OrderNextResultResponse

9

Response for requesting the next finished order

OrderResultSuccessDeliveredRequest

10

Request for confirmation of receipt of results

OrderResultSuccessDeliveredResponse

11

Response to request for confirmation of receipt of results

ContainerStatusResponse

14

Request for container status

OrderRequestResearch

Property

Data type

Commitment

Description

ServiceCode

String

True

Research code

ParameterId

Long

False

Not used

ReferralExternalId

String

False

Not used

Notification

String

False

Not used

Material

Property

Data type

Mandatory

Description

MaterialNumber

String

True

Biomaterial barcode

MaterialTypeID

String

True

Biomaterial code

TakeDate

DateTime

True

Date of biomaterial collection.

TakePlace

String

True

Address of collection

Researches

List<OrderRequestResearch>

True

List of studies

В ответ должна прийти следующая модель OrderCreateResponse:

Field

Data type

Description

MisID

Long

MIS Identifier

OrderNumber

String

Application number

LisID

Long

LIS referral identifier

Warnings

List<String>

Warnings/errors

GeneratedContainers

List<MContainers>

Generated containers

Code

ResponseCode

Response Code. 0 - Successful, 1 - Error, 2 - Expired token, 3 - Not used, 4 - Order cancelled

Error

String

Error Text

MContainers

Field

Data type

Description

Id

Int

Container type identifier

Name

String

Container type name

Barcode

Long

Barcode

Warnings

List<String>

Warnings/errors

GeneratedContainers

List<MContainers>

Generated containers

Biomaterial

String

Biomaterial

DestinationPunktName

String

Destination name

Example of order creation request

http://tempuri.org/ILisService/CreateOrder2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:CreateOrder2>

         <tem:Order>

            <ais:MessageType>CreateOrderRequest</ais:MessageType>

            <ais:Sender>SENDER NUMBER</ais:Sender>

            <ais:Comment>COMMENT</ais:Comment>

            <ais:HasCovidSimptoms>0</ais:HasCovidSimptoms>

            <ais:IdRecievePunkt>1</ais:IdRecievePunkt>

            <ais:IsCito>0</ais:IsCito>

            <ais:IsResident>0</ais:IsResident>

            <ais:MisID>0</ais:MisID>

            <ais:OrderNumber>123456</ais:OrderNumber>

            <ais:Person>

               <ais:BirthDate>2021-09-21T03:21:53.699Z</ais:BirthDate>

               <ais:CitizenshipID>0</ais:CitizenshipID>

               <ais:Code>IIN</ais:Code>

               <ais:FirstName>Test</ais:FirstName>

               <ais:IsUnknownPerson>0</ais:IsUnknownPerson>

               <ais:LastName>Testov</ais:LastName>

               <ais:MisID>0</ais:MisID>

               <ais:PersonAge>18</ais:PersonAge>

               <ais:SexID>Male</ais:SexID>

            </ais:Person>

            <ais:Researches>

               <!--Zero or more repetitions:-->

               <ais:OrderRequestResearch>

                  <ais:ServiceCode>09-017</ais:ServiceCode>

               </ais:OrderRequestResearch>

            </ais:Researches>

         </tem:Order>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:CreateOrder2>

   </soapenv:Body>

</soapenv:Envelope>

Response:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

    <s:Body>

        <CreateOrder2Response xmlns="http://tempuri.org/">

            <CreateOrder2Result xmlns:a="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                <a:Date>2022-04-07T09:12:43.0819648+06:00</a:Date>

                <a:MessageType>CreateOrderResponse</a:MessageType>

                <a:Sender>SENDER</a:Sender>

                <a:Code>Success</a:Code>

                <a:Error i:nil="true"/>

                <a:GeneratedContainers i:nil="true" xmlns:b="http://schemas.datacontract.org/2004/07/Ais.Business"/>

                <a:LisID>10038664</a:LisID>

                <a:MisID>0</a:MisID>

                <a:OrderNumber>123456</a:OrderNumber>

                <a:Warnings xmlns:b="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/>

            </CreateOrder2Result>

        </CreateOrder2Response>

    </s:Body>

</s:Envelope>

Receiving order status

/GetOrderStatus2

The method accepts the following parameters:

GetOrderStatus2 parameters

Parameter

Data type

Mandatory

Request

OrderRequest

True

Token

String

True

OrderRequest

Property

Data type

Obligability

Description

OrderNumber

String

True

Application number from external system

MisID

Long

False

Identifier of the external system

LisID

Long

True

LIS application identifier

Sender

String

True

Sender system code

MessageType

MessageType

True

Message type

The following OrderStatusResponse model should be received in response:

OrderStatusResponse

Title

Data type

Description

MisID

Long

External System Identifier

OrderNumber

String

Application number

LisID

Long

LIS referral identifier

Status

OrderStatusForExternalSystem

Status

Code

ResponseCode

Response code

Error

String

Error

OrderStatusForExternalSystem

Name

Value

Description

OrderNotFound

0

Order not found

NoMaterial

1

No material

HasMaterial

2

Material collected

TaskMustClarify

3

Task requires clarification

TasksCreated

4

The task is formed

HasHalfResults

5

Incomplete results obtained

HasPreResults

6

Preliminary results obtained

ResultsHalfApproved

7

Results are partially approved

OrderComplete

8

Order fulfilled

OrderClosed

9

The order is closed

ResultsIssuedToPatient

10

Results given to patient

ResultsSendedToSenderSystem

11

Results sent to sender system

OrderIsCanceled

12

Rejection of all tests in the order

Order status request example

http://tempuri.org/ILisService/GetOrderStatus2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:GetOrderStatus2>

         <tem:request>

            <ais:MessageType>OrderStatusRequest</ais:MessageType>

            <ais:Sender>SENDER</ais:Sender>

            <ais:LisID>10038664</ais:LisID>

            <ais:MisID>0</ais:MisID>

            <ais:OrderNumber>123456</ais:OrderNumber>

         </tem:request>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:GetOrderStatus2>

   </soapenv:Body>

</soapenv:Envelope>

Response:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

    <s:Body>

        <GetOrderStatus2Response xmlns="http://tempuri.org/">

            <GetOrderStatus2Result xmlns:a="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                <a:Date>2022-04-07T09:20:44.1662271+06:00</a:Date>

                <a:MessageType>OrderStatusResponse</a:MessageType>

                <a:Sender i:nil="true"/>

                <a:Code>Success</a:Code>

                <a:Error i:nil="true"/>

                <a:LisID>10038664</a:LisID>

                <a:MisID>0</a:MisID>

                <a:OrderNumber>123456</a:OrderNumber>

                <a:Status>TasksCreated</a:Status>

            </GetOrderStatus2Result>

        </GetOrderStatus2Response>

    </s:Body>

</s:Envelope>

Order deletion

/RemoveOrder2

The method accepts the following parameters:

GetOrderStatus2 parameters

Parameter

Data type

Mandatory

Request

OrderRequest

True

Token

String

True

The OrderResponse model should come in response:

OrderResponse

Field

Data type

Description

MisID

Long

External system identifier

OrderNumber

String

Order number

LisID

Long

LIS referral identifier

Code

ResponseCode

Response code

Error

String

Error

Example of RemoveOrder2 request

http://tempuri.org/ILisService/RemoveOrder2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:RemoveOrder2>

         <tem:request>

            <ais:MessageType>RemoveOrderRequest</ais:MessageType>

            <ais:Sender>SENDER</ais:Sender>

            <ais:LisID>10038664</ais:LisID>

            <ais:MisID>0</ais:MisID>

            <ais:OrderNumber>123456</ais:OrderNumber>

         </tem:request>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:RemoveOrder2>

   </soapenv:Body>

</soapenv:Envelope>

Response:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

    <s:Body>

        <RemoveOrder2Response xmlns="http://tempuri.org/">

            <RemoveOrder2Result xmlns:a="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                <a:Date>2022-04-07T09:28:58.733834+06:00</a:Date>

                <a:MessageType>RemoveOrderResponse</a:MessageType>

                <a:Sender i:nil="true"/>

                <a:Code>Success</a:Code>

                <a:Error/>

                <a:LisID>10038664</a:LisID>

                <a:MisID>0</a:MisID>

                <a:OrderNumber>123456</a:OrderNumber>

            </RemoveOrder2Result>

        </RemoveOrder2Response>

    </s:Body>

</s:Envelope>

Retrieving results by order number

/GetOrderResults2

The method accepts the following parameters:

GetOrderResults2 parameters

Parameter

Data type

Mandatory

Request

OrderRequest

True

Token

String

True

The following OrderResultResponse model should be received in response:

OrderResultResponse Parameters

Field

Data type

Description

MisID

Long

External system identifier

OrderNumber

String

Order number

LisID

Long

LIS referral identifier

Code

ResponseCode

Response code

Error

String

Error

ReceiveDate

DateTime

Date of receipt/registration

PersonFIO

String

Client name

IsManual

Bool

Not used

SenderFuncStructureID

Long

Sender's functional unit code

SenderPostID

Long

Sender's doctor code

OrderStatus

OrderStatusForExternalSystem

Order status

Person

Person

Patient information

Researches

List<OrderRequestResearch>

Studies in the order

Materials

List<Material>

Materials in referral

OrderResultXML

String

Result in XML

OrderResultFileID

long

Not used

OrderResultDate

DateTime

Date of result generation

OrderResultFile

Byte[]

Pdf file with results

ApprovedPostOriginalID

String

DOCTOR'S ID in RMS

ExtInfo

List<KmisAssayData>

Study data

Example of request to get results by order number

http://tempuri.org/ILisService/GetOrderResult2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:GetOrderResults2>

         <tem:request>

            <ais:MessageType>OrderResultsRequest</ais:MessageType>

            <ais:Sender>SENDER</ais:Sender>

            <ais:LisID>8962157</ais:LisID>

            <ais:MisID>0</ais:MisID>

            <ais:OrderNumber>2003670502202151125478</ais:OrderNumber>

         </tem:request>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:GetOrderResults2>

   </soapenv:Body>

</soapenv:Envelope>

Receiving the results of the sender's next finished order

​The method returns the next ready result to the sender. After receiving the results, the external system should send the Acknowledgement of results receipt in the form of method

/SaveOrderResultSuccessDelivered2

The sequence is as follows.

/GetOrderNextResults2

Accepts the following parameters:

Parameters for GetOrderNextResults2

Parameter

Data type Mandatory

Request

RequestBase

True

Token

String

True

RequestBase

Property

Data type

Obligability

Description

Sender

String

True

Sender system code

MessageType

MessageType

True

Message type

The OrderResultResponse model should be received in response.

Example request to receive the sender's next completed order

http://tempuri.org/ILisService/GetOrderNextResult2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:GetOrderNextResult2>

         <tem:request>

            <ais:MessageType>OrderNextResultRequest</ais:MessageType>

            <ais:Sender>Sender</ais:Sender>

         </tem:request>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:GetOrderNextResult2>

   </soapenv:Body>

</soapenv:Envelope>

Confirmation of receipt of results

/SaveOrderResultSuccessDelivered2

Accepts the following parameters:

Parameters for GetOrderNextResults2

Parameter

Data type

Mandatory

Request

OrderRequest

True

Token

String

True

The following ResponseBase model should be returned in the response:

ResponseBase

Property

Data Type

Description

Code

ResponseCode

Response code

Error

String

Error

Example of a query to confirm receipt of results

http://tempuri.org/ILisService/SaveOrderResultSuccessDelivered2

Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:ais="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService">

   <soapenv:Header/>

   <soapenv:Body>

      <tem:SaveOrderResultSuccessDelivered2>

         <tem:request>

            <ais:MessageType>OrderResultSuccessDeliveredRequest</ais:MessageType>

            <ais:Sender>SENDER</ais:Sender>

            <ais:LisID>10038664</ais:LisID>

            <ais:MisID>0</ais:MisID>

            <ais:OrderNumber>123456</ais:OrderNumber>

         </tem:request>

         <tem:token>d20iddf83jvh837py14t</tem:token>

      </tem:SaveOrderResultSuccessDelivered2>

   </soapenv:Body>

</soapenv:Envelope>

Response:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

    <s:Body>

        <SaveOrderResultSuccessDelivered2Response xmlns="http://tempuri.org/">

            <SaveOrderResultSuccessDelivered2Result xmlns:a="http://schemas.datacontract.org/2004/07/Ais.Business.Models.LisService" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                <a:Date>2022-04-07T10:01:18.763194+06:00</a:Date>

                <a:MessageType>OrderResultSuccessDeliveredResponse</a:MessageType>

                <a:Sender>SENDER</a:Sender>

                <a:Code>Success</a:Code>

                <a:Error i:nil="true"/>

            </SaveOrderResultSuccessDelivered2Result>

        </SaveOrderResultSuccessDelivered2Response>

    </s:Body>

</s:Envelope>