Budget: 5000 UAH Deadline: 5 days
Welcome! The Business Atlas team is ready to develop a medical referral routing service (Worklist) for you. Instead of writing heavy desktop software from scratch, we propose to deploy a flexible architecture based on Low-code platforms and custom microservices. In my experience, there are over 50 successful projects in the UA/EU markets, where automating complex data routing allowed for the creation of stable and fault-tolerant systems.
Our vision for technical implementation:
• Data reception (HL7 / XML): The main conductor of logic and data processing will be the n8n platform. It will automatically receive referrals from the MIS by reading XML files or working with the HL7 protocol. n8n will also provide flexible encoding conversion (Cyrillic/Latin) depending on the device profile.
• Referral transmission (DICOM Worklist): For integration with specific medical equipment, we will connect an isolated microservice (based on Python libraries for DICOM), which will be orchestrated through n8n. The system will automatically generate the necessary DICOM tags and send referrals to registered devices.
• Graphical interface (Admin Panel): Instead of developing an interface from scratch, we will assemble a quick web panel based on Budibase or Retool. In this GUI, you will be able to choose the method of data reception, add/remove DICOM tags, register new devices (AE-title, IP, port, encoding), and manage the service settings.
• Cross-platform and auto-start: The entire solution is packaged in Docker containers. This guarantees identical operation on both Windows OS and Linux (Ubuntu, Debian). The auto-start of the service upon operating system startup is implemented using standard tools (systemd / Docker daemon).
Estimated timelines and costs for MVP:
• Configuration of HL7/XML reception, transliteration logic, and data validation: 1.5 weeks.
• Integration of the DICOM module for communication with devices and tag configuration: 1.5 weeks.
• Development of the management web interface, containerization (Docker), and auto-start tests: 1 week.
Total implementation time: 3.5 – 4.5 weeks.
Estimated cost: $4,000 – $5,500 turnkey (depending on the final number of custom DICOM tags and the specifics of connecting your MIS).
Are you ready to discuss the technical details in person?
Budget: 15000 UAH Deadline: 12 days
Good day!
I am interested in your project for developing a Worklist service. I have experience working with medical information systems, the HL7 protocol, and the DICOM standard.
Here’s what I can offer for your project:
• Implementation of receiving referrals via HL7 (v2.x) and XML files
• Formation of DICOM Worklist (C-FIND SCP) and transmission to diagnostic devices
• Support for encodings: Latin-1 and UTF-8/Windows-1251 (Cyrillic) with auto-detection based on device settings
• Cross-platform development: Windows + Linux (Ubuntu/Debian) — systemd/Windows Service for auto-start
• GUI for configuration: AE Title, IP, port, management of DICOM tags, selection of referral reception mode
Technologies: Python (pynetdicom, python-hl7) or Java (dcm4che) — we can discuss what is preferable for your infrastructure.
I am ready to discuss details, timelines, and budget. Write to me — I will respond quickly.
Best regards
Budget: 27000 UAH Deadline: 30 days
I can execute this project comprehensively: from developing the referral reception service to configuring data transmission to diagnostic devices, taking into account various encodings, operating systems, and equipment features. I will pay special attention to the stability of the service, logging, fault tolerance, and ease of further administration. This is critically important for medical systems, where even a small error can disrupt the clinic's workflow.
The advantage of my work is that I do not create "temporary solutions." The service will be built with scalability in mind, allowing for the addition of new devices, new integration formats, and further development without completely rewriting the system. I will also implement an intuitive graphical interface for settings, so that staff can independently change parameters without the need to edit configurations manually. I will separately consider compatibility issues with various DICOM devices, as different manufacturers may have their own peculiarities in working with Cyrillic, tags, and transfer syntax. If necessary, I can provide examples of implemented integrations and architectural solutions upon request.
Work plan:
- Analysis of the structure of the MIS, HL7 format, and XML referrals
- Designing the architecture of the service and the mechanism for processing referrals
- Implementing data reception via HL7
- Implementing referral reception via XML
- Implementing data conversion to DICOM format
- Configuring support for Cyrillic and Latin
- Implementing logic for encoding selection depending on the device
- Creating a mechanism for registering DICOM devices
- Implementing management of DICOM tags
- Creating a graphical interface for settings
- Configuring operation under Windows and Linux
- Implementing service auto-start
- Testing data transmission between the MIS and equipment
- Checking stability and logging errors
- Preparing installation and administration instructions.
Budget: 15000 UAH Deadline: 10 days
Good day, I have experience in developing cross-platform services with a similar modular architecture. I also have a ready technology stack for the full implementation of the project.
Feel free to message me privately, we can discuss the details and some clarifications, and I will present a clear technical development plan. The project is interesting, so I would be happy to participate.
Budget: 10000 UAH Deadline: 7 days
Good afternoon
I have already worked on implementing data exchange using the dicom and hl7 protocols.
I am developing it in Python as a server using the pydicom and python-hl7 libraries.
A GUI client for management is being created with pyqt6.
From you, I will need requests regarding the design of the interface, a precise description of the admin panel functionality, and samples of the data to be transmitted.
Budget: 5000 UAH Deadline: 7 days
Ready to develop a Worklist service in Python. I will implement HL7/XML reception, conversion to DICOM, and a GUI for Windows/Linux. Deadline is 7 days, detailed plan after clarifying the specifications.
Budget: 24000 UAH Deadline: 7 days
Hello! I have relevant experience with similar tasks, and I can help with your project. I can quickly familiarize myself with the requirements, propose the best solution, and execute the work carefully. I am ready to discuss the details and get started.
Budget: 2000 UAH Deadline: 3 days
Hello! Your project has sparked great interest in me. I am ready to start working immediately and ensure high-quality execution.
Proposals concealed
Proposals are currently absent
Budget: 27000 UAH Deadline: 45 days
The benchmark for the first assessment is 240,000 UAH and 45 days for the working service with graphical configuration, HL7/XML reception, DICOM MWL, and installation on Windows and Linux. We will confirm this after reviewing message examples and checking the requirements of specific devices =)
Technically, I would implement this as a separate background service with a graphical interface for configuration - HL7/XML receiver, patient and referral normalization, a table for Cyrillic/Latin correspondence, DICOM tag mapping, a registry of devices by AE-title, IP, port, institution, event log, and auto-start in the OS. An important point - !!check Cyrillic in DICOM separately!!, as some devices read Latin well, while others start to go silent.
Questions
> Should this be specifically DICOM Modality Worklist SCP, or is there also a need to transmit as a DICOM file to the device?
> Are there examples of HL7 messages, XML files, and a list of diagnostic device models?
For similar medical systems
> https://business.ingello.com/lita - medical platform with roles, offices, and clinic processes
> https://business.ingello.com/lita-doctor - doctor interface and working with medical data
> https://systems-fl.ingello.com/ua - our profile landing for complex systems on the exchange
Budget: 27000 UAH Deadline: 45 days
We have almost ready architecture for such a Worklist service - we can quickly adapt it to your HIS and diagnostic devices, we can discuss it right now here on the marketplace, I am available =)
The benchmark for the first working version is 10,000 USD and 45 days, more precisely after checking the HL7 format, XML, and the requirements of specific devices.
For implementation, I would go through a separate service - receiving HL7 and XML, normalizing referrals, a table of transliteration rules or Cyrillic, DICOM Modality Worklist SCP, a registry of devices with AE title, IP, port, institution, UI for settings, and auto-start on Windows and Linux.
Look, here’s the nuance - it’s important to fix the set of DICOM tags that can be added or removed, and the mapping table of HIS fields to DICOM.
We need examples of HL7 messages, XML files, a list of device models, and whether there is a test DICOM node for verification.
To clarify - which specific HL7 messages are coming from the HIS - ORM, ORU, or another format.
Another question - do we only need to send referrals to the device, or should we also maintain a log of statuses, errors, and resends?
Similar medical cases Ingello - https://business.ingello.com/evrika - designing HIS for eHealth and medical processes.
Another close example - https://business.ingello.com/lita-doctor - doctors' offices and connection with the patient application.
Main page for FLH - https://systems-fl.ingello.com/ua
Proposals concealed
Current freelance projects in the category Python
Aspect
Development of a Telegram Mini App (Bot + WebApp) for selling digital goods and in-game currencies (Python / aiogram) Project description: A Telegram bot with a full WebApp interface is required for the automated sale of digital goods (Telegram Stars, Telegram Premium, in-game currencies/donations for PUBG Mobile, Steam, etc.). The project is called Aspect App. The main focus is on speed, smooth UI/UX in a Web3/minimalist style, and complete automation of product delivery after payment. Technology stack: Backend: Python 3.10+, aiogram 3.x (FastAPI for Webhook/API is welcome). Database: PostgreSQL / Redis (for sessions and caching). Frontend (WebApp): React.js / Vue.js / Next.js (at the developer's discretion, speed and smoothness of animations are important). Integrations: Telegram WebApp API. Main functionality (MVP): 1. Client side (Telegram Mini App): Main screen: Product categories (Telegram Assets, In-game Donations). Banner grid for promotions. Product catalog: Product cards with volume selection (e.g., 50, 100, 500 Telegram Stars or UC). Fields for entering player data (Player ID for PUBG). Cart and Checkout: Quick purchase in 2 clicks. Payment module: Integration of payment methods (CryptoBot API / TON Connect / other fiat gateways by agreement). Personal account: Order history, status tracking, referral system (balance within the app). 2. Admin panel (built into WebApp or separate bot): Catalog management (adding/removing products, changing prices). Order monitoring and sales statistics. User database mailing system. 3. Automation logic (A plus): Readiness of the architecture for integration with supplier APIs (API for auto-purchasing Stars/UC). At the MVP stage, some products may be issued with codes from the database. What is required from the contractor: 1. Development of the database and backend architecture in Python. 2. Layout and integration of WebApp (design mockup to be discussed, clean Web3 style, Glassmorphism is important). 3. Setting up secure transactions and payment webhooks. 4. Deployment on the server (Docker, Ubuntu, SSL setup). Candidate requirements: Experience in commercial development of Telegram WebApps for at least 1 year. Portfolio with launched and working Mini Apps (please provide links in your response). Clean, documented code. Working conditions: Work only through the Secure Deal (Safe / Escrow) of the platform. Payment is staged (the project is divided into Sprint 1: Backend + DB, Sprint 2: Frontend WebApp, Sprint 3: Payment integration and testing). Budget: To be discussed with the successful candidate (please indicate your price range and timelines in your response)
Technical task for a Telegram bot / mini-platform 1. Project goal Create a Telegram bot and mini-platform for finding specialists and posting requests from users. The user can leave a request, the specialist can respond, the administrator controls publications, moderation, payment, and security. 2. User roles User: can register; confirm phone number and email; create a request; view specialists; receive responses. Specialist: can register; fill out a questionnaire; specify services, prices, city, experience; add photos of completed work; respond to requests. Administrator: can moderate requests; verify specialists; review complaints; manage advertising; control payments; block users. 3. Registration Mandatory: confirmation of phone number via Telegram or code; confirmation of email via link or code; without confirmation of phone and email, the request is not published. 4. Requests The user fills out: service category; task description; city/region; deadline; budget; photo (if necessary); contact details. Limitations: no more than three requests per day from one user. 5. Moderation All requests initially go for moderation. Automatically block or send for manual review: photos of category 18+; spam; offensive statements; suspicious links; duplicate requests; mass requests from one account. 6. Specialists Specialist questionnaire: name; city; services; experience; prices; portfolio; photo; description; link; reviews; verification status. Important: the platform is not responsible for the quality of the specialist's services. This must be stated in the user agreement. 7. Payment Monetization options: paid placement of the specialist's profile; paid boosting of the profile; paid access to requests; advertising after approval by the administrator; subscription for specialists. Integrate payment: Stripe / Przelewy24 / PayU / Fondy — as per the developer's capabilities. 8. Administrative panel It is necessary to create a convenient admin panel: list of users; list of specialists; requests under moderation; complaints; payments; statistics; blocking users; editing categories; managing advertising; manual approval or rejection of publications. 9. Security Mandatory: protection against spam; request limit; message limit; protection against mass registrations; action logging; database backup; file and photo verification; CAPTCHA or other spam protection mechanism; blocking by phone number, IP address, or Telegram ID. 10. Responsibility The user agreement must specify: the platform is not an employer; the platform is not responsible for the actions of specialists; the user independently makes decisions about cooperation; the administration has the right to delete a request or profile without explanation; advertising is published only after approval by the administrator; spam, fraud, 18+ content, and any manifestations of aggression are prohibited.
Need a DevOps / Linux administrator for deploying a Telegram bot on a VPS. Specifically, server setup and production deployment are required. Project stack: Node.js 20+, Telegraf, Express, Prisma, PostgreSQL, Redis, Docker, Docker Compose, Telegram Mini Apps, OCR. What needs to be done: 1. Prepare Ubuntu VPS. 2. Set up SSH access with keys. 3. Configure the firewall. 4. Install Docker and Docker Compose. 5. Set up PostgreSQL. 6. Set up Redis. 7. Configure Nginx. 8. Connect the domain and SSL Let’s Encrypt. 9. Configure production .env. 10. Run Prisma migrations. 11. Launch the Node.js application. 12. Set up Telegram webhook. 13. Check /health and /ready. 14. Set up PostgreSQL backup. 15. Leave instructions on how to update, restart, view logs, and restore backup. Important: - No need to rewrite the code. - The project needs to be deployed on a VPS. - A person with experience in Docker + Node.js + PostgreSQL + Redis + Nginx is required. - It is preferable to show 2–3 similar projects.
I need a program or Telegram bot for bulk creation of shipping documents through the Nova Poshta API.Main Task I upload 50–100 orders at a time into an Excel/Google Sheets/CSV table or paste a list of orders into the program. Clients provide data in different formats, so the system must automatically recognize the data, sort it into the necessary fields, and create shipping documents through the Nova Poshta API.Input Requirements Possible options: Upload an Excel/CSV file. Copy a list of orders into the program. Paste client messages in free format.What the Program Must Recognize From each order, it is necessary to determine: Recipient's full name; Phone number; City; Nova Poshta branch; Product/comment; Cash on delivery amount; Weight/dimensions, if specified.Operational Logic I upload 50–100 orders. The program processes each order. Data is automatically distributed into columns. The program checks the city and branch through the Nova Poshta API. If there is an error or missing data for an order, it highlights that order and indicates what needs to be corrected. If everything is correct, it creates the shipping document. After creation, it shows a list of completed shipping documents. It allows exporting the result to Excel.Output After Processing For each order, it is necessary to obtain: Shipping document number; Client's full name; Phone; City; Branch; Cash on delivery amount; Delivery cost; Status: created / error / needs verification.Mandatory Functions Bulk creation of 50–100 shipping documents at once; Verification of city and Nova Poshta branch; Ability to edit an order before creating the shipping document; Saving sender data; Working with cash on delivery; Exporting created shipping documents to Excel; Log of created shipments.Desirable Telegram bot or simple program for Windows; Excel/CSV upload; Ability to paste a list of orders as text; Saving a database of regular clients; Reordering with one click; Product and weight templates; Printing/downloading labels for packages.Important I need not just a form for manual filling, but a tool for bulk processing of orders. Main scenario: I upload 50–100 data entries, the program sorts the information itself, checks for errors, and bulk generates shipping documents through the Nova Poshta API.
Project: YOKA ASSIST — intelligent diagnostic and training system for mining equipment Project Description It is required to develop the YOKA ASSIST intelligent system based on a Telegram bot using artificial intelligence. The main task of the project is to create a digital assistant for electricians, mechanics, operators, and engineering and technical personnel, which will assist in diagnosing faults, training employees, and storing a technical knowledge base. The first stage of the project is focused on mining equipment (EKG excavators, SBSh drilling rigs, and other equipment), but the architecture should be universal and easily scalable. Main Functionality Telegram Bot - Modern interface. - Menu with buttons. - User authorization. - Access rights separation (user, administrator, chief administrator). Artificial Intelligence Knowledge Base A knowledge storage system needs to be created. Support: - PDF; - Word; - Excel; - photographs; - diagrams; - videos; - instructions; - equipment passports; - technical documents. After information is added by the administrator, the AI should use it in responses without changing the program code. Equipment Diagnostics Search support: - by error code; - by protection name; - by cabinet; - by unit; - by equipment; - by symptoms. For each fault, it is desirable to provide: - description; - possible causes; - sequence of checks; - photographs; - diagrams; - video materials; - links to related documents. Dynamic Buttons Buttons should be generated automatically depending on the situation. For example: - Check cabinet. - View diagram. - View video. - Next stage of diagnostics. - Go back. Administrative Panel The chief administrator should be able to: - add equipment; - create new errors; - add documents; - upload photographs; - upload videos; - edit the knowledge base; - manage users; - assign administrators of individual departments. QR System Each cabinet, unit, or equipment can have its own QR code. After scanning, the user immediately enters the corresponding section of the Telegram bot. Repair Log A log of completed work needs to be implemented. Functions: - who performed the repair; - date and time; - equipment; - description of completed work; - materials used; - comments; - repair history. Analytics It is desirable to implement: - most common faults; - repair statistics; - time to resolve faults; - reports on equipment; - reports on employees. Scalability The architecture should allow for adding new types of equipment, new enterprises, new departments, and new knowledge bases without rewriting the project. Technologies Desirable: - Python; - Telegram Bot API; - PostgreSQL or SQLite (SQLite is allowed in the first stage); - integration with AI via API; - modular architecture; - possibility of further connecting a web panel. What is expected from the contractor - Development of a fully functional project. - Clean and understandable code. - Documented project structure. - Possibility of further development without complete redesign. - Assistance with initial deployment and setup of the project. The project is long-term. After successful completion of the first stage, further improvements and development of the system are possible.