Technological tasks
The Tech-tasks module is tasks related to the development, implementation and improvement of new technologies, products and processes. If you have development, implementation and other needs you can post information below.
An intelligent system for monitoring the execution of government contracts and monitoring the quality of work performed
Creation of a digital platform for objective monitoring of the performance of works and the provision of services under government contracts. The system should provide: photo and video recording of completed works; automatic geolocation of materials; control of deadlines; analysis of the actual performance of work using computer vision technologies; real-time contract monitoring; identification of risks of default; reporting for customers. Application example: The contractor has repaired the road, installed lighting, carried out landscaping or provides services for the maintenance of facilities. Materials with coordinates and shooting time are uploaded via the mobile application. The system automatically confirms that the work has been completed and identifies possible violations.
Decision acceptance deadline
22.06.26 (inclusive)
Preferred systems
бюджетный контроль, государственные закупки, мониторингNumber of applications
13
Development of the financial microservice "Cash Register, Billing and Financial Accounting" (Billing Service & POS terminal) for payment automation, cash shift management, billing and end-to-end financial analytics in the cloud-based medical information system Digital Clinic Hub (DCH)
Create a fault-tolerant, high-performance, and idempotent payment core that completely bridges the gap between medical admission and financial accounting. The cash register should seamlessly integrate with an Interactive Calendar and Electronic Medical Record (EHR), providing instant billing, transparent payment processing (including Kaspi QR and installments) and automatic generation of fiscal and analytical reports . Detailed description of the functionality and technical solutions: POS terminal interface: Development of a single cashier's desktop (two-column layout) based on Vue.js 2, where the entire payment flow fits without the need for scrolling . The composition of the invoice (services, prices, discounts) is displayed on the left, and the payment panel with an interactive 3×4 numpad is displayed on the right for quick entry of amounts and automatic calculation of the customer's change using the Change formula = Accepted − Total. Payment Methods and Mixed Billing: Support for multiple payment methods: Cash, Bank Cards/POS, Kaspi QR and Kaspi Installment . A complex "Mixed Payment" mechanism is implemented, which allows you to split one check into parts (for example, to pay in cash and part via QR), while the server creates two separate transactions with validation of matching amounts up to the amount. Deep integration with Kaspi Pay API: When you select Kaspi QR, the DCH backend sends a request to the Kaspi Pay API, generating a dynamic link and a QR code . The interface starts polling (every 3 seconds for 15 minutes) to check the status . Additionally, incoming Webhooks from Kaspi are being accepted with mandatory verification of the HMAC-SHA256 cryptographic signature to protect against status substitution . Strict management of cash shifts: Implementation of a financial responsibility system. The cashier cannot perform any operations without an open shift (the presence of shift_id in the JWT token is checked by Middleware) . When the shift is closed, the system automatically adjusts the balance, compares the estimated amount with the actual cash in the cash register, generates a PDF Z-report (via pdfkit or puppeteer) and saves it to S3 storage . An intermediate collection function is also available . Account lifecycle and debt control: The system supports the following statuses: draft, pending, partial, paid, owed, refunded, cancelled . If the patient pays only a part of the amount, the balance is automatically recorded as a debt, which is immediately highlighted to the coordinators and doctors in the patient's EHR header . The refunds and discounts module: Making refunds is only available from the paid status and requires you to fill in a text reason (at least 10 characters) . The discount system is strictly controlled by the JWT token: for example, the coordinator can make a discount of up to 10%, while the administrator has no restrictions . Integration and Notifications: After successful payment, the system automatically generates a fiscal/information receipt in PDF format and sends it to the patient via WhatsApp (via ChatApp) or Email . If the treatment is paid for, DCH instantly sends a Webhook to Bitrix24, transferring the transaction to the "Paid" stage (UF_PAYMENT_STATUS = 'paid') . DATABASE idempotence and security: All amounts in PostgreSQL are stored in the strict NUMERIC financial type(12.2) . To eliminate the risk of double charges (for example, if the cashier double-clicked on the button when the Internet was bad), the API requires the Idempotency-Key header. All cash transactions are recorded in the audit_log table.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
6
Development of the module "Department of care and Management of multi-stage procedures" (Care Department & Treatment Course Management) to coordinate treatment courses, track conversion statuses, record sessions, and distribute downloads of treatment rooms in the Digital Clinic Hub (DCH) cloud medical information system
To create a specialized digital tool for the staff of the "Department of Care" (Coordinators), which automates the management of patients through complex, multi-stage treatment courses (physiotherapy, CT, PREP therapy and rehabilitation). The main objective of the module is to link doctors' medical appointments with the schedule of treatment rooms and financial accounting, ensuring maximum conversion of patients from the initial consultation to the purchase of a full course of treatment. """""" Detailed description of functionality and technical solutions: ""Specialized Coordinator interface: Development of a separate workspace, where patients are divided into tabs of the appropriate treatment courses (for example, "Physio", "CT", "PRP", "FITNESS") . The coordinator sees lists of patients to whom doctors have prescribed procedures, with a display of treatment features . Recording and tracking sessions: Implementation of a strict monitoring system for the completion of courses. The Care Department's table automatically keeps accurate mathematical records: the total number of sessions scheduled, the number of procedures actually performed, and the number of visits missed by the patient are displayed . Procedure schedule management module: The staff of the Care Department have the opportunity to add appropriate procedures to patients, choosing the time required and convenient for the patient. . For this purpose, a special calendar grid is being developed (different from the doctors' calendar), focused on the workload of specific devices and rooms (for example, the schedule of the CT machine or the physiotherapy room) . Visit marking module: Integration of functionality that allows a doctor or coordinator to mark the fact of a patient's successful completion of a specific procedure from the course in one click . Conversion status management (Funnel): The coordinator works with his physical branch and is responsible for the patient's "follow-up". "He" is given the exclusive right to put down the most important conversion statuses in the system: "Bought a course of treatment" or "Did not buy a course ." Flexible Financial Rights (RBAC): To stimulate sales, the system grants the Coordinator partial cashier rights (through verification of the JWT token). The coordinator can independently create invoices, accept payments (in cash, by card, Kaspi QR) and apply a motivating discount of up to 10% . At the same time, the coordinator is strictly prohibited from making financial refunds, making discounts of more than 10%, or managing the closure of cash shifts.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
5
Development of an internal module "CRM system, Sales Funnels and End-to-end Integration" (CRM & Patient Journey Funnels) for patient lifecycle management, call center automation and deep two-way synchronization with Bitrix24 within the Digital Clinic Hub (DCH) cloud medical information system
Create a seamless lead management system (potential patients) that will combine the clinic's marketing efforts with the actual medical admission and cash register. The main objective of the module is to digitize the patient's Journey from the first click on an advertisement to the successful completion of the treatment plan, eliminate the loss of leads due to the human factor, and automate the task of setting operators to "wait" or return the patient. Detailed description of the functionality and technical solutions: Visual Kanban Boards (Funnels): Development of interactive sales funnels divided by branches . """"""""""The patient's card visually moves through the stages (stages of the transaction): "New treatment", ""Hired", "Made an appointment", "Came to the initial appointment", "Assigned course", "Bought course / Successfully completed", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal", "Refusal / He didn't come." The drag-and-drop mechanism for manual movement is supported, as well as automatic stage change based on system triggers. Deep two-way synchronization with Bitrix24: The module acts as an integration core between DCH and external CRM. Any change in DCH should be instantly reflected in Bitrix24 via Webhooks . If the CC operator selects a non-standard time in the DCH calendar, a new window is automatically created in Bitrix24 . Upon successful payment in the "Checkout" module, DCH sends a PATCH request to the Bitrix24 API to update the transaction stage and the UF_PAYMENT_STATUS = 'paid' field. The opposite direction also works: when an entry is created in the iDoctor aggregator application or in Bitrix24, it is automatically converted into a patient card and occupies a slot in the DCH calendar grid . Trigger automation and task setting: The system automatically responds to statuses from the Interactive Calendar. """" For example, if the Registrar sets the status "Not received," the CRM module automatically transfers the patient's card to the "Missed" stage and generates an urgent Task for the call center manager with a deadline - "Contact the patient to transfer the record." If the parish Department sets the status to "Canceled" , the system requires you to specify the reason and sets the task for quality control. Omnichannel and Communication (ChatApp): Integration with ChatApp, WhatsApp Business API and Facebook Messenger services to aggregate all correspondence with the patient directly in his card inside the CRM . Automatic sending of reminders 24 and 2 hours before the appointment to minimize the no-show rate . Analysis of the reasons for failures (Lost Reasons): A required field when transferring a card to the "Failure" stage or when canceling an entry . """" The data is aggregated into a special dashboard of the administrator, showing the churn funnel (for example, "Expensive", "Inconvenient time", "Chose competitors").
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
7
Development of an innovative "AI-Driven Quality Assurance Module" based on neural networks for automatic decoding, semantic analysis and evaluation of telephone conversations with patients within the Digital Clinic Hub (DCH) cloud medical information system
To create a high-tech artificial intelligence-based tool for 100% automated audit of communications between clinic operators and patients. The main task of the module is to replace manual listening to supervisors with machine analysis, algorithmically identify script violations, determine the emotional background of a conversation, and provide managers with ready—made recommendations for improving customer service . Detailed description of the functionality and technical solutions: Automatic transcription (Speech-to-Text): Implementation of a pipeline for translating audio calls into text. The main speech recognition engine will be OpenAI's Whisper API . For large clinics with strict security policies (NDAs), the optional implementation of DeepSpeech, a local offline speech recognition solution without transferring audio files to third—party servers , is provided. Semantic Analysis and NLP (Natural Language Processing): The processed text is passed through powerful language models (KazNLP, RuBERT, ChatGPT API) . The AI does not just transcribe the text, but performs a deep semantic analysis: it determines the emotional tone of the call (aggression, doubt, satisfaction) both from the patient's side and from the operator 's side. Checklist assessment (Custom Python Pipeline): Development of a specialized Python algorithm that compares the transcribed dialog with the approved corporate standards of the clinic . The system automatically assigns points: whether the manager greeted you, offered an alternative recording time, worked out the "expensive" objection, and showed empathy. Automated prompts and action triggers: Based on the analysis, the module generates hints for improving scripts and correcting operator behavior . "AI" also links the results of processing requests with subsequent actions in CRM: for example, if the AI realized that the patient did not make an appointment, but asked to call back tomorrow, the system will automatically create a "Repeat call" or "Make an appointment" task . Commercial model (SaaS): This innovative AI tool is positioned as part of the expanded functionality of the DCH platform and will be offered to clinics as an additional subscription (worth 10,000 tenge per user per month), which will generate tangible additional revenue for DCH
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
8
Development of the analytical core "End-to-End Analytics, financial reporting and BI Dashboards" for the aggregation of medical, operational and financial indicators of a network of clinics in the Digital Clinic Hub (DCH) cloud medical information system
Create a transparent tool (data-driven management) for clinic owners, chief physicians, and administrators. The main objective of the module is to consolidate disparate data from the calendar, EHR, and checkout modules into single interactive control panels, providing automatic and error—free calculation of employee KPIs, financial flow control, and identification of "bottlenecks" in the sales funnel without manually tabulating tables. Detailed description of the functionality and technical solutions: Isolated database architecture: In order for heavy analytical calculations not to slow down the work of the registry and cashiers, requests from the financial and operational dashboards are sent to the database replica (a separate server circuit) . This guarantees stable performance of the main API (response time is up to 1 second) . Summary dashboards by Call Center and Doctors: The module automatically aggregates calendar statuses (Received, Not Received, Canceled, Total) for each call center manager, doctor, and branch . For an objective assessment of sales, a strict formula for calculating conversions has been implemented: Received / (Total - Interim inspections) × 100% . Intermediate inspections (repeat visits) are algorithmically excluded from the calculation in order not to distort the actual achievements of the manager . Churn Analysis: A section that collects data from the Parish Department about cancelled entries. Visualizes a list of reasons for cancellations with their number and percentage of the total number, with the ability to upload an array of data to Excel for detailed study . Financial BI Dashboard: A dashboard with 5 key KPI cards (widgets) is being developed for management: revenue per day, revenue per month, total patient debts, average bill, and number of canceled bills . Visualization and detailing of payments: Integration of graphic libraries (Chart.js or ECharts) for constructing revenue histograms by day and pie charts broken down by payment methods (Cash, Kaspi QR, Bank Card, Installment Plan) . An interactive table of recent transactions is located under the charts . Reporting generation: Development of REST API endpoints (for example, /analytics/revenue, /analytics/avg-receipt, /reports/monthly) for generating daily and monthly reports . The summary data can be downloaded in Excel and PDF formats . Role-based Security (RBAC): Access to the shared dashboard, hidden analytics, and summary reports for all branches is strictly limited. This information can only be viewed by the "Admin" role, which eliminates the leakage of trade secrets to line staff.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
7
Development of the microservice "System of auto-notifications, omnichannel communications and trigger mailings" (Notification Engine & Patient Communications) for automation of service messages, distribution of fiscal/information receipts and reduction of patient non-attendance (no-show) in the cloud medical information system Digital Clinic Hub (DCH)
Create a reliable, fault-tolerant core for automatic interaction with patients without human intervention. The main objective of the module is to build a seamless digital service that will promptly remind patients of visits, instantly send supporting documents after payments, and collect feedback (NPS) to increase overall loyalty to DCH partner clinics. Detailed description of the functionality and technical solutions: Microservice architecture and Task queues: The notifications module is allocated to a fully independent microservice (notifications) based on Node.js . A queue broker (BullMQ) is used to process a huge array of outgoing messages and incoming webhooks without delay, ensuring message delivery and processing in less than 30 seconds . Omnichannel integration: Deep integration with ChatApp service is being implemented to work with WhatsApp Business API, as well as with Facebook Messenger . Additionally, backup (fallback) communication channels are configured: if the patient does not have WhatsApp, the system automatically sends a notification via the Kazakhstan SMS aggregator, and duplicate receipts are sent to Email via SMTP/SendGrid . CRON Schedulers and schedule triggers: Background CRON scripts are deployed on the server, which scan the DCH Calendar database every minute . 24 hours and 2 hours before the scheduled time, the system automatically generates and sends the patient a personalized message with a reminder of the visit, the address of the clinic and the name of the doctor. "Two" way communication and Webhooks: When receiving a reminder on WhatsApp, the patient can respond, for example, by clicking the "Confirm" or "Cancel" button. "ChatApp"'s incoming webhook is processed by the DCH server, which automatically changes the status of the entry in Calendar 2.0 (for example, to "Confirmed" or "Canceled"), instantly updating the administrators' interface. Automatic sending of receipts and documents: The notification module is tightly connected to the Cash Register module. Immediately after successful payment, the system (without the participation of the cashier) generates a PDF receipt detailing the services and sends a link to it to the patient via WhatsApp or Email . Feedback Collection (NPS): An hour after the registrar sets the status "Arrived", the Notification Engine sends the patient a short questionnaire (Net Promoter Score) with a request to evaluate the quality of the doctor's appointment from 1 to 10. If the score is low, the head of the clinic immediately gets an alert to resolve the conflict promptly.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
5
Development of an internal module "Corporate Task Calendar and Back-Office Planner" (DCH Back-Office Planner) for managing internal business processes, timing control (SLA), document management automation and coordinating the work of non-medical personnel (accounting, HR, lawyers, marketing, procurement department) in the Digital Clinic cloud medical information system Hub (DCH).
To create a pragmatic, transparent and automated task setting and reporting system for the clinic's back office. The main task of the module is to transfer the management of internal routine processes (from purchasing consumables to submitting tax reports) from the chaos of messengers to a single digital channel. This will provide management with a tool for monitoring deadlines and the quality of work, forming a full-fledged ecosystem of medical business management . Detailed description of the functionality and technical solutions: Two visualization modes (Kanban and Calendar): Development of an interactive interface based on Vue.js 2 . A "Kanban board" mode with status columns (To Do /In Progress / Review /Done) and drag-and-drop support is being introduced for project departments (marketing, IT). For departments tied to hard dates (accounting, lawyers), a "Calendar Grid" mode is provided, where tasks are displayed as timelines. Both views are instantly synchronized via WebSockets without reloading the page. Complex Task Engine: The assignment card includes advanced attributes: director, responsible, co-executors, observers, priority (Low/High/ Critical), time spent estimate and interactive checklists (for example, the task of "Purchasing MRI" is divided into stages: collect 3 KP, agree on a budget, sign a contract). The strict reporting module (Proof of Work): The key business innovation of the block. Technically, the contractor cannot close the task by simply switching to the "Done" status. When trying to close, the system calls up the mandatory modal window "Report Form", where the employee must enter a text summary and attach supporting media files (PDF scan of the certificate, photo of the repaired ultrasound machine, payment receipt). Files are securely stored in S3 cloud storage. "The supervisor" receives a notification and can either "Accept" the task or send it "For revision." Escalation and SLA control engine: Backend on Node.js implements an automatic deadline control system. 24 hours before the deadline, the task turns "yellow" and the performer receives a push notification. If the deadline is overdue, the task becomes red (Overdue), and the system trigger automatically sends an escalation notification to the higher management (chief medical officer or manager). """"Regular Task Scheduler (CRON): CRON scripts are implemented to automate repetitive business processes (for example, "Checkout reconciliation", "Inventory of the warehouse on the 1st day", "Submission of the tax form 200.00") . The supervisor sets up the template once, and the system generates new order cards on its own according to a set schedule, appointing those responsible. Role Model (RBAC): The core supports strict isolation of rights . The contractor sees only their own tasks and cannot move the deadline without requesting an app. The head of the department sees the boards of his subordinates, and the Administrator (SuperAdmin) has access to the cross-functional dashboards of the entire clinic network.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
5
Development of the integration core "External Integration Hub & eGov/DAMUMED Gateway" for secure and seamless data exchange between the Digital Clinic Hub (DCH) cloud medical information system and external CRM, aggregators, payment systems and government medical registries.
Create a fault-tolerant, high-speed, and secure data bus (API Gateway) that will free the DCH system from technological isolation. The main objective of the module is to provide algorithmic data flow between the clinic's marketing tools (Bitrix24), medical aggregators (iDoctor), fintech providers (Kaspi) and prepare the platform for legitimate data exchange with the state healthcare systems of the Republic of Kazakhstan. Detailed description of the functionality and technical solutions: Deep integration with Bitrix24 (Two-way synchronization): Development of a REST API and a Webhooks processing engine. If the manager creates a new (non-standard) window for the doctor in the DCH calendar, it is automatically duplicated in the Bitrix24 schedule. . Upon successful payment of the full course of treatment in the "Cash Register" module, the DCH gateway sends a PATCH request to the Bitrix24 API, automatically transferring the transaction to the required stage and updating the UF_PAYMENT_STATUS = 'paid' field. API bridge for Medical Aggregators (iDoctor): Creating a secure endpoint for accepting applications from the outside. When a patient makes an appointment through the external application of the iDoctor aggregator, the DCH gateway instantly accepts this payload, creates a patient card and automatically reserves a slot in the calendar grid without the participation of the registry administrator . Fintech Gateway and Kaspi Pay API: Integration of complex financial logic for generating dynamic QR codes, Kaspi Installment payments and making refunds (Kaspi Refund API) . Implementation of a listener for incoming Webhooks from Kaspi with mandatory cryptographic verification of the HMAC-SHA256 signature to prevent fraudsters from replacing payment statuses . Omnichannel communications: Linking the notification core with ChatApp providers (for WhatsApp Business API and Facebook Messenger) and Kazakhstani SMS aggregators (as a fallback channel). This will allow the system to send automatic reminders and PDF receipts . State Registries (eGov and DAMUMED): Architectural preparation (at the level of data models and APIs) for future integration with eGov API and DAMUMED platform . This will allow DCH partner clinics to transmit mandatory medical statistics to the Ministry of Health in one click without double manual entry. International security standards: Preparing the data exchange architecture for the requirements of international medical Data Transfer Protocols (HL7) and information security standards (ISO), which is necessary for the future scaling of the platform abroad.
Decision acceptance deadline
18.06.26 (inclusive)
Preferred systems
Other technological solutionsNumber of applications
7
Development of a universal positioning platform
Assessment of the possibility of developing and required resources of a Universal Positioning Platform for use in the Company's product solutions
Decision acceptance deadline
16.06.26 (inclusive)
Preferred systems
Positioning SystemsNumber of applications
18
