Virtual Pharma company

Article Index


This component communicates with the external enterprise environment, if needed, using native language to communicate to devices such as printers, aggregation stations, bar code readers, etc.  

Due to the diversity of external enterprise systems, translation algorithms used to communicate to the production line are built as separate components. The component is integrated with the Serialization Orchestration component, as commands for data exchange are commonly executed from the process server.  

The component itself has internal inputs, listeners that are receiving messages through the integration layer or from the application itself, and communicates to external systems and devices. Those components it is integrated with include:

  • Electronic Product Code Information Services (EPCIS) 
    EPCIS is a GS1 standard that enables trading partners to share information about the physical movement and status of products as they travel throughout the supply chain – from business to business and ultimately to consumers. It helps to answer the “what, where, when and why” questions to meet consumer and regulatory demands for accurate and detailed product information. 
    The goal of EPCIS is to enable disparate applications to create and share visibility event data, both within and across enterprises. This sharing is aimed at enabling users to gain a shared view of physical or digital objects within a relevant business context. 

    The EPCIS component includes the following parts: 
     - Data Definition Layer that defines a standard model for visibility events.
     - A Service Layer that defines two standard interfaces:  
       - The EPCIS Capture Interface (events) by which EPCIS data may be delivered from a capturing application to an EPCIS repository or other system capable of receiving EPCIS data.
       - The EPCIS Query Interface by which EPCIS accesses applications and trading partners may obtain EPCIS data after capture, typically by interacting with an EPCIS Repository. 

The basic unit of data in EPCIS is a structure that describes the completion of one business step within an overall business process; this structure is called an EPCIS event. A collection of EPCIS events provides a detailed picture of a business process in terms of time and place. 

The information content of a single EPCIS event is organized into four dimensions:  

  • What  
    The identifiers of the object(s) or other entities that are the subject of the event 
  • When   
    The date and time when the event took place, and the local time zone in effect 
  • Where  
    The identifier of the location at which the event occurred, and identifier of the location where the object(s) are expected to be following the event 
  • Why   
    Information about the business context, including: an identifier that indicates the business step taking place (e.g., shipping, receiving, etc.), an identifier that indicates the business state of the object(s) following the event (e.g., active, recalled, damaged, etc.), identifiers of the shipping and receiving parties (if the event is part of a process of transfer between parties), links to relevant business transaction documents (e.g., a purchase order, an invoice, etc.), instance- or lot-level master data, and/or other information defined via user extensions. 
  • Who  
    Information about the user/device who performed the action. 

Serialization Orchestration 

This component is a standard, readymade component that is integrated into the CureSync. It uses Business Process Modeling Language (BPML) to create executive structures (BPEL – Business Process Execution Language) and support graphical interfaces to describe serialization processes at the customer site.  

This component handles serialization process and orchestrates functionalities, events, alarms and notifications. It covers the following high level functions: 

  • Long running stateful processes and short running stateless or stateful processes 
  • In memory process execution for short running processes 
  • Message and time triggered message handling 
  • Secure invocation of partners, processes securely 
  • Supports task, sub-process and call activity types 
  • Supports user, manual, receive, script, service and task types 
  • Define Workflows Interacting with People 
  • Supports Human  
  • Integration of people for performing tasks and receiving notifications 
  • Role based access control for activities 

Other CureSync Components 

Other CureSync components are used to support the main functions already described. Those components are: 

  • Authentication of the users, which enables CureSync to verify users’ access rights. This can use the internal credentials system, or external LDAP, e.g. Active Directory 
  • Authorization of the users is performed by assigning roles to the users, either internal (system users) or external (partners or IT systems accessing CureSync). Roles are created by assigning actions from a list of available actions. 
  • Alarms, Events, Notifications is a component that handles system behavior if something unexpected occurs. All system messages are treated as events, e.g. a print order concluding successfully, and are further processed using Serialization Orchestration, which assigns a priority, and responds in order of priority) 
  • Approval paths allows easy alignment of system configurations without unnecessary revalidations. This is used by business users to adapt, modify, add business settings, e.g. serial number generation templates or label type without it being necessary to revalidate. Once the first system is configured with the new requirements, the change is sent through the Quality system for approval, and once approval is obtained, the change will become active. 
  • Audit trail is a general component that logs all of the information about changes into the system. From a forensic perspective it is easy to get answers to Who, What, When, Where questions, and information about the previous status of certain entities are provided, so it is possible to track all the changes from the moment of entity creation 
  • Signature confirmation when needed, it is easy to configure a request to the user to re-enter their password for any of the actions in the system. 
  • Attributes, Enumerations and Vocabularies - In order to secure flexibility, configurable items are allowed to be modelled using vocabulary-attributes component. Those configurable items are:
    • Products 
    • Subjects 
    • Market templates 
    • Printable Labels (1D, 2D, NFC content) 
    • User profiles 
    • Devices 
    • Organizational units 

Vocabularies are sets of attributes. Vocabularies can be grouped into hierarchies. Attributes should have validation rules, where the following types of validations are available: 

  • Allowed characters – either numeric or alphanumeric 
  • Length 
  • Number, with verification on greater than, less than 
  • Date (from, to) 
  • List with predefined value 
  • Boolean 
  • Placeholder for another attribute from other vocabulary  
  • Enumerations, including custom defined enumerations 

Multilanguage – CureSync allows each user to select from a list of languages, and the administrator is allowed to translate or adapt the language list, based on the company’s needs.

Dashboards – The system supports several dashboards which allow users to easily navigate to the most critical tasks, and newest events. The following dashboards are supported: 

  • Print queues 
  • Approvals  
  • Alarms, events, notifications  
  • Work orders 
  • ePedigree field information  
  • EPCIS events 

ePedigree information – Allows supplementation of EPCIS subject information with further data, e.g. warehousing or transportation temperature, etc.  Enables the provision of proper information to end users, including patients or inspectors using mobile technology. 



  • CMO's

    Can you continue your work without serialization solution? Since majority of MAH companies are outsourcing manufacturing to CMO’s you are...

    Read More ...

  • Generic and Originator Pharma

    Can I have 5 different solutions for 5 different markets? Most commonly manufacturers are operating on international market and their...

    Read More ...

  • Marketing Authorization Holder

    What are MAH obligation in regards to Serialization? MAHs are, from perspective of regulatory bodies, only legally recognized entities...

    Read More ...

  • Serialization

    Serialization is applying a traceable serial number to a smallest selling item. A serial number must be assigned to each selling item as...

    Read More ...

  • Supply Chain

    Wholesalers in the whole world are obliged to adapt to different regulations and directives, for example EU FMD – Falsified medicines...

    Read More ...

Working hours

+385 1 6264 199

08:00 - 17:00


Dear visitors, register your email address to receive all important announcement and news from TradeTicity.

We are here

Tvrtka: TRADETICITY d.o.o. za usluge / Skraćena tvrtka: TRADETICITY d.o.o. / Sjedište: 10 000 Zagreb, Ulica grada Vukovara 284 / Sud: Trgovački sud u Zagrebu / MBS: 080725073 / OIB: 32457970413 / Temeljni kapital: 3.700.000,00 kuna, uplaćen u cijelosti / Predsjednik uprave: Lidija Pozaić Frketić / Nadzorni odbor: Miodrag Mirčetić / Osobe ovlaštene za zastupanje: Lidija Pozaić Frketić / Banka i broj žiro računa: PRIVREDNA BANKA ZAGREB d.d. Zagreb / IBAN: HR9323400091110426328SWIFT address: PBZG HR 2X / ZAGREBAČKA BANKA d.d. ZAGREB / IBAN: HR9123600001102551948 / SWIFT address: ZABAHR2X