We are conducting a series of focused Technical Workshops to answer any technical questions you might have. Sessions will be virtual, and will take place every Thursday at 11:00 AM - 01:00 PM Dubai local time
To take part in the sessions, please click on this link: Tatmeen Weekly Technical Workshop
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by logistics supply chain participants involved in the movement of medical products for the following processes:
These processes are the first draft of this technical guide and it is expected that additional processes will be added in future versions of this document, as appropriate.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by dispensing participants such as pharmacies, hospitals, and clinics for the following process:
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by supply chain participants for the following processes:
These processes are the first draft of this technical guide, and it is expected that additional processes (e.g., the process for importation of unregistered drugs) will be added in future versions of this document, as appropriate.
Tatmeen Onboarding Event (MAH, LA, 3PL)
For Tatmeen Product master data and Partner master data are in scope. Master data refers to the characteristics and attributes of an object such as GTIN, product description, unit of measure, partner address, etc.
Product owners (MAHs, Licensed Agents) need to add their products in relevant MoHAP systems. All the supply chain entities that are part of Tatmeen scope such as MAH, Licensed Agent, Distributors, 3PLs, Hospital, Warehouse, and Pharmacy are responsible for registering their partner master data in the relevant MoHAP systems. MoHAP systems send all required product and partner master data to BrandSync GS1 where additional master data attributes are entered. BrandSync GS1 then makes this data available to Tatmeen.
To access Tatmeen, the user must first register in Tatmeen. For supply chain partners the process start with defining the SPOC in the partner master data in BrandSync. Once SPOC is registered in Tatmeen, he/she can create additional Portal and mobile users and Service (B2B) users.
In addition to using APIs (B2B connectivity), Tatmeen portal can also be used to share Commissioning and Aggregation events using File Upload functionality. Using this feature, authorized users (MAH / Licensed Agent) will be able to upload a CSV file, containing commissioning and aggregation events.
Mobile commissioning functionality will be available for MAH or Licensed Agents to manually commission a SGTIN for a product they’re authorized to manufacture and/or import. This functionality is to be used by entities that due to small product volumes or technical capabilities is not in position to report commissioning events via the B2B API as described in the Technical Guide for Manufacturers. Please consider that this functionality will only commission the product, but it will still be necessary to pack it using the Hierarchy Change -> Pack functionality of Tatmeen.
Supply Chain actors that don’t have the capability to generate SSCC themselves, will have option in Tatmeen to generate/request new SSCC codes (Serial Shipping Container Codes) and print SSCC labels for logistics unit.
Hierarchy Change indicates a change in packaging as the goods move through the distribution process and it involves Pack, Unpack, Unpack all transactions.
Each serialized item (SGTIN/SSCC) that is currently registered into Tatmeen is given a status. From the initial status of “Commissioned”, this value will be changed as the product moves through the supply chain until it is finally dispensed.
The Product Transfer functionality refers to the movement of a product from its current location to a new location. All Supply Chain entities can perform product transfer and must report product transfer events. Product transfer involves Shipping, Receiving, Return Shipping, Return Receiving transactions.
The status and detailed information of any serialized item can be checked at any time using Product Verification functionality. Based on a user's security level users will be able to see:
Message Log functionality will show the users details about the operations performed by them within Tatmeen. Successful processing of events such as product transfer documents and product status updates will be shown immediately. The outcome of other events such as EPCIS uploads will be available once their processing has been completed. To access the Message Log, select Message Log in the navigation menu in the Portal or Mobile to access the message log.
The Batch Recall functionality is used for managing the recall of product batches deemed unsuitable throughout the supply chain. The Batch Recall process has three steps:
The batch recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the batch are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiating entity once the process is completed. After completion, all items related to that batch are decommissioned in Tatmeen.
The Product Recall functionality is used to manage the recall of products deemed unsuitable. The Product Recall process has three steps:
The product recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the product are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiation entity once the process is completed. After completion, all items related to that product are decommissioned in Tatmeen.
The destruction functionality is used to manage the destruction of products deemed unsuitable in the UAE supply chain. Destruction has three steps:
Destruction is first initiated by a supply chain entity. After destruction is initiated, all items are blocked from any transfer and dispensation. After completion of destruction, all items are decommissioned.
This document provides information regarding the test scenarios, which are required for the onboarding of B2B.
This document is a template, which will be filled by the partner after executing the test scenarios result. This is a prerequisite step for partners for the onboarding of B2B.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by logistics supply chain participants involved in the movement of medical products for the following processes:
These processes are the first draft of this technical guide and it is expected that additional processes will be added in future versions of this document, as appropriate.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by dispensing participants such as pharmacies, hospitals, and clinics for the following process:
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by supply chain participants for the following processes:
These processes are the first draft of this technical guide, and it is expected that additional processes (e.g., the process for importation of unregistered drugs) will be added in future versions of this document, as appropriate.
Tatmeen Onboarding Event (MAH, LA, 3PL)
Tatmeen Technical Workshop for Distributors
For Tatmeen Product master data and Partner master data are in scope. Master data refers to the characteristics and attributes of an object such as GTIN, product description, unit of measure, partner address, etc.
Product owners (MAHs, Licensed Agents) need to add their products in relevant MoHAP systems. All the supply chain entities that are part of Tatmeen scope such as MAH, Licensed Agent, Distributors, 3PLs, Hospital, Warehouse, and Pharmacy are responsible for registering their partner master data in the relevant MoHAP systems. MoHAP systems send all required product and partner master data to BrandSync GS1 where additional master data attributes are entered. BrandSync GS1 then makes this data available to Tatmeen.
To access Tatmeen, the user must first register in Tatmeen. For supply chain partners the process start with defining the SPOC in the partner master data in BrandSync. Once SPOC is registered in Tatmeen, he/she can create additional Portal and mobile users and Service (B2B) users.
Hierarchy Change indicates a change in packaging as the goods move through the distribution process and it involves Pack, Unpack, Unpack all transactions.
TSupply Chain actors that don’t have the capability to generate SSCC themselves, will have option in Tatmeen to generate/request new SSCC codes (Serial Shipping Container Codes) and print SSCC labels for logistics unit.
Each serialized item (SGTIN/SSCC) that is currently registered into Tatmeen is given a status. From the initial status of “Commissioned”, this value will be changed as the product moves through the supply chain until it is finally dispensed.
The Product Transfer functionality refers to the movement of a product from its current location to a new location. All Supply Chain entities can perform product transfer and must report product transfer events. Product transfer involves Shipping, Receiving, Return Shipping, Return Receiving transactions.
The status and detailed information of any serialized item can be checked at any time using Product Verification functionality. Based on a user's security level users will be able to see:
Message Log functionality will show the users details about the operations performed by them within Tatmeen. Successful processing of events such as product transfer documents and product status updates will be shown immediately. The outcome of other events such as EPCIS uploads will be available once their processing has been completed. To access the Message Log, select Message Log in the navigation menu in the Portal or Mobile to access the message log.
The Batch Recall functionality is used for managing the recall of product batches deemed unsuitable throughout the supply chain. The Batch Recall process has three steps:
The batch recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the batch are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiating entity once the process is completed. After completion, all items related to that batch are decommissioned in Tatmeen.
The Product Recall functionality is used to manage the recall of products deemed unsuitable. The Product Recall process has three steps:
The product recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the product are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiation entity once the process is completed. After completion, all items related to that product are decommissioned in Tatmeen.
The destruction functionality is used to manage the destruction of products deemed unsuitable in the UAE supply chain. Destruction has three steps:
Destruction is first initiated by a supply chain entity. After destruction is initiated, all items are blocked from any transfer and dispensation. After completion of destruction, all items are decommissioned.
This document provides information regarding the test scenarios, which are required for the onboarding of B2B.
This document is a template, which partner should use for the test scenarios (which are required for the onboarding of B2B) result.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by logistics supply chain participants involved in the movement of medical products for the following processes:
These processes are the first draft of this technical guide and it is expected that additional processes will be added in future versions of this document, as appropriate.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by dispensing participants such as pharmacies, hospitals, and clinics for the following process:
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by supply chain participants for the following processes:
These processes are the first draft of this technical guide, and it is expected that additional processes (e.g., the process for importation of unregistered drugs) will be added in future versions of this document, as appropriate.
Tatmeen Technical Workshop for Hospitals
Tatmeen Technical Workshop for Pharmacies
For Tatmeen Product master data and Partner master data are in scope. Master data refers to the characteristics and attributes of an object such as GTIN, product description, unit of measure, partner address, etc.
Product owners (MAHs, Licensed Agents) need to add their products in relevant MoHAP systems. All the supply chain entities that are part of Tatmeen scope such as MAH, Licensed Agent, Distributors, 3PLs, Hospital, Warehouse, and Pharmacy are responsible for registering their partner master data in the relevant MoHAP systems. MoHAP systems send all required product and partner master data to BrandSync GS1 where additional master data attributes are entered. BrandSync GS1 then makes this data available to Tatmeen.
To access Tatmeen, the user must first register in Tatmeen. For supply chain partners the process start with defining the SPOC in the partner master data in BrandSync. Once SPOC is registered in Tatmeen, he/she can create additional Portal and mobile users and Service (B2B) users.
Hierarchy Change indicates a change in packaging as the goods move through the distribution process and it involves Pack, Unpack, Unpack all transactions.
Each serialized item (SGTIN/SSCC) that is currently registered into Tatmeen is given a status. From the initial status of “Commissioned”, this value will be changed as the product moves through the supply chain until it is finally dispensed.
Supply Chain actors that don’t have the capability to generate SSCC themselves, will have option in Tatmeen to generate/request new SSCC codes (Serial Shipping Container Codes) and print SSCC labels for logistics unit.
The Product Transfer functionality refers to the movement of a product from its current location to a new location. All Supply Chain entities can perform product transfer and must report product transfer events. Product transfer involves Shipping, Receiving, Return Shipping, Return Receiving transactions.
Pharmacies, hospitals, and clinics, among others, where drugs are dispensed, are required to capture an exit event - dispensing.
The dispensing process starts with providing a list of the item(s) intended to be dispensed within Tatmeen.
The state of the serialized products, in order to be successfully dispensed, can only be “Commissioned”. Products that are decommissioned for any reason, for instance, expired products, won’t be allowed to be dispensed.
The status and detailed information of any serialized item can be checked at any time using Product Verification functionality. Based on a user's security level users will be able to see:
Message Log functionality will show the users details about the operations performed by them within Tatmeen. Successful processing of events such as product transfer documents and product status updates will be shown immediately. The outcome of other events such as EPCIS uploads will be available once their processing has been completed. To access the Message Log, select Message Log in the navigation menu in the Portal or Mobile to access the message log.
The Batch Recall functionality is used for managing the recall of product batches deemed unsuitable throughout the supply chain. The Batch Recall process has three steps:
The batch recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the batch are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiating entity once the process is completed. After completion, all items related to that batch are decommissioned in Tatmeen.
The Product Recall functionality is used to manage the recall of products deemed unsuitable. The Product Recall process has three steps:
The product recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the product are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiation entity once the process is completed. After completion, all items related to that product are decommissioned in Tatmeen.
The destruction functionality is used to manage the destruction of products deemed unsuitable in the UAE supply chain. Destruction has three steps:
Destruction is first initiated by a supply chain entity. After destruction is initiated, all items are blocked from any transfer and dispensation. After completion of destruction, all items are decommissioned.
This document provides information regarding the test scenarios, which are required for the onboarding of B2B.
This document is a template, which partner should use for the test scenarios (which are required for the onboarding of B2B) result.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by logistics supply chain participants involved in the movement of medical products for the following processes:
These processes are the first draft of this technical guide and it is expected that additional processes will be added in future versions of this document, as appropriate.
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by dispensing participants such as pharmacies, hospitals, and clinics for the following process:
The purpose of this document is to define the information that must be sent under the MoHAP regulations to the Tatmeen traceability system by supply chain participants for the following processes:
These processes are the first draft of this technical guide, and it is expected that additional processes (e.g., the process for importation of unregistered drugs) will be added in future versions of this document, as appropriate.
For Tatmeen Product master data and Partner master data are in scope. Master data refers to the characteristics and attributes of an object such as GTIN, product description, unit of measure, partner address, etc.
Product owners (MAHs, Licensed Agents) need to add their products in relevant MoHAP systems. All the supply chain entities that are part of Tatmeen scope such as MAH, Licensed Agent, Distributors, 3PLs, Hospital, Warehouse, and Pharmacy are responsible for registering their partner master data in the relevant MoHAP systems. MoHAP systems send all required product and partner master data to BrandSync GS1 where additional master data attributes are entered. BrandSync GS1 then makes this data available to Tatmeen.
To access Tatmeen, the user must first register in Tatmeen. For supply chain partners the process start with defining the SPOC in the partner master data in BrandSync. Once SPOC is registered in Tatmeen, he/she can create additional Portal and mobile users and Service (B2B) users.
All the products in scope of Tatmeen must be product cleared. In essence, for imported product, each shipment must have a valid shipment import permit (SHP), and follow the import process which consists of three steps:
Once the product is market released, it can be freely moved through the UAE supply. For products manufactured inside UAE, the shipment must have a valid local sales permit (LSP), and follow the Market Release process.
Hierarchy Change indicates a change in packaging as the goods move through the distribution process and it involves Pack, Unpack, Unpack all transactions.
Supply Chain actors that don’t have the capability to generate SSCC themselves, will have option in Tatmeen to generate/request new SSCC codes (Serial Shipping Container Codes) and print SSCC labels for logistics unit.
Each serialized item (SGTIN/SSCC) that is currently registered into Tatmeen is given a status. From the initial status of “Commissioned”, this value will be changed as the product moves through the supply chain until it is finally dispensed.
The Product Transfer functionality refers to the movement of a product from its current location to a new location. All Supply Chain entities can perform product transfer and must report product transfer events. Product transfer involves Shipping, Receiving, Return Shipping, Return Receiving transactions.
The status and detailed information of any serialized item can be checked at any time using Product Verification functionality. Based on a user's security level users will be able to see:
Message Log functionality will show the users details about the operations performed by them within Tatmeen. Successful processing of events such as product transfer documents and product status updates will be shown immediately. The outcome of other events such as EPCIS uploads will be available once their processing has been completed. To access the Message Log, select Message Log in the navigation menu in the Portal or Mobile to access the message log.
The Batch Recall functionality is used for managing the recall of product batches deemed unsuitable throughout the supply chain. The Batch Recall process has three steps:
The batch recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the batch are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiating entity once the process is completed. After completion, all items related to that batch are decommissioned in Tatmeen.
The Product Recall functionality is used to manage the recall of products deemed unsuitable. The Product Recall process has three steps:
The product recall is first initiated by the MAH/Scientific Office/Licensed Agents or by MOHAP Drug Dept – Pharma-Co-vigilance/DOH Pharma-Co-vigilance/DHA Pharma-Co-vigilance.
After initiation, the recall must be approved by MoHAP PV. Once approved, all items of the product are blocked from dispensation, but transfer is still allowed.
As the last step, the recall is marked as completed by the initiation entity once the process is completed. After completion, all items related to that product are decommissioned in Tatmeen.
The destruction functionality is used to manage the destruction of products deemed unsuitable in the UAE supply chain. Destruction has three steps:
Destruction is first initiated by a supply chain entity. After destruction is initiated, all items are blocked from any transfer and dispensation. After completion of destruction, all items are decommissioned.
This document provides information regarding the test scenarios, which are required for the onboarding of B2B.
This document is a template, which partner should use for the test scenarios (which are required for the onboarding of B2B) result.
