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 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
Current freelance projects in the category Python
-
Not specified
Refinement of the Python program for the new Twitter (X) chat interface.
Desktop Apps 49 proposals 31 July
-
67 USD
Signal bot for trading
Bot Development 54 proposals 31 July
-
Not specified
Website parsing, bypassing Akamai protection
Data Parsing 39 proposals 30 July
-
446 USD
Development of an AI bot for receiving and processing orders from restaurants in Telegram with integration into 1C.
72 proposals 29 July
-
Not specified
Need to fix a bug in the current version of the bot.
Bot Development 87 proposals 27 July