Hogart ZSMOPL

Experience & References

One of the most experienced partner on the Polish market
More than 30 ZSMOPL implementations on Polish market
More than 26 years of experience
Over 20 corporate implementations
Extensive references among international corporations and local businesses
We specialize in providing enterprise software in a comprehensive service of accounting / finance by providing proven and effective solutions such as:
ERP System (Sun Systems)
IBM Cognos TM1 Planning and Budgeting
Tableau
Dedicated software made by Hogart Software House preparing our clients for changes in law ( e- invoicing, debt collection, Vat Checker, e- declarations).
We implement modern reporting tools, we create dashboards, deliver report packages etc. (working on Tableau and QlikView).
Experienced with working for Pharma market. In 26 year history we delivered our services with success for such a companies like i. a:

• Adamed
• Aflofarm
• Baxter
• Boiron
• Ewopharma AG
• Pfizer
• Pharma Select
• Servier
• Stada Poland

Hogart ZSMOPL Reporting System description

According to the amendment of the Pharmaceutical Law, enterprises dealing in medicinal products, foodstuffs and medical devices are to be obliged to send information on various logistic operations to the Integrated Monitoring System for Medicinal Products (ZSMOPL).
In response to the requirements of the Integrated Monitoring System for Medicinal Products (Zintegrowany System Monitorowania Obrotu Produktami Leczniczymi – ZSMOPL), we present our solution that will enable daily delivery of reports in the format provided by Authorities in the message specifications for software manufacturers.
The Hogart solution allows you to meet the requirements of the new regulations for the transmission of required data to ZSMOPL. Information such as inventory and inventory movements, planned deliveries and stock gaps. The process implemented in our system can be presented as follows:
Download data from system or source systems
Preparing messages to ZSMOPL as XML files
Upload XML files electronically as required by ZSMOPL – WebService integration with the Ministry of Health (SOAP)
Receiving and handling feedback messages (e.g. acknowledgment of receipt or error) from ZSMOPL
Logging confirmation from ZSMOPL system in log
In the event of an error, log in and send an email notification of an error to a defined email address

Hogart also supports communication with ZSMOPL even if there is no direct communication with ZSMOPL from the internal customer network. In this case the process is divided into two stages:

Stage I

• Download data from system or source systems
• Preparing messages to ZSMOPL as XML files
• Secure XML (encrypted) files for shipment outside the internal network of the client
• Send XML files outside the internal network via e-mail

Stage II

• Receiving XML files on a server outside the internal network of the client
• Send XML files as required by ZSMOPL from a server outside the internal network of the client
• Receiving and handling feedback messages (e.g. acknowledgment of receipt or error) from ZSMOPL
• Logging confirmation from ZSMOPL system in log
• In the event of an error, log in and send an email notification of an error to a defined email address

The Hogart solution can work on the MS Windows platform. For the communication with ZSMOPL module it can be both MS Windows and Linux.
As part of the implementation project, Hogart offers support in transaction analysis and an indication of the scope of customer customization to generate ZSMOPL data, in connection with the new requirements of pharmaceutical law. Client system customization can include the preparation of a solution in the client system of the change that will generate messages and send them automatically to the ZSMOPL.

Technical details

Hogart ZSMOPL Reporting System software is a complete solution for advanced processing of generation ZSMOPL format files (XML) along with the technical data validation to the XSD schemas. Hogart ZSMOPL Reporting System is also a repository of generated and submitted data together with the possibility of the recall, viewing, filtering and grouping.

Application features:

• Variety of possible data sources: SQL database, Oracle database, MsExcel files, CSV files,
• Flexible selection criteria to generate ZSMOPL XML file, depending on the ZSMOPL statements structure,
• Test and production run,
• Preview of output data in tabular form – searching, filtering and grouping,
• Archiving of output xml files,
• Sending xml files to ZSMOPL webservice.

Hogart ZSMOPL Reporting System architecture

Hogart ZSMOPL Reporting System application performance is based on two main processes:

1. A collection of batch processes implemented on the side of operating database tables (CACHE),
2. Management of batch processes, transferring data to the resulting ZSMOPL database tables and generating XML output files.

The purpose of the batch process is to prepare data collected from sources (eg. SQL/Oracle database, MsExcel files) into structured tables of operating CACHE database. The data are prepared basing on the set-up managed by Hogart ZSMOPL Reporting System.
The batch process is based on stored procedures or additional applications (eg. processing data from MsExcel files) called with the parameters stored in the current application set-up. Batch processes make entries in a dedicated run log table and processing errors table. It allows to keep track of the progress of all processes. As a result of batch processes entries are created in the operation CACHE tables and then output data are generated in Hogart ZSMOPL Reporting System.

Hogart ZSMOPL Reporting System

Standalone application written in C#, in Microsoft Visual Studio programming environment and compiled on target framework .NET 4.5. The database connection is realized by:

• .NET Framework Data Provider for Oracle
• .NET Framework Data Provider for MS SQL

Client Webservice

Tool to send xml files – communication with ZSMOPL webservice
Prepared in Java

Software requirements

Software / Hardware environment (physical or virtual machine)
Windows 2008 or higher
MS SQL 2008 R2 or higher
.NET 4.5
Java ( min. 1.8.0_121)
Min. 8 GB RAM
Min. 10 GB free space

Client workstations: Windows 7/8/10, .NET 4.5, minimum 4GB RAM

Active certificate and private key to sign ZSMOPL file – delivered to customer by CSIOZ (Center of Healthcare IT Systems).

Security

Access to JDE views (only data required for ZSMOPL reporting):
Read only permissions (dedicated user, schema)

Access to Hogart MS SQL database:
Dedicated SQL user with password (read and write permissions)

Access to Hogart ZSMOPL Reporting System:
only for authorized persons, after logging in with individual password.

Each user has its own assigned role depending on which has the access to the specific functionality.

Basic roles

Client webservice (transfer of xml files to ZSMOPL webservice):
Interface was prepared according to Ministry of Health specification:
SOAP protocol (https)
Implementation of electronic sign – dedicated certificate and private key (with pass) are generated by CSIOZ

Hogart ZSMOPL application

Running the application is preceded by an application login window. It is also possible to use the domain login mechanism.

Main application window.

The program allows you to work in the context of many entities reporting messages. One application can handle many companies.

Defining program users and roles they fulfill in the system. Possible sharing to selected users.

The program defines all three types of messages. You can specify their additional parameters such as frequency of execution (important for automation) or activity.

Versions of messages you to differentiate the process of downloading data for different entities. You can create any number of message versions based on predefined types.

The working versions area contains processes that still contain unverified data, immediately after downloading from data sources. If the data is correct, the user with the appropriate permissions can accept it.

The accepted data is transferred to the prepared data area. From here they can be sent directly to the gateway or dedicated process to the station from which this shipment will be made.

If sent to the data gateway is confirmed, the data package is transferred to the archive where it can be viewed.