InnerWeb
Skip to main content

Entry system next to GMP systems: recommendations for IT and validation

The IT department at a pharmaceutical plant already has validated quality systems and a working access control system. An independent entry and guest system is meant to supplement them, not replace them. Below are six recommendations on what to settle before go-live, so that functions are not duplicated and unnecessary integrations are not opened.

0
access control readers supplied by InnerWeb
Source: company fact: InnerWeb is a software producer
1
declaration row per person per day
Source: feature card: Health statement

Who these recommendations are for

For the IT manager, the person responsible for validating computerized systems, and the owner of the access control system. The recommendations do not decide for the plant whether a given system falls under validation: that is a quality decision based on a risk analysis. They do show which questions IT should ask before the entry system starts working alongside the existing ones.

Recommendation 1: decide who is the source of truth for what

Start with a responsibility table. The access control system is the source of truth for a card tap at the reader. InnerWeb is an independent supplementary system: it links the tap event with qualifications, permits, visits, the declaration and attendance. The quality system remains the owner of documentation, procedures and decisions. Each function has one owner, and a dispute about who is 'right' is settled by an entry in this table, not by a discussion on the day of a failure.

Example split of responsibility in the IT table

Example split of responsibility in the IT tableBar chart: for example 2 functions on the access control side, 4 on the InnerWeb side, 3 on the quality system side.01234functionsAccess control system: 2 functions2Access control systemInnerWeb: 4 functions4InnerWebQuality system: 3 functions3Quality system
Source: Example calculation: number of functions in a sample responsibility table; the plant sets its own.

Recommendation 2: do not order readers from us

InnerWeb does not produce access control readers and integrates with the client's existing access control system. It receives card tap events by webhook. This means the plant does not replace readers, cards or controllers, and the IT team does not have to run a second reader network. The scope of changes on the access control side is the configuration of event sending, agreed with its vendor.

We recommend writing down the event specification together with the access control vendor: card identifier, timestamp, tap point and direction, if the system knows it. The shorter the set of fields, the lower the risk of discrepancies.

Recommendation 3: the declaration as a gate, not a quality module

The guest's health declaration is a condition of entry, not a box to tick: a guest without today's declaration does not enter, and the entry is not recorded. The requirement is switched on with a setting in the administrator panel and is off by default. For IT this is important: switching it on is a configuration change in one installation, and other installations keep working unchanged.

The text of the declaration is a plant setting (a text field), with an optional English version. An empty field means a generic text without the plant name. Make sure that a change to the text goes through the same approval workflow as other quality documents.

Recommendation 4: plan the behavior during failures and duplicates

The database holds one declaration row per person per day, and a repeated confirmation returns the first entry. This simplifies integrations and scripts: there is no need to write deduplication logic. In turn, a missing declaration gives a third gate response, with no refusal in the SIEM log; the security team should know this so that correlation rules are set up correctly.

Also define what security does when the system is unavailable: the emergency procedure is part of the plant's business continuity plan and should not depend on the guard's memory.

Recommendations 5 and 6: validation scope and evidence

The EU GMP guidelines (EudraLex, Volume 4) include the chapter on personnel and Annex 1 on the manufacture of sterile medicinal products, in the version applicable from 25 August 2023. Whether and to what extent the entry system is subject to validation is decided by the quality risk analysis. We recommend that IT prepare in advance a list of functions that affect quality decisions (declaration, training, register) and separate lists of supporting functions.

The last recommendation concerns evidence. Ask the vendor for function documentation and a change log of settings, and before go-live plan an acceptance test on scenarios: a guest with a declaration, without a declaration, with a visit, and with a training error.

Video

Frequently asked questions

Does InnerWeb replace the access control system?

No. InnerWeb integrates with the client's existing access control system and receives card tap events by webhook, without replacing readers.

Does switching on the declaration change other installations?

No. The requirement is switched on with a setting in the administrator panel and is off by default, so other installations keep working unchanged.

Who decides on validation?

The plant, based on a quality risk analysis. The vendor supplies function documentation and evidence from acceptance tests.

Sources

Let us agree the scope with IT and validation

We will prepare a table of function split and an event specification for a conversation with the access control vendor.

Let's talk