# E2B Generation: PMDA E2B(R3) Mapping

When you export a Case to an E2B file, either for an outbound Transmission or directly from the Case page, Vault Safety maps all case data and documents to the appropriate E2B data elements. This article describes how Vault maps information to generate PMDA E2B(R3) files.

For details about all other E2B formats supported by Vault, see <a href="/en/lr/01288/">E2B Generation Data Mapping</a>. For details about other PMDA report formats, see <a href="/en/lr/827489/">PMDA MHLW Paper Form Generation Data Mapping</a>.



<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault automatically <a href="/en/lr/01226/">validates E2B files</a>. In addition, Vault enables you to <a href="/en/lr/01461/">configure custom <em>Validation Criteria</em></a> for <em>Case</em> data through the user-friendly Vault Expression Engine.</p>
    </div>
  </div>
</div>



## <a id="pmda-e2b-r3"></a>PMDA E2B(R3) Mapping

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: A Japan Localized Case must contain at least one (1) <strong>Local Reporting Details</strong> record that includes a Case Product Registration assigned PMDA Rank <code class="language-plaintext highlighter-rouge">1</code> (primary) and a <strong>PMDA Transmission</strong> record.</p>
    </div>
  </div>
</div>



Per PMDA guidance, certain data elements are transmitted only for specific PMDA Reporting Categories (J2.1a). The PMDA Reporting Categories for which each element is transmitted are outlined in the following Excel file: <a class="download-link " href="https://platform.veevavault.help/assets/downloads/saf-data-transmitted-by-pmda-reporting-category.xlsx" target="_blank" rel="noopener">Data Transmitted by PMDA Reporting Category<i class="fa fa-download" aria-hidden="true"></i></a>

The following tables define how each E2B data element is mapped for a PMDA E2B(R3) file. Use [the section below][1] to review only regional PMDA mappings that are different from the ICH mappings.

<div>

<!----filter sections---->





<!----show the appropriate heading level---->

<h3>N.1 ICH ICSR Transmission Identification (batch wrapper)</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>N.1.1 Types of Message in batch</td>
            <td>This value is always <code>1</code> for <strong>ICH ICSR</strong>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>N.1.2 Batch Number</td>
            <td>The value in the <em>E2B Message ID</em> field on the <a href="../01264/#icsr-transmission-types">ICSR <em>Transmission</em></a>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>N.1.3 Batch Sender Identifier</td>
            <td>The value in the <em>Origin ID</em> field on the <em>Transmission Profile</em> associated with the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>N.1.4 Batch Receiver Identifier</td>
            <td>The value in the <em>Destination ID</em> field on the <em>Transmission Profile</em> associated with the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>N.1.5 Date of Batch Transmission</td>
            <td>The value in the <em>Transmission Date</em> field on the ICSR <em>Transmission</em>. Otherwise, the date and time when the report was generated or transmitted. The time is converted to Japan Standard Time (JST) and transmitted in the format <code>CCYYMMDDhhmmss+0900</code>.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>N.2.r ICH ICSR Message Header (message wrapper)</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>N.2.r.1 Message Identifier</td>
            <td><p>For PMDA, Vault generates this value during E2B generation using the following fields:</p> <p><code>(case_version__v.reporter_country__v.abbreviation_2__v)<br>(transmission_profile__v.origin_id__v)<br>(local_reporting_details__v.report_uid__v)</code></p> <p>For example: JP-VertBio-000001AB</p>
      <div class="note-border alert-info">
        <div class="alert alert-info" role="alert">
            <div><i class="far fa-info-circle"></i></div>
            <div class="alert-text">
              <strong>Note</strong> For Vault to generate this value, all three fields must be populated. If any field is blank, this data element is not exported.
            </div>
          </div>
        </div>
<p>PMDA requires that when multiple ICSRs are submitted from a single Case, N.2.r.1 and C.1.1 must be different for each ICSR.</p> <p>To achieve this, Vault Safety adds logic to append suffix (AA-ZZ) to the existing UID generation logic to make it unique per submission.
   The generated UID is stored in the <strong>Report UID</strong> field of the <strong>Local Reporting Details</strong> (<code>local_reporting_details__v.report_uid__v</code>) record.</p>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>N.2.r.2 Message Sender Identifier</td>
            <td>The value in the <em>Origin ID</em> field on the <em>Transmission Profile</em> associated with the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>N.2.r.3 Message Receiver Identifier</td>
            <td>The value in the <em>Destination ID</em> field on the <em>Transmission Profile</em> associated with the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>N.2.r.4 Date of Message Creation</td>
            <td>The exact date and time when the report was generated, in the format <code>CCYYMMDDhhmmss+0900</code>. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>C.1 Identification of the Case Safety Report</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>C.1.1 Sender's (case) Safety Report Unique Identifier</td>
            <td><p>For PMDA, Vault generates this value during E2B generation using the following fields:</p> <p><code>(case_version__v.reporter_country__v.abbreviation_2__v)<br>(transmission_profile__v.origin_id__v)<br>(local_reporting_details__v.report_uid_v)</code></p> <p>For example: JP-VertBio-000001AB</p>
  <div class="note-border alert-info">
    <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
      <div class="alert-text">
        <strong>Note</strong> For Vault to generate this value, all three fields must be populated. If any field is blank, this data element is exported with no value populated.
      </div>
    </div>
  </div>
<p>See N.2.r.1 for unique report UID generation.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.2 Date of Creation</td>
            <td>The exact date and time when the report was generated, in the format <code>CCYYMMDDhhmmss+0900</code>. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.3 Type of Report</td>
            <td>Vault populates a code based on the <em>Report Type</em> of the <em>Case</em>:
       <ul>
           <li><code>1</code>: Spontaneous</li>
           <li><code>2</code>: Study</li>
           <li><code>3</code>: Other</li>
           <li><code>4</code>: Unknown</li>
       </ul>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.4 Date Report Was First Received from Source</td>
            <td><ul>
  <li>For initial Cases, the date in the <strong>Local Initial Receipt Date</strong> field on the Localized Case. If blank, the date in the <strong>Receipt Date</strong> field on the Global Case is exported.</li>
  <li>For Follow-Up Cases, the date in the <strong>Local Initial Receipt Date</strong> field on the Localized Case. If blank, the date in the <strong>Initial Receipt Date</strong> field on the Global Case is exported.</li>
</ul> <p>The time is converted to Japan Standard Time (JST).</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.5 Date of Most Recent Information for This Report</td>
            <td>The date in the <strong>Local New Info Date</strong> field on the Localized Case. If blank, the date in the <strong>New Info Date</strong> field from the Global Case is exported. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.7 Does This Case Fulfil the Local Criteria for an Expedited Report?</td>
            <td>If the <em>Local Expedited Criteria</em> (<code>case_expedited__v</code>) field on the ICSR <em>Transmission</em> has a value, Vault uses this value. If this field is not specified on the <em>Transmission</em>, Vault looks at the <em>Expedited</em> field on the <em>Case</em>. If the value is <em>Yes</em>, Vault populates this element with <code>1</code> (expedited). Otherwise, Vault populates this element with <code>2</code> (non-expedited).  <p>If both fields are blank, nullFlavor (<code>NI</code>) is exported.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>C.1.6 Additional Available Documents Held by Sender</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>C.1.6.1 Are Additional Documents Available?</td>
            <td>Populated as True if there are documents attached to the Case with the document type of <strong>Case > Source > Attachment</strong>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.6.1.r.1 Documents Held by Sender</td>
            <td>For documents with the <em>Case > Source > Attachment</em> document type, Vault attempts to populate the <em>Attachment Description</em> from the <em>Localized Case Document</em> that is linked to the document, to a limit of 2,000 characters. If unavailable, Vault populates the <em>Description</em> from the global <em>Case Document</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.6.1.r.2 Included Documents</td>
            <td><p>If any documents are attached to the <em>Case</em> with the document type of <em>Case > Source > Attachment</em> and the <em>Retransmit</em> field set to <em>Yes</em>, they are encoded. If the <em>Retransmit</em> field is set to <em>No</em> or is blank, documents are not encoded.</p> <p>Depending on your Admin's configuration, Vault may <a href="../826501/#attach-incl-control">exclude attachment contents</a> on <em>Transmissions</em> for domestic <em>Cases</em> or <em>Localized Cases</em> with previous <em>Transmissions</em> that included the attachment to the same reporting destination.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>C.1.8 Worldwide Unique Case Identification</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>C.1.8.1 Worldwide Unique Case Identification Number</td>
            <td>The <em>Worldwide UID</em> on the <em>Case Version</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.8.2 First Sender of This Case</td>
            <td>The value in the <em>First Sender</em> field on the original <a href="../907890/"><em>Inbound Transmission</em></a>. <p>The transmission date is used to find the original <em>Transmission</em>.</p>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.9.1 Other Case Identifiers in Previous Transmissions</td>
            <td>Populated as True if there are any Case Identifier objects associated with the Case. If there are no Case Identifier objects associated with the Case, <code>NI</code> is exported.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.9.1.r.1 Source(s) of the Case Identifier</td>
            <td>Repeated for the value in the <strong>Source</strong> field on each Localized Case Identifier object under the Japanese Localized Case. <p>This element is transmitted only when the Case Identifier <strong>Type</strong> (<code>type__v</code>) is set to <strong>Re-Transmittable</strong> or is blank.</p>
                
                <code>localized_case_identifier__v.source__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.9.1.r.2 Case Identifier(s)</td>
            <td>The value in the <strong>Case Identifier</strong> field on the Case Identifier object. <p>This element is transmitted only when the Case Identifier <strong>Type</strong> (<code>type__v</code>) is set to <strong>Re-Transmittable</strong> or is blank.</p>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.10.r Identification Number of the Report Which Is Linked to This Report</td>
            <td>The value in the <strong>Related Case Identifier</strong> field on the Case Relationship object. This value is exported when the <strong>Retransmit</strong> field on the record is set to <strong>Yes</strong>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.11.1 Report Nullification/Amendment</td>
            <td>The appropriate value is populated, based on the option selected in the <strong>Reason</strong> field on the Transmission:
       <ul>
           <li><code>1</code>: Nullification</li>
           <li><code>2</code>: Amendment</li>
       </ul>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.1.11.2 Reason for Nullification/Amendment</td>
            <td>The text in the <strong>Reason Text</strong> field on the Transmission, to a limit of 2,000 characters.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>C.2.r Primary Source(s) of Information</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.2.r.3 Reporter's Country Code</td>
            <td>The ISO code in the <em>Country</em> field on the primary Reporter-type <em>Case Contact</em>. This field is transmitted only if C.2.r.5 is set to <code>1</code> (Primary Source) for the corresponding Reporter-type <em>Case Contact</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.2.r.4 Qualification</td>
            <td>The value in the <em>Qualification</em> field on a Reporter-type <em>Case Contact</em>. If <em>Patient</em> or <em>Parent</em> is selected in this field, then the E2B code of <code>5</code> is mapped.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.2.r.5 Primary Source for Regulatory Purposes</td>
            <td>Populated with <code>1</code> (true) if the <em>Primary Source</em> field is set to <em>Yes</em> on the associated Reporter-type <em>Case Contact</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>C.3 Information on Sender of Case Safety Report</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>C.3.1 Sender Type</td>
            <td>The value in the <em>Sender Type</em> field in the <em>Organization</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.<br>If the <em>Sender (User)</em> is not specified on the <em>Transmission</em>, Vault maps the <em>Sender Type</em> from the <em>Organization</em> on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.3.2 Sender Organization</td>
            <td>The Organization in the <em>Origin</em> field on the PMDA Transmission Profile.
                
                <code>transmission_profile__v.origin_transmission_id__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.3.3.2 Sender's Title</td>
            <td>The value in the <em>Title</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.3.3 Sender's Given Name</td>
            <td>The value in the <em>First Name</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.3.4 Sender's Middle Name</td>
            <td>The value in the <em>Middle Name</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.3.5 Sender's Family Name</td>
            <td>The value in the <em>Last Name</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.1 Sender's Street Address</td>
            <td>The value in the <em>Street</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.2 Sender's City</td>
            <td>The value in the <em>City</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.3 Sender's State or Province</td>
            <td>The value in the <em>State / Province</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.4 Sender's Postcode</td>
            <td>The value in the <em>Zip/Postal Code</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.5 Sender's Country Code</td>
            <td>The 2-letter ISO code associated with the country selected in the <em>Country</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.6 Sender's Telephone</td>
            <td>The value in the <em>Telephone</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.3.4.7 Sender's Fax</td>
            <td>The value in the <em>Fax</em> field in the <em>User</em> record associated with the <em>Sender (User)</em> on the ICSR <em>Transmission</em>.
                
            </td>
        </tr>
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>C.4.r Literature Reference(s)</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>C.4.r.1 Literature Reference(s)</td>
            <td><p>For <em>Case</em> attachments with the document type <em>Case > Source > Literature</em>, <em>Literature > Literature Article > Summary</em> and <em>Literature > Literature Article > Full-text</em>, Vault retrieves the corresponding Japan <em>Localized Case Document</em> and populates this element with the value in the <em>Reference</em> field to a limit of 500 characters.</p> <p>For <em>Case</em> attachments with the document type <em>Literature > Literature Article</em> and for each document identified in the J2.15.r Country of Publication data element, Vault maps a value using the following priority order:</p> <ul> <li>The <em>Reference</em> field value from the <em>Localized Case Document</em></li> <li>The value from the C.4.r.1 data element on the E2B file for the global <em>Case</em></li> </ul> <div class="note-border alert-info">
        <div class="alert alert-info" role="alert">
          <div><i class="far fa-info-circle"></i></div>
          <div class="alert-text">
            <strong>Note</strong> When reporting literature <em>Cases</em> to the PMDA, because information exported to the PMDA E2B(R3) file is based on <em>Localized Case Documents</em>, you must also attach all <em>Localized Case Documents</em> to the <em>Case</em>.
          </div>
        </div>
      </div>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.4.r.2 Included Documents</td>
            <td><p><em>Case</em> documents of the following classifications with the <em>Retransmit</em> field value of <em>Yes</em> are encoded in <em>Transmissions</em>:</p> <ul> <li><em>Case > Source > Literature</em></li> <li><em>Literature > Literature Article > Full-Text</em></li> <li><em>Literature > Literature Article > Summary</em></li> </ul> <p>Depending on your Admin's configuration, Vault may <a href="../826501/#lit-incl-control">exclude the contents of literature articles</a> on <em>Transmissions</em> for domestic <em>Cases</em> or <em>Localized Cases</em> with previous <em>Transmissions</em> that included the literature article to the same reporting destination.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>C.5 Study Identification</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>C.5.1.r.1 Study Registration Number</td>
            <td>The <em>Registration Number</em> on the <em>Case Study Registration</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.5.1.r.2 Study Registration Country</td>
            <td>The 2-letter ISO code associated with the <em>Country</em> on the <em>Case Study Registration</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.5.2 Study Name</td>
            <td><p>The value in the <em>Study Name</em> field on the <em>Localized Study</em> for Japan associated with the <em>Study</em> on the global <em>Case</em>.</p> <p>If there is no <em>Localized Study</em> for Japan, Vault exports the value in the <em>Study Name</em> field on the associated global <em>Case</em>.</p>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>C.5.3 Sponsor Study Number</td>
            <td>The <em>Study Number</em> on the associated <em>Study</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.5.4 Study Type Where Reaction(s) / Event(s) Were Observed</td>
            <td>Based on the <em>Study Type</em> on the <em>Case</em>, Vault populates an E2B code corresponding to the <a href="../01195/#study-type"><em>Study Type</em></a> controlled vocabulary.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>D Patient Characteristics</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>D.1 Patient (name or initials)</td>
            <td>The value in the <strong>Patient Initials / ID</strong> field on the Case.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>D.1.1 Patient Medical Record Number(s) and Source(s) of the Record Number</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>D.1.1.1 Patient Medical Record Number(s) and Source(s) of the Record Number (GP Medical Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - GP</strong> (<code>mrn_gp_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_gp_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.2 Patient Medical Record Number(s) and Source(s) of the Record Number (Specialist Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Specialist</strong> (<code>mrn_specialist_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_specialist_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.3 Patient Medical Record Number(s) and Source(s) of the Record Number (Hospital Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Hospital</strong> (<code>mrn_hospital_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_hospital_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.4 Patient Medical Record Number(s) and Source(s) of the Record Number (Investigation Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Investigation</strong> (<code>mrn_investigation_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_investigation_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>D.2 Age Information</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.2.1 Date of Birth</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the <em>Case Date of Birth</em> (<code>dob_idate__v</code>) field has the full date with year, month, and day, or is set to any Reason Omitted (<code>dob_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.2.2a Age at Time of Onset of Reaction / Event (number)</td>
            <td>The <em>Age</em> on the <em>Case</em>. In accordance with ICH guidelines, Vault does not transmit this data element if the D.2.1 Date of Birth data element includes a value.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.2.2b Age at Time of Onset of Reaction / Event (unit)</td>
            <td>The <em>Age (unit)</em> on the <em>Case</em>. In accordance with ICH guidelines, Vault does not transmit this data element if the D.2.1 Date of Birth data element includes a value.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.2.2.1a Gestation Period When Reaction / Event Was Observed in the Foetus (number)</td>
            <td>The value in the <em>Gestation</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.2.2.1b Gestation Period When Reaction/Event Was Observed in the Foetus (unit)</td>
            <td>The unit in the <em>Gestation (unit)</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.2.3 Patient Age Group (as per reporter)</td>
            <td>The value in the <em>Age Group</em> field on the <em>Case</em>. In accordance with ICH guidelines, this element is transmitted only when both the Patient Date of Birth (D.2.1) and Age at Onset (D.2.2) are not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.3 Body Weight (kg)</td>
            <td>The value in the <em>Weight</em> field on the <em>Case</em>, normalized to the accepted unit.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.4 Height (cm)</td>
            <td>The value in the <em>Height</em> field on the <em>Case</em>, normalized to the accepted unit.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.5 Sex</td>
            <td>The value in the <em>Sex</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.6 Last Menstrual Period Date</td>
            <td>The date in the <em>Last Menstrual</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>D.7 Relevant Medical History and Concurrent Conditions</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>D.7.1.r.1a MedDRA Version for Medical History</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.7.1.r.1b Medical History (disease / surgical procedure / etc.) (MedDRA code)</td>
            <td>The MedDRA LLT coded on the <strong>Case Medical History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.7.1.r.2 Start Date</td>
            <td>The date in the <strong>Start Date</strong> field on the <strong>Case Medical History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.7.1.r.3 Continuing</td>
            <td>The appropriate value is populated, based on the <strong>Continuing</strong> field on the <strong>Case Medical History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.7.1.r.4 End Date</td>
            <td>The date in the <strong>End Date</strong> field on the <strong>Case Medical History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.7.1.r.5 Comments</td>
            <td>Repeated for each Localized Case Medical History record related to the Japanese Localized Case. Mapped from the <strong>Comments</strong> field (<code>localized_case_medical_history__v.comments__v</code>), to a limit of 2,000 characters.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.7.1.r.6 Family History</td>
            <td>The value in the <strong>Family History</strong> field on the <strong>Case Medical History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.7.2 Text for Relevant Medical History and Concurrent Conditions (not including reaction / event)</td>
            <td>The text in the <strong>Medical History Text</strong> field on the Japan Localized Case, to a limit of 10,000 characters.
                
                <code>localized_case__v.medical_history_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.7.3 Concomitant Therapies</td>
            <td>Set to True when the <strong>Concomitant Therapies</strong> field is set to <strong>Yes</strong> on the Case.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>D.8.r Relevant Past Drug History</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.1 Name of Drug as Reported</td>
            <td><p>Repeated for each Localized Case Drug History under the Japan Localized Case. Mapped from one of the following sources:</p> <ul>
    <li>Vault first attempts to map this value from the <strong>Drug (Reported)</strong> field.
    <code>localized_case_drug_history__v.name_reported__v</code></li>
    <li>If the Drug (Reported) field is blank, Vault maps the <strong>Drug (Coded)</strong> field.
  <code>localized_case_drug_history__v.product_name__v</code></li>
</ul>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.2a MPID Version Date/Number</td>
            <td>The <em>MPID Version</em> on the <em>Case Drug History</em> record. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.2b Medicinal Product Identifier (MPID)</td>
            <td>The value entered in the <strong>MPID</strong> field on the <strong>Case Drug History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.3a PhPID Version Date/Number</td>
            <td>The <em>PhPID Version</em> on the <em>Case Drug History</em> record. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.3b Pharmaceutical Product Identifier (PhPID)</td>
            <td>The value in the <strong>PhPID</strong> field on the <strong>Case Drug History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.4 Start Date</td>
            <td>The date in the <em>Start Date</em> field on the <em>Case Drug History</em> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.5 End Date</td>
            <td>The date in the <em>End Date</em> field on the <em>Case Drug History</em> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.6a MedDRA Version for Indication</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.6b Indication (MedDRA code)</td>
            <td>The MedDRA LLT coded for the indication on the <strong>Case Drug History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.7a MedDRA Version for Reaction</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.8.r.7b Reaction (MedDRA code)</td>
            <td>The value in the <strong>Reaction MedDRA</strong> field on the <strong>Case Drug History</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>
















<!----show the appropriate heading level---->

<h4>D.9 In case of Death</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>D.9.1 Date of Death</td>
            <td>The date in the <em>Date of Death</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.9.2.r.1a MedDRA Version for Reported Cause(s) of Death</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.9.2.r.1b Reported Cause(s) of Death (MedDRA code)</td>
            <td>The MedDRA LLT coded on the Reported Case Cause of Death object.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.9.2.r.2 Reported Cause(s) of Death (free text)</td>
            <td>Repeated for each Localized Case Cause of Death under the Japan Localized Case. Mapped from the text entered in the <strong>Name (Reported)</strong> field.
                
                <code>localized_case_cause_of_death__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.9.3 Was Autopsy Done?</td>
            <td>The value in the <em>Autopsy</em> field on the <em>Case</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.9.4.r.1a MedDRA Version for Autopsy-determined Cause(s) of Death</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.9.4.r.1b Autopsy-determined Cause(s) of Death (MedDRA code)</td>
            <td>The MedDRA LLT coded on the Autopsy-Determined Case Cause of Death object.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.9.4.r.2 Autopsy-determined Cause(s) of Death (free text)</td>
            <td>Repeated for each Autopsy-Determined Localized Case Cause of Death under the Japan Localized Case. Mapped from the value in the <strong>Name (Reported)</strong> field.
                
                <code>localized_case_cause_of_death__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>D.10 For a Parent-child / Foetus Report, Information Concerning the Parent</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>D.10.2.1 Date of Birth of Parent</td>
            <td>The <em>Date of Birth</em> on the associated <em>Parent Information</em>. For Vault to transmit this value, the full date is required with year, month, and day.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.2.2a Age of Parent (number)</td>
            <td>The <em>Age</em> on the associated <em>Parent Information</em>. In accordance with ICH guidelines, Vault does not transmit this data element if the D.10.2.1 Date of Birth of Parent data element includes a value.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.2.2b Age of Parent (unit)</td>
            <td>The <em>Age (unit)</em> on the associated <em>Parent Information</em>. In accordance with ICH guidelines, Vault does not transmit this data element if the D.10.2.1 Date of Birth of Parent data element includes a value.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.3 Last Menstrual Period Date of Parent</td>
            <td>The date in the <strong>Last Menstrual</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.4 Body Weight (kg) of Parent</td>
            <td>The value in the <strong>Weight</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.5 Height (cm) of Parent</td>
            <td>The value in the <strong>Height (normalized)</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.6 Sex of Parent</td>
            <td>The value in the <em>Sex</em> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.1a MedDRA Version for Medical History</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.1b Medical History (disease / surgical procedure / etc.) (MedDRA code)</td>
            <td>The MedDRA LLT coded on the <strong>Case Medical History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.2 Start Date</td>
            <td>The date in the <strong>Start Date</strong> field on the <strong>Case Medical History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.3 Continuing</td>
            <td>The value in the <strong>Continuing</strong> field on the <strong>Case Medical History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.4 End Date</td>
            <td>The date in the <strong>End Date</strong> field on the <strong>Case Medical History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.5 Comments</td>
            <td>Repeated for each Localized Case Medical History from the Localized Case for the associated <em>Parent Information</em>. Mapped from the <strong>Comments</strong> field, to a limit of 2,000 characters.
                
                <code>localized_case_medical_history__v.comments__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.10.7.2 Text for Relevant Medical History and Concurrent Conditions of Parent</td>
            <td>The text in the <strong>Medical History Text</strong> field, to a limit of 10,000 characters, from the Localized Case for the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>D.10.8.r Relevant Past Drug History of Parent</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.8.r.1 Name of Drug as Reported</td>
            <td>Repeated for each Localized Case Drug History under a <em>Parent Information</em> related to the Japan Localized Case. Mapped from the value entered in the <strong>Name Reported</strong> field.
                
                <code>localized_case_drug_history__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.8.r.2a MPID Version Date/Number</td>
            <td>The <em>MPID Version</em> on the <em>Case Drug History</em> record on the associated <em>Parent Information</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.8.r.2b Medicinal Product Identifier (MPID)</td>
            <td>The value in the <strong>MPID</strong> field on the <strong>Case Drug History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.8.r.3a PhPID Version Date/Number</td>
            <td>The <em>PhPID Version</em> on the <em>Case Drug History</em> record on the associated <em>Parent Information</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.3b Pharmaceutical Product Identifier (PhPID)</td>
            <td>The value in the <strong>PhPID</strong> field on the <strong>Case Drug History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.4 Start Date</td>
            <td>The date in the <strong>Start Date</strong> field on the <strong>Case Drug History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.5 End Date</td>
            <td>The date in the <strong>End Date</strong> field on the <strong>Case Drug History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.6a MedDRA Version for Indication</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.6b Indication (MedDRA code)</td>
            <td>The indication MedDRA LLT coded on the <strong>Case Drug History</strong> record on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.7a MedDRA Version for Reaction</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>D.10.8.r.7b Reactions (MedDRA code)</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field on the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>




















<!----show the appropriate heading level---->

<h3>E.I Reaction/Event as Reported by the Primary Source</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>E.i.1.1a Reaction / Event as Reported by the Primary Source in Native Language</td>
            <td>If the <strong>Event (Reported) - Language</strong> field is set to either English or Japanese, this value is mapped from the text entered in the <strong>Event (Reported)</strong> field on the Case Adverse Event.
                
                <code>case_adverse_event__v.event_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>E.i.1.1b Reaction / Event as Reported by the Primary Source Language</td>
            <td>If the <strong>Event (Reported) - Language</strong> field is set to either English or Japanese, this value is mapped from the text entered in the <strong>Event (Reported) - Language</strong> field on the Case Adverse Event.
                
                <code>case_adverse_event__v.event_reported_language__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>E.i.1.2 Reaction / Event as Reported by the Primary Source for Translation</td>
            <td>Repeated for each Localized Case Adverse Event under the Japan Localized Case. Mapped from the text in the <strong>Event (Reported)</strong> field on the Case Adverse Event.
                
                <code>localized_case_adverse_event__v.event_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>E.i.2.1a MedDRA Version for Reaction / Event</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.2.1b Reaction / Event (MedDRA code)</td>
            <td>The <em>Event (LLT)</em> on the <em>Case Adverse Event</em>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.3.1 Term Highlighted by the Reporter</td>
            <td>The value in the <strong>Highlighted Term</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>E.i.3.2 Seriousness Criteria at Event Level<a id="ei32"></a></h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>E.i.3.2a Results in Death</td>
            <td>Set to True when <strong>Results in death</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.3.2b Life Threatening</td>
            <td>Set to True when <strong>Life threatening</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.3.2c Caused / Prolonged Hospitalisation</td>
            <td>Set to True when <strong>Caused / prolonged hospitalisation</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>E.i.3.2d Disabling / Incapacitating</td>
            <td>Set to True when <strong>Disabling / incapacitating</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.3.2e Congenital Anomaly / Birth Defect</td>
            <td>Set to True when <strong>Congenital anomaly / birth defect</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.3.2f Other Medically Important Condition</td>
            <td>Set to True when <strong>Other medically important condition</strong> or <strong>Required Intervention to Prevent Permanent Impairment/Damage (Devices)</strong> is selected in the <strong>Seriousness</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>E.i.4 Date of Start of Reaction / Event</td>
            <td>The date in the <strong>Onset</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>E.i.5 Date of End of Reaction / Event</td>
            <td>The date in the <strong>Resolved</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>E.i.6a Duration of Reaction / Event (number)</td>
            <td>The value in the <strong>Duration</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.6b Duration of Reaction / Event (unit)</td>
            <td>The unit in the <strong>Duration (unit)</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.7 Outcome of Reaction / Event at the Time of Last Observation</td>
            <td><p>The value in the <strong>Outcome</strong> field on the Case Adverse Event.</p>
  <p>You must select a Vault E2B code value for this section.</p> 
  <p>See the following table for the E2B code values and their corresponding E2B(R3) Code values.</p>
        <table>
            <thead>
                <tr>
                    <th>Vault E2B Code</th>
                    <th>E2B(R3) Code</th>
                </tr>
            </thead>
            <tbody>
                <tr>
                    <td><code>1</code> - Recovered/Resolved</td>
                    <td><code>1</code> - Recovered/Resolved</td>
                </tr>
                <tr>
                    <td><code>2</code> - Recovering/Resolving</td>
                    <td><code>2</code> - Recovering/Resolving</td>
                </tr>
                <tr>
                    <td><code>3</code> - Not Recovered/Not Resolved/Ongoing</td>
                    <td><code>3</code> - Not Recovered/Not Resolved.Ongoing</td>
                </tr>
                <tr>
                    <td><code>4</code> - Recovered/Resolved with Sequelae</td>
                    <td><code>4</code> - Recovered/Resolved with Sequelae</td>
                </tr>
                <tr>
                    <td><code>5</code> - Fatal</td>
                    <td><code>5</code> - Fatal</td>
                </tr>
                <tr>
                    <td><code>0</code> - Unknown</td>
                    <td><code>0</code> - Unknown</td>
                </tr>
            </tbody>
        </table>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.8 Medical Confirmation by Healthcare Professional</td>
            <td>Populated based on the value in the <strong>HCP Confirmed</strong> field on the Case Adverse Event. This field is only transmitted when the <strong>Qualification</strong> field on the primary (Rank 1) Reporter-type Case Contact does not designate a health professional. That is, the Qualification Controlled Vocabulary does not correspond to E2B codes <code>1</code>, <code>2</code>, or <code>3</code>.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>E.i.9 Identification of the Country Where the Reaction / Event Occurred</td>
            <td>The value in the <strong>Event Country</strong> field on the Case Adverse Event.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>F.r Results of Tests and Procedures Relevant to the Investigation of the Patient</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->

<div>For PMDA, section F.r is repeated for each Case Test Result, in ascending order by date.</div>


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>F.r.1 Test Date</td>
            <td>The date or the <em>Reason Omitted</em> value in the <em>Test Date</em> field on the <em>Case Test Result</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>F.r.2.1 Test Name (free text)</td>
            <td>The value in the <strong>Test Name (Reported)</strong> field on the Japan Localized Case Test Result.
                
                <code>localized_case_test_result__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.2.2a MedDRA Version for Test Name</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.2.2b Test Name (MedDRA code)</td>
            <td>The MedDRA LLT coded on the Case Test Result.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.3.1 Test Result (code)</td>
            <td>The value in the <strong>Result (code)</strong> field on the Case Test Result.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.3.2 Test Result (value / qualifier)</td>
            <td>The values in the <strong>Test Result (Qualifier)</strong> and <strong>(Number)</strong> fields on the Case Test Result. In accordance with ICH guidelines, this element is not populated if the Test Result (code) (F.r.3.1) is provided. <div class="note-border alert-info"> <div class="alert alert-info" role="alert"> <div><i class="far fa-info-circle"></i></div> <div class="alert-text"> <strong>Note</strong> When the <strong>Test Result (Number)</strong> field is populated but the <strong>Test Result (Unit)</strong> field is blank, if there is a value in the <strong>Result (Unit) Text</strong> field, this element is not populated. Instead, the <strong>Test Result (Number)</strong> and <strong>Result (Unit) Text</strong> fields are mapped to F.r.3.4. </div> </div> </div>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.3.3 Test Result (unit)</td>
            <td>The unit in the <strong>Result (Unit)</strong> field on the Case Test Result. In accordance with ICH guidelines, this element is not populated if the Test Result (code) (F.r.3.1) is provided.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.3.4 Result Unstructured Data (free text)</td>
            <td>The <em>Result (Text)</em> on the Japan <em>Localized Case Test Result</em>. In accordance with ICH guidelines, Vault: <ul>
    <li>Allows numeric values only and does not map values with non-numeric characters.</li>
    <li>Does not populate this data element if the Test Result (code) (F.r.3.1) or F.r.3.2 Test Result (value / qualifier) is provided.</li>
</ul> <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <strong>Note</strong> When a <em>Test Result (Number)</em> exists but the <em>Test Result (Unit)</em> is blank, if there is a value in the <em>Result (Unit) Text</em> field, Vault populates the number and unit text in this data element.
    </div>
  </div>
</div>

                
                <code>localized_case_test_result__v.result_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.4 Normal Low Value</td>
            <td>The unit and value in the <strong>Normal Low Value</strong> field on the Case Test Result.<br> If the result does not have a unit, Vault will map any text entered instead.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.5 Normal High Value</td>
            <td>The unit and value in the <strong>Normal High Value</strong> field on the Case Test Result.<br> If the result does not have a unit, Vault will map any text entered instead.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>F.r.6 Comments (free text)</td>
            <td>The value in the <strong>Comments</strong> field on the Japan Localized Case Test Result.
                
                <code>localized_case_test_result__v.comments__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>F.r.7 More Information Available</td>
            <td>The value in the <strong>More Information Available</strong> field on the Case Test Result.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h3>G.k Drug(s) Information</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->

<div><p>Vault transmits section G.k for all Local Reporting Details / Product Joins under the Local Reporting Details associated with the Transmission, ordered by Rank.</p>
  <div class="note-border alert-info">
    <div class="alert alert-info" role="alert">
      <div><i class="far fa-info-circle"></i></div>
      <div class="alert-text">
        <strong>Note</strong> When Local Reporting Details are not associated with the Transmission or there is no Case Product Registration associated with the Local Reporting Details, the G.k. section will not be exported properly.
      </div>
    </div>
  </div>
<p>If some Local Reporting Details / Product Joins do not have a Rank assigned, Vault transmits Local Reporting Details / Product Joins in the following order:</p> <ol>
  <li>Case Product Registrations with a Drug Role of "Suspect"</li>
  <li>Company Product-type Case Products with a Drug Role of "Suspect" that do not have a Case Product Registration in Japan</li>
  <li>External Product-type Case Products with a Drug Role of "Suspect" that do not have a Case Product Registration in Japan</li>
  <li>Case Product Registrations with a Drug Role of "Interacting"</li>
  <li>Case Product Registrations with a Drug Role of "Concomitant"</li>
  <li>Case Product Registrations without a Drug Role</li>
  <li>Company Product-type Case Products that do not have a Case Product Registration in Japan</li>
  <li>External Product-type Case Products that do not have a Case Product Registration in Japan</li>
</ol> <p>When multiple Local Reporting Details / Product Joins have the same or no Rank and the associated Products have the same Drug Role, Vault exports them in order of First Administration Date, starting with the earliest date. If the First Administration Date is blank, Products are exported in order of Creation Date.</p> <p>Following the above transmissions, Vault also transmits section G.k for all Case Products that are not associated with a Local Reporting Details / Product Join in the following order:</p> <ol>
  <li>Case Products with a Drug Role of "Suspect"</li>
  <li>Case Products with a Drug Role of "Interacting"</li>
  <li>Case Products with any other Drug Role</li>
</ol>
</div>


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>G.k.1 Characterisation of Drug Role</td>
            <td>The <em>Drug Role</em> on the <em>Case Product</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.4 Identification of the Country Where the Drug Was Obtained</td>
            <td>The value in the <strong>Country Obtained</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.2.5 Investigational Product Blinded</td>
            <td>The value in the <strong>Blinded</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.5a Cumulative Dose to First Reaction (number)</td>
            <td><p>The value in the <strong>Cumulative Dose</strong> field on the <strong>Case Product</strong> record.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.5b Cumulative Dose to First Reaction (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.5b Cumulative Dose to First Reaction (unit)</td>
            <td><p>The unit in the <strong>Cumulative Dose (unit)</strong> field on the <strong>Case Product</strong> record.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.5a Cumulative Dose to First Reaction (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.6a Gestation Period at Time of Exposure (number)</td>
            <td>The value in the <strong>Gestation Exposure</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.6b Gestation Period at Time of Exposure (unit)</td>
            <td>The unit in the <strong>Gestation Exposure (unit)</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.8 Action(s) Taken with Drug</td>
            <td><p>The value in the <strong>Action Taken</strong> field on the <strong>Case Product</strong> record.</p> <p>You must select a Vault E2B code value for this section.</p>  <p>See the following table for the E2B code values and their corresponding E2B(R3) Code values.</p>
    <table>
       <thead>
              <tr>
                  <th>Vault E2B Code</th>
                  <th>E2B(R3) Code</th>
              </tr>
          </thead>
          <tbody>
              <tr>
                  <td><code>1</code> - Drug Withdrawn</td>
                  <td><code>1</code> - Drug Withdrawn</td>
              </tr>
              <tr>
                  <td><code>2</code> - Dose Reduced</td>
                  <td><code>2</code> - Dose Reduced</td>
              </tr>
              <tr>
                  <td><code>3</code> - Dose Increased</td>
                  <td><code>3</code> - Dose Increased</td>
              </tr>
              <tr>
                  <td><code>4</code> - Dose Not Changed</td>
                  <td><code>4</code> - Dose Not Changed</td>
              </tr>
              <tr>
                  <td><code>0</code> - Unknown</td>
                  <td><code>0</code> - Unknown</td>
              </tr>
              <tr>
                  <td><code>9</code> - Not Applicable</td>
                  <td><code>9</code> - Not Applicable</td>
              </tr>
          </tbody>
      </table>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.10.r Additional Information on Drug (coded)</td>
            <td>The value in the <strong>Additional Information</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.11 Additional Information on Drug (free text)</td>
            <td><p>The value in the <strong>Additional Information (text)</strong> field on the <strong>Localized Case Product</strong> record.</p> <p><code>localized_case_product__v.additional_information_on_text__v</code></p> <p>When the <strong>TIKEN</strong> checkbox is selected on the Localized Case <strong>Local Reporting Details</strong> record, Vault prepends "TIKEN" to this data element for the primary Case Product Registration.</p> <p>Any text that exceeds the 2000-character limit for this data element is truncated.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>












<!----show the appropriate heading level---->

<h4>G.k.2 Drug Identification<a id="gk2-drug"></a></h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>G.k.2.1.1a MPID Version Date / Number</td>
            <td>The <em>MPID Version</em> on the <em>Case Product</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.1.1b Medicinal Product Identifier (MPID)</td>
            <td>The value entered in the <strong>MPID</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.1.2a PhPID Version Date/Number</td>
            <td>The <em>PhPID Version</em> on the <em>Case Product</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.2.1.2b Pharmaceutical Product Identifier (PhPID)</td>
            <td>The value in the <strong>PhPID</strong> field on the <strong>Case Product</strong> record.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.2 Medicinal Product Name as Reported by the Primary Source</td>
            <td><p>For products assigned a PMDA Rank, Vault maps data from the Case Product Registration:</p> <ul>
  <li>Vault first attempts to map this value from the <strong>Product (Reported) Override</strong> field.
  <code>case_product_registration__v.case_product_reported_override__v</code></li>
  <li> If the Product (Reported) Override is blank, Vault attempts to map this value from the <strong>Local Product Code</strong>.
  <code>case_product_registration__v.case_local_product_code__v</code></li>
  <li>If the Local Product Code is blank, Vault then attempts to map the <strong>Clinical Compound Number</strong>.
  <code>case_product_registration__v.clinical_compound_number__v</code></li>
  <li>If the Clinical Compound Number is also blank Vault maps the <strong>Name</strong>.
  <code>case_product_registration__v.name__v</code></li>
</ul> <p>For Company and External Products without a PMDA Rank, Vault maps data from the Localized Case Product:</p> <ul>
  <li>Vault first attempts to map this value from the <strong>Local MPID</strong>.
  <code>localized_case_product__v.local_mpid__v</code></li>
  <li>If the Local MPID is blank, Vault then attempts to map the <strong>Product Name</strong>.
  <code>localized_case_product__v.product_name__v</code></li>
  <li>If the Local MPID is also blank Vault maps the <strong>Product (Reported)</strong>.
  <code>localized_case_product__v.product_reported__v</code></li>
</ul> <p>When required, Vault truncates text to meet the 250-character limit for this data element. Vault first truncates the list of substances that appear within parentheses. If the remaining text is too long, Vault truncates the text to the first 250 characters.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>












<!----show the appropriate heading level---->

<h4>G.k.2.3.r Substance / Specified Substance Identifier and Strength<a id="gkr-substance"></a></h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.1 Substance / Specified Substance Name</td>
            <td><p>For each <em>Case Product Substance</em> that is a child of a <em>Case Product</em> transmitted in section G.k, if the <em>Japan Product Code Type</em> of the <em>Case Product</em> is <em>J-Drug Code</em>, Vault populates this data element as follows:</p> <ul>
  <li>For <em>Company Products</em>, Vault maps the first seven (7) characters of the <em>Local Product Code</em> on the <em>Case Product Registration</em>.</li>
  <li>For <em>External Products</em>, Vault maps the first seven (7) characters of the <em>Local MPID</em> on the <em>Localized Case Product</em>.</li>
</ul> <p>If a <em>Case Product</em> includes multiple <em>Substances</em>, Vault exports a code as described above for only the first <em>Substance</em> on the <em>Product</em> record. If a <em>Case Product</em> is blinded, Vault exports a code as described for the earliest created <em>Substance</em> on the <em>Product</em> record.</p> <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <strong>Note</strong> When the code for a <em>Case Product Substance</em> related to a <em>Case Product</em> with a <em>Japan Product Code Type</em> of <em>J-Drug Code</em> has fewer than seven (7) digits, Vault exports the code, but also generates a validation warning on the <em>Transmission</em>.
    </div>
  </div>
</div> <p>If <em>Case Products</em> do not have a <em>Japan Product Code Type</em> of <em>J-Drug Code</em>, for each <em>Case Product Substance</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Substance</em>, and then maps the substance name using the following logic:</p> <ul>
  <li>Vault first attempts to map the <em>Local Product Code</em> field value.</li>
  <li>If the <em>Local Product Code</em> is blank, Vault then attempts to map the <em>Name (Reported)</em> field value.</li>
  <li>If the <em>Name (Reported)</em> is also blank, then Vault maps the <em>Name (Reported)</em> field value on the <em>Case Product Substance</em> from the global <em>Case</em>.</li>
</ul>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.2a Substance / Specified Substance TermID Version Date/Number</td>
            <td><p>The <em>TermID Version</em> on the <em>Case Product Substance</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.</p> <p>When the G.k.2.3.r.1 Substance / Specified Substance Name data element includes a <em>Case Product</em> with a <em>Japan Product Code Type</em> of <em>J-Drug Code</em>, Vault does not export this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.2b Substance / Specified Substance TermID</td>
            <td><p>The value in the <strong>TermID</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.3a Strength (number)</td>
            <td><p>The value in the <strong>Strength (Number)</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.2.3.r.3b Strength (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.3b Strength (unit)</td>
            <td><p>The unit in the <strong>Strength (Unit)</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.2.3.r.3a Strength (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>G.k.3 Holder and Authorisation / Application Number of Drug</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.3.1 Authorisation / Application Number</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the <strong>Registration Number</strong> field on the Case Product Registration.
                
                <code>case_product_registration__v.registration_number__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.3.2 Country of Authorisation / Application</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the 2-letter country code for the country selected in the <strong>Registration Country</strong> on the Case Product Registration.
                
                <code>case_product_registration__v.registration_country__vr.abbreviation_2__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.3.3 Name of Holder / Applicant</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the <strong>Registration Holder/Applicant</strong> on the Case Product Registration.
                
                <code>case_product_registration__v.registration_mah__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>G.k.4.r Dosage and Relevant Information</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.4.r.1a Dose (number)</td>
            <td><p>The value in the <strong>Dose (number)</strong> field on the Case Product Dosage.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.4.r.1b Dose (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.1b Dose (unit)</td>
            <td><p>The unit in the <strong>Dose (unit)</strong> field on the Case Product Dosage.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.4.r.1a Dose (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.4.r.2 Number of Units in the Interval</td>
            <td>The value in the <strong>Frequency (number)</strong> field on the Case Product Dosage.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.4.r.3 Definition of the Time Interval Unit</td>
            <td>The unit in the <strong>Frequency (unit)</strong> field on the Case Product Dosage.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.4.r.4 Date and Time of Start of Drug</td>
            <td>The value in the <em>First Admin Date</em> field on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.5 Date and Time of Last Administration</td>
            <td>The value in the <em>Last Admin Date</em> field on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.6a Duration of Drug Administration (number)</td>
            <td>The <em>Duration (number)</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.6b Duration of Drug Administration (unit)</td>
            <td>The unit in the <strong>Duration (unit)</strong> field on the Case Product Dosage.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.7 Batch / Lot Number</td>
            <td>The value in the <strong>Batch/Lot Number</strong> field on the Case Product Dosage. <p>This element is not transmitted when nullFlavors are selected.</p>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.8 Dosage Text</td>
            <td>For each Case Product Dosage that is a child of a Case Product transmitted in section G.k, Vault finds the corresponding Japan Localized Case Product Dosage, and then maps the <strong>Dosage Text</strong> field.
                
                <code>localized_case_product_dosage__v.dose_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.1 Pharmaceutical Dose Form (free text)</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the Japan <em>Localized Dose Form</em> corresponding to the value selected in the <em>Dose Form</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.2a Pharmaceutical Dose Form TermID Version Date/Number</td>
            <td>The <em>Dose Form TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.2b Pharmaceutical Dose Form TermID</td>
            <td>The <em>Dose Form TermID</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.1 Route of Administration</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Dosage</em>, and then exports the value from the <em>Patient RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.2a Route of Administration TermID Version Date / Number</td>
            <td>The <em>Patient RoA TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.2b Route of Administration TermID</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the E2B code corresponding to the value selected in the <em>Patient RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.1 Parent Route of Administration (free text)</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Dosage</em>, and then exports the value in the <em>Patient RoA Text</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.2a Parent Route of Administration TermID Version Date / Number</td>
            <td>The <em>Parent RoA TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.2b Parent Route of Administration TermID</td>
            <td>This element is transmitted for parent-child/fetus cases only. For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the E2B code corresponding to the value selected the <em>Parent RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>G.k.7.r Indication for Use in Case</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.7.r.1 Indication as Reported by the Primary Source</td>
            <td>The text from the <strong>Name (Reported)</strong> field on the Japan Localized Case Product Indication.
                
                <code>localized_case_product_indication__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.7.r.2a MedDRA Version for Indication</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.7.r.2b Indication (MedDRA code)</td>
            <td>The MedDRA LLT coded on the Case Product Indication.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>G.k.9.i Drug-reaction(s) / Event(s) Matrix</h4>


<!----input common section introduction---->

<div><p>Vault does not export this section for <a href="../740208/#device-contituent-case-assessments">device constituent assessments</a>.</p>
</div>


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>G.k.9.i.1 Reaction(s) / Event(s) Assessed</td>
            <td>The specific reaction or event being assessed, referenced in the <strong>Case Adverse Event</strong> field on the Case Assessment. This is not a user-entered element.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.9.i.3.1a Time Interval between Beginning of Drug Administration and Start of Reaction / Event (number)</td>
            <td>The <em>First Dose Latency (number)</em> on the <em>Case Assessment</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.3.1b Time Interval between Beginning of Drug Administration and Start of Reaction / Event (unit)</td>
            <td>The unit in the <strong>First Dose Latency (unit)</strong> field on the Case Assessment.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.9.i.3.2a Time Interval between Last Dose of Drug and Start of Reaction / Event (number)</td>
            <td>The <em>Last Dose Latency (number)</em> on the <em>Case Assessment</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.3.2b Time Interval between Last Dose of Drug and Start of Reaction / Event (unit)</td>
            <td>The unit in the <strong>Last Dose Latency (unit)</strong> field on the Case Assessment.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>G.k.9.i.4 Did Reaction Recur on Re-administration?</td>
            <td>The appropriate value is populated, based on the value in the <strong>Reaction Recurrence</strong> field on the Case Assessment: 
    <ul>
        <li><code>1</code>: yes - yes (rechallenge was done, reaction recurred)</li>
        <li><code>2</code>: yes - no (rechallenge was done, reaction did not recur)</li>
        <li><code>3</code>: yes - unk (rechallenge was done, outcome unknown)</li>
        <li><code>4</code>: no - n/a (no rechallenge was done, recurrence is not applicable)</li>
    </ul>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>G.k.9.i.2.r Assessment of Relatedness of Drug to Reaction(s) / Event(s)</h4>


<!----input common section introduction---->

<div><p>Vault does not export this section for <a href="../740208/#device-contituent-case-assessments">device constituent assessments</a>.</p>
</div>


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.1 Source of Assessment</td>
            <td>Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Source Type</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority: <ol> <li>The <em>Source (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Source (text)</em> on the <em>Case Assessment Result</em></li> </ol>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.2 Method of Assessment</td>
            <td>Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Method of Assessment</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority: <ol> <li>The <em>Method (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Method (text)</em> on the <em>Case Assessment Result</em></li> </ol>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.3 Result of Assessment</td>
            <td>Vault finds the record <em>Name</em> of the <em>Assessment Result (Override)</em> controlled vocabulary. <div class="note-border alert-info"> <div class="alert alert-info" role="alert"> <div><i class="far fa-info-circle"></i></div> <div class="alert-text"> <strong>Note</strong> Your Admin must add the <em>Assessment Result (Override)</em> field to the layout and Veeva Support must enable this usage in your Vault. In addition, there is a limitation with the <em>Assessment Result (Override)</em> controlled vocabulary where Vault will find the English record <em>Name</em> instead of the Japan localized record. This limitation will be addressed in a future release. </div> </div> </div> <p>If the <em>Assessment Result (Override)</em> is not available, Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Assessment Result</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority:</p> <ol> <li>The <em>Result (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Result (text)</em> on the <em>Case Assessment Result</em></li> </ol>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>
























<!----show the appropriate heading level---->

<h3>H Narrative Case Summary and Further Information</h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>H.1 Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information</td>
            <td>The text from the <em>Narrative</em> on the Japan <em>Localized Case</em>, to a limit of 100,000 characters.
                
                <code>localized_case__v.narrative_document__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>H.2 Reporter's Comments</td>
            <td>The <em>Reporter's Comments</em> on the Japan <em>Localized Case</em>, to a limit of 20,000 characters.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>H.4 Sender's Comments</td>
            <td><p>Vault selects the Case Comment that matches the Local Reporting Details of the Transmission if:</p>
  <ul>
    <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Company Comments</strong> (<code>companys_comments_v</code>)</li>
    <li>The <strong>Case Comment</strong> has Local Reporting Details specified</li>
  </ul>
<p>If there is no match but there is a Comment with no Local Reporting Details specified, Vault selects that Comment.
   The <strong>H.4 Sender's Comments</strong> field is then mapped to the Comments Text of the selected Case Comment.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>H.3.r Sender's Diagnosis</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>H.3.r.1a MedDRA Version for Sender's Diagnosis / Syndrome and / or Reclassification of Reaction / Event</td>
            <td>Populated with the active MedDRA dictionary on the Case, taken from the <strong>MedDRA Version</strong> field.
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>H.3.r.1b Sender's Diagnosis / Syndrome and / or Reclassification of Reaction / Event (MedDRA code)</td>
            <td>The MedDRA LLT coded on the Case Diagnosis.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>










<!----show the appropriate heading level---->

<h3>Section J<a id="j-section"></a></h3>


<!----input common section introduction---->


<!----input pmda section introduction---->


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.1a PMDA Reporting Category</td>
            <td>The E2B code corresponding to the PMDA Reporting Category of the Local Reporting Details related to the Transmission.
                
                <code>transmission__v.local_reporting_details__v.<br>pmda_reporting_category__v.controlled_vocabulary__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.1b PMDA Identification Number</td>
            <td>The value from the <strong>Destination Case ID</strong> field from the Local Reporting Details for the Transmission. Populate this value for follow-up reports only.
                
                <code>transmission__v.local_reporting_details__v.destination_case_id__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.2.1 Day 0 of Reporting Timeframe</td>
            <td>The date from the <strong>Local Awareness Date</strong> on the Japan Localized Case, in the format <code>YYYYMMDD</code>.
                
                <code>localized_case__v.local_awareness_date__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.2.2 Comments on Initial Date for Reporting</td>
            <td><p>This field is mapped from the <strong>Comments Text</strong> field if:</p>
  <ul>
    <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Receipt Date Comments</strong> (<code>receipt_date_comments__v</code>)</li>
    <li>The Local Reporting Details matches those of the Transmission</li>
  </ul>
<p>Otherwise, this field is mapped from the <strong>Comments Text</strong> field where the Localized Case Comment's Label matches the Receipt Date Comments.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.3 Flag for Immediate Report</td>
            <td>If the <strong>Immediate Report Type</strong> field is set to System (E2B) (<code>system_e2b__v</code>) on the Local Reporting Details related to the Transmission, this element is transmitted with <code>1</code>.
                
                <code>transmission__v.local_reporting_details__v.immediate_report_type__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.4.k License Category of New Drug</td>
            <td>Repeated with the E2B code for the <strong>Registration Type</strong> on each Case Product Registration corresponding to products transmitted in the G.k section for <em>Company Products</em>.
                
                <code>case_product_registration__v.registration_type_cv__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.5.k Classification of OTC drugs</td>
            <td>Repeated with the E2B code for the <strong>OTC Drug Classification</strong> on each Case Product Registration corresponding to products transmitted in the G.k section.
                
                <code>case_product_registration__v.otc_drug_classification__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.6.k Obtaining channels for OTC drugs</td>
            <td>Repeated with the E2B code or nullFlavor for the <strong>OTC Drug Channel</strong> on each Case Product Registration corresponding to products transmitted in the G.k section.
                
                <code>case_product_registration__v.otc_drug_channel__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.7.1 Completion flag</td>
            <td>The E2B code for the Completeness on the Local Reporting Details related to the Transmission.
                
                <code>transmission__v.local_reporting_details__v.completeness__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.7.2 Comments on Incompletion</td>
            <td><p>This field is mapped from the <strong>Comments Text</strong> field if:</p> <ul>
  <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Comments on Completeness</strong> (<code>comments_on_completeness_v</code>)</li>
  <li>The Local Reporting Details matches those of the Transmission</li>
</ul> <p>Otherwise, this field is mapped from the <strong>Comments Text</strong> field where the Localized Case Comment's Label matches the <strong>Comments on Completeness</strong>.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.8.1 Downgrade Report</td>
            <td>If the Downgraded field is set to <strong>Yes</strong> on this Transmission, this element is transmitted with <code>1</code>.
                
                <code>transmission__v.downgraded__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.8.2 Reason for Downgrading Report</td>
            <td><p>When J2.8.1 is transmitted with <code>1</code>, this field is mapped from the <strong>Comments Text</strong> field if:</p> <ul>
  <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Downgrade Reason</strong> (<code>downgrade_reason__v</code>)</li>
  <li>The Local Reporting Details matches those of the Transmission</li>
</ul>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.9 Retrospective analysis of infections</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Retrospective analysis of infections</strong> (<code>retrospective_analysis_of_infections__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.10 Action to be taken</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Action to be Taken</strong> (<code>future_actions_v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.11 Other references</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Other References</strong> (<code>other_references__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.12 Clinical Compound Number (CCN)</td>
            <td>For investigational products only. <p>When reporting Study Cases for Clinical Trial Studies registered in Japan, Vault maps this value from the <strong>Clinical Compound Number</strong> field on the Japanese Study Registration.</p> <code>(Study Registration).clinical_compound_number__v WHERE <br>(Study Registration).study__v = (Case).(Study) and <br>(Study Registration).country__v = "Japan"</code> <p>If the Study is not conducted in Japan and Japanese Study Registration information doesn't exist, this field is populated from the Clinical Compound Number of the Primary Case Product Registration of the Local Reporting Details related to the Transmission.</p> <code>transmission__v.local_reporting_details__v.<br>primary_case_product_registration_v.clinical_compound_number__v</code>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.14.i Expectedness</td>
            <td><p>This is mapped from the value in the <strong>Expected</strong> field on each Localized Case Assessment related to the primary PMDA product under the Japan Localized Case:</p> <ul>
  <li>If Yes, <code>2</code> is transmitted</li>
  <li>If No, <code>1</code> is transmitted</li>
  <li>Otherwise, this element is not transmitted</li>
</ul> <p>This element is repeated and placed under the appropriate E.i section, based on product and adverse event combination.</p> <p>If there are multiple products assigned a PMDA Rank and transmitted in section G.k, this element is only transmitted if the primary (Rank 1) PMDA product is the only suspect product (Drug Role = Suspect).</p> <p>Vault does not export this field for <a href="../740208/#device-contituent-case-assessments">device constituent assessments</a>.</p>

                
                <code>localized_case_assessment__v.expected__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.15.r Country of publication</td>
            <td><p>For each <em>Localized Case Document</em> exported to the C.4.r.1 Literature Reference(s) data element, Vault maps the 2-letter country code for the <em>Publication Country</em> on the <em>Localized Case Document</em> record.</p> <p>If <em>Publication Country</em> is blank on the <em>Localized Case Document</em> record, Vault maps the country code for the <em>Publication Country</em> on each document attached to the <em>Case</em> with the document type of <em>Case > Source > Literature</em>.</p>

                
                <code>publication_country__v.abbreviation_2__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.16 Overview of the report</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Report Overview</strong> (<code>report_overview__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.17.r Classification of trial/research</td>
            <td>For each document identified in J2.15.r, Vault maps the E2B code for the <em>Literature Classification</em> on the <em>Localized Case Document</em> record. If <em>Literature Classification</em> is blank on the <em>Localized Case Document</em> record, Vault maps the E2B code for the <em>Literature Classification</em> on each document.
                
                <code>literature_classification__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>Section J2.13.r</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->

<div><p>This section is populated only when element J2.12 is transmitted.</p><p>This section is repeated for each Study with a Japan Study Registration that has the same <strong>Clinical Compound Number</strong> as the CCN transmitted in J2.12. For each matching Study, Vault maps elements J2.13.r.1 to J2.13.r.4 using the corresponding Japan Localized Study.</p></div>


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.13.r.1 Number of CTN</td>
            <td>The value from the <strong>Number of Clinical Trial Notifications</strong> field on the Japan Localized Study.
                
                <code>localized_study__v.number_of_clinical_trial_notifications__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.2 Study indications</td>
            <td>The value from the <strong>Target Disease</strong> field on the Japan Localized Study.
                
                <code>localized_study__v.target_disease__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.3 Development phase</td>
            <td>The E2B code corresponding to the value from the <strong>Development Phase</strong> field on the global Study related to the Japan Localized Study.
                
                <code>localized_study__v.study__v.development_phase__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.4 Existence of subjects</td>
            <td>The value from the <strong>Existence of Subjects</strong> field on the Japan Localized Study: <ul>
  <li>If Yes, <code>true</code> is transmitted</li>
  <li>If No, <code>false</code> is transmitted</li>
  <li>Otherwise, this element is not transmitted</li>
</ul>

                
                <code>localized_study__v.existence_of_subjects__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>








<!----show the appropriate heading level---->

<h4>Section J2.18</h4>


<!----input common section introduction---->


<!----input pmda section introduction---->

<div><p>Vault Safety uses the Receiver Person from the Transmission Profile to map to elements J2.18.2 to J2.18.4.</p>
</div>


<!----filter fields---->


<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.18.1 Recipient organization name</td>
            <td>Mapped using the Transmission for the Japan Localized Case. Vault finds the Japan Localized Organization corresponding to the Destination on the Transmission Profile used for the Transmission. From the Japan Localized Organization, Vault maps the <strong>Official Name</strong>.
                
                <code>localized_organization__v.official_name__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.2 Recipient title</td>
            <td>The <strong>Title</strong> field on the Receiver Person of the Transmission Profile.
                
                <code>person__sys.title__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.3 Recipient's family name</td>
            <td>The <strong>Last Name</strong> field on the Receiver Person of the Transmission Profile. If "Last Name" is selected in the <code>exclude_from_receiver_block__v</code> field on the associated Receiver Person, this element is omitted.
                
                <code>person__sys.last_name__sys</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.4 Recipient's given name</td>
            <td>The <strong>First Name</strong> field on the Receiver Person of the Transmission Profile. If "First Name" is selected in the <code>exclude_from_receiver_block__v</code> field on the associated Receiver Person, this element is omitted.
                
                <code>person__sys.first_name__sys</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>





</div>

<h2><a id="pmda-e2b-r3-regional"></a>PMDA E2B(R3) Mapping - PMDA Regional Mappings</h2>
<div>
<!----filter sections---->




<!----show the appropriate heading level---->

<h3>N.1 ICH ICSR Transmission Identification (batch wrapper)</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>N.1.5 Date of Batch Transmission</td>
            <td>The value in the <em>Transmission Date</em> field on the ICSR <em>Transmission</em>. Otherwise, the date and time when the report was generated or transmitted. The time is converted to Japan Standard Time (JST) and transmitted in the format <code>CCYYMMDDhhmmss+0900</code>.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>N.2.r ICH ICSR Message Header (message wrapper)</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>N.2.r.1 Message Identifier</td>
            <td><p>For PMDA, Vault generates this value during E2B generation using the following fields:</p> <p><code>(case_version__v.reporter_country__v.abbreviation_2__v)<br>(transmission_profile__v.origin_id__v)<br>(local_reporting_details__v.report_uid__v)</code></p> <p>For example: JP-VertBio-000001AB</p>
      <div class="note-border alert-info">
        <div class="alert alert-info" role="alert">
            <div><i class="far fa-info-circle"></i></div>
            <div class="alert-text">
              <strong>Note</strong> For Vault to generate this value, all three fields must be populated. If any field is blank, this data element is not exported.
            </div>
          </div>
        </div>
<p>PMDA requires that when multiple ICSRs are submitted from a single Case, N.2.r.1 and C.1.1 must be different for each ICSR.</p> <p>To achieve this, Vault Safety adds logic to append suffix (AA-ZZ) to the existing UID generation logic to make it unique per submission.
   The generated UID is stored in the <strong>Report UID</strong> field of the <strong>Local Reporting Details</strong> (<code>local_reporting_details__v.report_uid__v</code>) record.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>N.2.r.4 Date of Message Creation</td>
            <td>The exact date and time when the report was generated, in the format <code>CCYYMMDDhhmmss+0900</code>. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>C.1 Identification of the Case Safety Report</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>C.1.1 Sender's (case) Safety Report Unique Identifier</td>
            <td><p>For PMDA, Vault generates this value during E2B generation using the following fields:</p> <p><code>(case_version__v.reporter_country__v.abbreviation_2__v)<br>(transmission_profile__v.origin_id__v)<br>(local_reporting_details__v.report_uid_v)</code></p> <p>For example: JP-VertBio-000001AB</p>
  <div class="note-border alert-info">
    <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
      <div class="alert-text">
        <strong>Note</strong> For Vault to generate this value, all three fields must be populated. If any field is blank, this data element is exported with no value populated.
      </div>
    </div>
  </div>
<p>See N.2.r.1 for unique report UID generation.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.2 Date of Creation</td>
            <td>The exact date and time when the report was generated, in the format <code>CCYYMMDDhhmmss+0900</code>. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.4 Date Report Was First Received from Source</td>
            <td><ul>
  <li>For initial Cases, the date in the <strong>Local Initial Receipt Date</strong> field on the Localized Case. If blank, the date in the <strong>Receipt Date</strong> field on the Global Case is exported.</li>
  <li>For Follow-Up Cases, the date in the <strong>Local Initial Receipt Date</strong> field on the Localized Case. If blank, the date in the <strong>Initial Receipt Date</strong> field on the Global Case is exported.</li>
</ul> <p>The time is converted to Japan Standard Time (JST).</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.5 Date of Most Recent Information for This Report</td>
            <td>The date in the <strong>Local New Info Date</strong> field on the Localized Case. If blank, the date in the <strong>New Info Date</strong> field from the Global Case is exported. The time is converted to Japan Standard Time (JST).
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>C.1.6 Additional Available Documents Held by Sender</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.6.1.r.1 Documents Held by Sender</td>
            <td>For documents with the <em>Case > Source > Attachment</em> document type, Vault attempts to populate the <em>Attachment Description</em> from the <em>Localized Case Document</em> that is linked to the document, to a limit of 2,000 characters. If unavailable, Vault populates the <em>Description</em> from the global <em>Case Document</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.1.6.1.r.2 Included Documents</td>
            <td><p>If any documents are attached to the <em>Case</em> with the document type of <em>Case > Source > Attachment</em> and the <em>Retransmit</em> field set to <em>Yes</em>, they are encoded. If the <em>Retransmit</em> field is set to <em>No</em> or is blank, documents are not encoded.</p> <p>Depending on your Admin's configuration, Vault may <a href="../826501/#attach-incl-control">exclude attachment contents</a> on <em>Transmissions</em> for domestic <em>Cases</em> or <em>Localized Cases</em> with previous <em>Transmissions</em> that included the attachment to the same reporting destination.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>C.1.8 Worldwide Unique Case Identification</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.1.9.1.r.1 Source(s) of the Case Identifier</td>
            <td>Repeated for the value in the <strong>Source</strong> field on each Localized Case Identifier object under the Japanese Localized Case. <p>This element is transmitted only when the Case Identifier <strong>Type</strong> (<code>type__v</code>) is set to <strong>Re-Transmittable</strong> or is blank.</p>
                
                <code>localized_case_identifier__v.source__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>C.2.r Primary Source(s) of Information</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.2.r.3 Reporter's Country Code</td>
            <td>The ISO code in the <em>Country</em> field on the primary Reporter-type <em>Case Contact</em>. This field is transmitted only if C.2.r.5 is set to <code>1</code> (Primary Source) for the corresponding Reporter-type <em>Case Contact</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>C.3 Information on Sender of Case Safety Report</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.3.2 Sender Organization</td>
            <td>The Organization in the <em>Origin</em> field on the PMDA Transmission Profile.
                
                <code>transmission_profile__v.origin_transmission_id__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>C.4.r Literature Reference(s)</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>C.4.r.1 Literature Reference(s)</td>
            <td><p>For <em>Case</em> attachments with the document type <em>Case > Source > Literature</em>, <em>Literature > Literature Article > Summary</em> and <em>Literature > Literature Article > Full-text</em>, Vault retrieves the corresponding Japan <em>Localized Case Document</em> and populates this element with the value in the <em>Reference</em> field to a limit of 500 characters.</p> <p>For <em>Case</em> attachments with the document type <em>Literature > Literature Article</em> and for each document identified in the J2.15.r Country of Publication data element, Vault maps a value using the following priority order:</p> <ul> <li>The <em>Reference</em> field value from the <em>Localized Case Document</em></li> <li>The value from the C.4.r.1 data element on the E2B file for the global <em>Case</em></li> </ul> <div class="note-border alert-info">
        <div class="alert alert-info" role="alert">
          <div><i class="far fa-info-circle"></i></div>
          <div class="alert-text">
            <strong>Note</strong> When reporting literature <em>Cases</em> to the PMDA, because information exported to the PMDA E2B(R3) file is based on <em>Localized Case Documents</em>, you must also attach all <em>Localized Case Documents</em> to the <em>Case</em>.
          </div>
        </div>
      </div>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>C.4.r.2 Included Documents</td>
            <td><p><em>Case</em> documents of the following classifications with the <em>Retransmit</em> field value of <em>Yes</em> are encoded in <em>Transmissions</em>:</p> <ul> <li><em>Case > Source > Literature</em></li> <li><em>Literature > Literature Article > Full-Text</em></li> <li><em>Literature > Literature Article > Summary</em></li> </ul> <p>Depending on your Admin's configuration, Vault may <a href="../826501/#lit-incl-control">exclude the contents of literature articles</a> on <em>Transmissions</em> for domestic <em>Cases</em> or <em>Localized Cases</em> with previous <em>Transmissions</em> that included the literature article to the same reporting destination.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>C.5 Study Identification</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>C.5.2 Study Name</td>
            <td><p>The value in the <em>Study Name</em> field on the <em>Localized Study</em> for Japan associated with the <em>Study</em> on the global <em>Case</em>.</p> <p>If there is no <em>Localized Study</em> for Japan, Vault exports the value in the <em>Study Name</em> field on the associated global <em>Case</em>.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>











<!----show the appropriate heading level---->

<h4>D.1.1 Patient Medical Record Number(s) and Source(s) of the Record Number</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>D.1.1.1 Patient Medical Record Number(s) and Source(s) of the Record Number (GP Medical Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - GP</strong> (<code>mrn_gp_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_gp_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.2 Patient Medical Record Number(s) and Source(s) of the Record Number (Specialist Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Specialist</strong> (<code>mrn_specialist_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_specialist_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.3 Patient Medical Record Number(s) and Source(s) of the Record Number (Hospital Record Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Hospital</strong> (<code>mrn_hospital_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_hospital_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.1.1.4 Patient Medical Record Number(s) and Source(s) of the Record Number (Investigation Number)</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the Case <strong>MRN - Investigation</strong> (<code>mrn_investigation_value__v</code>) field has any value or is set to any Reason Omitted (<code>mrn_investigation_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>D.2 Age Information</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.2.1 Date of Birth</td>
            <td>This element is transmitted with nullFlavor <code>MSK</code> when the <em>Case Date of Birth</em> (<code>dob_idate__v</code>) field has the full date with year, month, and day, or is set to any Reason Omitted (<code>dob_reason_omitted__v</code>). Otherwise, this element is not transmitted.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>D.7 Relevant Medical History and Concurrent Conditions</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.7.1.r.5 Comments</td>
            <td>Repeated for each Localized Case Medical History record related to the Japanese Localized Case. Mapped from the <strong>Comments</strong> field (<code>localized_case_medical_history__v.comments__v</code>), to a limit of 2,000 characters.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.7.2 Text for Relevant Medical History and Concurrent Conditions (not including reaction / event)</td>
            <td>The text in the <strong>Medical History Text</strong> field on the Japan Localized Case, to a limit of 10,000 characters.
                
                <code>localized_case__v.medical_history_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>D.8.r Relevant Past Drug History</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.8.r.1 Name of Drug as Reported</td>
            <td><p>Repeated for each Localized Case Drug History under the Japan Localized Case. Mapped from one of the following sources:</p> <ul>
    <li>Vault first attempts to map this value from the <strong>Drug (Reported)</strong> field.
    <code>localized_case_drug_history__v.name_reported__v</code></li>
    <li>If the Drug (Reported) field is blank, Vault maps the <strong>Drug (Coded)</strong> field.
  <code>localized_case_drug_history__v.product_name__v</code></li>
</ul>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>















<!----show the appropriate heading level---->

<h4>D.9 In case of Death</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.9.2.r.2 Reported Cause(s) of Death (free text)</td>
            <td>Repeated for each Localized Case Cause of Death under the Japan Localized Case. Mapped from the text entered in the <strong>Name (Reported)</strong> field.
                
                <code>localized_case_cause_of_death__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.9.4.r.2 Autopsy-determined Cause(s) of Death (free text)</td>
            <td>Repeated for each Autopsy-Determined Localized Case Cause of Death under the Japan Localized Case. Mapped from the value in the <strong>Name (Reported)</strong> field.
                
                <code>localized_case_cause_of_death__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>D.10 For a Parent-child / Foetus Report, Information Concerning the Parent</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.7.1.r.5 Comments</td>
            <td>Repeated for each Localized Case Medical History from the Localized Case for the associated <em>Parent Information</em>. Mapped from the <strong>Comments</strong> field, to a limit of 2,000 characters.
                
                <code>localized_case_medical_history__v.comments__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>D.10.7.2 Text for Relevant Medical History and Concurrent Conditions of Parent</td>
            <td>The text in the <strong>Medical History Text</strong> field, to a limit of 10,000 characters, from the Localized Case for the associated <em>Parent Information</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>D.10.8.r Relevant Past Drug History of Parent</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>D.10.8.r.1 Name of Drug as Reported</td>
            <td>Repeated for each Localized Case Drug History under a <em>Parent Information</em> related to the Japan Localized Case. Mapped from the value entered in the <strong>Name Reported</strong> field.
                
                <code>localized_case_drug_history__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>



















<!----show the appropriate heading level---->

<h3>E.I Reaction/Event as Reported by the Primary Source</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>E.i.1.1a Reaction / Event as Reported by the Primary Source in Native Language</td>
            <td>If the <strong>Event (Reported) - Language</strong> field is set to either English or Japanese, this value is mapped from the text entered in the <strong>Event (Reported)</strong> field on the Case Adverse Event.
                
                <code>case_adverse_event__v.event_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>E.i.1.1b Reaction / Event as Reported by the Primary Source Language</td>
            <td>If the <strong>Event (Reported) - Language</strong> field is set to either English or Japanese, this value is mapped from the text entered in the <strong>Event (Reported) - Language</strong> field on the Case Adverse Event.
                
                <code>case_adverse_event__v.event_reported_language__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>E.i.1.2 Reaction / Event as Reported by the Primary Source for Translation</td>
            <td>Repeated for each Localized Case Adverse Event under the Japan Localized Case. Mapped from the text in the <strong>Event (Reported)</strong> field on the Case Adverse Event.
                
                <code>localized_case_adverse_event__v.event_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>











<!----show the appropriate heading level---->

<h3>F.r Results of Tests and Procedures Relevant to the Investigation of the Patient</h3>


<!----input pmda section introduction---->

<div>For PMDA, section F.r is repeated for each Case Test Result, in ascending order by date.</div>


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.2.1 Test Name (free text)</td>
            <td>The value in the <strong>Test Name (Reported)</strong> field on the Japan Localized Case Test Result.
                
                <code>localized_case_test_result__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.3.2 Test Result (value / qualifier)</td>
            <td>The values in the <strong>Test Result (Qualifier)</strong> and <strong>(Number)</strong> fields on the Case Test Result. In accordance with ICH guidelines, this element is not populated if the Test Result (code) (F.r.3.1) is provided. <div class="note-border alert-info"> <div class="alert alert-info" role="alert"> <div><i class="far fa-info-circle"></i></div> <div class="alert-text"> <strong>Note</strong> When the <strong>Test Result (Number)</strong> field is populated but the <strong>Test Result (Unit)</strong> field is blank, if there is a value in the <strong>Result (Unit) Text</strong> field, this element is not populated. Instead, the <strong>Test Result (Number)</strong> and <strong>Result (Unit) Text</strong> fields are mapped to F.r.3.4. </div> </div> </div>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.3.4 Result Unstructured Data (free text)</td>
            <td>The <em>Result (Text)</em> on the Japan <em>Localized Case Test Result</em>. In accordance with ICH guidelines, Vault: <ul>
    <li>Allows numeric values only and does not map values with non-numeric characters.</li>
    <li>Does not populate this data element if the Test Result (code) (F.r.3.1) or F.r.3.2 Test Result (value / qualifier) is provided.</li>
</ul> <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <strong>Note</strong> When a <em>Test Result (Number)</em> exists but the <em>Test Result (Unit)</em> is blank, if there is a value in the <em>Result (Unit) Text</em> field, Vault populates the number and unit text in this data element.
    </div>
  </div>
</div>

                
                <code>localized_case_test_result__v.result_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>F.r.6 Comments (free text)</td>
            <td>The value in the <strong>Comments</strong> field on the Japan Localized Case Test Result.
                
                <code>localized_case_test_result__v.comments__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h3>G.k Drug(s) Information</h3>


<!----input pmda section introduction---->

<div><p>Vault transmits section G.k for all Local Reporting Details / Product Joins under the Local Reporting Details associated with the Transmission, ordered by Rank.</p>
  <div class="note-border alert-info">
    <div class="alert alert-info" role="alert">
      <div><i class="far fa-info-circle"></i></div>
      <div class="alert-text">
        <strong>Note</strong> When Local Reporting Details are not associated with the Transmission or there is no Case Product Registration associated with the Local Reporting Details, the G.k. section will not be exported properly.
      </div>
    </div>
  </div>
<p>If some Local Reporting Details / Product Joins do not have a Rank assigned, Vault transmits Local Reporting Details / Product Joins in the following order:</p> <ol>
  <li>Case Product Registrations with a Drug Role of "Suspect"</li>
  <li>Company Product-type Case Products with a Drug Role of "Suspect" that do not have a Case Product Registration in Japan</li>
  <li>External Product-type Case Products with a Drug Role of "Suspect" that do not have a Case Product Registration in Japan</li>
  <li>Case Product Registrations with a Drug Role of "Interacting"</li>
  <li>Case Product Registrations with a Drug Role of "Concomitant"</li>
  <li>Case Product Registrations without a Drug Role</li>
  <li>Company Product-type Case Products that do not have a Case Product Registration in Japan</li>
  <li>External Product-type Case Products that do not have a Case Product Registration in Japan</li>
</ol> <p>When multiple Local Reporting Details / Product Joins have the same or no Rank and the associated Products have the same Drug Role, Vault exports them in order of First Administration Date, starting with the earliest date. If the First Administration Date is blank, Products are exported in order of Creation Date.</p> <p>Following the above transmissions, Vault also transmits section G.k for all Case Products that are not associated with a Local Reporting Details / Product Join in the following order:</p> <ol>
  <li>Case Products with a Drug Role of "Suspect"</li>
  <li>Case Products with a Drug Role of "Interacting"</li>
  <li>Case Products with any other Drug Role</li>
</ol>
</div>


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.5a Cumulative Dose to First Reaction (number)</td>
            <td><p>The value in the <strong>Cumulative Dose</strong> field on the <strong>Case Product</strong> record.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.5b Cumulative Dose to First Reaction (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.5b Cumulative Dose to First Reaction (unit)</td>
            <td><p>The unit in the <strong>Cumulative Dose (unit)</strong> field on the <strong>Case Product</strong> record.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.5a Cumulative Dose to First Reaction (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.11 Additional Information on Drug (free text)</td>
            <td><p>The value in the <strong>Additional Information (text)</strong> field on the <strong>Localized Case Product</strong> record.</p> <p><code>localized_case_product__v.additional_information_on_text__v</code></p> <p>When the <strong>TIKEN</strong> checkbox is selected on the Localized Case <strong>Local Reporting Details</strong> record, Vault prepends "TIKEN" to this data element for the primary Case Product Registration.</p> <p>Any text that exceeds the 2000-character limit for this data element is truncated.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>











<!----show the appropriate heading level---->

<h4>G.k.2 Drug Identification<a id="gk2-drug"></a></h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.2 Medicinal Product Name as Reported by the Primary Source</td>
            <td><p>For products assigned a PMDA Rank, Vault maps data from the Case Product Registration:</p> <ul>
  <li>Vault first attempts to map this value from the <strong>Product (Reported) Override</strong> field.
  <code>case_product_registration__v.case_product_reported_override__v</code></li>
  <li> If the Product (Reported) Override is blank, Vault attempts to map this value from the <strong>Local Product Code</strong>.
  <code>case_product_registration__v.case_local_product_code__v</code></li>
  <li>If the Local Product Code is blank, Vault then attempts to map the <strong>Clinical Compound Number</strong>.
  <code>case_product_registration__v.clinical_compound_number__v</code></li>
  <li>If the Clinical Compound Number is also blank Vault maps the <strong>Name</strong>.
  <code>case_product_registration__v.name__v</code></li>
</ul> <p>For Company and External Products without a PMDA Rank, Vault maps data from the Localized Case Product:</p> <ul>
  <li>Vault first attempts to map this value from the <strong>Local MPID</strong>.
  <code>localized_case_product__v.local_mpid__v</code></li>
  <li>If the Local MPID is blank, Vault then attempts to map the <strong>Product Name</strong>.
  <code>localized_case_product__v.product_name__v</code></li>
  <li>If the Local MPID is also blank Vault maps the <strong>Product (Reported)</strong>.
  <code>localized_case_product__v.product_reported__v</code></li>
</ul> <p>When required, Vault truncates text to meet the 250-character limit for this data element. Vault first truncates the list of substances that appear within parentheses. If the remaining text is too long, Vault truncates the text to the first 250 characters.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>











<!----show the appropriate heading level---->

<h4>G.k.2.3.r Substance / Specified Substance Identifier and Strength<a id="gkr-substance"></a></h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.1 Substance / Specified Substance Name</td>
            <td><p>For each <em>Case Product Substance</em> that is a child of a <em>Case Product</em> transmitted in section G.k, if the <em>Japan Product Code Type</em> of the <em>Case Product</em> is <em>J-Drug Code</em>, Vault populates this data element as follows:</p> <ul>
  <li>For <em>Company Products</em>, Vault maps the first seven (7) characters of the <em>Local Product Code</em> on the <em>Case Product Registration</em>.</li>
  <li>For <em>External Products</em>, Vault maps the first seven (7) characters of the <em>Local MPID</em> on the <em>Localized Case Product</em>.</li>
</ul> <p>If a <em>Case Product</em> includes multiple <em>Substances</em>, Vault exports a code as described above for only the first <em>Substance</em> on the <em>Product</em> record. If a <em>Case Product</em> is blinded, Vault exports a code as described for the earliest created <em>Substance</em> on the <em>Product</em> record.</p> <div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <strong>Note</strong> When the code for a <em>Case Product Substance</em> related to a <em>Case Product</em> with a <em>Japan Product Code Type</em> of <em>J-Drug Code</em> has fewer than seven (7) digits, Vault exports the code, but also generates a validation warning on the <em>Transmission</em>.
    </div>
  </div>
</div> <p>If <em>Case Products</em> do not have a <em>Japan Product Code Type</em> of <em>J-Drug Code</em>, for each <em>Case Product Substance</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Substance</em>, and then maps the substance name using the following logic:</p> <ul>
  <li>Vault first attempts to map the <em>Local Product Code</em> field value.</li>
  <li>If the <em>Local Product Code</em> is blank, Vault then attempts to map the <em>Name (Reported)</em> field value.</li>
  <li>If the <em>Name (Reported)</em> is also blank, then Vault maps the <em>Name (Reported)</em> field value on the <em>Case Product Substance</em> from the global <em>Case</em>.</li>
</ul>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.2a Substance / Specified Substance TermID Version Date/Number</td>
            <td><p>The <em>TermID Version</em> on the <em>Case Product Substance</em>. When the value corresponds to a date, Vault converts it to <code>YYYYMMDD</code> format.</p> <p>When the G.k.2.3.r.1 Substance / Specified Substance Name data element includes a <em>Case Product</em> with a <em>Japan Product Code Type</em> of <em>J-Drug Code</em>, Vault does not export this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.2b Substance / Specified Substance TermID</td>
            <td><p>The value in the <strong>TermID</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.3a Strength (number)</td>
            <td><p>The value in the <strong>Strength (Number)</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.2.3.r.3b Strength (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.2.3.r.3b Strength (unit)</td>
            <td><p>The unit in the <strong>Strength (Unit)</strong> field on the Case Product Substance.</p> <p>When the <strong>G.k.2.3.r.1 Substance / Specified Substance Name</strong> data element includes a Case Product with a <strong>Japan Product Code Type</strong> of <strong>J-Drug Code</strong>, Vault does not export this data element.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.2.3.r.3a Strength (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>G.k.3 Holder and Authorisation / Application Number of Drug</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.3.1 Authorisation / Application Number</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the <strong>Registration Number</strong> field on the Case Product Registration.
                
                <code>case_product_registration__v.registration_number__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.3.2 Country of Authorisation / Application</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the 2-letter country code for the country selected in the <strong>Registration Country</strong> on the Case Product Registration.
                
                <code>case_product_registration__v.registration_country__vr.abbreviation_2__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.3.3 Name of Holder / Applicant</td>
            <td>This element is transmitted only for products assigned a PMDA Rank on the Case Product Registration. This value is mapped from the <strong>Registration Holder/Applicant</strong> on the Case Product Registration.
                
                <code>case_product_registration__v.registration_mah__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>G.k.4.r Dosage and Relevant Information</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.4.r.1a Dose (number)</td>
            <td><p>The value in the <strong>Dose (number)</strong> field on the Case Product Dosage.</p> <p>Your Admin can configure your Vault to exclude units of measurement that the PMDA does not accept. If configured and the <strong>G.k.4.r.1b Dose (unit)</strong> data element is excluded, Vault also excludes this data element for that unit.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.1b Dose (unit)</td>
            <td><p>The unit in the <strong>Dose (unit)</strong> field on the Case Product Dosage.</p> <p>Your Admin can configure your Vault to exclude or replace units of measurement that the PMDA does not accept. If set to exclude, when Vault excludes this data element, it also excludes the related <strong>G.k.4.r.1a Dose (number)</strong> data element. If set to replace, Vault exports <code>{DF}</code> to this data element.</p>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.7 Batch / Lot Number</td>
            <td>The value in the <strong>Batch/Lot Number</strong> field on the Case Product Dosage. <p>This element is not transmitted when nullFlavors are selected.</p>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.8 Dosage Text</td>
            <td>For each Case Product Dosage that is a child of a Case Product transmitted in section G.k, Vault finds the corresponding Japan Localized Case Product Dosage, and then maps the <strong>Dosage Text</strong> field.
                
                <code>localized_case_product_dosage__v.dose_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.1 Pharmaceutical Dose Form (free text)</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the Japan <em>Localized Dose Form</em> corresponding to the value selected in the <em>Dose Form</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.2a Pharmaceutical Dose Form TermID Version Date/Number</td>
            <td>The <em>Dose Form TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.9.2b Pharmaceutical Dose Form TermID</td>
            <td>The <em>Dose Form TermID</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.1 Route of Administration</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Dosage</em>, and then exports the value from the <em>Patient RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.2a Route of Administration TermID Version Date / Number</td>
            <td>The <em>Patient RoA TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.10.2b Route of Administration TermID</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the E2B code corresponding to the value selected in the <em>Patient RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.1 Parent Route of Administration (free text)</td>
            <td>For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault finds the corresponding Japan <em>Localized Case Product Dosage</em>, and then exports the value in the <em>Patient RoA Text</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.2a Parent Route of Administration TermID Version Date / Number</td>
            <td>The <em>Parent RoA TermID Version</em> on the <em>Case Product Dosage</em>.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.4.r.11.2b Parent Route of Administration TermID</td>
            <td>This element is transmitted for parent-child/fetus cases only. For each <em>Case Product Dosage</em> that is a child of a <em>Case Product</em> transmitted in section G.k, Vault maps the E2B code corresponding to the value selected the <em>Parent RoA</em> field.
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>G.k.7.r Indication for Use in Case</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
        <tr>
            <td>G.k.7.r.1 Indication as Reported by the Primary Source</td>
            <td>The text from the <strong>Name (Reported)</strong> field on the Japan Localized Case Product Indication.
                
                <code>localized_case_product_indication__v.name_reported__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>











<!----show the appropriate heading level---->

<h4>G.k.9.i.2.r Assessment of Relatedness of Drug to Reaction(s) / Event(s)</h4>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.1 Source of Assessment</td>
            <td>Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Source Type</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority: <ol> <li>The <em>Source (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Source (text)</em> on the <em>Case Assessment Result</em></li> </ol>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.2 Method of Assessment</td>
            <td>Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Method of Assessment</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority: <ol> <li>The <em>Method (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Method (text)</em> on the <em>Case Assessment Result</em></li> </ol>

                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>G.k.9.i.2.r.3 Result of Assessment</td>
            <td>Vault finds the record <em>Name</em> of the <em>Assessment Result (Override)</em> controlled vocabulary. <div class="note-border alert-info"> <div class="alert alert-info" role="alert"> <div><i class="far fa-info-circle"></i></div> <div class="alert-text"> <strong>Note</strong> Your Admin must add the <em>Assessment Result (Override)</em> field to the layout and Veeva Support must enable this usage in your Vault. In addition, there is a limitation with the <em>Assessment Result (Override)</em> controlled vocabulary where Vault will find the English record <em>Name</em> instead of the Japan localized record. This limitation will be addressed in a future release. </div> </div> </div> <p>If the <em>Assessment Result (Override)</em> is not available, Vault finds the Japan <em>Localized Controlled Vocabulary</em> corresponding to the <em>Assessment Result</em> on the <em>Case Assessment</em>, and then maps the record <em>Name</em>. If unavailable, Vault maps a value using the following priority:</p> <ol> <li>The <em>Result (text)</em> on the Japan <em>Localized Case Assessment Result</em></li> <li>The <em>Result (text)</em> on the <em>Case Assessment Result</em></li> </ol>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    </tbody>
</table>























<!----show the appropriate heading level---->

<h3>H Narrative Case Summary and Further Information</h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
    
    
    
    
    
    
        <tr>
            <td>H.1 Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information</td>
            <td>The text from the <em>Narrative</em> on the Japan <em>Localized Case</em>, to a limit of 100,000 characters.
                
                <code>localized_case__v.narrative_document__v</code>
                
            </td>
        </tr>
    
    
    
    
    
    
    
    
    
    
    
        <tr>
            <td>H.2 Reporter's Comments</td>
            <td>The <em>Reporter's Comments</em> on the Japan <em>Localized Case</em>, to a limit of 20,000 characters.
                
            </td>
        </tr>
    
    
    
    
    
    
    
        <tr>
            <td>H.4 Sender's Comments</td>
            <td><p>Vault selects the Case Comment that matches the Local Reporting Details of the Transmission if:</p>
  <ul>
    <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Company Comments</strong> (<code>companys_comments_v</code>)</li>
    <li>The <strong>Case Comment</strong> has Local Reporting Details specified</li>
  </ul>
<p>If there is no match but there is a Comment with no Local Reporting Details specified, Vault selects that Comment.
   The <strong>H.4 Sender's Comments</strong> field is then mapped to the Comments Text of the selected Case Comment.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>













<!----show the appropriate heading level---->

<h3>Section J<a id="j-section"></a></h3>


<!----input pmda section introduction---->


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.1a PMDA Reporting Category</td>
            <td>The E2B code corresponding to the PMDA Reporting Category of the Local Reporting Details related to the Transmission.
                
                <code>transmission__v.local_reporting_details__v.<br>pmda_reporting_category__v.controlled_vocabulary__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.1b PMDA Identification Number</td>
            <td>The value from the <strong>Destination Case ID</strong> field from the Local Reporting Details for the Transmission. Populate this value for follow-up reports only.
                
                <code>transmission__v.local_reporting_details__v.destination_case_id__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.2.1 Day 0 of Reporting Timeframe</td>
            <td>The date from the <strong>Local Awareness Date</strong> on the Japan Localized Case, in the format <code>YYYYMMDD</code>.
                
                <code>localized_case__v.local_awareness_date__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.2.2 Comments on Initial Date for Reporting</td>
            <td><p>This field is mapped from the <strong>Comments Text</strong> field if:</p>
  <ul>
    <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Receipt Date Comments</strong> (<code>receipt_date_comments__v</code>)</li>
    <li>The Local Reporting Details matches those of the Transmission</li>
  </ul>
<p>Otherwise, this field is mapped from the <strong>Comments Text</strong> field where the Localized Case Comment's Label matches the Receipt Date Comments.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.3 Flag for Immediate Report</td>
            <td>If the <strong>Immediate Report Type</strong> field is set to System (E2B) (<code>system_e2b__v</code>) on the Local Reporting Details related to the Transmission, this element is transmitted with <code>1</code>.
                
                <code>transmission__v.local_reporting_details__v.immediate_report_type__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.4.k License Category of New Drug</td>
            <td>Repeated with the E2B code for the <strong>Registration Type</strong> on each Case Product Registration corresponding to products transmitted in the G.k section for <em>Company Products</em>.
                
                <code>case_product_registration__v.registration_type_cv__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.5.k Classification of OTC drugs</td>
            <td>Repeated with the E2B code for the <strong>OTC Drug Classification</strong> on each Case Product Registration corresponding to products transmitted in the G.k section.
                
                <code>case_product_registration__v.otc_drug_classification__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.6.k Obtaining channels for OTC drugs</td>
            <td>Repeated with the E2B code or nullFlavor for the <strong>OTC Drug Channel</strong> on each Case Product Registration corresponding to products transmitted in the G.k section.
                
                <code>case_product_registration__v.otc_drug_channel__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.7.1 Completion flag</td>
            <td>The E2B code for the Completeness on the Local Reporting Details related to the Transmission.
                
                <code>transmission__v.local_reporting_details__v.completeness__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.7.2 Comments on Incompletion</td>
            <td><p>This field is mapped from the <strong>Comments Text</strong> field if:</p> <ul>
  <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Comments on Completeness</strong> (<code>comments_on_completeness_v</code>)</li>
  <li>The Local Reporting Details matches those of the Transmission</li>
</ul> <p>Otherwise, this field is mapped from the <strong>Comments Text</strong> field where the Localized Case Comment's Label matches the <strong>Comments on Completeness</strong>.</p>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.8.1 Downgrade Report</td>
            <td>If the Downgraded field is set to <strong>Yes</strong> on this Transmission, this element is transmitted with <code>1</code>.
                
                <code>transmission__v.downgraded__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.8.2 Reason for Downgrading Report</td>
            <td><p>When J2.8.1 is transmitted with <code>1</code>, this field is mapped from the <strong>Comments Text</strong> field if:</p> <ul>
  <li>The Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Downgrade Reason</strong> (<code>downgrade_reason__v</code>)</li>
  <li>The Local Reporting Details matches those of the Transmission</li>
</ul>

                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.9 Retrospective analysis of infections</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Retrospective analysis of infections</strong> (<code>retrospective_analysis_of_infections__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.10 Action to be taken</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Action to be Taken</strong> (<code>future_actions_v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.11 Other references</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Other References</strong> (<code>other_references__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.12 Clinical Compound Number (CCN)</td>
            <td>For investigational products only. <p>When reporting Study Cases for Clinical Trial Studies registered in Japan, Vault maps this value from the <strong>Clinical Compound Number</strong> field on the Japanese Study Registration.</p> <code>(Study Registration).clinical_compound_number__v WHERE <br>(Study Registration).study__v = (Case).(Study) and <br>(Study Registration).country__v = "Japan"</code> <p>If the Study is not conducted in Japan and Japanese Study Registration information doesn't exist, this field is populated from the Clinical Compound Number of the Primary Case Product Registration of the Local Reporting Details related to the Transmission.</p> <code>transmission__v.local_reporting_details__v.<br>primary_case_product_registration_v.clinical_compound_number__v</code>

                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.14.i Expectedness</td>
            <td><p>This is mapped from the value in the <strong>Expected</strong> field on each Localized Case Assessment related to the primary PMDA product under the Japan Localized Case:</p> <ul>
  <li>If Yes, <code>2</code> is transmitted</li>
  <li>If No, <code>1</code> is transmitted</li>
  <li>Otherwise, this element is not transmitted</li>
</ul> <p>This element is repeated and placed under the appropriate E.i section, based on product and adverse event combination.</p> <p>If there are multiple products assigned a PMDA Rank and transmitted in section G.k, this element is only transmitted if the primary (Rank 1) PMDA product is the only suspect product (Drug Role = Suspect).</p> <p>Vault does not export this field for <a href="../740208/#device-contituent-case-assessments">device constituent assessments</a>.</p>

                
                <code>localized_case_assessment__v.expected__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.15.r Country of publication</td>
            <td><p>For each <em>Localized Case Document</em> exported to the C.4.r.1 Literature Reference(s) data element, Vault maps the 2-letter country code for the <em>Publication Country</em> on the <em>Localized Case Document</em> record.</p> <p>If <em>Publication Country</em> is blank on the <em>Localized Case Document</em> record, Vault maps the country code for the <em>Publication Country</em> on each document attached to the <em>Case</em> with the document type of <em>Case > Source > Literature</em>.</p>

                
                <code>publication_country__v.abbreviation_2__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.16 Overview of the report</td>
            <td>If the Japan Localized Case contains a Localized Case Comment where the <strong>Comments Label</strong> (<code>comments_label__v</code>) field is set to <strong>Report Overview</strong> (<code>report_overview__v</code>) and the Local Reporting Details matches those of the Transmission, this field is mapped from the <strong>Comments Text</strong> field.
                
                <code>localized_case_comment__v.comments_text__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.17.r Classification of trial/research</td>
            <td>For each document identified in J2.15.r, Vault maps the E2B code for the <em>Literature Classification</em> on the <em>Localized Case Document</em> record. If <em>Literature Classification</em> is blank on the <em>Localized Case Document</em> record, Vault maps the E2B code for the <em>Literature Classification</em> on each document.
                
                <code>literature_classification__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>Section J2.13.r</h4>


<!----input pmda section introduction---->

<div><p>This section is populated only when element J2.12 is transmitted.</p><p>This section is repeated for each Study with a Japan Study Registration that has the same <strong>Clinical Compound Number</strong> as the CCN transmitted in J2.12. For each matching Study, Vault maps elements J2.13.r.1 to J2.13.r.4 using the corresponding Japan Localized Study.</p></div>


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.13.r.1 Number of CTN</td>
            <td>The value from the <strong>Number of Clinical Trial Notifications</strong> field on the Japan Localized Study.
                
                <code>localized_study__v.number_of_clinical_trial_notifications__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.2 Study indications</td>
            <td>The value from the <strong>Target Disease</strong> field on the Japan Localized Study.
                
                <code>localized_study__v.target_disease__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.3 Development phase</td>
            <td>The E2B code corresponding to the value from the <strong>Development Phase</strong> field on the global Study related to the Japan Localized Study.
                
                <code>localized_study__v.study__v.development_phase__v.e2b_code__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.13.r.4 Existence of subjects</td>
            <td>The value from the <strong>Existence of Subjects</strong> field on the Japan Localized Study: <ul>
  <li>If Yes, <code>true</code> is transmitted</li>
  <li>If No, <code>false</code> is transmitted</li>
  <li>Otherwise, this element is not transmitted</li>
</ul>

                
                <code>localized_study__v.existence_of_subjects__v</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>







<!----show the appropriate heading level---->

<h4>Section J2.18</h4>


<!----input pmda section introduction---->

<div><p>Vault Safety uses the Receiver Person from the Transmission Profile to map to elements J2.18.2 to J2.18.4.</p>
</div>


<!----filter fields---->

<table>
    <thead>
        <tr>
            <th>E2B Data Element Name</th>
            <th>Populated Value</th>
        </tr>
    </thead>
    <tbody>
    
    
    
        <tr>
            <td>J2.18.1 Recipient organization name</td>
            <td>Mapped using the Transmission for the Japan Localized Case. Vault finds the Japan Localized Organization corresponding to the Destination on the Transmission Profile used for the Transmission. From the Japan Localized Organization, Vault maps the <strong>Official Name</strong>.
                
                <code>localized_organization__v.official_name__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.2 Recipient title</td>
            <td>The <strong>Title</strong> field on the Receiver Person of the Transmission Profile.
                
                <code>person__sys.title__v</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.3 Recipient's family name</td>
            <td>The <strong>Last Name</strong> field on the Receiver Person of the Transmission Profile. If "Last Name" is selected in the <code>exclude_from_receiver_block__v</code> field on the associated Receiver Person, this element is omitted.
                
                <code>person__sys.last_name__sys</code>
                
            </td>
        </tr>
    
    
    
    
    
        <tr>
            <td>J2.18.4 Recipient's given name</td>
            <td>The <strong>First Name</strong> field on the Receiver Person of the Transmission Profile. If "First Name" is selected in the <code>exclude_from_receiver_block__v</code> field on the associated Receiver Person, this element is omitted.
                
                <code>person__sys.first_name__sys</code>
                
            </td>
        </tr>
    
    
    
    </tbody>
</table>




</div>

[1]: #pmda-e2b-r3-regional