Case Study: Radom Ambulance Station services

Implementation of 7 e-services provided by the RSPR for patients and external entities

Duration of the project: 8 months
Project end date: August 2018

Simple S.A.

Sector: medical systems

Location: Warsaw, Poland

Size: 200 employees


About the company

The company is publicly traded on the Warsaw Stock Exchange and is one of the most frequently chosen business partners when it comes to deploying ERP, HCM, CRM, BI, Workflow and medical (HIS) systems.

About the project

During our 8 month collaboration with Simple S.A. we were responsible for the implementation of e-services in the Radom Ambulance Station. Our job was to prepare an independent analysis of the client’s needs, prepare project documentation, develop the solution and deploy it, along with providing necessary training and facilitating the project acceptance procedure.

“The company’s incredible commitment

has allowed them to create

a nearly-perfect product”

– a satisfied client

Sławomir Góraj,

project manager for the RAS

What has been done for the client?

Reduction in the number of documents

Client satisfaction

Timely delivery

Number of meetings in the client’s office
-20% 95% 100% 12

The challenge

The Radom Ambulance Station services 24 towns using 41 ambulances and medical teams. Apart from medical interventions, the unit also provides medical coverage during mass events, medical transportation for newborns and hospital patients and provides medical documentation to authorized parties. Before the new solution was implemented, a large number of requests and a complex document workflow system, has caused delays, hindered communication with the requesting party and led to misunderstandings. The project had the goal of unifying the communications channels, enabling the monitoring of request status and streamlining the exchange of information.

The approach

Due to the nature of the project (a call for bids issued by a public institution)
it was necessary to combine the requirements specified in the Statement of Conditions with actual needs
and requirements determined through detailed analyses and talks with the client. We spent 12 days at meetings
in order to learn the needs of each group of users (the patients, the financial and statistical department, the nurses,
the paramedics and the managers). The result was an active prototype ( and each stage began only
after the previous one was accepted.

1. Analysis of client’s needs (4 weeks):

– appointing a leading person on the part of the client,

– meetings in the client’s offices to identify needs,

– defining the functional and non-functional requirements,

– active consulting with regards to functionality,

2. Preparing documentation (2 weeks):

– writing down requirements and creating an active prototype (,

– creating documentation in the form of a Word file.

3. Development (5 months):

– developing the solution and integrating it with external systems,

– iteratively adjusting the development direction according to the needs of the client.

4. Testing (4 weeks)

– testing on a pre-production environment,

– integration testing with external systems.

5. Deployment (2 weeks)

– personnel training with first-run assistance,

6. Post-deployment support

– solving reported problems (3rd line support).

7. Maintenance

– implementing changes according to client’s requests.

The solution

Right from the first meeting with the client, it was clear that the solution
was going to be a multi-platform system shared by over 50 employees working at the station,
as well as by 15 outside companies and the patients. The solution should be integrated with the Medinet Medicom medical system and the Simple’s XPRIMER document management platform (HRM, DOK) Our job was to:

– develop a web application for patients and partners,

– develop a web application for personnel,

– deploy 8 tablets for use by the paramedics

– deploy 4 interactive kiosks for use by the personnel,

– deploy 4 LCD displays over medical rooms.

After conducting a technical analysis, we decided to develop a solution based on a single shared service,

running on an independent IIS server. The entire solution has been based on the .NET framework which

was used to develop an application server, providing RestAPI endpoints, serving as a single point of communication

for all devices (web apps, tablets, interactive kiosks, LCD displays). Using an independent server reduced the potential

effects of a DDoS attack launched against the hospital’s infrastructure, while the SSL TSL 1.2 ensured communication

confidentiality. Physical servers were provided by our partner – Simple S.A. and configured based on Windows Server

and MSSQL 2017. Patients and external parties were provided with access to an e-service, available through a website

and accessed by logging into the user’s account or into their e-PUAP profile. Requests for transportation or providing documentation

are submitted into the integrated document management platform. Once the request is analyzed, the requesting party

receives return information along with any attachments. This information is made available through the e-service website.

For paramedics and doctors

The challenge was to make sure that there was a 100% guarantee that a paramedic will receive the request. The MioCARE L135 GPS-enabled medical tablet was chosen as the tool to be used on the job. Each request Is communicated by a sound and a graphical indication (in the app through an internet connection and via SMS) and the paramedic is required to confirm the received request; everything is overseen by a dispatcher, with access to the current status of the request.

Responsive image
Responsive image

At any moment, the paramedic can access the patient’s online data and the medical data is synchronized with the medical system’s database. He can also save the data to a PDF file, use printouts based on Reporting Services and print a card detailing performed medical procedures using a portable HP printer.

For the patients

The solution also included a multimedia kiosk equipped with a touchscreen.

After inputting his PESEL number, the patient is looked up in the external eWuś system operated by NFZ in order to verify his health insurance. Integration with a EBRA printer lets the patient print out his or her number in the waiting line. The solution is based on Windows 10 and is built into a tastefully designed and durable kiosk. The upcoming number in line is displayed on an LCD screen, hooked into a Raspberry PI Zero through HDMI.

Responsive image
Tools that we used in the project:


lobo solution

Rzeźnicza, 28-31, p. 3
50-130 Wrocław

NIP: 754-281-41-16
REGON: 160141920

opening hours

8.00 – 18.00

social media