Take a look at our completed projects

Project description

DocPlanner is a worldwide healthcare solution that can be tailored to the specific needs of each country. Special plug-ins connect the platform to national healthcare systems. NubiSoft designs, builds, and launches these plug-ins to fit local requirements.

NubiSoft has created many plug-ins for DocPlanner's digital health services. Our most important eServices include e-prescriptions, electronic health records (EHR), e-sick leaves, e-referrals.

During development, we dealt with the following topics and used the following technologies:

• Frontend development (Vue.js)
• Backend development (Java + Spring Boot)
• Relational databases (PostgreSQL)
• Implementation of medical standards (HL7 CDA, FHIR)
• Responsive web design
• High availability
• API integrations with national healthcare platforms
• Microservice architectures
• Containerization (Docker)
• Management of container applications (Kubernetes)
• Automated CI/CD pipelines

Achieved goals

Our partnership began with developing an e-referral plugin, allowing doctors to store and upload certificates.

After that, we added e-referral issuing capabilities.

Docplanner initially used a third-party solution for e-prescribing. Due to our successful work on e-referrals, we were then asked to integrate e-prescribing and medical event reporting.

The positive experience led to two more projects: integrating with the ZUS system for e-sick leaves and verifying patient insurance in NFZ systems.

Challenges

Docplanner, initially a rating site for doctors, grew into a tool to help doctors find patients and manage staff. This required integrating with national health systems. They needed a partner to create plugins for their electronic health records (EHR) to work with Poland's e-health systems, specifically P1 for reporting medical events and NFZ for checking insurance.

Project description

A white-label AI assistant that integrates seamlessly with healthcare providers' systems. It enables doctors to check personalized drug-patient interactions with just one click and thus avoid medication errors. At the same time, the assistant significantly reduces the time doctors have to spend analyzing drug interactions.

During development, we dealt with the following topics and technologies:

• Frontend development (Vue.js)
• Backend development (Python)
• Database (PostgreSQL, ChromaDB)
• Large Language Model (LLM)
• Retrieval Augmented Generation (RAG)
• Interface to pharmaceutical databases
• Connections to the systems of healthcare providers (PVS)

Achieved goals

The tool created significantly reduces the time it takes to make a medical recommendation, making the whole process faster, easier and safer for both doctors and patients.

Challenges

Creating a reliable AI-drug interaction assistant isn't a piece of cake:

• Data - Ensuring accuracy, integrating diverse sources, and handling incomplete patient records.
• Technical - Utilizing advanced natural language processing, achieving system compatibility, and ensuring scalability for large data volumes.
• Medical Knowledge - Accounting for complex drug interactions and staying current with evolving medical information.

These challenges underscore the need for a robust approach that addresses data, technical, and medical complexities to deliver accurate and reliable drug interaction information.

Project description

TIM, a messenger client specially developed for medical personnel, enables individual and group chats on both smartphones and computers. TIM transmits messages and files securely and confidentially in real-time. The aim of developing TIM was to meet all the requirements of the Gematik specification to enable product approval.

The TI-Messenger is based on the Matrix protocol, an open standard for secure and decentralized communication.

During development, we dealt with the following topics and used the following technologies:

• Frontend development (React.js)
• Backend development (Java, Synapse / Matrix)
• Database (PostgreSQL)
• High availability
• Web and mobile client (PWA)
• End-to-end encryption
• Integration with the central systems of healthcare providers

Achieved goals

At this point, our Web/PWA client for TIM is developed.

We offer it in a white-label model, ensuring flexibility and seamless customization to match your brand’s look and feel.

Challenges

We overcame key challenges in creating a secure communication platform for healthcare professionals. These included implementing robust end-to-end encryption, ensuring seamless integration with various healthcare systems, designing an intuitive user interface, ensuring scalability for real-time communications, and obtaining necessary certifications.

Project description

The web-based hospital pharmacy for German hospitals supports medical professionals in ordering medicines and issuing e-prescriptions. This application integrates with pharmaceutical suppliers via external APIs using the MSV3 protocol. The creation and digital signing of e-prescriptions is made possible by the connection to the German Telematics Infrastructure.

From information on ingredients and storage to specialist and usage information, users are spared time-consuming searches. The development was designed to meet all the requirements for certification by the National Association of Statutory Health Insurance (KBV).

During development, we dealt with the following topics and technologies:

• Frontend development (Angular)
• Backend development (Java, Spring Boot)
• Relational database (PostgreSQL)
• TI connector API integration
• MSV3 API integration
• Reading and management of SMC-B and HBA cards
• Connection to the ABDA medication database
• Full-text search functions (Apache Lucene)

Achieved goals

In developing our pharmacy app for Germany, we successfully achieved KBV certification, ensuring compliance with national healthcare standards. We implemented secure e-prescription management, enabling the creation, signing, and transmission of e-prescriptions through integration with the German Telematics Infrastructure.

Additionally, we streamlined the medication ordering process with an intuitive user interface, saving valuable time for medical professionals. We also integrated a comprehensive full-text search feature using Apache Lucene, providing easy access to detailed drug information.

Furthermore, we integrated with third-party pharmaceutical suppliers via the MSV3 protocol and connected to the ABDA medication database, enhancing the app's functionality and utility for German pharmacies.

Challenges

In developing our pharmacy app for Germany, we successfully faced significant challenges in security and compliance, ensuring full adherence to KBV certification and GDPR while safeguarding sensitive medical data.

Project description

The whole world is transforming toward 'online'. Depending on the area and geographical region, these transformations are progressing faster or slower. Currently, a lot is being done in Poland regarding the digitization of individual areas of state administration. For example, healthcare legislation has recently been improved, which now allows drug prescriptions and sick leave to be issued online instead of formerly required paper forms.

This opens up completely new possibilities for improving the effectiveness of treatment processes. However, the software of many providers of this type of solutions on the healthcare market is often implemented in the architecture of fat clients, which prevents the use of these new opportunities, for example in the case of services provided in the patient's place of residence (so-called home visits). Therefore, having previous experience in the healthcare industry, we decided to build an online platform for issuing sick leave using a light web application running on laptops, tablets and mobile phones.

To optimize the issue of sick leave we designed a responsive, intuitive user interface and minimized the number of user-system interactions necessary to achieve the user's goals and applied several improvements like intelligent suggesting of previously entered data or advance validation of processed information.

To ensure the required level of security, we implemented user authentication and digital signing of sick leaves using personal medical certificates issued by Social Insurance Institution. To further security increase, we integrated the system with cloud storage services: DropBox, Google Drive and OneDrive where doctors can store certificates in their private accounts.

Currently, a doctor, free of charge, being equipped only with a mobile phone, using our solution can safely, conveniently and effectively issue a sick leave. We also offer a paid premium version dedicated to doctors who issue many sick leaves. The purchase of a premium license is fully automated using online payment and invoicing.

We are glad that we can contribute to improving the effectiveness of treatment processes in Poland, and the constantly growing list of satisfied doctors using our solution gives us additional satisfaction.

During the development of the ezlapka.pl platform, we addressed the following issues and used the following technologies:

• responsive web design,
• high availability,
• containerization,
• relational database (PostgreSQL),
• Java + Spring,
• vue.js,
• domain APIs integration: Social Insurance Institution.
• infrastructure API integration: DropBox, Google Drive, OneDrive, online payment.

Achieved goals

We successfully streamlined the issuance process, enabling electronic sick leave generation and eliminating manual paperwork. We prioritized security by implementing user authentication, digital signing, and secure cloud storage for medical certificates.

Additionally, we enhanced the user experience through an intuitive interface with intelligent data suggestions and validation.

We also implemented a successful premium subscription model with automated payment and invoicing. Our platform has positively impacted healthcare efficiency in Poland, as evidenced by the growing number of doctors utilizing our solution.

Challenges

We faced several key challenges. Ensuring robust security and compliance with Polish healthcare regulations and GDPR while safeguarding sensitive medical data was paramount.

We also tackled the complexity of integrating with diverse systems, including the Social Insurance Institution's APIs and cloud storage providers. Additionally, we focused on optimizing the user experience by designing an intuitive and responsive interface for seamless use across various devices.

Ensuring high availability and scalability to accommodate a large user base and maintain optimal performance were also crucial considerations.

Project description

Campstar is a startup founded by three wonderful gentlemen from Germany (more specifically from Hamburg). With the aspirations to enter the global camping services market, they set a very high bar - the creation of a worldwide platform for booking campsites, motorhomes, and the sale of camping equipment.

During the development of the campstar.com platform, we addressed the following issues and used the following technologies:

• high availability,
• containerization,
• relational database (PostgreSQL),
• full-text search engine (Luciene),
• GIS searching (PostGIS),
• Java + Spring,
• React.js,
• Express.js,
• domain APIs integration: ctoutvert,
• infrastructure API integration.

Achieved goals

First, we migrated the existing solution from the Azure test account to the AWS cloud, because as a startup they got a lot of credit from Amazon Web Services.

Then, we provided a full-stack team (from design activities to the database development and DevOpsing), that using the SCRUM approach, built the entire platform with them.

Challenges

They needed a partner to help finish their initial product and add features for renting campers. The main challenges were a tight deadline, ensuring the solution worked well, and dealing with different booking and rental rules in various countries, especially for payments and descriptions.

Project description

There is probably no one who would not have heard of companies providing taxi applications such as Uber, Bolt or FreeNow. In many countries, taxi drivers who want to use these applications must work in conjunction with their fleet partners. This is due to national laws. Countries adapt their laws so that such taxi services are carried out while respecting the interests of passengers. The providers of these taxi applications supply fleet partners with only minimal information about trips made by their drivers, but in various heterogeneous formats. In addition, partners for drivers provide their additional services for a fee - fuel cards, vehicle servicing, rental of cash registers and much more. All this makes settling a given driver very tedious and laborious.

That is why the CABIO platform was created!

Thanks to the integration with data sources such as information about trips from individual taxi applications (Uber, Uber Eats, Bolt, FreeNow, Glovo) or fuel card issuers (Orlen, Flotex, Circle K), the CABIO platform gives fleet partners the option of easy management and settlement with drivers. What's more and more important - fleet partners using the CABIO platform are no longer tied to a specific provider of taxi applications.

Regardless of whether the supplier of such an application will change the data access interface or in the future a new taxi application will be created on the market - the fleet partner using CABIO does not have to worry about it - it will be completely transparent for him.

Achieved goals

The CABIO platform was created, a web-based service that helps billing partners and fleet partners manage relationships (including billing) with cooperating drivers of taxi and delivery apps such as Uber, Bolt, FreeNow, Glovo and Wolt.

Challenges

• National laws - Taxi drivers using apps often need to work with fleet partners due to local regulations.
• Data limitations - App providers give fleet partners minimal trip data, and in different formats.
• Partner fees - Fleet partners charge drivers for additional services like fuel cards and vehicle maintenance.
• Tedious settlements - Calculating driver earnings is complex and time-consuming due to the involvement of multiple parties and varied data.