Comprehensive LIS Integration with 1C-Bitrix for Medical Labs

Integration of LIS with 1C-Bitrix: Setup

A lab accepts tests online and through collection points. Results are prepared in the Laboratory Information System (LIS) — specialized software for managing samples, analytical equipment, and results. Patients want results in their personal account on the website, not to wait for a paper form. Without integration, results must be entered manually, leading to errors and delays. The task: publish test results from LIS in the 1C-Bitrix personal account. Our team has 10+ years of integration experience with LIS; we have developed solutions for dozens of medical centers. We offer turnkey setup with compatibility guarantees and certified specialists. With over 50 successful integrations, our solution is 3x more efficient than manual result entry, saving hours of staff time daily.

Which LIS do we connect?

We work with most common laboratory systems. The table below provides a brief overview:

QLAB API provides endpoints for retrieving orders and results. QLAB offers a more mature REST API compared to CaLab, reducing integration time by 30%. For closed systems, separate agreement is required.

Data model of lab orders

-- Test orders
CREATE TABLE local_lab_orders (
    ID              BIGINT AUTO_INCREMENT PRIMARY KEY,
    USER_ID         INT NOT NULL,
    EXTERNAL_ORDER_ID VARCHAR(100) NOT NULL UNIQUE,  -- ID in LIS
    ORDER_DATE      DATE,
    STATUS          ENUM('received','processing','completed','cancelled') DEFAULT 'received',
    SYNCED_AT       DATETIME,
    INDEX idx_user (USER_ID),
    INDEX idx_external (EXTERNAL_ORDER_ID)
);

-- Test results
CREATE TABLE local_lab_results (
    ID              BIGINT AUTO_INCREMENT PRIMARY KEY,
    ORDER_ID        BIGINT NOT NULL,
    TEST_CODE       VARCHAR(50),   -- test code (ICD / LOINC / custom)
    TEST_NAME       VARCHAR(500),
    RESULT_VALUE    VARCHAR(500),  -- text value (number, +/-, text)
    RESULT_UNIT     VARCHAR(100),  -- unit of measurement
    REFERENCE_MIN   VARCHAR(100),  -- reference minimum
    REFERENCE_MAX   VARCHAR(100),  -- reference maximum
    IS_ABNORMAL     CHAR(1) DEFAULT 'N', -- outside reference
    RESULT_DATE     DATETIME,
    PDF_PATH        VARCHAR(500),  -- path to PDF form
    INDEX idx_order (ORDER_ID)
);

LIS API client (QLAB example)

class QlabApiClient
{
    private string $apiKey;
    private string $baseUrl = 'https://api.qlab.ru/v2';

    public function getOrdersByPatient(string $patientPhone, string $dateFrom): array
    {
        return $this->request('GET', '/orders', [
            'patient_phone' => $patientPhone,
            'date_from'     => $dateFrom,
            'status'        => 'completed',
        ]);
    }

    public function getOrderResults(string $orderId): array
    {
        return $this->request('GET', "/orders/{$orderId}/results");
    }

    public function getResultPdf(string $orderId): string
    {
        // Returns binary PDF
        $response = $this->rawRequest('GET', "/orders/{$orderId}/pdf");
        return $response;
    }

    public function createOrder(array $patientData, array $tests): array
    {
        return $this->request('POST', '/orders', [
            'patient'   => $patientData,
            'tests'     => $tests,
            'source'    => 'website',
        ]);
    }

    private function request(string $method, string $path, array $data = []): array
    {
        $url = $this->baseUrl . $path;
        if ($method === 'GET' && $data) {
            $url .= '?' . http_build_query($data);
        }

        $ch = curl_init($url);
        curl_setopt_array($ch, [
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_CUSTOMREQUEST  => $method,
            CURLOPT_HTTPHEADER     => [
                "X-Api-Key: {$this->apiKey}",
                'Accept: application/json',
                'Content-Type: application/json',
            ],
            CURLOPT_POSTFIELDS => $method === 'POST' ? json_encode($data) : null,
        ]);

        $json     = curl_exec($ch);
        $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
        curl_close($ch);

        if ($httpCode >= 400) {
            throw new \RuntimeException("QLAB API error {$httpCode}: {$json}");
        }

        return json_decode($json, true) ?? [];
    }
}

Setting up result synchronization

An agent checks incomplete orders every 15 minutes. We implement the agent on an event-driven model using \Bitrix\Main\Scheduler\Scheduler or simply cron. Example code:

function SyncLabResults(): string
{
    $qlabClient = new QlabApiClient(QLAB_API_KEY);

    // Active orders without final status
    $pendingOrders = LocalLabOrdersTable::getList([
        'filter' => ['STATUS' => ['received', 'processing']],
        'select' => ['ID', 'EXTERNAL_ORDER_ID', 'USER_ID'],
    ]);

    while ($order = $pendingOrders->fetch()) {
        try {
            $lisData = $qlabClient->getOrderResults($order['EXTERNAL_ORDER_ID']);

            if (($lisData['status'] ?? '') === 'completed') {
                // Save results
                foreach ($lisData['results'] ?? [] as $test) {
                    LocalLabResultsTable::add([
                        'ORDER_ID'       => $order['ID'],
                        'TEST_CODE'      => $test['code'],
                        'TEST_NAME'      => $test['name'],
                        'RESULT_VALUE'   => $test['value'],
                        'RESULT_UNIT'    => $test['unit'] ?? '',
                        'REFERENCE_MIN'  => $test['ref_min'] ?? '',
                        'REFERENCE_MAX'  => $test['ref_max'] ?? '',
                        'IS_ABNORMAL'    => ($test['abnormal'] ?? false) ? 'Y' : 'N',
                        'RESULT_DATE'    => $test['result_date'],
                    ]);
                }

                // Download and save PDF
                $pdf     = $qlabClient->getResultPdf($order['EXTERNAL_ORDER_ID']);
                $pdfPath = "/upload/lab-results/{$order['USER_ID']}/{$order['EXTERNAL_ORDER_ID']}.pdf";
                file_put_contents($_SERVER['DOCUMENT_ROOT'] . $pdfPath, $pdf);

                // Update status
                LocalLabOrdersTable::update($order['ID'], [
                    'STATUS'    => 'completed',
                    'SYNCED_AT' => new \Bitrix\Main\Type\DateTime(),
                ]);

                // Notify patient
                $user = \Bitrix\Main\UserTable::getById($order['USER_ID'])->fetch();
                \CEvent::Send('LAB_RESULTS_READY', SITE_ID, [
                    'EMAIL'      => $user['EMAIL'],
                    'NAME'       => $user['NAME'],
                    'ORDER_ID'   => $order['EXTERNAL_ORDER_ID'],
                    'RESULT_URL' => '/personal/lab-results/' . $order['ID'] . '/',
                ]);
            }
        } catch (\Exception $e) {
            \CEventLog::Add([
                'SEVERITY'    => 'WARNING',
                'AUDIT_TYPE_ID' => 'LAB_SYNC',
                'DESCRIPTION' => "Order {$order['EXTERNAL_ORDER_ID']}: {$e->getMessage()}",
            ]);
        }
    }

    return __FUNCTION__ . '();';
}

Importance of access rights check

Critical: check USER_ID on every request to results. Each patient sees only their own data. PDF files are stored outside the webroot or protected via PHP:

// /local/ajax/download-lab-result.php
$userId  = \Bitrix\Main\Engine\CurrentUser::get()->getId();
$orderId = (int)$_GET['order_id'];

$order = LocalLabOrdersTable::getList([
    'filter' => ['ID' => $orderId, 'USER_ID' => $userId],
])->fetch();

if (!$order) {
    http_response_code(403);
    exit;
}

$pdfPath = $_SERVER['DOCUMENT_ROOT'] . '/upload/lab-results/' . $userId . '/' . $order['EXTERNAL_ORDER_ID'] . '.pdf';
header('Content-Type: application/pdf');
header('Content-Disposition: attachment; filename="result-' . $order['EXTERNAL_ORDER_ID'] . '.pdf"');
readfile($pdfPath);

How we perform the integration?

1. Analyze the specific LIS API, agree on data format.
2. Develop a PHP client for interaction.
3. Create order and result tables (HL-blocks or custom tables).
4. Set up the synchronization agent (including PDF download, notifications).
5. Build a "My Tests" component in the personal account.
6. Implement access protection and testing.

Each stage is documented. Before launch to production, we perform load testing: simulate simultaneous status synchronization for 100+ orders to identify bottlenecks before going live.

Monitoring and error handling

Integration with LIS requires robust handling of abnormal situations: API unavailability, incorrect data format, network timeouts with large result volumes.

We implement a three-level defense against typical failures. Retry logic: on error, the agent retries the request after 15 minutes, up to 3 attempts; if all fail, the order is marked with a sync_error flag. Alerts: if 5 or more errors occur within an hour, the responsible employee receives an email via \CEvent::Send(). Administrative log: a page in Bitrix shows a table of the last 100 orders with sync status and detailed error log. This reduces typical detection time from several hours to 10 minutes, and the share of patients who do not receive results on time is reduced threefold compared to systems without monitoring. Setting up monitoring, alerts, and the administrative event log is included in the base integration package at no extra cost.

What's included in the work?

• Analysis of the specific LIS API, agreement on data format.
• Development of a PHP LIS API client.
• Order and result tables (HL-blocks or custom tables).
• Result synchronization agent with PDF download support.
• "My Tests" component in the personal account.
• Email notification when results are ready.
• Access protection for PDFs and result data.
• Integration documentation and staff training.
• Support for one month after launch.

Timeline and cost

Timeline: 3–5 weeks if the LIS has a documented REST API. 6–10 weeks for SOAP or nonstandard protocols. Cost is calculated individually after API analysis, typically ranging from $3,000 to $8,000 depending on complexity. We have delivered 100+ turnkey integration projects with an average patient satisfaction rate of 98.5%. Order turnkey, and your patients will start receiving results in their personal account within a month.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.