A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"SA_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"SA_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"SA_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"SA_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"SA_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"SA_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"SA_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"SA_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"SA_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"SA_registration_faq_227":{"text":"Yes, all drugs are tracked including unregistered drugs and must be reported upon every step in the supply chain."},"SA_registration_faq_10":{"text":"

RSD (Rassd) is Saudi Arabia's pharmaceutical track and trace system, operated by the Saudi Food and Drug Authority (SFDA).

It mandates serialization and EPCIS reporting for all pharmaceutical products in the Saudi market.

View Saudi Arabia regulations

"},"SA_registration_faq_228":{"text":"Registration is optional for foreign manufacturers. They must either register through their KSA scientific office or authorize an agent to manage their account via authorization form."},"SA_registration_faq_229":{"text":"No, the RSD system rejects duplicated license numbers or GLNs for multiple registrations. Each entity must have unique identifiers."},"SA_registration_faq_230":{"text":"Yes, it is mandatory to register each location independently and track operations between them."},"SA_registration_faq_231":{"text":"All medications will be added automatically in the system within two days of approval by SFDA."},"SA_registration_faq_232":{"text":"No, you cannot use the same serial number on drugs that have the same GTIN. Each serial must be unique per GTIN."},"SA_registration_faq_233":{"text":"Yes, all movement of drugs should be reported on the system until the drug is sold to the end consumer."},"SA_registration_faq_234":{"text":"RSD responds immediately in real time for all reporting submissions."},"SA_registration_faq_235":{"text":"Report after finishing all the processes inside the establishment. Batch reporting is acceptable."},"SA_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"SA_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"SA_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"SA_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"SA_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"SA_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"SA_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"SA_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"SA_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"SA_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"SA_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"SA_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"SA_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"SA_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"SA_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"SA_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"SA_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"SA_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"SA_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"SA_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"AE_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"AE_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"AE_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"AE_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"AE_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"AE_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"AE_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"AE_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"AE_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"AE_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"AE_registration_faq_201":{"text":"Tatmeen is a Ministry of Health and Prevention digital platform that enables the tracking and tracing of all pharmaceutical products in the UAE. It ensures product authenticity and safety throughout the supply chain."},"AE_registration_faq_7":{"text":"

TATMEEN is the UAE's national pharmaceutical track and trace system, operated by the Ministry of Health and Prevention (MoHAP).

It requires manufacturers and importers to serialize products and report EPCIS events throughout the supply chain.

View UAE regulations

"},"AE_registration_faq_202":{"text":"Serialisation is the application of a GS1 approved 2D Matrix barcode and human readable information onto all drug secondary packing. This enables unique identification of each product unit."},"AE_registration_faq_203":{"text":"Tatmeen became operational on December 13th, 2022, which was 18 months after the decree was issued on June 14, 2021."},"AE_registration_faq_204":{"text":"Supply Chain Partners are organizations collaborating to move pharmaceuticals from manufacturer to consumer. This includes MAHs (Marketing Authorization Holders), Licensed Agents, 3PL companies, and dispensaries."},"AE_registration_faq_205":{"text":"The decree applies to all supply chain participants that produce, transport, store, or dispense pharmaceutical products in the UAE."},"AE_registration_faq_8":{"text":"

To register with TATMEEN:

Visit the TATMEEN portal at tatmeen.mohap.gov.ae
Complete the company registration form
Submit required documents (trade license, drug registration certificates)
Wait for approval from MoHAP
Receive credentials and begin integration testing

View complete UAE onboarding guide

"},"AE_registration_faq_206":{"text":"Tatmeen applies to Conventional and Biological Medicines in the first phase. Other product categories will follow in subsequent phases."},"AE_registration_faq_207":{"text":"Yes, barcodes apply to both registered and unregistered drugs that are distributed in the UAE."},"AE_registration_faq_208":{"text":"No special software is required. Companies can use a web browser, mobile app, or connect their ERP/WMS systems via B2B API integration."},"AE_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"AE_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"AE_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"AE_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"AE_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"AE_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"AE_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"AE_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"AE_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"AE_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"AE_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"AE_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"AE_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"AE_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"AE_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"AE_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"AE_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"AE_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"AE_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"AE_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"NG_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"NG_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"NG_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"NG_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"NG_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"NG_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"NG_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"NG_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"NG_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"NG_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"NG_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"NG_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"NG_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"NG_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"NG_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"NG_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"NG_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"NG_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"NG_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"NG_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"NG_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"NG_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"NG_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"NG_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"NG_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"NG_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"NG_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"NG_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"NG_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"NG_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"BH_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"BH_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"BH_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"BH_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"BH_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"BH_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"BH_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"BH_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"BH_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"BH_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"BH_registration_faq_250":{"text":"Yes, all invoicing companies (MAHs/manufacturers), agents/distributors, and dispensers must register with NHRA-MVC. MAHs require proof of drug registration in the DUR, a Global Location Number, and a Company Prefix from GS1."},"BH_registration_faq_14":{"text":"

NHRA-MVC (Medicine Verification Center) is Bahrain's pharmaceutical track and trace system, operated by the National Health Regulatory Authority (NHRA).

View Bahrain regulations

"},"BH_registration_faq_251":{"text":"Yes. All legally registered invoicing companies must enroll, sign a Participation Agreement, and pay required fees to support hub maintenance."},"BH_registration_faq_252":{"text":"Yes, both registrations are required. BrandSync submission is mandated by the Medicines Barcoding and Serialization Guideline for product master information. NHRA-MVC tracks medicines from shipment through dispensing."},"BH_registration_faq_253":{"text":"The process involves 10 steps: obtaining a Company Prefix, assigning numbers, selecting printing processes, environments, barcode types, sizes, formatting, colors, placement, and building quality plans."},"BH_registration_faq_254":{"text":"Use the GS1 Lookup Directory or consult your GS1 membership documentation for assigned GLN and GCP numbers."},"BH_registration_faq_107":{"text":"

NHRA (National Health Regulatory Authority) is Bahrain's healthcare regulatory body responsible for:

Medicine and medical device regulation
Healthcare facility licensing
Track and trace compliance

"},"BH_registration_faq_255":{"text":"Aggregation defines parent-child barcode relationships, allowing receivers to scan one code for complete shipment details at case and pallet levels."},"BH_registration_faq_256":{"text":"Both secondary (case/shipper) and tertiary (pallet) packaging require serialization. SGTIN for units/cases and SSCC for pallets."},"BH_registration_faq_257":{"text":"Registration involves two stages: first connecting to the TEST hub with formatted data files, then to PRODUCTION for operations once certified."},"BH_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"BH_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"BH_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"BH_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"BH_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"BH_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"BH_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"BH_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"BH_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"BH_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"BH_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"BH_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"BH_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"BH_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"BH_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"BH_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"BH_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"BH_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"BH_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"BH_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"EG_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"EG_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"EG_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"EG_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"EG_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"EG_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"EG_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"EG_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"EG_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"EG_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"EG_registration_faq_273":{"text":"

Expired products are reported as a “Decommission Event.”

Example: Batch B123 expired Dec 2026 → all serials from B123 marked “Decommissioned – Expired.”

"},"EG_registration_faq_282":{"text":"

Only if current ones can’t read 2D Data Matrix codes.

"},"EG_registration_faq_281":{"text":"

The reporting model will be vertical, with all traceability events reported directly to the national hub. At this stage, no requirements have been defined for partner-to-partner data sharing.

"},"EG_registration_faq_280":{"text":"

The EDA Unified National Track & Trace Platform will follow a centralized model, requiring all traceability events to be reported directly to the national hub

"},"EG_registration_faq_279":{"text":"

Integration is via GS1 EPCIS standards. Data can be transmitted using secure APIs or file exchanges in XML/JSON/CSV formats. Detailed technical specifications and API documentation are provided during company onboarding. A dedicated company Technical Helpdesk is available to support manufacturers and importers during integration.

"},"EG_registration_faq_278":{"text":"

Yes. During the transition stage, factories that do not have DataMatrix printing capability on their packaging lines may apply to use alternate carriers such as RFID or NFC.

These carriers will temporarily represent the same GS1 DataMatrix data (GTIN, UID, Batch, Expiry) until the factory is ready to upgrade its printing technology.

Conditions:

• The alternate carrier must hold the same information as the GS1 DataMatrix.

• The company must provide the necessary middleware or mapping to ensure the data is fully compatible with the national Track & Trace system.

• This option is temporary. After the transition period, only GS1 DataMatrix printed on-pack will be accepted.

Please review the standard published by GS1 (link below) concerning use of RFID as an example of what EDA MIGHT approve. https://www.gs1.org/standards/rfid

"},"EG_registration_faq_277":{"text":"

The 3PL records aggregation, shipping, and receiving using its GLN.

"},"EG_registration_faq_276":{"text":"

Yes. 3PLs within Egypt must register GLNs and are responsible for reporting aggregation, shipping, and receiving events from their facilities. Regional Hubs outside Egypt need not register with GLN. Brand owners remain accountable to EDA for ensuring 3PL compliance.

"},"EG_registration_faq_275":{"text":"

Local Products: For local manufacturers, commissioning and aggregation must be recorded as events directly in the national system at the time of packaging.

Imported Products: EPCIS data must be uploaded before the products enter Egypt.

o If shipments are consolidated at regional hubs, EPCIS reporting can take place at the point of dispatch from the hub, provided it is before Egyptian customs clearance.

o Commissioning and aggregation events performed outside Egypt are not registered as events in the national system. Instead, importers must upload the related data files as reference.

o Once the shipment physically enters Egypt and receives customs release and EDA approval, these transactions must then be recorded as official trackable events in the national system.

Example:

A company imports 100,000 packs from a foreign manufacturer. EPCIS data is uploaded prior to clearance at Alexandria Port or Cairo Airport. Once cleared by customs and approved by EDA, the commissioning and aggregation events for those packs are entered into the system as official events.

"},"EG_registration_faq_274":{"text":"

The manufacturer or importer initiates a “Recall Event.” All affected serials are blocked. Pharmacies scanning them will receive “Invalid – Recalled.”

"},"EG_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"EG_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"EG_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"EG_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"EG_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"EG_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"EG_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"EG_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"EG_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"EG_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"EG_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"EG_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"EG_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"EG_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"EG_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"EG_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"EG_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"EG_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"EG_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"EG_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"ET_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"ET_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"ET_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"ET_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"ET_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"ET_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"ET_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"ET_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"ET_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"ET_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"ET_registration_faq_259":{"text":"Yes, registration is required per the Pharmaceutical Products Traceability Directive No 43/2019 and related directives issued by EFDA."},"ET_registration_faq_260":{"text":"Yes. All supply chain participants must obtain a Global Location Number (GLN) to identify their organizations and key operational locations per the traceability directive."},"ET_registration_faq_261":{"text":"Invoicing Companies and Marketing Authorization Holders must register with GS1. GLN and GCP information can be found using the GS1 Lookup Directory and GTIN Management site."},"ET_registration_faq_262":{"text":"Aggregation defines parent-child barcode relationships, allowing receivers to scan one code and understand complete shipment contents. Serialized GTINs are used at unit and case levels; SSCC applies to pallets."},"ET_registration_faq_263":{"text":"The registration process involves administrative registration and technical onboarding, including TEST hub connection and PRODUCTION hub go-live after demonstrating compliance."},"ET_registration_faq_264":{"text":"The Invoicing Company is the entity handling invoicing, which may be the manufacturer or a separate company managing pharmaceutical distribution."},"ET_registration_faq_265":{"text":"Yes, all legally registered Invoicing Companies must be EFDA-approved, complete signup, sign participation agreements, and pay required fees."},"ET_registration_faq_266":{"text":"Complete MAH approval with EFDA, register with GS1, obtain GLN and GTIN, visit EFDA-MVC portal, complete the application form, finalize participation agreement, then begin technical onboarding."},"ET_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"ET_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"ET_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"ET_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"ET_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"ET_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"ET_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"ET_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"ET_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"ET_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"ET_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"ET_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"ET_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"ET_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"ET_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"ET_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"ET_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"ET_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"ET_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"ET_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"GH_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"GH_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"GH_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"GH_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"GH_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"GH_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"GH_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"GH_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"GH_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"GH_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"GH_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"GH_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"GH_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"GH_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"GH_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"GH_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"GH_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"GH_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"GH_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"GH_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"GH_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"GH_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"GH_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"GH_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"GH_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"GH_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"GH_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"GH_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"GH_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"GH_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"GW_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"GW_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"GW_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"GW_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"GW_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"GW_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"GW_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"GW_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"GW_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"GW_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"GW_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"GW_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"GW_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"GW_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"GW_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"GW_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"GW_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"GW_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"GW_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"GW_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"GW_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"GW_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"GW_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"GW_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"GW_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"GW_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"GW_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"GW_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"GW_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"GW_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"JO_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"JO_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"JO_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"JO_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"JO_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"JO_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"JO_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"JO_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"JO_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"JO_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"JO_registration_faq_15":{"text":"

Jordan's serialization requirements are managed by the Jordan Food and Drug Administration (JFDA):

Unit-level serialization with DataMatrix barcode
GTIN, serial number, batch, and expiry encoding
EPCIS event reporting
Focus on high-risk and imported products initially

View Jordan regulations

"},"JO_registration_faq_112":{"text":"

JFDA (Jordan Food and Drug Administration) is the regulatory authority responsible for:

Food and drug safety
Product registration
Track and trace requirements
Import/export control

"},"JO_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"JO_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"JO_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"JO_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"JO_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"JO_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"JO_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"JO_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"JO_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"JO_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"JO_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"JO_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"JO_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"JO_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"JO_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"JO_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"JO_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"JO_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"JO_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"JO_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"GM_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"GM_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"GM_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"GM_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"GM_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"GM_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"GM_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"GM_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"GM_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"GM_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"GM_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"GM_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"GM_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"GM_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"GM_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"GM_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"GM_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"GM_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"GM_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"GM_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"GM_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"GM_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"GM_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"GM_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"GM_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"GM_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"GM_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"GM_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"GM_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"GM_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"IQ_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"IQ_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"IQ_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"IQ_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"IQ_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"IQ_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"IQ_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"IQ_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"IQ_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"IQ_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"IQ_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"IQ_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"IQ_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"IQ_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"IQ_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"IQ_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"IQ_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"IQ_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"IQ_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"IQ_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"IQ_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"IQ_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"IQ_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"IQ_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"IQ_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"IQ_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"IQ_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"IQ_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"IQ_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"IQ_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"KE_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"KE_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"KE_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"KE_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"KE_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"KE_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"KE_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"KE_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"KE_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"KE_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"KE_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"KE_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"KE_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"KE_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"KE_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"KE_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"KE_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"KE_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"KE_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"KE_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"KE_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"KE_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"KE_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"KE_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"KE_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"KE_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"KE_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"KE_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"KE_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"KE_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"LB_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"LB_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"LB_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"LB_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"LB_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"LB_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"LB_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"LB_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"LB_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"LB_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"LB_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"LB_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"LB_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"LB_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"LB_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"LB_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"LB_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"LB_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"LB_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"LB_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"LB_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"LB_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"LB_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"LB_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"LB_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"LB_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"LB_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"LB_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"LB_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"LB_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"LY_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"LY_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"LY_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"LY_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"LY_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"LY_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"LY_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"LY_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"LY_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"LY_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"LY_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"LY_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"LY_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"LY_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"LY_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"LY_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"LY_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"LY_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"LY_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"LY_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"LY_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"LY_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"LY_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"LY_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"LY_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"LY_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"LY_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"LY_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"LY_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"LY_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"RW_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"RW_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"RW_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"RW_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"RW_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"RW_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"RW_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"RW_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"RW_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"RW_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"RW_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"RW_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"RW_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"RW_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"RW_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"RW_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"RW_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"RW_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"RW_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"RW_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"RW_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"RW_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"RW_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"RW_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"RW_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"RW_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"RW_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"RW_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"RW_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"RW_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"za_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"za_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"za_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"za_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"za_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"za_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"za_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"za_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"za_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"za_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"za_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"za_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"za_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"za_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"za_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"za_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"za_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"za_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"za_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"za_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"za_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"za_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"za_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"za_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"za_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"za_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"za_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"za_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"za_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"za_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"UG_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"UG_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"UG_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"UG_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"UG_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"UG_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"UG_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"UG_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"UG_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"UG_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"UG_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"UG_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"UG_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"UG_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"UG_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"UG_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"UG_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"UG_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"UG_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"UG_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"UG_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"UG_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"UG_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"UG_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"UG_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"UG_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"UG_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"UG_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"UG_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"UG_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"ZW_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"ZW_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"ZW_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"ZW_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"ZW_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"ZW_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"ZW_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"ZW_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"ZW_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"ZW_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"ZW_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"ZW_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"ZW_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"ZW_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"ZW_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"ZW_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"ZW_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"ZW_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"ZW_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"ZW_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"ZW_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"ZW_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"ZW_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"ZW_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"ZW_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"ZW_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"ZW_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"ZW_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"ZW_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"ZW_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"},"DZ_general_faq_186":{"text":"

A verification response confirms product authenticity:

GTIN + Serial + Lot + Expiry verified
Response: Valid/Invalid/Unknown
Required at point of dispense
Real-time query to repository

"},"DZ_general_faq_188":{"text":"

Lot number: Identifies production batch (many units share same lot)
Serial number: Unique identifier for each unit

Both required for full traceability
Lot = quality tracking
Serial = individual tracking

"},"DZ_general_faq_181":{"text":"

Master data is reference information:

Product data (GTIN, description)
Location data (GLN, address)
Trading partner data
Must be synchronized across systems

"},"DZ_general_faq_187":{"text":"

Batch traceability tracks products by production batch:

Same lot number = same production run
Enables batch-level recalls
Links to quality records
Part of GMP requirements

"},"DZ_general_faq_190":{"text":"

Exception handling manages serialization issues:

Rejected units on line
Failed submissions to portal
Verification failures
Data discrepancies

Requires documented procedures.

"},"DZ_general_faq_184":{"text":"

Key difference:

Master data: Static reference data (product info, locations)
Event data: Dynamic transaction records (what, when, where, why)

Both needed for complete traceability.

"},"DZ_general_faq_182":{"text":"

Data synchronization keeps data consistent:

Between internal systems
With trading partners
With regulatory portals
Critical for EPCIS accuracy

"},"DZ_general_faq_185":{"text":"

Compliance reports demonstrate regulatory adherence:

Serialization status by product
Event submission statistics
Error rates and resolution
Required for audits

"},"DZ_general_faq_183":{"text":"

A transaction ID links business transactions:

Purchase order number
Invoice number
Delivery note number
Required in EPCIS transaction events

"},"DZ_general_faq_189":{"text":"

Data retention requirements:

Keep records for specified period
Typically 1 year after expiry + buffer
Country-specific requirements
Must be retrievable for audits

"},"DZ_technical_faq_66":{"text":"

EPCIS stands for Electronic Product Code Information Services. It is a GS1 standard for sharing event data between trading partners in the supply chain.

"},"DZ_technical_faq_67":{"text":"

EPCIS defines four event types:

ObjectEvent: Observation of objects (commissioning, shipping, receiving)
AggregationEvent: Parent-child relationships (packing/unpacking)
TransactionEvent: Links objects to business transactions
TransformationEvent: Input/output relationships (manufacturing)

"},"DZ_technical_faq_68":{"text":"

An ObjectEvent captures observations about objects at a point in time. Common uses:

Commissioning (serial number activation)
Shipping (products leaving a location)
Receiving (products arriving)
Dispensing (products given to patient)

Action types: ADD, OBSERVE, DELETE

"},"DZ_technical_faq_69":{"text":"

An AggregationEvent records parent-child relationships between containers and their contents:

ADD: Items packed into a container
DELETE: Items unpacked from a container
OBSERVE: Confirmation of aggregation

Essential for case and pallet tracking.

"},"DZ_technical_faq_73":{"text":"

Common bizStep values in pharmaceutical track and trace:

commissioning: Serial number activation
packing: Items packed into container
shipping: Products shipped
receiving: Products received
dispensing: Given to patient
destroying: Product destruction

"},"DZ_technical_faq_77":{"text":"

EPCs (Electronic Product Codes) in EPCIS follow URN format:

SGTIN: urn:epc:id:sgtin:CompanyPrefix.ItemRef.Serial
SSCC: urn:epc:id:sscc:CompanyPrefix.SerialRef
GLN: urn:epc:id:sgln:CompanyPrefix.LocationRef.Extension

"},"DZ_technical_faq_72":{"text":"

CBV (Core Business Vocabulary) defines standard values for EPCIS fields:

Business steps (commissioning, shipping, receiving)
Dispositions (active, inactive, recalled)
Business transaction types
Source/Destination types

Using CBV ensures interoperability between systems.

"},"DZ_technical_faq_78":{"text":"

EPCIS 2.0 is the latest version of the standard with new features:

JSON-LD support (in addition to XML)
REST API bindings
Sensor data integration
Digital link URIs
Enhanced CBV 2.0

EPCIS 2.0 was released in 2022.

"},"DZ_technical_faq_74":{"text":"

Disposition indicates the business state of objects after an event:

active: Normal, sellable state
inactive: Not available for sale
recalled: Subject to recall
expired: Past expiry date
destroyed: Physically destroyed

"},"DZ_technical_faq_76":{"text":"

An EPCIS Repository is a system that stores EPCIS events and provides:

Capture interface (to receive events)
Query interface (to retrieve events)
Event persistence and management

Regulatory portals like TATMEEN and RSD act as EPCIS repositories.

"},"DZ_serialization_faq_51":{"text":"

GS1 is a global non-profit organization that develops and maintains supply chain standards. Key GS1 standards for pharmaceuticals include:

GTIN - Product identification
GLN - Location identification
SSCC - Logistics unit identification
GS1 DataMatrix - 2D barcode
EPCIS - Event sharing

Visit gs1.org for more information.

"},"DZ_serialization_faq_52":{"text":"

Application Identifiers (AIs) are GS1 prefixes that define the meaning and format of data elements in barcodes. Common pharmaceutical AIs:

AI 01: GTIN (14 digits)
AI 10: Batch/Lot number
AI 17: Expiry date (YYMMDD)
AI 21: Serial number

Example: (01)00614141123452(17)251231(10)ABC123(21)12345

"},"DZ_serialization_faq_53":{"text":"

GTIN-14 is a 14-digit Global Trade Item Number used in pharmaceutical serialization. It consists of:

Indicator digit (packaging level)
GS1 Company Prefix
Item reference
Check digit

Example: 00614141123452

"},"DZ_serialization_faq_54":{"text":"

SGTIN (Serialized GTIN) is the combination of a GTIN and a unique serial number that identifies a specific individual product unit.

Format: GTIN + Serial Number

Example: GTIN 00614141123452 + Serial 12345ABC = SGTIN

SGTINs are used in EPCIS events to track individual products.

"},"DZ_serialization_faq_55":{"text":"

A GS1 Company Prefix is a unique number assigned to your company by GS1. It forms the basis for creating:

GTINs for your products
SSCCs for your logistics units
GLNs for your locations

Contact your local GS1 Member Organization to obtain a prefix.

"},"DZ_serialization_faq_56":{"text":"

The GTIN check digit is calculated using the Modulo 10 algorithm:

Multiply alternate digits by 3 and 1 (starting from right)
Sum all results
Check digit = (10 - (sum mod 10)) mod 10

Use our Barcode Decoder to verify check digits automatically.

"},"DZ_serialization_faq_62":{"text":"

A batch/lot number identifies products manufactured under the same conditions. In GS1 barcodes:

Encoded with AI 10
Variable length (up to 20 alphanumeric characters)
Critical for recalls and quality control

Example: (10)BATCH123

"},"DZ_serialization_faq_63":{"text":"

Expiry date is encoded using AI 17 in YYMMDD format:

YY = Year (00-99)
MM = Month (01-12)
DD = Day (01-31, or 00 for end of month)

Example: (17)251231 = December 31, 2025

"},"DZ_serialization_faq_57":{"text":"

GS1-128 (formerly UCC/EAN-128) is a linear barcode symbology used primarily for:

Shipping labels
Case and pallet identification
Encoding multiple data elements

It uses Application Identifiers and is commonly seen on logistics labels alongside 2D DataMatrix codes.

"},"DZ_serialization_faq_59":{"text":"

Different GTIN lengths serve different purposes:

GTIN-8: Small items (rare in pharma)
GTIN-12: North American retail (UPC)
GTIN-13: International retail (EAN)
GTIN-14: Trade items and cases (standard for pharma serialization)

All can be converted to GTIN-14 by adding leading zeros.

"}}}

EFDA-MVC Integration Engineer (Remote)

Document