Patients and medical record
PatientsDental chartMedical record and quality controlTherapy and prescriptionsTreatment plans and coursesPatient balancePatient portalFinance and cash desk
Invoices and paymentsFiscal receipts (54-FZ)Payment receiptDebtors and tax certificatesWarehousePayrollConnect the EHR with EGISZ, telephony, notifications, online booking, cash registers and payment. We will show the available connections and estimate a custom integration.
DIVAMED has a working connector. Before going live we check access, the provider's plan and a full test scenario for the specific clinic.
First we check whether an API exists, the set of data and the service's limitations, then we confirm the timeline and the cost of implementation.
Transfer of medical documents, sending statuses and connection of external systems through the API.
EGISZCreating, signing, sending and tracking the statuses of medical documents.
Document statuses are tracked in the EHR.
APIExchange with websites, BI tools, internal systems and the clinic's custom setups.
The scenario and the set of data are agreed before connection.
Booking confirmations, reminders, cancellations, message templates and communication history. Telegram and MAX chats are included in the Premium and Corporate plans and can be added to the others as an extra module.
TGA bot, webhook and automatic messages to patients.
Messages and replies stay in the working loop.
MAXA messenger channel for notifications and conversations.
The clinic uses a channel the patient is used to.
SMTPEmails, confirmation codes, booking notifications and sending documents.
Emails are sent from the clinic's configured address.
VKMessages to patients and handling of replies from VK.
Confirmations, reminders and booking cancellations through the clinic's chosen SMS provider.
TSSending SMS and tracking the result through the API.
SMSTransactional SMS through the SMS.RU API.
SMSCSending messages and receiving the SMS identifier.
STSMS notifications through the provider's REST API.
DEVTransactional messages through the Devino API.
UGSending transactional SMS through UniSender Go.
MTSSending SMS through the Exolve communication platform.
BEESMS campaigns through the Beeline Business API.
EDTransactional SMS through the edna platform.
ΣSending SMS through the Sigma Messaging API.
Incoming events, call history, the default provider, call recordings and webhooks.
MANGOVirtual PBX, call events and call recordings.
UISCall tracking, PBX, call events and enquiry sources.
ZADCloud PBX, SIP numbers, webhooks and links to recordings.
MTSMTS API platform for numbers, calls and events.
RTKRostelecom virtual PBX for incoming calls.
BeelineVirtual PBX for handling calls and notifications.
TFTelephony integration through the API and webhooks.
SIPCloud PBX and call scenarios for the clinic.
GRCalls from the clinic, call recordings and enquiry history in the patient record.
*Your own PBX through AMI/ARI and links to recordings.
NFCloud telephony, call events and enquiry history.
Synchronization of the schedule, requests, reviews and enquiry sources from external platforms.
SBERPatient bookings from the platform land in the clinic's schedule.
PDRequests, schedule and enquiry source.
NPIntegration of bookings, schedule and reviews.
DOCExchange of requests and patient booking with the platform.
YRequests and data from the maps are passed into the clinic's workflow.
2GISBookings and enquiries from the platform are convenient to handle in DIVAMED.
ZOONSynchronization of external bookings and reviews.
Automatic receipt printing, test/production modes, tax ID, tax system and cash register data.
ATOLAutomatic fiscalization of payments and printing of online receipts.
The payment is passed for fiscalization under the configured scenario.
CLOUDOnline receipts for the clinic's paid services.
ODTransfer of payment data to the cash register and the tax authority.
EVOFiscalization of payments and work with the clinic's cash register.
MKOnline receipts and cash operations for medical services.
B.RUAutomatic sending of receipts after payment.
Creating payment links, returning the patient after payment, test and live modes.
ЮKPaying for services by link and passing the payment status to DIVAMED.
TOnline invoice payment and control of successful payments.
SBERAccepting payments from patients and marking payment in the system.
APayment links for patients and accounting of service payments.
PSBAccepting online payment and returning the patient after payment.
VTBPaying the clinic's invoices through bank acquiring.
GPBOnline payment for services and updating the invoice status.
RSHBPatient payments on the clinic's invoices.
SKBAcquiring for paying for medical services online.
MTSAccepting online payments and reconciling payment in DIVAMED.
BSPBBank payment of invoices and passing on the result of the payment.
YMPayment links and online payment for the clinic's services.
Import of patients and appointments from the systems the clinic is moving from.
Import of patients and appointments from IDENT.
Import of patients and appointments from StomX.
Import of patients and appointments from Medesk.
Import of patients and appointments from Future IT Dent.
Import of patients and appointments from YCLIENTS.
Custom exchange with CRM, accounting and electronic document management systems.
AMOPassing enquiries, deals and patient sources.
B24Exchange of leads, contacts and the clinic's tasks.
KDElectronic document exchange with counterparties.
SBISExchange of documents and accounting data at the clinic's request.
Before work begins we confirm the feasibility of the specific scenario, the provider's terms and the acceptance criteria.
We clarify the service, the provider's plan, the events needed and the set of data.
The clinic issues API keys or sets up a webhook in the provider's account.
We check creating a booking, a call, a document, a receipt or a payment on a test scenario.
We record the responsible people, the error log and the way of working after launch.
Tell us the service and the scenario: the clinic website, BI, CRM or an internal system. Before work begins we agree the data to exchange, access, API limitations, timeline and cost. A service in the catalog does not mean every scenario is available without configuration.