Medical Portal Development: Booking, Patient Account, MIS, Telemedicine
A clinic patient spends an average of 15 minutes scheduling an appointment by phone, while the administrator spends another 10 minutes searching for an available slot in a paper journal. Result: 30% dissatisfied patients and 20% no-shows. A medical portal solves these problems through automation: online booking, synchronization with the Medical Information System (MIS), and reminders. However, developing such a portal is not just a technical task. It must comply with Federal Law No. 152-FZ (personal data), 323-FZ (healthcare fundamentals), integrate with MIS (1C:Medicine, Medialog), authenticate via ESIA, and support telemedicine. Our team has created over 30 medical portals—from private practices to federal services. With over 10 years of experience in medical information systems, we guarantee full regulatory compliance and data protection.
Challenges We Solve
Typical problems: schedules not syncing with the MIS, patients seeing already booked slots, doctors wasting time on manual data entry. Or—data leaks: unencrypted channels, weak authentication, no audit trail. We eliminate these risks at the design stage.
Our Approach: A Real Case
In one project for the clinic network "Health+", we faced a situation: direct database integration to the MIS caused schedule desynchronization and data leaks. After migrating to HL7 FHIR R4, synchronization time dropped from 5 minutes to 10 seconds, and booking errors disappeared completely.
How We Ensure Security of Medical Data
Medical data is a special category of personal data. According to Article 6 of 152-FZ, medical data falls under this category. Requirements:
- Encryption at rest: database encryption (PostgreSQL column-level encryption or TDE)
- Encryption in transit: TLS 1.3 for all connections
- Access auditing: every data access is logged (who, when, what was viewed)
- Role-based access: doctors see only their patients
- Data deletion upon patient request (considering 25-year retention period)
Example security architecture: PostgreSQL column-level encryption for PHI, network segmentation with WAF, all actions logged to a SIEM. Deployment on certified servers in Russia: Yandex.Cloud (152-FZ certificate), Sber Cloud, MTS Cloud.
Why MIS Integration Matters
The MIS is the clinic's primary accounting system. Without integration, schedules and patient histories don't sync. Popular MIS: 1C:Medicine, Medialog, Infoclinic, Bars.Zdorovye. Integration is possible via REST API, HL7 FHIR, or direct database connection (not recommended). FHIR requests:
GET /fhir/Patient?identifier=123456789 GET /fhir/Appointment?patient=Patient/456&status=booked POST /fhir/Appointment Comparison of integration methods:
| Method | Speed | Security | Flexibility |
|---|---|---|---|
| REST API | Medium | High | Medium |
| HL7 FHIR | High (3x faster) | High | High |
| Direct DB connection | High | Low (security risk) | Low |
How to Reduce Patient No-Shows
Automatic reminders 24 and 2 hours before appointment via SMS and email. One-click rescheduling. No-show analytics to adjust schedules. Result: no-shows reduced by 30–50%.
Patient Features
- Personal account: visit history, test results, referrals, prescriptions in PDF.
- Telemedicine: video consultations (WebRTC/Livekit), chat, recording storage.
- Online payment: prepayment or post-payment (YooKassa, Stripe).
Doctor Features
Schedule with slot management, today's patient list, patient history, attach documents to visits, remote consultations.
ESIA and Authentication
For state services—mandatory integration with ESIA. Private clinics may use email/SMS with passport verification.
What's Included in the Work
- Technical specification and prototype
- Portal development (Frontend: React/Next.js, Backend: Laravel 11, PostgreSQL)
- MIS integration (REST API or HL7 FHIR)
- ESIA integration (optional)
- Telemedicine (WebRTC video conferences)
- Load testing and penetration testing
- Deployment on certified cloud (Yandex.Cloud)
- Staff training and documentation
- 6 months warranty support
Project Stages
| Stage | Result |
|---|---|
| Analysis | Technical specification, data schema, prototype |
| Design | Architecture, stack selection (React/Next.js, Laravel, PostgreSQL) |
| Implementation | Portal development, MIS and ESIA integration |
| Testing | Functional, load, penetration |
| Deployment | Hosting on certified cloud |
| Training | Instructions for administrators and doctors |
| Support | 6-month warranty |
Timeline and Cost
MVP with booking, personal account, and integration with one MIS: 3–5 months. Full-featured portal with telemedicine, FHIR, and ESIA: 6–10 months. Cost is calculated individually. Get a consultation from an engineer to evaluate your project. Contact us to discuss integration with your MIS.