A patient took tests on Monday. On Tuesday, they call the clinic to get results — "call back tomorrow." On Wednesday, they call again — "the results are with the doctor." On Thursday, the doctor calls back, but the patient is in a meeting. On Friday, the patient comes in person. Five days for something that could have been resolved with a push notification "Your results are ready" and a view button in the personal account. We design portals that solve such problems. Our track record: 10+ years and over 50 medical projects.
A clinic portal on 1C-Bitrix is not a business card with an address and a list of doctors — it's a working tool for interaction between clinic and patient. It reduces the load on the call center and reception, automates booking and notifications. Call center resource savings after implementation reach up to 50%, which, in terms of operator salaries, averages 1–2 million rubles saved annually per 10,000 active patients.
How the patient personal account works
The personal account is the central element of the portal. Without it, the portal reduces to an informational site. With it, it becomes a service channel.
- Appointment booking — selection of doctor, specialty, date and time from the current schedule
- My appointments — upcoming and past visits, option to cancel/reschedule
- Test results — PDF or structured data from the laboratory system
- Medical documents — extracts, conclusions, referrals
- Prescriptions — electronic prescriptions with renewal request
- Finances — payment history, invoices, deposit balance
- Family access — managing appointments for children and elderly relatives
Authorization — via phone number with SMS code (patients don't remember passwords for medical portals). Additionally — login via State Services (ESIA) for public clinics.
Why MIS integration is critical?
MIS (Medical Information System) is the core of clinic automation: doctor schedules, electronic medical records, lab orders, billing. A portal without MIS integration — two parallel worlds: the administrator manually enters the appointment into MIS after the patient books on the site.
Typical MIS and integration methods:
| MIS | Protocol | Features |
|---|---|---|
| Infoklinika | SOAP/REST API | Widely used, documented API |
| MEDIALOG | REST API | Modular architecture, flexible API |
| 1C:Medicine | COM/REST | Native integration with 1C-Bitrix via exchange module |
| qMS | REST API | Modern API, webhook notifications |
| Custom MIS | Depends on implementation | Often direct DB access or CSV exchange |
What is synchronized:
-
Schedule — portal requests free slots via MIS API every 5–15 minutes or in real time on user request
-
Appointment — when appointment created on portal, API call to MIS to book the slot. On cancellation — release.
-
Test results — MIS sends webhook or portal polls. Result saved in infoblock linked to patient.
-
Invoices and payments — synchronization via 1C-Bitrix
salemodule and MIS payment module.
Example: increasing reliability via queue
Direct portal-MIS integration is fragile. If MIS is unavailable — portal fails. Solution — intermediate queue (RabbitMQ or buffer table in DB). Appointment created on portal, placed in queue, handler passes to MIS. Patient sees status "Appointment processing", then "Confirmed". Queue-based integration is 2–3 times more reliable than direct integration — confirmed by our experience and open sources (see RabbitMQ vs direct API).How to organize online booking considering clinic specifics
Booking an appointment at a clinic is not the same as booking a table at a restaurant. Nuances:
- First-time vs repeat visit — different slot durations (30 min vs 15 min), different cost.
- Referrals — patient can only book with specialists they have a referral for (check via MIS).
- Preparation for the visit — when booking ultrasound, gastroscopy, tests — automatic sending of instructions 48 hours before.
- Comprehensive programs — a checkup of 5 appointments that need to be scheduled sequentially in one day.
- Room schedules — doctor is available but room is occupied. Integration considers both doctor and room.
Patient notifications:
| Notification type | Channel | Time before visit | Show-up conversion |
|---|---|---|---|
| Confirmation | email + SMS | immediately | — |
| Reminder | SMS | 24 hours | +30% |
| Push notification | mobile app | 2 hours | +15% |
| Review request | 24 hours after | — |
Test results and documents
Viewing results is the feature that brings patients back to the portal. Implementation:
- Results from lab enter MIS → webhook notifies portal → portal saves result in infoblock → patient receives push/SMS "Results are ready".
- Display format: structured table (parameter, value, normal range, deviation) + PDF for download.
- Reference values — deviations from norm highlighted in color (red — above/below norm).
- History — patient sees parameter trends over time (e.g., hemoglobin over last 12 months) on a graph.
Medical documents (extracts, conclusions) are stored in the 1C-Bitrix "Drive" module or a separate infoblock with file properties. Access — only to the owner (patient) and their attending physician.
Telemedicine
Telemedicine consultations are a mandatory feature of a modern portal. Patients expect remote consultation.
Video consultation implementation:
- Integration with Jitsi Meet (self-hosted, no limitations), Zoom API, or Bitrix24 Video Calls.
- Booking teleconsultation — through the same schedule but marked "online".
- 10 minutes before start — link to video room in personal account and via SMS.
- Doctor connects from MIS interface or a separate portal office.
- Consultation recording (with patient consent) — for legal documentation.
Doctor chat: asynchronous text consultation — patient asks a question, doctor replies within the working day. Implemented via the "Web Messenger" module (im) or custom chat linked to medical record.
How to ensure data protection under 152-FZ?
Medical data is a special category of personal data. The portal development cost includes mandatory protection measures, averaging 15–20% of the project budget (from 300 thousand to 1 million rubles depending on scale).
Technical measures:
- Data storage within the Russian Federation.
- Database encryption (at least disk encryption, recommended encryption of specific fields: policy number, diagnoses).
- Two-factor authentication for medical staff.
- Access log — who, when, what data viewed. Implemented via 1C-Bitrix event handlers and custom log table.
- Automatic session timeout — after 15 minutes of inactivity for doctor's office.
- Consent to processing — at registration, at each appointment, when sharing with third parties.
- WAF — 1C-Bitrix "Proactive Protection" module + external WAF (ModSecurity or CloudFlare).
SEO and marketing for a medical portal
- Doctor cards —
Physicianmicrodata, unique meta tags, photo, list of services. - Service pages —
MedicalProcedureper Schema.org, description, indications, preparation. - Online booking in Google — integration with Google Reserve ("Book" button in search results).
- Reviews —
AggregateRatingfor stars in snippet. - Clinic blog — expert articles by doctors with author name and qualifications (E-E-A-T).
- LocalBusiness — markup for each branch with address, phone, hours.
What's included in portal development?
We provide:
- Analysis and technical specification.
- Architecture design and prototyping.
- Portal development from scratch or on a ready-made solution.
- Integration with MIS and external services (CDEK, YooKassa, ATOL).
- Deployment and hosting setup.
- Staff training and documentation handover.
- 1-year warranty on code and technical support.
How development proceeds:
- Analysis and requirements gathering (1-3 weeks)
- Architecture design and prototyping (2-4 weeks)
- Development and integration (4-12 weeks)
- Testing and debugging (2-4 weeks)
- Deployment and launch (1-2 weeks)
- Support and improvements (post-release)
The project cost is calculated individually based on the scope of integrations and functionality. Approximate budget for clinic portal development — from 2 to 6 million rubles. Get a free consultation — contact us to evaluate your technical specification. Order development of a clinic portal on 1C-Bitrix and increase patient loyalty.







