Our own project · KSM+

A connected clinic system

Apps, records, calls and analytics form one working process.

iOS / WEB1C / CallTouchAPI / ANALYTICS

KSM+ · our own project

Patient and team apps

The project is built around native iOS apps with a shared backend and role-based access.

Patient: specialist and time selection, confirmation, booking history and cancellation.
Team: working sections, management summaries and access controls.
Web: a manager portal; the patient PWA is being developed as a separate prototype.

Android development is demonstrated by the separate SEOPRO showcase app with emulator checks. Clinic platforms are at different stages; store publication is not claimed.

The diagram illustrates the project architecture. Images and demonstration data were created specifically for this showcase.

01 / SYSTEM FLOW

One chain across separate systems

Select a stage to see the data and actions connected by the system.

01 / 06

Ads and sources

Yandex Direct spend, Metrika visits and CallTouch enquiries are collected for matching. Incomplete reports are flagged.

Enquiry and call

A call or enquiry is linked to its source where identifiers are available. Telephony supplies waiting times, missed calls and callbacks.

1C and operational data

Services, prices, schedules and booking states come through agreed 1C interfaces. Freshness is checked before an action.

App and booking

The patient iOS project includes selecting a specialist and time, confirmation, viewing and cancellation. The team has separate sections and permissions.

Full-funnel matching

The code matches an enquiry to bookings, completed visits and available payments. Windows, repeat enquiries and uncertain links need explicit rules.

Dashboard and report

Role-based portals combine metrics. Recurring Telegram and PDF summaries, freshness checks and source reconciliation are provided for in the project.

What the project connects

Apps and portals

Two native iOS versions: patient and team. A manager web portal and a patient PWA prototype are developed separately.

1C connection

Services, prices, schedules and bookings through OData, change monitoring and the latest successful snapshot when the source is unavailable.

Ads and attribution

Direct, Metrika and CallTouch: spend, visits and enquiries. ClientID and phone matching use defined rules and uncertainty labels.

Call centre

Inbound and outbound calls, missed calls, waiting and callbacks. Available recordings use SpeechKit and defined rule checks, with errors and exclusions accounted for.

Operational reporting

Role-based portals, server summaries, Telegram and PDF. Metrics are checked for freshness and source discrepancies.

Reviews and feedback

Collection of available Yandex Maps, 2GIS, sector-platform and app reviews is provided for, with issues grouped for the responsible employee.

Project status and scope

The listed features are confirmed in reviewed source code. This is our own evolving project; current availability of every live workflow was not verified in this review.
Android experience is demonstrated by the separate SEOPRO showcase, with a build and emulator checks. We do not claim a ready native Android clinic app or App Store or Google Play publication here.
Google Ads connections and specialised Google Maps APIs for a customer project first require access, API and platform-requirement checks.
Conversation review depends on audio availability and processing conditions. A person reviews disputed scores; coverage and errors are shown separately.

What we can build for your business

Start with one chain: enquiry → team action → outcome → report. Agree a prototype, access, scope and acceptance criteria, then expand around your business.