<img alt="" src="https://secure.perk0mean.com/184386.png" style="display:none;">

GxP Compliance in
Monitoring Solutions

The ELPRO Cloud is an intuitive and efficient reporting tool that visualizes the activities of your sensors and provides you with everything you need to set up a professional GxP-compliant
temperature monitoring solution.

Learn more

GxP Compliance in
Monitoring Solutions

The ELPRO Cloud is an intuitive and efficient reporting tool that visualizes the activities of your sensors and provides you with everything you need to set up a professional GxP-compliant
temperature monitoring solution.


How is GxP Compliance in Monitoring Solutions defined?


FDA Title 21 CFR Part 11 and how it applies to a monitoring solution


GxP Compliance in User Management & Authentification


What is an audit trail?


How to deal with Temperature Excursions?


Why is a Dashboard important?


Why is a periodic reporting important?


How is data archived?

Download PDF Summary

The Regulatory Environment of Pharma Companies: 
GMP & GDP Guidelines

Companies that research, produce, store, transport or sell pharmaceutical products are subject to regulatory requirements. The most common known practices are:

  • Good Manufacturing Practices (GMP): GMP are the practices required in order to conform to the guidelines recommended by agencies that control the authorization and licensing of the manufacture and sale of food and beverages, cosmetics, pharmaceutical products, dietary supplements, and medical devices. These guidelines provide minimum requirements that a manufacturer must meet to ensure that their products are consistently high in quality, from batch to batch, for their intended use.
  • Good Distribution Practices (GDP): Good distribution practice (GDP) describes the minimum standards that a wholesale distributor must meet to ensure that the quality and integrity of medicines is maintained throughout the supply chain.

The laws and regulations are specific to each country and typically include a national or international authority like the FDA (Food and Drug Administration) in the United States); EU (European Union) in Europe; or Swissmedic (in Switzerland), all coordinated by the ICH (International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use).

In addition to official regulations, there are a number of important associations issuing guidance documents supporting and detailing the regulations and their application in specific situations. Some of the most influential organizations relevant to the pharmaceutical supply chain industry are the ISPE (International Society for Pharmaceutical Engineering), the USP (United States Pharmacopeia), the PDA (Parental Drug Association) and the WHO (World Health Organization). The regulatory framework is therefore a living organism which changes almost daily with new laws becoming effective and new guidance documents being published.

GMP vs. GDP – what are the differences?

From a drug supply chain perspective, the cornerstones of the regulatory framework are the Good Manufacturing Practice system (GMP) and the Good Distribution Practice system (GDP). These are often referred to jointly as GxP. While GMP lays its focus on activities around manufacturing (including testing, release & storage), GDP focuses on the distribution including transportation, storage and wholesale of pharmaceuticals products. Both, GMP and GDP aim to increase public health by ensuring the product quality. 

In a nutshell

If you store or transport pharmaceutical products you have to comply to GMP and GDP guidelines. Thus, you must ensure that:


Qualification & Mapping

All you need to know about qualification, validation & mapping

Temperature Calibration

All you need to know about the calibration of temperature sensors

Temperature Monitoring

All you need to know about Temperature Monitoring of Pharmaceuticals

What is Title 21 CFR Part 11?

If a company transports pharmaceutical products and wants to comply to GDP guidelines it must store and transport the products in qualified facilities, transport containers and networks. The temperature sensors must be calibrated and the product release must take place in a qualified and complaint system. What does compliance in combination with a temperature monitoring solution mean? In this chapter, we will explain compliance from a Cold Chain perspective.

“Title 21 CFR Part 11” is the part of the Title 21 of the Code of Federal Regulations written by the United States Food and Drug Administration (FDA). Title 21 contains regulations on electronic records and electronic signatures. Part 11 defines the criteria by which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records to ensure GxP compliance.

A monitoring solution which stores electronic records which are critical to patient safety must be in compliance to Title 21 CFR Part 11. In order to do so it is important to understand the main risks. 

How Does Title 21 CFR Part 11 Apply
to a Cold Chain Monitoring Solution?

Electronic data could be deleted, accidentally modified or intentionally modified. Title 21 CFR Part 11 defines criteria by which electronic data is trustworthy, reliable and equivalent to paper records and handwritten signatures executed on paper. If you follow those rules your electronic records will be complete, intact, maintained in the original context, and geared towards compliance. In the context of a Cold Chain monitoring solution this means the following:

Complete Data Monitoring temperature with the help of sensors, a communication bridge and the software solution, one of the main challenges is the completeness of data. Mechanisms need to be in place to ensure compliance so that no data is lost on the way from the wireless sensors through the communication bridge to the monitoring software. Therefore, in case of a disconnection between the sensors and the radio bridge or the cloud storage, data must be buffered in the sensors until the cloud confirms that the connection has been re-established and the data has arrived. 

When monitoring data in a Cold Chain environment the completeness of the data is THE main concern and cause for problems. Therefore, the Cold Chain database should include mechanisms to mitigate the following risks:

  • Somebody has forgotten to equip the pallet with a sensor
  • The sensor was started early or stopped late
  • The raw data file from the USB data logger was not uploaded
  • The real-time logger lost connection and data never arrived

Intact Data Although the risk for accidental or intentional modification is minimal, the integrity of data in a measurement chain can only be achieved by encrypting the data all the way from the measuring wireless sensor through the communication bridge (LPWAN network or email) to the cloud. Once the data has arrived in the software it is important that no raw data can be deleted or modified. No user should not be able to change the raw data, however it is possible to add certain types of additional information. For example, in order to add an interpretation of the data, certain comments or acknowledgements about the raw data can be added to the system. Furthermore, in order to create selective views on the raw data, reports can be created and exported.

Maintaining Electronic Data in its Original Context – Keeping the data in one single source on a central cloud infrastructure ensures that it is kept in its original recorded context and the risk of misinterpretation is therefore eliminated. Warnings, alarms, and reports should always refer to the unique sensor name, event number, and time stamp.

Checklist cloud-based Temperature Monitoring

Download a summary on everything you need to know about storing temperature data in the Cloud.


Executive Summary Temperature Monitoring

Download a summary on everything you need to know about temperature monitoring.


The Audit Trail: 
Compliance in User Management and Authentification

There are many rules to follow when it comes to compliance in user management. Every user with access to the solution must be identified by a unique username and password and must have a clear role and rights. Additionally, every action taken by the user in the system must be identified and tracked. When conducting critical operations, such as the acknowledgement of an alarm, the user even needs to confirm his action by inserting his password a second time. In order to avoid unauthorized access it is important to implement a time-out mechanism in case the user is not taking action for a longer time period.

The result tracking functionalities mentioned above is a complete audit trail aligned with compliance. It answers the questions: who has done what and why? Technically, the audit trail keeps track of every single automated event the system is generating and every single manual task a user is performing. So, regardless from which perspective one takes a look into the system, a full audit trail could be:

  • Sensors: Timeline of all events on a sensor like measurement values, status, setting changes, warnings, alarms, and acknowledgments
  • Warnings and alarms: Time stamps, statistics, who has commented on what, who has acknowledged something, and when
  • Reports: Sensor names, timeline, and the user that created the report

In a Cold Chain database the question of audit trail is much more complex than for a solution monitoring rooms and equipment. Why? Because there are many more participants included.

Automated Events in the Audit Trail

A temperature monitoring system typically executes the following different automated mechanisms and workflows:

  • monitoring the system availability and performance (to trigger a system warning)
  • monitoring the sensors (battery status, wireless connection, validity of the delivered data to trigger sensor warning)
  • measuring, storing and evaluating temperature values, and matching them with the defined limits to trigger high/low temperature warnings and alarms (For further information see the section below on "How to Deal with Temperature Excursions")
  • monitoring all settings and setting changes

Manual Tasks in the Audit Trail

In addition to automated events, the system must keep track of every single manual task a user performs including the time stamps of each task. The following manual events could be tracked:

  • Who is logged into the system and what are the roles and rights of this individual?
  • Who has logged in/out, and at which times?
  • Who has changed settings and what were the settings like before and after the change?
  • Who has commented or acknowledged a warning or an alarm?
  • Who has generated a report?

What to Ensure in An Audit Trail
When Monitoring Products in Transit?

In a Cold Chain database, the question of an audit trail is much more complex than for a solution monitoring rooms and equipment. Why? Because there are many more participants included:

  • Who owns the system: Product owner, e.g. Market Authorization Holder (MAH) is responsible for the system
  • Who configures the individual sensor: Many different warehouse employees at different sending sites.
  • Who views and comments on temperature deviations: Many different parties can be involved including the warehouse recipient, warehouse sender, logistics service providers, quality assurance recipient, and quality management sender.

The Cold Chain database must keep an audit trail aligned with compliance and verify who has done what, and why? Yet even more important is to limit the user rights, preventing any intended or unintended changes which are not absolutely necessary to perform the specific process in the given situation. A full Cold Chain audit trail could be:

  • Acceptance Criteria (stability budget): What set of stability budget is used, who has released this set, and when?
  • Configuration of Shipment and Data Logger: Which system (or person) has configured the specific shipment and defined the chosen configuration and link to the stability budget?
  • Temperature Data: Measurement values, status, setting changes
  • Warnings and Alarms: Who has been informed of a warning or alarm, and by when?
  • Comments, Reassessments and Releases: Who has commented on a shipment, performed a manual or automated re-assessment, and finally released the product?
  • Reports: Sensor ID, shipment information, and the user that created the report

IATA, TCR and the 
CEIV Pharma Program

The International Air Transport Association (IATA) has recognized that the pharmaceutical industry tries to avoid air transportation whenever possible. “A majority of all temperature excursions that occur happen while the package is in the hands of airlines, airports and their contractors.” More than 15 years ago, IATA initiated the Time and Temperature Working Group (TTWG) that developed the Temperature Control Regulations (TCR), a guide designed to enable stakeholders involved in the transport and handling of temperature sensitive products to meet the requirements of the pharmaceutical industry. This guide raised the awareness of these issues within the entire logistics industry. The group also introduced the “Time & Temperature Sensitive” label, which still today remains a well-known standard.

However, IATA has recognized that a label was not enough and created the Center of Excellence for Independent Validators in Pharmaceutical Logistics (CEIV Pharma). The CEIV Pharma certification program aims to support the air cargo supply chain in achieving pharmaceutical handling excellence and increase safety, security, compliance and efficiency by the creation of this globally consistent and recognized pharmaceutical product handling certification. Airports, trade lanes, service providers, and entire networks can now be certified by training personnel, improving equipment, and introducing checklists and processes.

How to Qualify a Data Logger and Database

GMP and GDP clearly require qualifying all equipment used to produce, store, and transport temperature sensitive pharmaceuticals. This obviously includes data loggers. As a pharmaceutical company using a data logger and/or a cold chain database, you need to proof that it fulfills the intended purpose.

Qualification is the documented proof by the Market Authorization Holder (MAH), that the Cold Chain monitoring solution fulfills its intended purpose: documenting a release decision.

The company using the Cold Chain monitoring solution must perform the qualification job itself and individually on the specific process. The qualification documentation of the Cold Chain monitoring company is a popular target during FDA audits. Qualification of a Cold Chain monitoring solution in a specific situation can be kept simple, if the supplier qualifies all elements of the solution (i.e. hardware, software, services) beforehand, and provides profound documentation to support it. Although qualification is the better term, this activity is often called “component validation.”

Each component used in a Cold Chain monitoring solution must be validated/qualified by the supplier. They must provide documented proof that each component fulfills its intended purpose. 

Comprehensive qualification support packages provided by data logger vendors include:

  1. URS template describing all functionalities
  2. High level risk analysis rating the risk (probability, severity and detectability) and mitigation measures
  3. Validation plan and validation report summarizing referring versions and documents
  4. Qualification template for an OQ

The supplier typically provides guidance during the qualification and is open for audits. During audits, the detailed V-Model documents can be inspected.


How to deal with Temperature Excursions?

GMP and GDP standards define that pharmaceutical products must be stored and transported according to the required temperature conditions mentioned on the drug label to ensure compliance. Every excursion from these temperature conditions must be documented. The monitoring system should support the user in creating automated excursion reports to which the user can still add certain information. The following procedure gives an example on which questions a Quality Manager should ask, once a temperature excursion has occurred. 

Excursion Report

A temperature excursion triggers an alarm. The alarm can be seen on the sensor itself or the dashboard display and can be sent out via email or SMS text containing an excursion report with the following information:

  • Where did the alarm go off? Which facility, container or sensor had an excursion?

  • When did the temperature excursion occur and when were the drug label conditions re-established?

  • How long has the product been exposed to temperatures outside the drug label conditions?

  • What was the highest/lowest temperature measured?

Manual Information to be Added by a User to the Temperature Monitoring System

  • Affected Product? Which product, batch or pallet has been potentially affected?
  • Risks? Is it likely that the core temperature of the product has been affected, thus damaging the product?

  • Severity? Is there sufficient stability budget left to justify a release of the product or is a product recall necessary?

  • Corrective actions needed? What is the cause of the temperature excursion and does it have to be corrected? Do people need to be informed about the findings?

  • Preventive Actions needed? In case of high-risk and/or repetitive errors, which preventive actions can be performed in order to avoid a repetition of the event? Are changes implemented?

The Dashboard

Why is a Dashboard Important?

A dashboard gives a brief overview on the current status of each sensor. The sensors can be grouped in a meaningful way or placed on top of a floor plan to illustrate their physical location. The dashboard should show the currently measured value, show the alarm status, and give further meaningful information on the technical status of the sensor. The benefits of a dashboard are:

  • Clear entry screen into the software and easy navigation from the dashboard
  • Quick overview screen for operators to see whether the production is running smoothly or not

Why is Periodic Reporting Important?

Besides a clear alarming mechanism, it is vital to have periodic reporting on all sensors on a system. Reports can serve different purposes and therefore, contain different content. If the report serves as an archive of data, it should be in compliance with the ISO standards for long-term archiving. If the report is sent to customers, it might be beneficial to combine various sensors together, providing a comprehensive overview of the customer's project. Examples of regular reports may include:

  • Monthly reports for each sensor (for archiving purposes)
  • Weekly reports of various sensors combined (for customer reports)
  • Daily reports for each sensor (for data exports to a batch system)

How is Data Archived?

Archiving is not clearly defined in GxP regulations and is left open to interpretation. Many people have the unrealistic idea that once data is archived, it should be available forever in the same way it was generated. Data archiving is the process of "moving data that is no longer actively used to a separate storage device for long-term retention. Archive data consists of older data that remains important to the organization or must be retained for future reference or regulatory compliance reasons.” As a result, "archive data" has a different form than "process data."

Process Data

Process data is “fresh data” which is used to execute business decisions (e.g. data of a product, mean kinetic temperature calculation of a stability study). The service provider must ensure that, for two years, process data is available electronically for visualizations (e.g. zoom, overlay); statistics (e.g. calculate MKT); reports (e.g. release decision); and exports of the data (e.g. to a higher batch management system). Furthermore, it must be possible to add comments related to the data in the system.

Archive Data

After the first two years, the data is typically not needed in business processes anymore and its location and form will be changed to archive data. The service provider must ensure that archive data is available for at least 10 years and fulfils the following requirements:

  • Naming conventions clearly labeled (e.g. "monthly report Sensor A")
  • Data must be stored as a record in a readable form. For example the "PDF/A" format, which follows the ISO 19005 standards for archived documents
  • Data must be stored in a secured data archive

Further topics to discover

Qualification and Mapping

If you work with pharmaceutical products and want to comply with GMP and GDP guidelines, you must know more about Qualification.


More about Qualification

Temperature Monitoring

Get more insights with our experts about temperature monitoring of pharmaceutical products.


More about Temperature Monitoring

Calibration of Equipment

Find out more about the process of a calibration and why it is even necessary to calibrate a sensor.


More about Calibration