Integrate 1C-Bitrix with EMIAS: API, mTLS, and Agents for Online Doctor Appointments

1C-Bitrix and EMIAS: From Bureaucracy to a Working API

EMIAS is Moscow's state healthcare platform for clinics and hospitals. Integrating it allows your medical institution's website to show real doctor schedules and accept online appointments directly into the system, bypassing the reception desk. Our engineers have completed 15+ such projects, including complex cases with non-standard requirements. For instance, a large polyclinic couldn't transmit doctor data due to an outdated SOAP client—we rewrote the integration from scratch, speeding up appointments by 4x and saving up to 40% of reception time. Another project: a network of clinics with 30 branches integrated EMIAS and Bitrix24—within the first month, online bookings accounted for 60% of all visits, and manual work was reduced by 70%.

Avoid common mistakes—order a professional integration. We've already walked this path and are ready to help you.

Problems We Solve

• Slow API Access. Getting EMIAS API access is a bureaucratic process lasting 1–3 months. We handle the application, assist with documentation, and configure mTLS.
• SOAP and mTLS Complexity. EMIAS uses WCF services with client certificates. Implementing a correct SOAP client requires deep expertise—we've already done it.
• ESIA Authorization. Appointments require SNILS and OMS policy. Integration with Gosuslugi is mandatory and non-trivial: request signing, OAuth 2.0, system certification.
• Performance. Direct EMIAS queries for every schedule display are unacceptable. The solution is local synchronization via agents, reducing API load by 20–50 times.

Without these solutions, the site will either work incorrectly or fail certification.

How to Get EMIAS API Access?

The process consists of four steps:

1. Submit a request to the Moscow Department of Information Technologies (DIT).
2. Sign an information interaction agreement.
3. Obtain a client certificate for mTLS.
4. Receive a test environment and documentation.

EMIAS API uses WCF or REST. For schedule management, the service is ScheduleService.

SOAP Client for EMIAS

If EMIAS provides a WSDL, we build a SOAP client with mTLS support:

class EmiasClient
{
    private \SoapClient $client;
    private string $certPath;
    private string $certPassword;

    public function __construct(string $wsdlUrl, string $certPath, string $certPassword)
    {
        $this->certPath     = $certPath;
        $this->certPassword = $certPassword;

        // EMIAS requires mTLS—client certificate
        $context = stream_context_create([
            'ssl' => [
                'local_cert'        => $certPath,
                'passphrase'        => $certPassword,
                'verify_peer'       => true,
                'verify_peer_name'  => true,
                'cafile'            => '/etc/ssl/certs/emias-ca.crt',
            ],
        ]);

        $this->client = new \SoapClient($wsdlUrl, [
            'soap_version'  => SOAP_1_2,
            'encoding'      => 'UTF-8',
            'trace'         => false,
            'exceptions'    => true,
            'stream_context' => $context,
        ]);
    }

    public function getDoctorSchedule(string $lpuCode, int $doctorId, \DateTime $date): array
    {
        try {
            $result = $this->client->GetSchedule([
                'lpuCode'    => $lpuCode,
                'doctorId'   => $doctorId,
                'dateFrom'   => $date->format('Y-m-d'),
                'dateTo'     => $date->format('Y-m-d'),
            ]);

            return $this->parseScheduleResult($result);
        } catch (\SoapFault $e) {
            \Bitrix\Main\Diag\Debug::writeToFile(
                "EMIAS SOAP fault: {$e->faultcode} — {$e->faultstring}",
                '',
                '/local/logs/emias.log'
            );
            throw new \RuntimeException("EMIAS error: {$e->faultstring}");
        }
    }

    public function createAppointment(array $params): string
    {
        $result = $this->client->CreateAppointment([
            'lpuCode'     => $params['lpu_code'],
            'doctorId'    => $params['doctor_id'],
            'slotId'      => $params['slot_id'],
            'patient'     => [
                'lastName'    => $params['last_name'],
                'firstName'   => $params['first_name'],
                'middleName'  => $params['middle_name'] ?? '',
                'birthDate'   => $params['birth_date'], // DD.MM.YYYY
                'snils'       => $params['snils'],       // Mandatory for EMIAS
                'oms'         => $params['oms_policy'],  // OMS policy
            ],
        ]);

        return (string)$result->AppointmentId;
    }
}

SNILS and OMS policy are mandatory fields. This fundamentally distinguishes EMIAS from commercial MIS.

Patient Verification via Gosuslugi

Since EMIAS requires SNILS, integrating with ESIA for patient authorization is a logical next step. The patient logs in via Gosuslugi → the system gets their SNILS and data → passes them to EMIAS.

class GosuslugiEsiaService
{
    // ESIA OAuth 2.0
    private string $clientId;    // System mnemonic in ESIA
    private string $certPath;    // System certificate for request signing

    public function getAuthUrl(string $state): string
    {
        $timestamp = date('Y.m.d H:i:s O');
        $scope     = 'openid fullname snils medical';

        // ESIA requires a signed request
        $clientSecret = $this->signRequest(implode('', [
            $scope, $timestamp, $this->clientId, $state
        ]));

        return 'https://esia.gosuslugi.ru/aas/oauth2/ac?' . http_build_query([
            'client_id'     => $this->clientId,
            'client_secret' => $clientSecret,
            'redirect_uri'  => SITE_SERVER_NAME . '/esia/callback/',
            'scope'         => $scope,
            'response_type' => 'code',
            'state'         => $state,
            'timestamp'     => $timestamp,
            'access_type'   => 'online',
        ]);
    }

    private function signRequest(string $data): string
    {
        // Sign via openssl with the system certificate
        $pkcs7 = '';
        openssl_pkcs7_sign(
            tempnam(sys_get_temp_dir(), 'esia_'),
            tempnam(sys_get_temp_dir(), 'esia_out_'),
            file_get_contents($this->certPath),
            ['', ''],
            [],
            PKCS7_DETACHED | PKCS7_NOATTR
        );
        return base64_encode($pkcs7);
    }
}

Integrating with ESIA is a separate project with system certification requirements.

Why Schedule Synchronization is Necessary

Direct EMIAS queries for every schedule display are slow and rate-limited. Approach comparison:

Local sync is 20–50 times faster and reduces load on the state API. An agent every 5–15 minutes loads slots into a local table:

class EmiasSyncAgent
{
    public function syncSchedule(): string
    {
        $doctors = $this->getActiveDoctors();
        $dateRange = [
            'from' => date('Y-m-d'),
            'to'   => date('Y-m-d', strtotime('+30 days')),
        ];

        foreach ($doctors as $doctor) {
            try {
                $schedule = $this->emiasClient->getDoctorSchedule(
                    $doctor['LPU_CODE'],
                    $doctor['EMIAS_DOCTOR_ID'],
                    new \DateTime($dateRange['from'])
                );

                $this->upsertSlots($doctor['ID'], $schedule);
            } catch (\RuntimeException $e) {
                \CEventLog::Add(['SEVERITY' => 'WARNING', 'DESCRIPTION' => $e->getMessage()]);
            }
        }

        return __FUNCTION__ . '();';
    }
}

Slots are stored in local_emias_slots: DOCTOR_ID, SLOT_DATE, SLOT_TIME, EMIAS_SLOT_ID, IS_FREE. The site reads from the local table, not from EMIAS directly.

Simultaneous Booking Conflicts

A user picks a 15:00 slot → fills the form → someone else booked the same slot via the EMIAS portal. Solution:

1. When the form opens, soft-reserve the slot in the local table (mark it).
2. Reserve lasts 5 minutes.
3. On final submission, write to the EMIAS API.
4. If EMIAS returns a "slot taken" error, show the nearest available slots.

This approach reduces conflicts to a minimum (in practice, less than 5% rejections) and improves patient convenience.

Typical Integration Errors

Avoid these pitfalls—order a professional integration.

What's Included

Estimated timelines: administrative procedures—1–3 months, technical development—6–12 weeks after access is granted. Get a consultation—we'll evaluate your project individually.

EMIAS — Moscow's state healthcare system.

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.