Healthcare Websites on 1C-Bitrix

Medical Websites and Portals on 1C-Bitrix

The trickiest integration in medical projects is schedule synchronization with the MIS. MEDIALOG delivers slots via SOAP, INFOCLINIKA uses REST with token-based auth, 1C:Medicine works through a COM object or web service. And each interprets "available slot" differently: with or without buffer time between appointments, with or without a lunch block. If you don't account for these nuances — you get double bookings and furious patients at the reception desk. We build medical solutions on 1C-Bitrix with detailed engineering of precisely this layer — integrations with MIS, LIS, and insurance systems.

Types of Medical Projects

Clinic and medical center websites. Not a brochure, but a working appointment tool:

• Service catalog via an infoblock linked to the price list from 1C:Medicine
• Doctor profiles: specializations, experience, certifications — all from the MIS directory, not manually duplicated
• Online booking with real-time schedules from the MIS via bidirectional synchronization
• Patient portal: visit history, test results, prescriptions. Data is pulled by patient_id from the MIS
• Cost calculator for examination programs — a component querying b_iblock_element with prices
• Corporate health and occupational screening section for business clients

Laboratory portals. The key factor is speed of result delivery:

• Test catalog with preparation guidelines and turnaround times
• Online ordering: choose a lab location or schedule a home visit
• Patient portal with PDF results and interactive trend charts (chart.js with data from the LIS)
• Interpretation: reference ranges, deviations, recommendations — generated automatically from reference values
• LIS integration for automatic result publishing. The patient gets a push notification, not a phone call
• Check-ups — comprehensive programs combining multiple tests

Online pharmacies. E-commerce with pharmaceutical specifics — you can't just "bolt on a shopping cart":

• Catalog linked to the State Drug Registry — a mandatory requirement
• Prescription vs. OTC: different checkout logic. Prescription drugs — reservation only with in-store pickup, remote sale prohibited by federal law
• Integration with drug serialization and track-and-trace systems
• Stock and price verification across pharmacy locations via warehouse system API
• Generics and equivalents: comparison by INN (International Nonproprietary Name)

Telemedicine. Not a "promising direction" — a mandatory channel:

• Video conferencing via WebRTC with encryption
• Electronic prescriptions, referrals
• Chat: text, photos, documents — stored in encrypted form
• Integration with EMR (Electronic Medical Records)
• Online consultation scheduling and payment via sale.paysystem

Online Appointment Booking — the Main Stumbling Block

This is where most medical projects break down. A patient who can't get through leaves for a competitor who answered in 30 seconds. The booking module must work flawlessly.

• Schedule — available slots accounting for appointment duration by service type. Not a vague "there's an opening," but a specific interval from the MIS. Synchronization every 2-3 minutes — a compromise between load and freshness.
• Multi-channel booking — website, mobile app, Telegram bot, widget. All channels hit a single API endpoint that locks the slot via SELECT ... FOR UPDATE until confirmation.
• Reminders — SMS via sms.ru or smsc.ru API at 24 hours and 2 hours before. Reduces no-shows by 30-40%.
• Cancellation and rescheduling — from the patient portal, no phone call needed. The slot is released in the MIS automatically.
• Anti-collision — double bookings are eliminated at the database transaction level. If the MIS and the website simultaneously try to claim a slot — whoever commits first wins.

Security and Personal Data

Medical data is a special category of personal data under privacy legislation. Leaking a diagnosis isn't just a fine — it's criminal liability.

• Data protection compliance — full documentation set: consent forms, privacy policy, regulatory notification. Not a checkbox formality, but working documents.
• Medical confidentiality — access control via Bitrix roles (CUser::GetUserGroup()). The medical record is visible to the attending physician and department head; the receptionist sees only the schedule.
• Encryption — TLS 1.3, encryption of sensitive fields in the DB via pgcrypto (PostgreSQL) or AES at the application layer.
• Access audit — log in b_event_log: who accessed which records and when. A handler on every SELECT to tables containing medical data.
• Proactive protection — Bitrix WAF, file integrity monitoring via filechecker, anomaly detection.
• Hosting — Tier III data center, certified for medical data processing.

Medical System Integrations

This is 70% of the project's complexity. The rest is essentially standard Bitrix.

MIS:

• MEDIALOG — SOAP services, schedule synchronization, appointment records, patient data. Closed documentation — we work from the WSDL.
• INFOCLINIKA — REST API with OAuth. A more modern interface, but with its own timezone quirks.
• 1C:Medicine — exchange via web service or CommerceML. Price lists, financial data, reporting.
• N3.Health (national health information system) — data submission to the unified state system. Mandatory for licensed healthcare facilities.

LIS:

• Automatic result delivery to the patient portal — via webhook or polling. The patient receives a push notification.
• Trend charts for regular tests (glucose, cholesterol) — visualization of dynamics.

Insurance:

• Real-time policy verification and limit checks via the insurer's API
• Automated service pre-authorization
• Claims register export — format depends on the insurer, each has its own XSD

SEO for Medical Websites

YMYL territory. Google and other search engines apply heightened standards, and "keyword-stuffed text" doesn't work here.

• E-E-A-T — content is written or verified by physicians. Qualifications are listed, sources are cited (PubMed, clinical guidelines)
• Schema.org — MedicalOrganization, Physician, MedicalProcedure, MedicalCondition markup. Implemented via a component that generates JSON-LD from infoblock data.
• Local SEO — Google Business Profile, map listings, review aggregation
• Advertising regulations — mandatory contraindication warnings on every service page. Automated insertion via a component template.

Mobile Adaptation

Over 70% of patients search for a doctor on their phone. An inconvenient mobile booking experience means a lost patient.

• Mobile-first design, priority on booking forms
• "Call" and "Book" buttons — sticky on screen
• Booking in 2-3 taps
• PWA with push notifications via Service Worker + FCM
• Optimization: Lighthouse Performance > 90 on mobile networks

Timeline

The bulk of time goes to MIS integration and testing edge cases in the booking flow. The Bitrix website itself is a standard task, but the layer of medical logic on top of it requires deep domain expertise.