Online Appointment Booking: Bitrix & MIS Integration – From $5,000

Online Appointment Booking: Bitrix & MIS Synchronization

Your private clinic's website accepts online appointments with doctors. The MIS — Medical Information System — is the clinic's operating system: doctor schedules, medical history, electronic health records, service accounting, cash register. MIS — Medical Information System. The challenge: appointments from the site must automatically appear in the MIS schedule, and vacant slots must be displayed on the site in real time. Each hour of downtime or manual data transfer costs up to 30% of lost patients — we've seen this repeatedly.

The MIS market is diverse: Infoclinic, 1C:Medicine, qMS, Medesk, Renaissance-M, ArchiMed+, Medods — each has its own API (or lack thereof). The integration architecture of 1C-Bitrix with the MIS depends on the specific system. We guarantee selecting the optimal scenario and turnkey implementation with full testing.

Typical Integration Scenarios

Scenario A: MIS provides REST/SOAP API. The site directly calls the MIS API to fetch schedules and book a patient. This is the cleanest option, but not all MIS support it.

Scenario B: Intermediate broker. The MIS publishes the schedule to an intermediate database (PostgreSQL or MySQL), the site reads from there. Booking on the site creates a request in an intermediate table, and the MIS picks it up via cron.

Scenario C: Integration bus. For large clinics with multiple MIS and numerous systems — a dedicated integration service (e.g., based on RabbitMQ or Apache Kafka) that synchronizes data between systems.

Which Integration Scenario to Choose?

The choice of scenario is determined by budget, number of systems, and latency requirements. Below is a comparison of key parameters.

REST API is 2–3 times faster to implement than intermediate database and provides real-time data, but requires a stable endpoint. The intermediate database suits MIS without API or with strict limits. The integration bus is for complex landscapes.

Why REST API Integration Is Optimal?

REST API is the fastest and most transparent integration method. In 90% of cases, we use it: the client gets real-time data, and the codebase remains clean. Below is an example implementation for Medesk — one of the popular MIS.

class MedeskApiClient
{
    private string $apiKey;
    private string $baseUrl = 'https://api.medesk.net/api/v2';

    public function getDoctorSchedule(int $doctorId, string $dateFrom, string $dateTo): array
    {
        return $this->request('GET', '/schedules', [
            'doctor_id' => $doctorId,
            'from'      => $dateFrom,
            'to'        => $dateTo,
            'include'   => 'free_slots',
        ]);
    }

    public function createAppointment(array $patientData, int $slotId): array
    {
        return $this->request('POST', '/appointments', [
            'slot_id'       => $slotId,
            'patient'       => [
                'first_name'  => $patientData['name'],
                'last_name'   => $patientData['surname'],
                'phone'       => $patientData['phone'],
                'email'       => $patientData['email'],
                'birth_date'  => $patientData['birth_date'],
            ],
            'comment'       => $patientData['comment'] ?? '',
            'source'        => 'website',
        ]);
    }

    public function cancelAppointment(int $appointmentId, string $reason = ''): array
    {
        return $this->request('DELETE', "/appointments/{$appointmentId}", [
            'reason' => $reason,
        ]);
    }

    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     => [
                'Content-Type: application/json',
                "Authorization: Bearer {$this->apiKey}",
            ],
            CURLOPT_POSTFIELDS => in_array($method, ['POST', 'PUT', 'PATCH'])
                ? json_encode($data) : null,
        ]);

        $response = json_decode(curl_exec($ch), true);
        $httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
        curl_close($ch);

        if ($httpCode >= 400) {
            \Bitrix\Main\Diag\Debug::writeToFile(
                "MIS API Error {$httpCode}: " . json_encode($response),
                'MIS',
                '/local/logs/mis-integration.log'
            );
            throw new \RuntimeException("MIS API error: {$httpCode}");
        }

        return $response ?? [];
    }
}

Why Schedule Caching Is Critical?

Directly calling the MIS API on every doctor page visit is a bad idea: the MIS can be slow or have request limits (e.g., 100 requests per minute). Caching reduces the load on the MIS by 10–20 times and speeds up page load to 200 ms. Implementation details:

class DoctorScheduleService
{
    private MedeskApiClient $mis;

    public function getAvailableSlots(int $doctorId, string $date): array
    {
        $cacheKey  = "doctor_slots_{$doctorId}_{$date}";
        $cacheTtl  = 180; // 3 миnyты — баланс актуальности и нагрузки

        $cache = \Bitrix\Main\Data\Cache::createInstance();
        if ($cache->initCache($cacheTtl, $cacheKey, '/mis/slots/')) {
            return $cache->getVars()['slots'];
        }

        $schedule = $this->mis->getDoctorSchedule($doctorId, $date, $date);
        $slots    = $this->formatSlots($schedule);

        $cache->startDataCache();
        $cache->endDataCache(['slots' => $slots]);

        return $slots;
    }

    public function bookSlot(int $slotId, array $patientData): array
    {
        $result = $this->mis->createAppointment($patientData, $slotId);

        // Инвалидируем кеш расписания для этого врача
        $date      = date('Y-m-d');
        $doctorId  = $this->getSlotDoctorId($slotId);
        \Bitrix\Main\Data\Cache::clearByTag("doctor_slots_{$doctorId}_{$date}");

        // Сохраняем запись в Битрикс
        $this->saveAppointmentInBitrix($result, $patientData);

        return $result;
    }
}

Storing Appointments in Bitrix

We duplicate appointments in Bitrix — for history, notifications, and operation without the MIS when it's unavailable:

class AppointmentTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'local_mis_appointments'; }

    public static function getMap(): array
    {
        return [
            new \Bitrix\Main\ORM\Fields\IntegerField('ID',          ['primary' => true, 'autocomplete' => true]),
            new \Bitrix\Main\ORM\Fields\IntegerField('USER_ID'),
            new \Bitrix\Main\ORM\Fields\IntegerField('MIS_APPOINTMENT_ID'),
            new \Bitrix\Main\ORM\Fields\IntegerField('DOCTOR_ID'),
            new \Bitrix\Main\ORM\Fields\DatetimeField('APPOINTMENT_TIME'),
            new \Bitrix\Main\ORM\Fields\StringField('STATUS'),      // booked|confirmed|cancelled|completed
            new \Bitrix\Main\ORM\Fields\StringField('SERVICE_NAME'),
            new \Bitrix\Main\ORM\Fields\StringField('PATIENT_PHONE'),
            new \Bitrix\Main\ORM\Fields\DatetimeField('CREATED_AT'),
        ];
    }
}

Patient Notifications

After booking — SMS and email confirmation via Bitrix. Reminders 24 hours and 2 hours before the appointment. Reminders are implemented via a Bitrix agent that checks appointments every hour:

function SendMisAppointmentReminders(): string
{
    $now      = new \Bitrix\Main\Type\DateTime();
    $in24h    = (new \DateTime())->modify('+24 hours');
    $in2h     = (new \DateTime())->modify('+2 hours');

    $appointments = AppointmentTable::getList([
        'filter' => [
            'STATUS'              => 'booked',
            '>=APPOINTMENT_TIME'  => \Bitrix\Main\Type\DateTime::createFromTimestamp($in2h->getTimestamp()),
            '<=APPOINTMENT_TIME'  => \Bitrix\Main\Type\DateTime::createFromTimestamp($in24h->getTimestamp()),
            'REMINDER_24H_SENT'  => 'N',
        ],
    ]);

    while ($row = $appointments->fetch()) {
        SmsService::send($row['PATIENT_PHONE'],
            "Reminder of your appointment on " . date('d.m.Y H:i', strtotime($row['APPOINTMENT_TIME']))
        );
        AppointmentTable::update($row['ID'], ['REMINDER_24H_SENT' => 'Y']);
    }

    return __FUNCTION__ . '();';
}

Handling MIS Errors

The MIS may be unavailable (maintenance, server issues). Our strategy: if the MIS is unreachable, we save the request in the local_mis_pending_appointments table with status pending, display to the patient "Appointment accepted, we will contact you for confirmation." An agent tries to send pending records to the MIS every 5 minutes. After repeated failures, the record is marked manual — an operator contacts the patient. We implement this mechanism in every project and guarantee zero loss of requests.

How to Guarantee Zero Lost Requests?

If the MIS is unavailable, the request is saved in local_mis_pending_appointments table with status pending. An agent retries every 5 minutes. After 10 failed attempts, status changes to manual, and an operator contacts the patient. This scheme works in all projects and eliminates request loss.

What's Included in the Work

• Analysis of the specific MIS API documentation and selection of scenario
• Development of a PHP API client with error handling and retries
• Schedule caching with invalidation on booking
• Custom online booking component on the site (tailored to clinic design)
• Appointment table in Bitrix with status synchronization
• SMS/email notification setup (confirmation + reminders)
• Organization of a pending queue for requests when MIS is unavailable
• Load and fault tolerance testing
• Operational documentation and administrator training

How We Integrate MIS in 5 Steps

1. MIS API analysis and scenario agreement (1–2 weeks).
2. Client API development and backup storage (3–6 weeks).
3. Booking component integration on the site (1–2 weeks).
4. Notification and error queue setup (1 week).
5. Load testing and staff training (1–2 weeks).

Timelines: from 5 to 14 weeks depending on complexity. Integration costs start at $5,000; typical projects run $5,000–$15,000. Clinics save up to 30% of administrative time and eliminate manual data entry errors. Order integration with zero loss guarantee — our certified specialists with 10 years of experience will select the right solution.

Get a free consultation and project estimate — we will choose the optimal integration scenario and suggest timelines.

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.