medical factory  supplies storage indoor

Phar­maceu­ti­cal who­le­sa­lers

Role in the system Since February 9, 2019, pharmaceutical wholesalers have been verifying the authenticity of the unique identifier of pharmaceutical packages in their physical possession by scanning the Data Matrix Code and the resulting comparison with the securPharm system. At the very least, they must check medicines, that are...

Role in the sys­tem

Sin­ce Febru­ary 9, 2019, phar­maceu­ti­cal who­le­sa­lers have been veri­fy­ing the authen­ti­ci­ty of the uni­que iden­ti­fier of phar­maceu­ti­cal packa­ges in their phy­si­cal pos­ses­si­on by scan­ning the Data Matrix Code and the resul­ting com­pa­ri­son with the secur­Ph­arm sys­tem. At the very least, they must check medi­ci­nes,

  • that are retur­ned by phar­maci­es or ano­ther phar­maceu­ti­cal who­le­sa­ler
  • .
  • which they recei­ve from ano­ther who­le­sa­ler who is neither the manu­fac­tu­rer nor the who­le­sa­ler with a mar­ke­ting aut­ho­riza­ti­on nor a who­le­sa­ler desi­gna­ted by the mar­ke­ting aut­ho­riza­ti­on hol­der by means of a writ­ten con­tract to store and dis­tri­bu­te on his behalf the medi­cinal pro­ducts cover­ed by his mar­ke­ting aut­ho­riza­ti­on.

In addi­ti­on, who­le­sa­lers must dere­co­gni­ze the uni­que iden­ti­fier for medi­cinal pro­ducts,

  • that are to be dis­tri­bu­ted out­side the EU
  • .
  • that have been retur­ned to the who­le­sa­ler and can­not be included in the saleable stock, e.g. in the case of returns due to a recall
  • that are desti­ned for des­truc­tion.
  • which are reques­ted by the aut­ho­ri­ty for rehear­sal
  • .
  • that are sup­pli­ed to per­sons who are aut­ho­ri­zed and entit­led to dis­pen­se medi­cinal pro­ducts but who do not work in a health­ca­re faci­li­ty or phar­ma­cy, as well as to vete­ri­na­ri­ans, den­tists, the Ger­man Armed Forces, the poli­ce, govern­ment insti­tu­ti­ons, uni­ver­si­ties or other hig­her edu­ca­ti­on insti­tu­ti­ons in accordance with Sec­tion 6 (1a) of the Ger­man Medi­cinal Pro­ducts Trade Ordi­nan­ce
  • .

In order to inform the stake­hol­ders, secur­Ph­arm e. V. has pre­pared and sent a let­ter to all phar­maceu­ti­cal who­le­sa­lers 

.

The EU Com­mis­si­on lists the obli­ga­ti­ons of the indi­vi­du­al par­ties invol­ved in the imple­men­ta­ti­on of the Fal­si­fied Medi­ci­nes Direc­ti­ve in the let­ter of Octo­ber 18, 2018 

.

Sys­tem access

Who­le­sa­lers con­nect to the secur­Ph­arm sys­tem via the phar­ma­cy sys­tem. The phar­ma­cy sys­tem is ope­ra­ted by NGDA - Netz­werk­ge­sell­schaft deut­scher Apo­the­ker mbH. Infor­ma­ti­on on the tech­ni­cal and con­trac­tu­al spe­ci­fi­ca­ti­ons is available via the ser­vice por­tal of NGDA available. More about the NGDA at www.ngda.de.

Sys­tem access

The check­list pro­vi­des an initi­al over­view of the con­nec­tion to the secur­Ph­arm sys­tem and important topics for imple­men­ting the Fal­si­fied Medi­ci­nes Direc­ti­ve.

Mitteilungen

Alarm pro­ces­sing as an important pie­ce of the puz­zle: sup­port for offi­ci­al recon­nais­sance

From May 19, 2025, all aut­ho­ri­ties that alre­a­dy have access to the secur­Ph­arm sys­tem will have access to an addi­tio­nal modu­le: the Natio­nal Alert Manage­ment Sys­tem (NAMS).

Many sys­tem actions can be tra­cked with the help of so-cal­led aut­ho­ri­ty reports, but this is not pos­si­ble in all cases. Espe­ci­al­ly in …

Mehr Erfahren ...

Inspec­tions

On Janu­ary 22, 2020, the EU Com­mis­si­on issued an Aide Memoi­re on the inspec­tion of who­le­sa­lers regar­ding the imple­men­ta­ti­on of the Anti-Coun­ter­feit­ing Direc­ti­ve and the Dele­ga­ted Regu­la­ti­on.…

Mehr Erfahren ...

Prac­ti­cal examp­les and illus­tra­ted tips (Febru­ary 2019)

Prac­ti­cal examp­les and illus­tra­ted ins­truc­tions are sum­ma­ri­zed in the docu­ment Ins­truc­tions on first-ope­ning pro­tec­tion and the Data Matrix Code.…

Mehr Erfahren ...

Ansprechpartner finden

Haben Sie Fragen oder brauchen Sie Hilfe? Unsere Übersicht hilft Ihnen, den richtigen Ansprechpartner zu finden. Dieser kann Ihnen dann weiterhelfen. Behörden wenden sich bitte direkt an den securPharm e.V.

Kontakt aufnehmen

Fragen und Antworten

Why do we need a pro­tec­tion sys­tem for medi­ci­nes?

The­re are hard­ly any coun­ter­feits in the
legal sup­p­ly chain.
So far, the­re have only rare­ly been coun­ter­feit medi­ci­nes in the legal sup­p­ly chain. The avai­la­bi­li­ty of well
of well-made coun­ter­feits increa­ses the risk. The pro­tec­tion sys­tem has the­r­e­fo­re been
intro­du­ced to main­tain and fur­ther impro­ve the high level of safe­ty in the legal phar­maceu­ti­cal trade.
fur­ther impro­ve it.

Who is secur­Ph­arm e.V.?

secur­Ph­arm e. V. is the Ger­man orga­niza­ti­on for the authen­ti­ca­ti­on of phar­maceu­ti­cals and
respon­si­ble for the ope­ra­ti­on of the sys­tem for the authen­ti­ca­ti­on of medi­cinal pro­ducts. The asso­cia­ti­on
was foun­ded to imple­ment the EU Fal­si­fied Medi­ci­nes Direc­ti­ve 2011/62/EU and Dele­ga­ted Regu­la­ti­on (EU) No. 2016/EU.
(EU) No. 2016/161 by ABDA, BAH, BPI, PHAGRO and the vfa. The foun­ding
Avo­xa - Medi­en­grup­pe Deut­scher Apo­the­ker GmbH and IFA Infor­ma­ti­ons­stel­le für Arz­nei­mit­tel GmbH are also foun­ding mem­bers.
- Infor­ma­ti­ons­stel­le für Arz­nei­mit­tel GmbH. secur­Ph­arm ope­ra­tes as a non-pro­fit orga­niza­ti­on.
orga­niza­ti­on. secur­Ph­arm is the Ger­man com­po­nent of the EU-wide EMVS net­work against coun­ter­feit drugs.
coun­ter­feit medi­ci­nes.

How can Veri­fy­ing Bodies con­nect to the secur­Ph­arm sys­tem?

Veri­fy­ing enti­ties con­nect to the secur­Ph­arm sys­tem via the phar­ma­cy ser­ver. The
tech­ni­cal imple­men­ta­ti­on is car­ri­ed out by the soft­ware part­ner. The ope­ra­tor of the phar­ma­cy ser­ver is
Netz­ge­sell­schaft deut­scher Apo­the­ker mbH (NGDA), a 100% sub­si­dia­ry of Avo­xa.
NGDA is respon­si­ble for the legi­ti­miza­ti­on and con­nec­tion of the par­ti­ci­pan­ts (phar­macists, who­le­sa­lers,
health care faci­li­ties).

Who can con­nect to the phar­ma­cy sys­tem?

All play­ers affec­ted by the Fal­si­fied Medi­ci­nes Direc­ti­ve and who are not phar­maceu­ti­cal com­pa­nies can join the phar­ma­cy sys­tem.
and are not phar­maceu­ti­cal com­pa­nies, in par­ti­cu­lar public phar­maci­es, hos­pi­tals and phar­maceu­ti­cal who­le­sa­lers,
hos­pi­tals and phar­maceu­ti­cal who­le­sa­lers.

What secu­ri­ty fea­tures does the Fal­si­fied Medi­ci­nes Direc­ti­ve requi­re?

Sin­ce Febru­ary 9, 2019, the Fal­si­fied Medi­ci­nes Direc­ti­ve has sti­pu­la­ted two new secu­ri­ty fea­tures
on the pack­a­ging of pre­scrip­ti­on medi­ci­nes. A first-ope­ning pro­tec­tion (anti
tam­pe­ring device), which indi­ca­tes whe­ther a pack has alre­a­dy been ope­ned, is inten­ded to
gua­ran­tee that the con­tents of the pack are genui­ne. An indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture (Uni­que
iden­ti­fier) is inten­ded to make each pack uni­que­ly iden­ti­fia­ble.

What does the uni­que iden­ti­fier look like?

The uni­que iden­ti­fier is a data matrix code in which the indi­vi­du­al seri­al num­ber, the pro­duct code, the cha­rac
num­ber, the pro­duct code, the batch desi­gna­ti­on and the expiry date. In addi­ti­on
this infor­ma­ti­on is also prin­ted in plain text on the pack.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 6

Sin­ce when have the con­nec­tion to the secur­Ph­arm sys­tem and the authen­ti­ci­ty check been
man­da­to­ry?

Medi­cinal pro­ducts sub­ject to man­da­to­ry veri­fi­ca­ti­on that have been released for mar­ke­ting by the manu­fac­tu­rer sin­ce Febru­ary 9, 2019
may only be dis­pen­sed after suc­cessful authen­ti­ca­ti­on.
Medi­cinal pro­ducts that were released for mar­ke­ting befo­re the cut-off date may be sup­pli­ed until the end of their
expiry date wit­hout the safe­ty fea­tures and the­r­e­fo­re wit­hout authen­ti­ca­ti­on.
and the­r­e­fo­re wit­hout authen­ti­ci­ty test­ing.

Which medi­cinal pro­ducts are sub­ject to the new safe­ty mea­su­res?

In prin­ci­ple, the new requi­re­ments app­ly to all pre­scrip­ti­on-only medi­cinal pro­ducts for human use
with the excep­ti­on of medi­cinal pro­ducts on the so-cal­led white list (Annex I to the Dele­ga­ted Regu­la­ti­on).
lis­ted medi­cinal pro­ducts. The white list is a list of pre­scrip­ti­on-only medi­cinal pro­ducts and medi­cinal pro­duct
cate­go­ries of medi­cinal pro­ducts that may not bear the safe­ty fea­tures. This list con­ta­ins 14
pro­duct cate­go­ries, inclu­ding home­opa­thics, all­er­gen extra­cts, con­trast media and par­en­te­ral nut­ri­ti­on solu­ti­ons.
solu­ti­ons for par­en­te­ral nut­ri­ti­on. Non-pre­scrip­ti­on medi­ci­nes may not bear the
safe­ty fea­tures. Excep­ti­ons are the medi­cinal pro­ducts lis­ted in the Black List (Annex II to the Dele­ga­ted
Regu­la­ti­on). The Black List is a list of non-pre­scrip­ti­on medi­cinal pro­ducts and
The Black List is a list of non-pre­scrip­ti­on medi­ci­nes and cate­go­ries of medi­ci­nes that must bear the safe­ty fea­tures.
So far, only ome­pra­zo­le is included in two dif­fe­rent strengths.

Can OTCs vol­un­t­a­ri­ly car­ry a Data Matrix Code?

Accor­ding to the EU Com­mis­si­on, the appli­ca­ti­on of a Data Matrix Code to OTC packs is per­mit­ted as long as the Data Matrix Code does not con­tain any seri­al num­bers.
the Data Matrix Code does not con­tain a seri­al num­ber, the pro­duct code, expiry date and batch
date and batch num­ber can be included in a machi­ne-rea­da­ble form. Vol­un­t­a­ry par­ti­ci­pa­ti­on in the
in the authen­ti­ca­ti­on of medi­cinal pro­ducts is not pos­si­ble.

May OTCs vol­un­t­a­ri­ly car­ry first-ope­ning pro­tec­tion?

In an announce­ment dated April 11, 2017, the PEI and BfArM (BAnz AT 26.04.2017 B3.) cla­ri­fied
that OTC packs may bear a first-ope­ning pro­tec­tion on a vol­un­t­a­ry basis.

How does the secur­Ph­arm sys­tem for the veri­fi­ca­ti­on of medi­cinal pro­ducts work?

During the pro­duc­tion pro­cess, the phar­maceu­ti­cal manu­fac­tu­rer pro­vi­des each pack of a medi­cinal pro­duct sub­ject to veri­fi­ca­ti­on
phar­maceu­ti­cal pro­duct with an indi­vi­du­al seri­al num­ber. This seri­al num­ber is stored tog­e­ther
tog­e­ther with the pro­duct code (as PPN or NTIN wrap­ped PZN), batch desi­gna­ti­on and expiry date in the Data Matrix Code (and
date in the Data Matrix Code (and also in plain text) on the pack. At the same time
This infor­ma­ti­on is uploa­ded to the data­ba­se sys­tem of the phar­maceu­ti­cal indus­try.
To veri­fy the authen­ti­ci­ty of a pack, the Data Matrix Code of the pack is scan­ned by the veri­fier.
scan­ned by the veri­fy­ing body. This trig­gers a check of the seri­al num­ber and pro­duct code
against the data­ba­se of the phar­maceu­ti­cal indus­try. The veri­fi­ca­ti­on requests are
for­ward­ed anony­mously via the phar­ma­cy ser­ver. The sta­tus of a pack recor­ded in this data­ba­se
sta­tus of a pack is repor­ted back to the veri­fy­ing body. If the pack is dis­pen­sed after
posi­ti­ve feed­back, the sta­tus is set to “dis­pen­sed”. If a
second pack with an iden­ti­cal seri­al and pro­duct num­ber is veri­fied, it will be noted that it has alre­a­dy been
this has alre­a­dy been dis­pen­sed.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 7

Why are the­re two sub­sys­tems?

The Ger­man stake­hol­ders have opted for a sys­tem that con­sists of dis­tri­bu­ted data
banks for phar­maci­es and phar­maceu­ti­cal com­pa­nies. The design of a
model ensu­res spe­cial pro­tec­tion of sen­si­ti­ve data, as data for the veri­fi­ca­ti­on pro­ces­ses (veri­fi­ca­ti­on and
for the veri­fi­ca­ti­on pro­ces­ses (veri­fi­ca­ti­on and sta­tus chan­ges) are only exch­an­ged anony­mously. The
The sub­sys­tems are also ope­ra­ted by dif­fe­rent com­pa­nies. The data­ba­se
sys­tem for phar­maceu­ti­cal com­pa­nies is ope­ra­ted by ACS Phar­ma­Pro­tect GmbH, a com­pa­ny of the phar­maceu­ti­cal
of the phar­maceu­ti­cal asso­cia­ti­ons. The data­ba­se sys­tem for the phar­maceu­ti­cal indus­try
all phar­maceu­ti­cal com­pa­nies who­se pro­ducts are sub­ject to the veri­fi­ca­ti­on obli­ga­ti­on.
sub­ject to the veri­fi­ca­ti­on obli­ga­ti­on. The phar­ma­cy ser­ver is ope­ra­ted by Netz­ge­sell­schaft Deut­scher Apo­the­ker
mbH (NGDA).

Why is this sys­tem also cal­led an “end-to-end sys­tem”?

The phar­maceu­ti­cal com­pa­ny crea­tes a safe­ty fea­ture at one end of the sup­p­ly chain - when pack­a­ging the medi­ci­ne.
the drug - while at the other end of the chain - befo­re dis­pen­sing to the pati­ent in the phar­ma­cy - this
to the pati­ent in the phar­ma­cy - this safe­ty fea­ture is veri­fied and the seri­al num­ber is
writ­ten out.

Why is the Data Matrix Code used for this sys­tem?

Two-dimen­sio­nal bar­codes can hold a lot of data (e.g. in addi­ti­on to the pro­duct code inclu­ding PZN
seri­al num­ber, the batch desi­gna­ti­on and the expiry date) and dis­play them with a very small
space requi­re­ment.

Do par­al­lel imports car­ry Ger­man or for­eign coding?

Par­al­lel imports car­ry Ger­man coding in the Ger­man mar­ket. Par­al­lel importers must
the uni­que iden­ti­fier of the pro­duct they mar­ket under their own name from the sys­tem of the ori­gi­nal mar­ket.
from the sys­tem of the ori­gi­nal mar­ket and book it out. They then
posi­ti­on as a phar­maceu­ti­cal entre­pre­neur and crea­te a new uni­que iden­ti­fier, which they enter in the
which they upload to the secur­Ph­arm sys­tem.

How are for­eign packs (indi­vi­du­al imports) hand­led?

For­eign packs must be hand­led in the same way as Ger­man packs. The scan of the Data
matrix code trig­gers a veri­fi­ca­ti­on request, which is for­ward­ed via the Euro­pean hub to the respec­ti­ve natio­nal
natio­nal sys­tem in which the pack data is stored. This pro­cess is also known as
The pro­cess is also known as an IMT (Inter­mar­ket Tran­sac­tion). For exam­p­le, veri­fy the packs uploa­ded to the
Spa­nish sys­tem, the veri­fi­ca­ti­on request is for­ward­ed to the Spa­nish sys­tem via the Euro­pean hub.
for­ward­ed to the Spa­nish natio­nal veri­fi­ca­ti­on sys­tem via the Euro­pean hub. Indi­vi­du­al imports
from a Euro­pean coun­try in which the medi­ci­ne is not sub­ject to man­da­to­ry veri­fi­ca­ti­on are also
are not sub­ject to the veri­fi­ca­ti­on obli­ga­ti­on in Ger­ma­ny.

What data is gene­ra­ted when end users use the secur­Ph­arm sys­tem?

When a pack is veri­fied or boo­ked out, a request is sent to the phar­ma­cy sys­tem
(AP sys­tem) is sent. N-ID (i.e. the pseud­ony­mi­zed user ID/APO-
num­ber), the time stamp, the action/process and the pack data con­tai­ned in the Data Matrix Code
Data Matrix Code (PC, SN, LOT, EXP) are trans­mit­ted. Only NGDA has access to this data. From the

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 8

APS, the request is for­ward­ed to the data­ba­se of the phar­maceu­ti­cal indus­try (PU sys­tem)
is for­ward­ed. Howe­ver, the iden­ti­ty of a veri­fy­ing body remains hid­den from the PU sys­tem
becau­se all requests are for­ward­ed anony­mously under a spe­cial NGDA user ID.
Per­so­nal data is not trans­mit­ted to the PU sys­tem. The query is used exclu­si­ve­ly
to compa­re the infor­ma­ti­on read out (safe­ty fea­tures of the pack) with the data stored in the
data stored in the sys­tem for the respec­ti­ve pack. The data exch­an­ge allows the authen­ti­ci­ty of the
authen­ti­ci­ty of the medi­ci­ne can be veri­fied.
Every request to the data­ba­ses is saved. This enables the respon­si­ble super­vi­so­ry
aut­ho­ri­ties to inves­ti­ga­te a suspec­ted case of fal­si­fi­ca­ti­on and com­pli­ance with the Dele­ga­ted Regu­la­ti­on.
inves­ti­ga­ti­on.

What is the Euro­pean hub?

The Euro­pean hub is nee­ded to enable cross-bor­der flows of goods. It
net­works the veri­fi­ca­ti­on sys­tems of the indi­vi­du­al mem­ber sta­tes with each other, so that every packa­ge
pack of medi­ci­nes bea­ring the safe­ty fea­tures can be che­cked in every phar­ma­cy in Euro­pe.
phar­ma­cy in Euro­pe. In addi­ti­on, phar­maceu­ti­cal com­pa­nies upload the pack data to the Euro­pean hub (EU hub).
hub) to upload the pack data to the respec­ti­ve natio­nal sys­tem. The ope­ra­tor of the EU Hub is EMVO,
the Euro­pean Medi­ci­nes Veri­fi­ca­ti­on Orga­niza­ti­on. More about EMVO at https://emvo-
medicines.eu/

Which count­ries are con­nec­ted to the Euro­pean hub?

The authen­ti­ca­ti­on sys­tems of the EU mem­ber sta­tes as well as Ice­land, Liech­ten­stein, Nor­way, Nor­t­hern
mem­ber sta­tes as well as Ice­land, Liech­ten­stein, Nor­way, Nor­t­hern Ire­land and Switz­er­land are con­nec­ted to the Euro­pean hub. The sys­tems of
Ita­ly and Greece will not be added until 2025. The­se have been gran­ted a tran­si­ti­on peri­od by the legis­la­tor.
The­se count­ries have been gran­ted a tran­si­tio­nal peri­od by the legis­la­tor becau­se the­se count­ries alre­a­dy had
regu­la­ti­on came into force, the­se count­ries alre­a­dy had sys­tems in place for the veri­fi­ca­ti­on of medi­cinal
have to be adapt­ed to the Euro­pean requi­re­ments.

Who is the EMVO?

The Euro­pean Medi­ci­nes Veri­fi­ca­ti­on Orga­niza­ti­on (EMVO) ope­ra­tes the EU hub through which the indi­vi­du­al
the indi­vi­du­al coun­try sys­tems exch­an­ge the pack­a­ging data. A cor­re­spon­ding agree­ment was con­cluded bet­ween EMVO and secur­Ph­arm
agree­ment was con­cluded bet­ween EMVO and secur­Ph­arm to con­nect the secur­Ph­arm sys­tem with the EU Hub
and thus inte­gra­te it into the Euro­pean anti-coun­ter­feit­ing sys­tem.

What is the EMVS?

The Euro­pean Medi­ci­nes Veri­fi­ca­ti­on Sys­tem (EMVS) is the Euro­pe-wide anti-coun­ter­feit­ing sys­tem.
It con­sists of two com­pon­ents. One com­po­nent is for­med by the natio­nal orga­niza­ti­ons for
the Dele­ga­ted Regu­la­ti­on (NMVOs) with the cor­re­spon­ding natio­nal sys­tems (NMVS).
(NMVS).
The second com­po­nent of the EMVS is for­med by the Euro­pean hub. This hub
This hub acts as a rou­ter (con­nec­tion point) to ensu­re the exch­an­ge of data from the natio­nal data
and is also used by phar­maceu­ti­cal com­pa­nies to upload pack­a­ging data.
used by the phar­maceu­ti­cal com­pa­nies.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 9

How are the secu­ri­ty fea­tures inten­ded to increase coun­ter­feit pro­tec­tion?

The new anti-coun­ter­feit­ing pro­tec­tion con­sis­ting of an indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture and first-ope­ning pro­tec­tion
coun­ter­feits are easier to reco­gni­ze. The indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture makes each pack
uni­que, making coun­ter­feit­ing less attrac­ti­ve and the risk of detec­tion high.
is high.

Whe­re can I find out which coun­ter­feits have been detec­ted by the secur­Ph­arm sys­tem?

Is the­re
Is the­re a list of detec­ted coun­ter­feits?
secur­Ph­arm sup­ports the respon­si­ble super­vi­so­ry aut­ho­ri­ties in the inves­ti­ga­ti­on of suspec­ted coun­ter­feit­ing
by pro­vi­ding reports from the secur­Ph­arm sys­tem, the so-cal­led audit trails of indi­vi­du­al packs.
of indi­vi­du­al packs. As a rule, secur­Ph­arm does not recei­ve any infor­ma­ti­on about the
gene­ral­ly does not recei­ve any infor­ma­ti­on. Infor­ma­ti­on on coun­ter­feits must the­r­e­fo­re be obtai­ned from the respon­si­ble
super­vi­so­ry aut­ho­ri­ties.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 10

2. ques­ti­ons regar­ding the con­nec­tion to the secur­Ph­arm sys­tem

What are the requi­re­ments for using the secur­Ph­arm sys­tem?

In addi­ti­on to the tech­ni­cal requi­re­ments (hard­ware and soft­ware, Inter­net con­nec­tion), the use of the secur­Ph­arm sys­tem requi­res
and soft­ware, Inter­net con­nec­tion), access to the phar­ma­cy ser­ver of the secur­Ph­arm sys­tem in the form of an
sys­tem in the form of an elec­tro­nic cer­ti­fi­ca­te (N-ID). In order to pre­vent unaut­ho­ri­zed use of the sys
sys­tem, a user goes through a legi­ti­miza­ti­on pro­cess befo­re acces­sing the sys­tem. The
legi­ti­ma­ti­on is che­cked at regu­lar inter­vals and the user is re-aut­ho­ri­zed. This
This is done for the veri­fy­ing body via the NGDA por­tal.

What is the NGDA por­tal?

The NGDA por­tal pro­vi­des access for various tar­get groups. Per­sons respon­si­ble
can use the NGDA por­tal to mana­ge the cer­ti­fi­ca­tes of one or more ope­ra­ting sites.
ope­ra­ting sites. Each busi­ness pre­mi­ses recei­ves its own N-ID in the N-Ident pro­ce­du­re. The
cont­act details of the respec­ti­ve ope­ra­ting site (inclu­ding e-mail address) should always be kept up to date.
be kept up to date. A user name and pass­word are defi­ned when regis­tering in the NGDA por­tal.
The por­tal can be acces­sed at www.ngda.de.

What is the N-ID?

The N-ID is the elec­tro­nic iden­ti­ty of an indi­vi­du­al busi­ness estab­lish­ment veri­fied as part of the N-Ident pro­cess.
busi­ness pre­mi­ses. It is used to access digi­tal ser­vices and sys­tems wit­hout addi­tio­nal regis­tra
regis­tra­ti­on and is a man­da­to­ry requi­re­ment for par­ti­ci­pa­ti­on in the secur­Ph­arm sys­tem. Behind the N-ID
is a cer­ti­fi­ca­te that is valid for 24 months.
When regis­tering and legi­ti­mi­zing a busi­ness estab­lish­ment in the NGDA por­tal, an N-ID cer­ti­fi­ca­te can be acqui­red.
cer­ti­fi­ca­te can be acqui­red. With the cer­ti­fi­ca­te, a user recei­ves a com­bi­na­ti­on of user name,
the N-ID and pass­word. If the cer­ti­fi­ca­te for the indi­vi­du­al busi­ness pre­mi­ses has been rene­wed, a new
new pass­word is issued for the cer­ti­fi­ca­te, but the user name (N-ID) for the site remains the same.
remains the same.

What can be done if dif­fi­cul­ties ari­se when log­ging into the NGDA por­tal?

If you have for­got­ten your pass­word, you can obtain a new pass­word from the NGDA web­site.
pass­word. To do this, you must enter your user name and the e-mail address you have pro­vi­ded.
You can find help with this at www.ngda.de.

What can I do if I have dif­fi­cul­ties log­ging in to the secur­Ph­arm GUI?

To log in to the secur­Ph­arm GUI, you will need the N-ID and pass­word from the first PIN let­ter you recei­ved by post.
let­ter that was sent by post. When rene­wing a cer­ti­fi­ca­te, users recei­ve
recei­ve a new pass­word, but the pass­word from the first PIN let­ter is still used to access the
GUI.
In the event that the pass­word is for­got­ten, a new pass­word can be obtai­ned from the NGDA web­site.
pass­word. The user name and the e-mail address stored must be ente­red for this pur­po­se.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 11

The pass­word is sent to the e-mail address stored in the NGDA por­tal for this ope­ra­ting site.
sent. It is the­r­e­fo­re important to keep the e-mail address stored in the NGDA por­tal up to date.
The secur­Ph­arm GUI can be rea­ched at: https://securpharm-gui.ngda.de/ .

Who is respon­si­ble for con­nec­ting to the sys­tem?

The respon­si­bi­li­ty for imple­men­ting the legal requi­re­ments of the Fal­si­fied Medi­ci­nes Direc­ti­ve
and the Dele­ga­ted Regu­la­ti­on, which also includes the con­nec­tion to secur­Ph­arm via the phar­ma­cy
ser­ver, is the respon­si­bi­li­ty of the veri­fy­ing body.

What does the con­nec­tion to the secur­Ph­arm sys­tem cost?

The cos­ts can be obtai­ned from the NGDA.

How do I app­ly for an N-ID for the first time?

The N-Ident regis­tra­ti­on pro­ce­du­re is divi­ded into three stages. First, an account must be crea­ted at
https://ngda.de/ must be crea­ted. Then each busi­ness estab­lish­ment for which an N-ID is requi­red must be
is requi­red must be crea­ted in the account. Final­ly, the access aut­ho­riza­ti­on must be che­cked.
To do this, the rele­vant docu­ments must be sub­mit­ted to the NGDA for veri­fi­ca­ti­on by uploa­ding the requi­red docu­ments.
uploa­ding the requi­red docu­ments. Once the docu­ments have been suc­cessful­ly che­cked,
the N-ID can be acqui­red for the busi­ness pre­mi­ses. Once pay­ment has been recei­ved, the cer­ti­fi-
cer­ti­fi­ca­te is issued. The PIN for the down­load is sent to the busi­ness pre­mi­ses by post. Sub­se­quent­ly
the cer­ti­fi­ca­te can be down­loa­ded and inte­gra­ted.
The NGDA recom­mends allo­wing a peri­od of 4 weeks for the legi­ti­miza­ti­on pro­cess descri­bed abo­ve befo­re ope­ning a busi­ness pre­mi­ses.
weeks befo­re the ope­ning of a branch.

When do I have to re-legi­ti­mi­ze my branch?

Re-legi­ti­miza­ti­on is requi­red every 24 months in con­nec­tion with the cer­ti­fi­ca­te rene­wal in order to
to pro­ve the con­tin­ued aut­ho­riza­ti­on to use the digi­tal ser­vices. For
fur­ther infor­ma­ti­on, such as which docu­ments are requi­red for rele­gi­ti­miza­ti­on, plea­se cont­act the NGDA.
for fur­ther infor­ma­ti­on.

Are the­re any dis­ad­van­ta­ges if I app­ly for a new cer­ti­fi­ca­te befo­re the cer­ti­fi­ca­te expi­res?
cer­ti­fi­ca­te?

The cer­ti­fi­ca­te has a term of 24 months, which beg­ins with the first down­load. As
the pro­cess of re-legi­ti­miza­ti­on and cer­ti­fi­ca­te rene­wal takes some time, the NGDA recom
NGDA recom­mends rene­wing the cer­ti­fi­ca­te at an ear­ly stage. The cer­ti­fi­ca­te can be reques­ted and acti­va­ted up to three
reques­ted and acti­va­ted up to three months in advan­ce (down­load and inte­gra­te) wit­hout
dis­ad­van­ta­ges for the veri­fy­ing body.
The cer­ti­fi­ca­te is only dis­play­ed as acti­ve in the NGDA por­tal after the first down­load.

How do I know when an N-ID cer­ti­fi­ca­te rene­wal is due?

NGDA will inform you by e-mail in good time befo­re the cer­ti­fi­ca­te expi­res so that the
order pro­cess can be initia­ted in good time. To recei­ve a remin­der, the
cont­act details in the NGDA por­tal for the respec­ti­ve ope­ra­ting site must be kept up to date.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 12

What do I have to con­sider in the N-Ident pro­ce­du­re if I have seve­ral busi­ness pre­mi­ses?

For owners of seve­ral busi­ness pre­mi­ses (e.g. bran­ches or sub­si­dia­ries), a sin­gle regis­tra­ti­on in the
regis­tra­ti­on in the NGDA por­tal is suf­fi­ci­ent. Each busi­ness estab­lish­ment must be legi­ti­mi­zed and
requi­res its own elec­tro­nic cer­ti­fi­ca­te. Plea­se ensu­re that you enter the cont­act details
cont­act details (e.g. e-mail address) asso­cia­ted with the respec­ti­ve busi­ness pre­mi­ses up to date at all times.

What do I need to bear in mind if I give up or clo­se my busi­ness pre­mi­ses?

The cur­rent hol­der can­cels the cer­ti­fi­ca­te for the busi­ness pre­mi­ses, sta­ting the date of ter­mi­na­ti­on.
date of ter­mi­na­ti­on. The noti­ce of ter­mi­na­ti­on is sent by e-mail to kuendigung@ngda.de, sta­ting the
the estab­lish­ment num­ber, the full address and the date of ter­mi­na­ti­on.
Plea­se note that, if pos­si­ble, the e-mail should be sent from the same address as the e-mail address of the N-Ident account.
e-mail address of the N-Ident account hol­der. An employee of NGDA will check the ter­mi­na­ti­on
After recei­ving the noti­ce of ter­mi­na­ti­on, an NGDA employee will check it again and then initia­te all the neces­sa­ry steps.

I have taken over a busi­ness pre­mi­ses, can I also take over the N-ID?

The exis­ting N-ID cer­ti­fi­ca­te can­not be trans­fer­red. The regis­tra­ti­on for an exis­ting
exis­ting busi­ness pre­mi­ses can take place in two ways:
” The new owner has not yet regis­tered a per­ma­nent estab­lish­ment with the NGDA.
In this case, the regis­tra­ti­on of an N-Ident account inclu­ding the crea­ti­on of the busi­ness pre­mi­ses is neces­sa­ry.
neces­sa­ry.
” The new owner alre­a­dy has one or more per­ma­nent estab­lish­ments.
In this case, a new busi­ness estab­lish­ment must be crea­ted within the NGDA por­tal.

Why do I recei­ve a PIN let­ter?

To acqui­re the N-ID cer­ti­fi­ca­te, the veri­fy­ing body recei­ves a let­ter with a pass­word (PIN).
pass­word (PIN). Tog­e­ther with the cor­re­spon­ding N-ID (e.g. APOxxxxxxx), this PIN is used to
down­loa­ding and unpack­ing the cer­ti­fi­ca­te. Only after the first down­load is
the cer­ti­fi­ca­te is also dis­play­ed as acti­ve in the NGDA por­tal.
The access data should be stored secu­re­ly, as it is used not only for cer­ti­fi­ca­te rene­wal
also for the web inter­face of the secur­Ph­arm phar­ma­cy ser­ver (www.securpharm-gui.ngda.de/)
are requi­red.

My down­load did not work, what do I have to con­sider?

The NGDA has published the fol­lo­wing ins­truc­tions for down­loa­ding the N-ID cer­ti­fi­ca­te:
” It is pos­si­ble to down­load the cer­ti­fi­ca­te three times, unsuc­cessful attempts due to incor­rect ent­ry
of the N-ID (APO num­ber) or incor­rect PIN ent­ry will not be coun­ted. The spel­ling of the
N-ID with upper or lower case let­ters is irrele­vant.
” Cer­ti­fi­ca­te down­loads are not blo­cked if a sub­scri­ber enters the wrong PIN three times.
three times.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 13

” If a PIN is unclear (pos­si­bi­li­ty of con­fu­sing “O” and “0” or “l” and “=”), the cor­rect PIN can be deter­mi­ned by tri­al and error.
cor­rect PIN can be deter­mi­ned by tri­al and error.
” NGDA does not know the respec­ti­ve PINs, so unfort­u­na­te­ly it can­not pro­vi­de any assis­tance.
” Plea­se note that any exis­ting secu­ri­ty infra­struc­tu­re - such as a fire­wall - can also pre­vent the down­load.
a fire­wall - can pre­vent the down­load.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 14

3. ques­ti­ons about secur­Ph­arm in ever­y­day work

How can I reco­gni­ze a medi­cinal pro­duct sub­ject to veri­fi­ca­ti­on?

The IFA data­ba­se and the ABDA artic­le mas­ter have been expan­ded to include cor­re­spon­ding infor­ma­ti­on.
has been added. The mer­chan­di­se manage­ment sys­tem should, if it acces­ses the ABDA artic­le mas­ter, reco­gni­ze
reco­gni­ze whe­ther it is a pro­duct sub­ject to veri­fi­ca­ti­on.

If all the medi­ci­nes I dis­pen­se that are sub­ject to veri­fi­ca­ti­on are scan­ned, does the phar­maceu­ti­cal indus­try
will the phar­maceu­ti­cal indus­try find out about my sales figu­res?

No, not at all. secur­Ph­arm is based on the prin­ci­ple of sepa­ra­te data­ba­ses for phar­maceu­ti­cal com­pa­nies and veri­fiers.
phar­maceu­ti­cal com­pa­nies and veri­fy­ing aut­ho­ri­ties. The phar­ma­cy ser­ver to which your soft­ware is con­nec­ted
your soft­ware is con­nec­ted to, anony­mi­zes every tran­sac­tion so that no one knows whe­re the medi­ci­ne was dis­pen­sed.
was dis­pen­sed.

I have a pack in front of me wit­hout a Data Matrix code. How do I deal with it?

Scan the bar­code (“Code 39”). The mer­chan­di­se manage­ment sys­tem will, if it is based on the IFA
data or the ABDA artic­le mas­ter, the mer­chan­di­se manage­ment sys­tem will tell you whe­ther this pack must have a Data Matrix
code or whe­ther it is a stock item that was pla­ced on the mar­ket befo­re Febru­ary 9, 2019.
was pla­ced on the mar­ket.

Is it suf­fi­ci­ent to scan the PZN bar­code ins­tead of the Data Matrix code?

No, becau­se the pre­vious PZN bar­code only con­ta­ins the PZN in machi­ne-rea­da­ble form.
In addi­ti­on to the PZN, the Data Matrix Code also con­ta­ins the seri­al num­ber of the pack, which is used for verification/authenticity checks.
which is used for verification/authenticity checks against the data­ba­se. In addi­ti­on to the
the pro­duct code, the batch desi­gna­ti­on and the expiry date are also trans­mit­ted in the Data Matrix Code.
so that the­se can be recor­ded elec­tro­ni­cal­ly in the mer­chan­di­se manage­ment sys­tem in future. With
With the intro­duc­tion of the Data Matrix Code, the­re is also no lon­ger an obli­ga­ti­on to app­ly the Code 39
on the pack.

What fea­tures must be prin­ted on the pack­a­ging (in plain text)?

In addi­ti­on to the Data Matrix Code, packs sub­ject to man­da­to­ry veri­fi­ca­ti­on must con­tain the fol­lo­wing ele­ments
PZN, batch num­ber and expiry date, the pro­duct code and the seri­al num­ber must also be prin­ted in plain text on
in plain text. Par­ti­cu­lar­ly small packs are exempt from this regu­la­ti­on.
Fur­ther infor­ma­ti­on can be found on the IFA web­site.

What hap­pens when I scan the bar­code?

When you scan the bar­code, your mer­chan­di­se manage­ment sys­tem, pro­vi­ded it uses the ABDA
artic­le mas­ter, checks whe­ther it is a pro­duct that requi­res veri­fi­ca­ti­on and, if so, informs you
If this is the case, it will inform you that you must scan the Data Matrix Code.

What data is con­tai­ned in the Data Matrix Code?

The Data Matrix Code con­ta­ins the pro­duct code, which in turn con­ta­ins the PZN, as well as a
pack-spe­ci­fic seri­al num­ber, batch num­ber and expiry date.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 15

Is the­re a pre­scri­bed order for the infor­ma­ti­on in plain text?

No. Phar­maceu­ti­cal com­pa­nies are free to choo­se the order of the data ele­ments as long as the requi­red
long as the requi­red data ele­ments pro­duct code, seri­al num­ber, batch num­ber and expiry date are included.
expiry date are included. If the dimen­si­ons of the pack­a­ging allow, the human-rea­da­ble data
human-rea­da­ble data ele­ments are loca­ted next to the Data Matrix Code.

How can I tell which Data Matrix Code I need to scan for the authen­ti­ci­ty check?
if the­re are seve­ral Data Matrix Codes on the pack?

If the­re are seve­ral Data Matrix Codes on a pack, the Data Matrix Code for the authen­ti­ci­ty check is next to the Data
Matrix Code for the authen­ti­ci­ty check is the PPN mar­king.

In a hec­tic situa­ti­on, it some­ti­mes hap­pens that a pack is scanned/verified twice by mista­ke.
twice. Have I des­troy­ed the dis­pensa­bi­li­ty?

No. The Data Matrix code of a pack can be veri­fied by scan­ning as often as requi­red.
Howe­ver, it is important that you only veri­fy the pack and do not book it out of the sys­tem.
i.e. deac­ti­va­te the indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture. Howe­ver, if this error
error, you can cor­rect it within 10 days. The Dele­ga­ted Regu­la­ti­on
The Dele­ga­ted Regu­la­ti­on sti­pu­la­tes that packs who­se sta­tus has been set to “dis­pen­sed” and which have not left the
trol­led area of the phar­ma­cy can be retur­ned within 10 days in the same estab­lish­ment.
may be boo­ked back into the same site within 10 days.

May the pack data be prin­ted in white let­ters on a black back­ground (inver­se)?

Yes, the Data Matrix Code and the plain text infor­ma­ti­on may be prin­ted in white on a black back­ground.
on a black back­ground is per­mit­ted. A sui­ta­ble and cor­rect­ly adjus­ted scan­ner is capa­ble of rea­ding all appro­ved
read all appro­ved forms of pre­sen­ta­ti­on.

A pack has rea­ched its expiry date. Does it have to be writ­ten off when it is des­troy­ed?

No, the pack must not be writ­ten off, as this is done auto­ma­ti­cal­ly by the sys­tem at the time of expiry.
auto­ma­ti­cal­ly at the time of expiry. Other­wi­se an alarm is gene­ra­ted. If a pack requi­ring veri­fi­ca­ti­on
pack is des­troy­ed befo­re the expiry date, it must be boo­ked out.

How do you deal with coded inven­to­ry goods that were uploa­ded for test pur­po­ses befo­re the man­da­to­ry ope­ra­ti­on?
befo­re man­da­to­ry ope­ra­ti­on?

Inven­to­ry goods are goods that were released for dis­tri­bu­ti­on by the manu­fac­tu­rer befo­re Febru­ary 9, 2019, but which
for cir­cu­la­ti­on by the manu­fac­tu­rer befo­re 9 Febru­ary 2019, but which bear secu­ri­ty fea­tures that have
have been appli­ed for test pur­po­ses. The­se can cau­se fal­se alarms in the sys­tem under cer­tain cir­cum­s­tances. The pro­por­ti­on of
of coded stock has alre­a­dy fal­len signi­fi­cant­ly, so the pro­blem should occur less fre­quent­ly.
should occur less fre­quent­ly. Accor­ding to the dele­ga­ted regu­la­ti­on, the­se goods can gene­ral­ly be sold, pro­vi­ded the­re are no other
reasons speak against it.

May secur­Ph­arm e. V. pass on pro­to­cols with pack data from the secur­Ph­arm sys­tem to
veri­fy­ing bodies, e.g. if they want to know whe­ther or not they have alre­a­dy che­cked a pack
che­cked and boo­ked out or not?

No. Accor­ding to the requi­re­ments of the Dele­ga­ted Regu­la­ti­on, secur­Ph­arm e. V. is not allo­wed to trans­fer logs with pack
data from the secur­Ph­arm sys­tem only to aut­ho­ri­ties.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 16

What is the dif­fe­rence bet­ween veri­fy­ing and wri­ting off a pack?

Veri­fi­ca­ti­on is used to check the sta­tus of the pack, wher­eby the read-out or manu­al­ly
manu­al­ly ente­red pack data is com­pared with the pack data stored in the sys­tem.
stored in the sys­tem. A dis­play reflects the sta­tus of the pack. A pack can be veri­fied as often as requi­red.
veri­fied as often as requi­red.
The wri­te-off (dis­pen­sing) descri­bes the sta­tus chan­ge of an indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture
from “dis­pensable” or “acti­ve” to “dis­pen­sed” or “inac­ti­ve”. The dere­co­gni­ti­on the­r­e­fo­re deac­ti­va­tes
the indi­vi­du­al iden­ti­fi­ca­ti­on fea­ture.

How do I know if my scan­ner is sui­ta­ble and working pro­per­ly?

The NGDA has deve­lo­ped a scan­ner test that should be used to check the set­tings of all scan­ners.
should be che­cked. The con­fi­gu­ra­ti­on of the scan­ners is important, as this is the only way to ensu­re that the data is
read out and trans­mit­ted cor­rect­ly during scan­ning.
With incor­rect­ly con­fi­gu­red scan­ners, it is often obser­ved that the lan­guage set­ting trig­gers alarms.
trig­gers alarms. For exam­p­le, an Eng­lish lan­guage set­ting is often pre­set so that Y and Z are swap­ped when rea­ding out.
Y and Z are swap­ped when rea­ding. In addi­ti­on, incor­rect­ly set scan­ners can cau­se errors when
errors in the trans­mis­si­on of upper and lower case let­ters. Incor­rect­ly read inver­se codes
(white on a dark back­ground) are also a fre­quent source of errors that can be avo­ided by con­fi­gu­ring the scan­ner.
can be avo­ided by con­fi­gu­ring the scan­ner.
To ensu­re that the scan­ners in your faci­li­ty can read the Data Matrix code cor­rect­ly, plea­se test all scan­ners.
cor­rect­ly, plea­se test all scan­ners (e.g. inco­ming goods and HV). If you noti­ce any anoma­lies
or if you have any ques­ti­ons about the con­fi­gu­ra­ti­on of the scan­ner, the scan­ner manu­fac­tu­rer or sup­pli­er can
of the scan­ner can pro­vi­de assis­tance.
You can obtain the scan­ner test at: www.securPharm.de, www.ngda.de or in the secur­Ph­arm
GUI.

How long do I have to wait until I recei­ve a sys­tem respon­se after a scan?

The Dele­ga­ted Regu­la­ti­on sti­pu­la­tes that the respon­se time of the sys­tem must be less than 300 mil­li­se­conds for at least 95% of the queries.
queries must be less than 300 mil­li­se­conds.
The per­for­mance of the data repo­si­to­ry must enable veri­fy­ing aut­ho­ri­ties to car­ry out their acti­vi­ties wit­hout
car­ry out their acti­vi­ties wit­hout any signi­fi­cant time delay. Howe­ver, the respon­se time from the verifier’s point of view
the Inter­net con­nec­tion bet­ween a veri­fy­ing body and the phar­ma­cy sys­tem as well as the inter­nal
phar­ma­cy sys­tem and the inter­nal infra­struc­tu­re of the veri­fy­ing body, so that the total dura­ti­on of the
so that the total dura­ti­on of the request can exceed 300 mil­li­se­conds
If a respon­se takes a dis­pro­por­tio­na­te­ly long time, the avai­la­bi­li­ty of the secur­Ph­arm sys­tem can be che­cked on .
sys­tem can be che­cked at www.securpharm-status.de/.

How is the 10-day char­ge­back peri­od cal­cu­la­ted?

The char­ge­back peri­od beg­ins at the time of dere­gis­tra­ti­on and ends exact­ly after 10 calen­dar days at the same time.
days at the same time.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 17

What aspects must be taken into account for a char­ge­back?

A char­ge­back must be car­ri­ed out within the 10-day char­ge­back peri­od and may only be car­ri­ed out
only be car­ri­ed out if the pack has not left the verifier’s con­trol area.
has left the verifier’s con­trol area. =Once the sta­tus of the packa­ge has been set to “sto­len” or “des­troy­ed”, a char­ge­back is no lon­ger pos­si­ble.
rever­sal is no lon­ger pos­si­ble. The NGDA has no influence on the char­ge­back and can­not
reac­ti­va­te the pack or extend the peri­od until the dead­line expi­res.

Can the “des­troy­ed” or “sto­len” sta­tus be rever­sed?

No, the “des­troy­ed” or “sto­len” sta­tus can­not be reset. The pack may
no lon­ger be included in the sales stock.

How do I deal with recalls?

Do not deac­ti­va­te the pack if you return it to the phar­maceu­ti­cal who­le­sa­ler or com­pa­ny for dis­po­sal.
who­le­sa­ler or com­pa­ny for dis­po­sal, unless you are expli­cit­ly reques­ted to do so.
Only set the sta­tus of a pack to “Des­troy­ed” if you are dis­po­sing of it yours­elf.

What do I do with packs that have pas­sed their expiry date?

If the expiry date has been rea­ched, the pack must not be writ­ten off befo­re dis­po­sal. If the pack is
If the packa­ge is nevert­hel­ess boo­ked out befo­re dis­po­sal, an alarm is trig­ge­red. Veri­fi­ca­ti­on to check the sta­tus is still
of the sta­tus is still pos­si­ble wit­hout risk. The secur­Ph­arm sys­tem then responds with the
that the expiry date has been excee­ded and the pack must not be dis­po­sed of.

What do I have to con­sider when dis­po­sing of a dama­ged pack?

If the pack has been dama­ged at the veri­fy­ing office to such an ext­ent that it can no lon­ger be
can no lon­ger be dis­pen­sed, the code must be remo­ved from the sys­tem befo­re dis­po­sal.

Whe­re can I check whe­ther the secur­Ph­arm sys­tem is acces­si­ble?

The ope­ra­ting sta­tus of the secur­Ph­arm sub­sys­tems can be che­cked at www.securpharm-status.de
can be tra­cked.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 18

4 Deal­ing with alarms

What is an alarm or alert?

An alarm or alert is a war­ning mes­sa­ge. This mes­sa­ge pro­vi­des infor­ma­ti­on about a pos­si­ble
in the sys­tem. Depen­ding on the type of alert, dif­fe­rent actors within the secur­Ph­arm sys­tem are noti­fied.
secur­Ph­arm sys­tem are noti­fied. Sen­si­ti­ve data is sub­ject to spe­cial pro­tec­tion.
The occur­rence of a war­ning mes­sa­ge initi­al­ly says not­hing about the ori­gi­na­tor. Fur­ther­mo­re
not every alert is a fal­si­fi­ca­ti­on - tech­ni­cal errors, incom­ple­te­ly uploa­ded pack­a­ging data, pro­blems
incom­ple­te­ly uploa­ded pack­a­ging data, pro­blems with the coding, incor­rect­ly set scan­ners or
hand­ling errors (e.g. dou­ble boo­king out of a pack) can also be the cau­se.
be the cau­se.

How does an alarm occur in a veri­fy­ing point?

In a veri­fy­ing point, an alarm can be trig­ge­red both during veri­fi­ca­ti­on and when the sta­tus of a pack
sta­tus chan­ge of a packa­ge (e.g. wri­te-off).
A data com­pa­ri­son takes place during the veri­fi­ca­ti­on pro­cess. The pack data of the pack you have
pack is che­cked for con­sis­ten­cy with the data stored in the secur­Ph­arm sys­tem.
che­cked for con­sis­ten­cy. Veri­fi­ca­ti­on can be car­ri­ed out by the scan­ner or by manu­al­ly ente­ring the pack data.
pack data manu­al­ly. If the scan­ner does not read the data cor­rect­ly or a typ­ing error
the pack can­not be found in the sys­tem. This trig­gers an alarm,
This trig­gers an alarm becau­se a pack requi­ring veri­fi­ca­ti­on is being pro­ces­sed who­se iden­ti­ty is unknown to the legal sup­p­ly chain.
chain is unknown.
In the event of a sta­tus chan­ge, the exis­ting pack sta­tus is chan­ged, for exam­p­le from “rea­dy for
dis­pensable” (acti­ve) to “dis­pen­sed” (inac­ti­ve). =Howe­ver, if the desi­red pack sta­tus has alre­a­dy been set befo­re the chan­ge
alre­a­dy set befo­re the chan­ge, the attempt to chan­ge it trig­gers an alarm. In prac­ti­ce, this alarm
alarm often appears as a dou­ble check-out attempt. The cau­se may be a hand­ling error,
for exam­p­le, an inad­ver­tent wri­te-off in goods receipt and then a rene­wed wri­te-off when the goods are
when dis­pen­sing to the pati­ent. From the system’s point of view, such a pro­cess indi­ca­tes a pos­si­ble for­gery.
for­gery, as the­re is a risk that it is a copy of an ori­gi­nal pack.
ori­gi­nal pack.

What role does my scan­ner play?

The scan­ner is an important tool for recor­ding pack infor­ma­ti­on. It faci­li­ta­tes
and speeds up pro­ces­sing when dis­pen­sing packs and pre­vents incor­rect ent­ries during manu­al recor­ding.
when ente­ring infor­ma­ti­on manu­al­ly.
Howe­ver, if the scan­ner is not con­fi­gu­red cor­rect­ly, the pack data is read and trans­mit­ted incor­rect­ly.
trans­mit­ted incor­rect­ly. This can lead to an alarm becau­se the data read out does not match the data stored in the sys­tem.
stored in the sys­tem. This error pat­tern is often seen when upper and lower case
case is not read cor­rect­ly or the scan­ner swaps Y and Z (lan­guage set­ting).
ling). In prac­ti­ce, errors also fre­quent­ly occur when sepa­ra­tors are read over or
an inver­se Data Matrix code (white on a dark back­ground) is appli­ed to the pack­a­ging.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 19

To check whe­ther a scan­ner is set cor­rect­ly, plea­se test each of your scan­ners. The test
is pos­si­ble with the NGDA scan­ner test. You can obtain the cur­rent ver­si­on of the scan­ner test
at: www.securPharm.de, www.ngda.de or in the secur­Ph­arm GUI.

What must be obser­ved for manu­al ent­ry?

When ente­ring the data manu­al­ly via the secur­Ph­arm GUI, spe­cial atten­ti­on must be paid to the exact
the exact ent­ry of the pack data. In par­ti­cu­lar, the­re is a risk of con­fu­si­on
with “O” and “0” or “l” and “=”. An incor­rect ent­ry will ine­vi­ta­b­ly lead to an alarm, as the reques­ted
queried data is not stored in the sys­tem.

What is a dou­ble check-out attempt?

If a packa­ge that has alre­a­dy been boo­ked out is boo­ked out again, an alarm is trig­ge­red in the secur­Ph­arm sys­tem.
alarm is trig­ge­red in the secur­Ph­arm sys­tem. Each pack can be iden­ti­fied via the stored data (pro­duct code, seri­al no,
batch, expiry date). If a pack is boo­ked out seve­ral times, this indi­ca­tes that it has expi­red.
becau­se the­re is only one ori­gi­nal pack with this data com­bi­na­ti­on on the legal phar­maceu­ti­cal mar­ket.
phar­maceu­ti­cal mar­ket.
Uncer­tain­ty imme­dia­te­ly befo­re dis­pen­sing as to whe­ther a pack has alre­a­dy been boo­ked out or not can easi­ly ari­se.
has been boo­ked out or not can easi­ly ari­se. In this case, howe­ver, the pack should not be boo­ked out again
should not be boo­ked out again, becau­se if it has alre­a­dy been boo­ked out, an alarm is trig­ge­red. Ins­tead
Ins­tead, the sta­tus of the pack should first be che­cked (veri­fi­ca­ti­on). When veri­fy­ing
of a packa­ge known to the sys­tem, no alarm is trig­ge­red. It is gene­ral­ly
pro­ces­ses should be che­cked and, if neces­sa­ry, adjus­t­ments made to avo­id the occur­rence of
avo­id the occur­rence of dou­ble check-out attempts.
If you have inad­ver­t­ent­ly boo­ked out the packa­ge twice, you can repeat this pro­cess under cer­tain
cer­tain con­di­ti­ons (e.g. time limit).

Who is infor­med about the alarm?

With every veri­fi­ca­ti­on pro­cess and every chan­ge in the sta­tus of a pack, com­mu­ni­ca­ti­on takes place bet­ween the phar­ma­cy
bet­ween the phar­ma­cy ser­ver and the phar­maceu­ti­cal indus­try data­ba­se.
Howe­ver, the iden­ti­ty of the veri­fier remains hid­den from the phar­maceu­ti­cal indus­try data­ba­se.
howe­ver, remains hid­den from the phar­maceu­ti­cal indus­try data­ba­se. This also appli­es in the event of an alarm. The data­ba­se sys­tem of the
phar­maceu­ti­cal indus­try data­ba­se sys­tem and the phar­maceu­ti­cal com­pa­ny to which the alarm-trig­ge­ring pack
the alarm-trig­ge­ring pack the­r­e­fo­re recei­ve no infor­ma­ti­on about whe­re the alarm was trig­ge­red.
was trig­ge­red.
If an alarm is trig­ge­red, the respon­si­ble phar­maceu­ti­cal com­pa­ny is infor­med. The­re the
alarm can be clas­si­fied. Depen­ding on the assess­ment, the alarm is auto­ma­ti­cal­ly for­ward­ed to the secur­Ph­arm sys­tem.
alarm is auto­ma­ti­cal­ly for­ward­ed by the secur­Ph­arm sys­tem to the BfArM for fur­ther pro­ces­sing. The
BfArM acts as the cont­act for all super­vi­so­ry aut­ho­ri­ties.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 20

What infor­ma­ti­on is trans­mit­ted in the event of an alert?

In addi­ti­on to the pack­a­ging data (seri­al no,
seri­al num­ber, pro­duct code, batch num­ber, expiry date), the assi­gned alarm desi­gna­ti­on, an indi­vi­du­al
indi­vi­du­al iden­ti­fier of the alarm inci­dent (alarm ID), the time at which the alarm occur­red and the dyna
pseud­ony­mi­zed iden­ti­fier of the loca­ti­on that trig­ge­red the alarm.
If the­re is an auto­ma­tic or manu­al escala­ti­on by a veri­fy­ing body or the phar­maceu­ti­cal
or the phar­maceu­ti­cal com­pa­ny, the data from both data­ba­ses (PU and AP sys­tem) are mer­ged in a report.
AP sys­tem) are mer­ged into one report. The com­pe­tent super­vi­so­ry aut­ho­ri­ty has access to
this report, which is also cal­led the audit trail.
The audit trail con­ta­ins all infor­ma­ti­on on a pack. This means, in addi­ti­on to the pack data,
all tran­sac­tions (inclu­ding veri­fi­ca­ti­ons and sta­tus chan­ges) and alarm infor­ma­ti­on, the asso­cia­ted
asso­cia­ted times and the cor­re­spon­ding de-pseud­ony­mi­zed sys­tem users. Only the aut­ho­ri­ties
only the aut­ho­ri­ties are able to iden­ti­fy the respec­ti­ve veri­fy­ing body.

How is the alarm dis­play­ed in the software/merchandise manage­ment sys­tem?

An alarm is always dis­play­ed direct­ly in the soft­ware when it occurs, i.e. when an incor­rect
veri­fi­ca­ti­on pro­cess or an unsuc­cessful sta­tus chan­ge. Depen­ding on the soft­ware house
the dis­play of the “red traf­fic light” dif­fers. A war­ning win­dow is often ope­ned.
The scope of the infor­ma­ti­on dis­play­ed for the alarm also dif­fers depen­ding on the soft­ware house.
house.
His­to­ri­cal alarms can be dis­play­ed by many soft­ware manu­fac­tu­r­ers using an auto­ma­ti­cal­ly mana­ged
log in the software/merchandise manage­ment sys­tem. Plea­se also note the
secur­Ph­arm GUI.
If you have any ques­ti­ons about the dis­play and func­tion­al scope of the soft­ware pro­ducts, plea­se cont­act
plea­se cont­act your soft­ware manu­fac­tu­rer direct­ly.

Whe­re can I obtain fur­ther infor­ma­ti­on about an alarm?

In addi­ti­on to the dis­play in the phar­ma­cy software/merchandise manage­ment sys­tem, it is also pos­si­ble to use the
gra­phi­cal user inter­face of the phar­ma­cy ser­ver (secur­Ph­arm-GUI of NGDA). With
the “alarm moni­to­ring” func­tion con­tai­ned the­r­ein, the respec­ti­ve ope­ra­ting site recei­ves =infor
infor­ma­ti­on on alarm mes­sa­ges trig­ge­red by it. In addi­ti­on to mer­chan­di­se manage­ment, the
GUI pro­vi­des infor­ma­ti­on on the alarm sta­tus (crea­ted, de- and escala­ted), the alarm ID, as well as a com
a com­ment that a phar­maceu­ti­cal com­pa­ny can lea­ve when clas­si­fy­ing an alarm.
can lea­ve when clas­si­fy­ing an alarm. You can also fil­ter the alarms accor­ding to various cri­te­ria. Assis­tance
for using the user inter­face can be found in the GUI help docu­ment.
The secur­Ph­arm GUI is available at the fol­lo­wing link: https://securpharm-gui.ngda.de/
Plea­se note that the error codes dis­play­ed in the ERP sys­tem may dif­fer from tho­se in the GUI.
may dif­fer. A table of error codes can be found in the GUI help docu­ment.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 21

How to deal with packs who­se authen­ti­ci­ty could not be suc­cessful­ly veri­fied or a sta­tus chan­ge
or a sta­tus chan­ge is not suc­cessful?

In prin­ci­ple, a pack who­se veri­fi­ca­ti­on is nega­ti­ve must not be dis­pen­sed and must be sepa­ra­ted.
and must be sepa­ra­ted. In order to con­firm or refu­te the sus­pi­ci­on of a coun­ter­feit, an error ana­ly­sis must be car­ri­ed out.
an error ana­ly­sis must be car­ri­ed out. It is the­r­e­fo­re essen­ti­al that
veri­fy­ing bodies actively deal with the error mes­sa­ges that have occur­red in their
and get to the bot­tom of the cau­ses. At the same time, the respon­si­ble
phar­maceu­ti­cal com­pa­ny can initia­te an inves­ti­ga­ti­on.
The result of the phar­maceu­ti­cal company’s ana­ly­sis (alarm sta­tus and, if appli­ca­ble, com­ma
tary) can be che­cked via the alarm moni­to­ring in the secur­Ph­arm GUI (https://securpharm-gui.ngda.de/) using the alarm sta­tus.
can be che­cked using the alarm sta­tus. If, at the same time, the ana­ly­sis in the veri­fy­ing body
no good reasons to assu­me that a tech­ni­cal error or own hand­ling errors (e.g. acci­den­tal
(e.g. inad­ver­tent dere­co­gni­ti­on in the inco­ming goods depart­ment) is the reason for the alarm, the
pack­a­ging must con­ti­nue to be sepa­ra­ted and the offi­ci­al report­ing chan­nels must be fol­lo­wed.
If the sus­pi­ci­on of coun­ter­feit­ing is inva­li­da­ted by the error ana­ly­sis and the­re are no fur­ther
evi­dence of coun­ter­feit­ing, the pack can be released again. Plea­se note that
only “dis­pensable” (acti­ve) packs can be boo­ked out and dis­pen­sed. Make sure
the pack sta­tus by scan­ning (veri­fy­ing) the pack and only then pick up the pack again.
only then add the pack to the sales stock again.

How does the respon­si­ble phar­maceu­ti­cal com­pa­ny check an alert?

After an alarm has occur­red, the alarm can be review­ed by the respon­si­ble phar­maceu­ti­cal com­pa­ny within a time win­dow of seven calen­dar days.
days by the respon­si­ble phar­maceu­ti­cal com­pa­ny. If the respon­si­ble
If the respon­si­ble phar­maceu­ti­cal com­pa­ny deter­mi­nes that it is a fal­se alarm within the time win­dow, it is clas­si­fied as such
and thus de-escala­ted. If no reason for a fal­se alarm is found, the alarm must be clas­si­fied as a po
ten­ti­al case of suspec­ted fal­si­fi­ca­ti­on and the­r­e­fo­re escala­ted. If no assess­ment is made within the
If no assess­ment is made within the dead­line, the alarm is also auto­ma­ti­cal­ly escala­ted.
Plea­se note that the phar­maceu­ti­cal com­pa­ny may only esca­la­te the alarm in the case of errors that it has
errors (e.g. miss­ing data upload, incor­rect expiry date uploa­ded, incor­rect­ly prin­ted pack, etc.).
prin­ted pack, etc.) can only be de-escala­ted. It is the­r­e­fo­re all the more important that you
veri­fy­ing point, check the scan­ner set­tings and adjust the pro­ces­ses if neces­sa­ry.
adjust the pro­ces­ses if neces­sa­ry.
If an escala­ti­on occurs, the alarm mes­sa­ge is for­ward­ed by the secur­Ph­arm sys­tem to the BfArM.
for­ward­ed. The BfArM acts as the cont­act for all super­vi­so­ry aut­ho­ri­ties.
Plea­se note any report­ing obli­ga­ti­ons that exist inde­pendent­ly of the eva­lua­ti­on by the phar
phar­maceu­ti­cal com­pa­ny.

May a pack that has trig­ge­red an alarm be retur­ned to the sales stock befo­re the com­pe­tent
befo­re the review by the respon­si­ble phar­maceu­ti­cal com­pa­ny has been com­ple­ted?
has been com­ple­ted?

The decisi­ve fac­tor for the return to sales stock is the pack sta­tus, which is

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 22

first-ope­ning pro­tec­tion and the assess­ment of the veri­fy­ing body.
If, after careful ana­ly­sis, the­re are good reasons to assu­me that a tech­ni­cal error or own hand­ling
tech­ni­cal error or own hand­ling errors (e.g. inad­ver­tent wri­te-off in the inco­ming goods depart­ment) were
were the reason for the alarm and the­re are no other indi­ca­ti­ons of coun­ter­feit­ing, the sus­pi­ci­on can be
coun­ter­feit­ing, the sus­pi­ci­on of coun­ter­feit­ing can be refu­ted even wit­hout the exami­na­ti­on of the phar­maceu­ti­cal
com­pa­ny can be refu­ted. Manu­al veri­fi­ca­ti­on, the tran­sac­tion over­view in the soft­ware and the
over­view in the soft­ware as well as the alarm moni­to­ring in the secur­Ph­arm GUI can be hel­pful here.
(https://securpharm-gui.ngda.de/).
In addi­ti­on to the error ana­ly­sis and the veri­fy­ing body’s assess­ment of the
the pack­a­ging sta­tus in the secur­Ph­arm sys­tem is rele­vant for the assess­ment of dis­pensa­bi­li­ty.
eli­gi­bi­li­ty for dis­pen­sing. Only packs with the sta­tus “dis­pensable” may be included in the sales stock.
be included in the sales inven­to­ry.

What is the dif­fe­rence bet­ween alarm sta­tus and pack sta­tus?

The sta­tus of the alarm expres­ses whe­ther an alarm could indi­ca­te an actu­al suspec­ted case of coun­ter­feit­ing
or whe­ther a fal­se alarm has been trig­ge­red. The sta­tus of the pack deter­mi­nes whe­ther
the pack is “dis­pensable” (acti­ve) or not, wher­eby other fac­tors can rest­rict the dis­pensa­bi­li­ty despi­te the
acti­ve sta­tus. The pack sta­tus and alarm sta­tus can be che­cked via the
soft­ware and the secur­Ph­arm GUI.

What is the secur­Ph­arm GUI?

The secur­Ph­arm GUI is the web inter­face of the NGDA’s secur­Ph­arm phar­ma­cy ser­ver. GUI
stands for Gra­phi­cal User Inter­face. Via the GUI, a
veri­fy­ing body can access the fol­lo­wing func­tions via the GUI:
(a) Manu­al veri­fi­ca­ti­on and wri­te-off of medi­ci­nes sub­ject to veri­fi­ca­ti­on.
This opti­on allows you to manu­al­ly veri­fy medi­cinal pro­ducts sub­ject to man­da­to­ry veri­fi­ca­ti­on
and the opti­on to chan­ge the sta­tus of the pack. This func­tion is par­ti­cu­lar­ly useful in the event of
in the mer­chan­di­se manage­ment sys­tem.
b) Alarm moni­to­ring
The alarm moni­to­ring sys­tem pro­vi­des you with an over­view of alarms that have occur­red in your
and infor­ma­ti­on on the eva­lua­ti­on of the alarm. With the help of a search and
sort­ing func­tion, indi­vi­du­al alarms can be fil­te­red out. This infor­ma­ti­on can be hel­pful
to cla­ri­fy alarms, detect sources of error and avo­id them.
The secur­Ph­arm GUI is available at the fol­lo­wing link: https://securpharm-gui.ngda.de/
Plea­se also refer to the GUI alarm moni­to­ring docu­men­ta­ti­on, which you can find in the GUI under the
tab: “:help”.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 23

Whe­re can I view all tran­sac­tions (veri­fi­ca­ti­ons and sta­tus chan­ges) of my busi­ness pre­mi­ses?
retrie­ve?

Many soft­ware com­pa­nies offer the opti­on of using their soft­ware to view the pre­vious actions
in con­nec­tion with the Dele­ga­ted Regu­la­ti­on (sta­tus veri­fi­ca­ti­on and chan­ge).
to under­stand. This check is car­ri­ed out via a pro­to­col or log file. If you have any ques­ti­ons about this
plea­se cont­act your soft­ware manu­fac­tu­rer.

When is a suspec­ted case of fal­si­fi­ca­ti­on repor­ted to the aut­ho­ri­ties by the secur­Ph­arm sys­tem?
repor­ted?

After an alarm has occur­red in the sys­tem, this alarm can be repor­ted to the aut­ho­ri­ties by the respon­si­ble phar­maceu­ti­cal
phar­maceu­ti­cal com­pa­ny within a time win­dow of seven calen­dar days.
days. The result can be view­ed in the secur­Ph­arm GUI in the respec­ti­ve alarm sta­tus. If the phar­maceu­ti­cal
phar­maceu­ti­cal entre­pre­neur deter­mi­nes within this time win­dow that it is a fal­se alarm
is a fal­se alarm, it is clas­si­fied as such and thus de-escala­ted. De-escala­ti­on eli­mi­na­tes the need for au
auto­ma­tic noti­fi­ca­ti­on by the sys­tem. If no reason for a fal­se alarm is found, the alarm must be
the alarm must be clas­si­fied as a poten­ti­al case of suspec­ted fal­si­fi­ca­ti­on and the­r­e­fo­re escala­ted. If
If no assess­ment is made within the dead­line, the alarm is also escala­ted auto­ma­ti­cal­ly.
If an escala­ti­on occurs, the alarm mes­sa­ge is for­ward­ed by the secur­Ph­arm sys­tem to the BfArM.
for­ward­ed. The BfArM acts as the cont­act for all super­vi­so­ry aut­ho­ri­ties.
In this con­text, plea­se note that the com­pe­tent super­vi­so­ry aut­ho­ri­ties have a right to all infor­ma­ti­on
infor­ma­ti­on neces­sa­ry to check com­pli­ance with the Dele­ga­ted Regu­la­ti­on. Not appli­ca­ble
If the veri­fy­ing enti­ty or the secur­Ph­arm sys­tem fails to sub­mit a noti­fi­ca­ti­on, the super­vi­so­ry
aut­ho­ri­ties can still view all infor­ma­ti­on (inclu­ding tran­sac­tions and alarms) for this packa­ge.
pack can still be dis­play­ed.

When do I have to report an alert to the aut­ho­ri­ties?

An alarm could always indi­ca­te coun­ter­feit­ing. You should the­r­e­fo­re act imme­dia­te­ly. Inves­ti­ga­te
Inves­ti­ga­te the pack and the alarm, using all the infor­ma­ti­on available to you.
infor­ma­ti­on available to you (e.g. assess­ment of the alarm sta­tus by the respon­si­ble com­pa­ny, manu­al input and
and scan­ner test or the tran­sac­tion histo­ry in the soft­ware if available). Regar­ding the
Plea­se con­sult the rele­vant legis­la­ti­on for infor­ma­ti­on on report­ing dead­lines and chan­nels.

What infor­ma­ti­on does the aut­ho­ri­ty have access to?

Com­pe­tent super­vi­so­ry aut­ho­ri­ties have a right to all infor­ma­ti­on neces­sa­ry to veri­fy com­pli­ance with the Dele­ga­ted Regu­la­ti­on.
com­pli­ance with the Dele­ga­ted Regu­la­ti­on. This includes infor­ma­ti­on on alerts, but
the tran­sac­tion histo­ry of a packa­ge, inclu­ding veri­fi­ca­ti­ons and wri­te-offs. To obtain the
infor­ma­ti­on from the data repo­si­to­ry, secur­Ph­arm per­forms a de-pseud­ony­miza­ti­on of the ori­gi­na­ting
miza­ti­on of the ori­gi­na­tor towards the aut­ho­ri­ty. The iden­ti­ty of the veri­fy­ing
The iden­ti­ty of the veri­fy­ing body remains hid­den from the data­ba­se of the phar­maceu­ti­cal indus­try.
Up to now, the super­vi­so­ry aut­ho­ri­ties have acces­sed the data­ba­se by indi­vi­du­al­ly query­ing the so-cal­led
audit trails and the alert ID via the secur­Ph­arm office.

30.06.2021 Ver­si­on 1 crea­ted by secur­Ph­arm e. V. 24

In the future, this pro­cess will be auto­ma­ted and aut­ho­ri­ties will have direct access. Poten­ti­al
poten­ti­al vio­la­ti­ons of the Fal­si­fied Medi­ci­nes Direc­ti­ve can be tra­cked even more easi­ly and com­pre­hen­si­ve­ly.
more easi­ly and com­pre­hen­si­ve­ly. The respec­ti­ve asso­cia­ti­ons of the user groups will be infor­med in advan­ce.
inform in advan­ce.

Why should you deal with the secur­Ph­arm sys­tem and alarms?

In addi­ti­on to ful­fil­ling the legal requi­re­ments, each indi­vi­du­al user con­tri­bu­tes to main­tai­ning the high level of safe­ty in the legal phar­maceu­ti­cal trade.
level of safe­ty in the legal phar­maceu­ti­cal trade.
For the anti-coun­ter­feit­ing sys­tem to work, any alarms that occur must be regis­tered and cate­go­ri­zed.
clas­si­fied. The key ques­ti­on here is whe­ther the alarm indi­ca­tes a coun­ter­feit or a fal­se alarm.
a fal­se alarm.
So inves­ti­ga­te the cau­se and fami­lia­ri­ze yours­elf even more with the secur­Ph­arm sys­tem.
sys­tem: “What does the error code that appears when scan­ning or chan­ging the sta­tus of the pack mean?
“How do I reco­gni­ze a packa­ge that has been boo­ked out twice?”; “Is the scan­ner set up cor­rect­ly?“
cor­rect­ly set?”; “Which alarms indi­ca­te an incom­ple­te data upload?”; “What is the
secur­Ph­arm-GU=?”, “Who can help me with pro­blems and ques­ti­ons?”

Does the secur­Ph­arm sys­tem report a suspec­ted case of fal­si­fi­ca­ti­on to the super­vi­so­ry aut­ho­ri­ty?

4.20: Does the secur­Ph­arm sys­tem report a suspec­ted case of coun­ter­feit­ing to the super­vi­so­ry aut­ho­ri­ty?
Alarms are always stored in the secur­Ph­arm sys­tem so that they are available for pro­ces­sing by the aut­ho­ri­ties.
available for pro­ces­sing by the aut­ho­ri­ties. Aut­ho­ri­ties that recei­ve a suspec­ted fal­si­fied
repor­ted by mar­ket par­ti­ci­pan­ts using the data from the secur­Ph­arm sys­tem
from the secur­Ph­arm sys­tem curr­ent­ly still have to inqui­re with secur­Ph­arm to obtain the cor­re­spon­ding audit trails.
recei­ve the cor­re­spon­ding audit trails. After the plan­ned con­nec­tion of the aut­ho­ri­ties to the secur­Ph­arm sys­tem, they will have
will then have direct access to the data from the sys­tem.
It is also plan­ned that the secur­Ph­arm sys­tem will pro­vi­de the Fede­ral Insti­tu­te for Drugs and
Medi­cal Devices (BfArM) auto­ma­ti­cal­ly as soon as an alarm is escala­ted in the sys­tem.
The BfArM then coor­di­na­tes the cases in con­sul­ta­ti­on with the Paul Ehr­lich Insti­tu­te (PEI), enters them
into its own offi­ci­al coun­ter­feit data­ba­se and informs the super­vi­so­ry aut­ho­ri­ty respon­si­ble for the phar­maceu­ti­cal
respon­si­ble super­vi­so­ry aut­ho­ri­ty for the phar­maceu­ti­cal com­pa­ny.
The noti­fi­ca­ti­on by the secur­Ph­arm sys­tem is an addi­tio­nal noti­fi­ca­ti­on that does not replace the pre­vious
report­ing obli­ga­ti­ons of the mar­ket play­ers. The pre­vious report­ing obli­ga­ti­ons con­ti­nue to app­ly in the event of
a well-foun­ded sus­pi­ci­on of fal­si­fi­ca­ti­on.

Downloads & Links

Checkliste für den Systemzugang

In der Verfassung vom 15. Dezember 2022pdf, 112,27 KB

Aide Memoire der EU-Kommission für Inspektionen

In der Verfassung vom 20. Januar 2020pdf, 662,50 KB

Aktuelle Neuigkeiten

Joint gui­de­lines for alarm hand­ling in Ger­ma­ny - Uni­form approach for more secu­ri­ty in the sup­p­ly chain

06 November 2025

Updated secur­Ph­arm coding rules

20 Oktober 2025