Medmis

Medmis

This connector uses the MEDMIS API v1 (the integration bus of the Medmis clinic management platform, <your node>/apix/v1): branches, specialists and their schedules, appointments, patients, invoices, payments, the price list, reserves, stock, to-do tasks and the occupational check-up module (Профосмотры). It reads; booking or changing an appointment and creating a task are included but installed switched off. Nothing is ever deleted through this connector.

Setup (about 5 minutes)

1. Ask Medmis support ([email protected], subject marked DEV / API_CORE) or your Medmis administrator for an API user: a login, its password and the system name used to sign in. The API user's permissions decide what the tools can read (appointments.get, patients.get, patient_invoices.get, payments.get, schedules.get, stores.get, todo.tasks.get, profex.*...).
2. MEDMIS_URL is the address of your clinic's Medmis node, e.g. https://node3.medmis.ru, without /apix. Its API reference is at <MEDMIS_URL>/apix/swagger.
3. Fill in MEDMIS_LOGIN, MEDMIS_PASSWORD (at least 6 characters) and MEDMIS_SYSTEM_NAME, install, and run medmis_list_branches to check.

The connector signs in with POST /apix/v1/Auth/login and sends the access token as a Bearer header; tokens live about an hour and are renewed automatically.

Workflow

• Start with medmis_list_branches and medmis_list_employees (ids of branches, specialists and their specializations).
• Free time: medmis_get_schedule_grid with branchIds, dateFrom, dateTo and onlyFreeSlots=true.
• Appointments: medmis_list_appointments for a period (filter by specialist, status, patient), medmis_get_appointment, and medmis_list_appointment_reference (statuses, types, visitations, sources, tags) to read the ids.
• Patients: medmis_list_patients (name, phone, e-mail, card number), medmis_get_patient for the full record, medmis_list_patient_reference (tags, attractions, identity_doc_types).
• Money: medmis_list_invoices, medmis_get_invoice, medmis_list_invoice_services, medmis_list_payments, medmis_get_payment.
• Price list: medmis_list_service_categories, medmis_list_services, and a specialist's offer with medmis_list_employee_services.
• Other: medmis_list_reserves, medmis_get_reserve, medmis_get_branch; stock with medmis_list_stores (per branch), medmis_list_store_materials, medmis_get_stock_levels, medmis_list_material_series; tasks with medmis_list_tasks; check-ups with medmis_list_checkup_companies, medmis_list_checkup_contracts, medmis_list_checkup_patients.

Writes switched off: medmis_create_appointment (book a slot), medmis_update_appointment (move, cancel via status, change comment or tags) and medmis_create_task. They change the clinic's live schedule, so an admin turns them on deliberately; before each call show the user the patient, specialist, day and time and wait for a yes.

Patient data: patients, appointments, invoices and payments are personal health data. Read only what the question needs and do not repeat identity documents or contact data unless the user asks. The patient list leaves out identity document numbers, INN and SNILS.

Dates and ids: day filters are YYYY-MM-DD; change-time filters are yyyy-MM-ddTHH:mm:ss in UTC. Appointments carry both UTC and local times (datetimeFromLocal) plus utcOffsetMinutes; quote local times. Branches, specialists, patients, appointments and payments use UUIDs; invoices, stores, materials, tasks and check-up records use numbers. List filters ending in Ids take several values.

Pagination and limits: lists return items, page, pageSize, totalCount and totalPages; pageSize is at most 100, page starts at 1. Medmis limits each method: filtered lists 20 requests a minute (one per second), reference lists 40 a minute, single records 100 a minute, sign-in 40 a minute. Avoid tight loops; 429 means wait.

Errors: 401 means a wrong login, password or system name, or an expired session (the connector signs in again once). 403 means the API user lacks the permission for that method. 400 ValidationError lists the bad fields (e.g. a password shorter than 6 characters, a malformed date). 404 means the id does not exist on your node.