The version of the file being
supplied (reserved for future use, currently to have value 1.0)
This is a number supplied by the sender
to identify uniquely every message transaction sent
from the sender's point of view. It must be unique in every message file provided.
It can be a sequence e.g. 1, 2, 3 etc… It is NOT the business message ID.
Any source information the sender is willing
to attach (even using a hierarchical structure as this is ANY datatype) and that
will be communicated back to them within the response. This might store the business
source id of the document (CTA) so that senders can later match the message better
with their source systems etc....
Identifier for each NCA / sponsor for the EudraCT gateway community.
This ID is unique for each party communicating with EMA within each application (domain)
and is agreed between them and the gateway support.
A valid ECD username to be used for obtaining submission organization
information and saving to the database records
Identifier of the EudraCT gateway receiver community.
Will be provided by the EMA gateway support.
This is the generation date of the message.
The format for this date is:yyyyMMddHHmmSS, yyyy = 4-digit year – e.g. 2005
, MM = 2-digit month – e.g. 01, dd = 2-digit day – e.g. 02,
HH = 2-digit 24-hour format – e.g. 15,
mm = 2-digit minutes – e.g. 44, SS = 2-digit seconds – e.g. 55,
For example: 20120102154455
This is EU ESTRI Gateway message header used for routing.