The Domain Editor window provides a graphical interface for defining the mapping rules for a domain.

Important: The Domain Editor preview, SQL output, and transformations respect user privileges and configured Data Blinding rules. If the user or execution account has the Blinded Data View privilege, unblinded values may appear in previewed results and may be used in transformations and derived outputs. Verify that access privileges align with the study’s blinding strategy before developing or executing mappings that include sensitive data. Mapped domain blinding options (Default, Restrict Blinded Data, Map Blinded Data) further control how blinded data is handled during transformations.

Key items in the Domain Editor mapping window are:

1. Tables List: Lists source tables grouped by their parent data store (Staging Areas or Data Marts).
2. Show Data / SQL / Show Standard Variables: When a source table or a transformation is selected, the first 25 (default) records of that table or transformation display in the lower section of the window (the Preview area).
   • The Page x of xxx displays on the right; use the arrows to navigate through additional pages of data. Click the drop-down next to 25 to change the number of rows displayed. Options include 10, 25, 50, and 100.
   • The display can be toggled to view the corresponding generated SQL code, or Show Standard Variables (see Conformance Data Check - Show Standard Variables below for details).

   • Select the Suppress Preview checkbox on the right (below Domain Properties) to stop the data preview feature. This option can help with larger, more complex mappings by enlarging the layout area.

     Note: Data displayed in the Preview area reflects the current user’s privileges and Data Blinding configuration. Users with the Blinded Data View privilege may see unblinded values in previewed results.

3. Transformations Layout: This window provides a graphical display of mapped elements and table-level transformations (joins, unions, etc.). If a comment was added in Domain Properties, the comment displays as a tooltip when the user hovers over the transformation.

   Note: If a domain in the transformation layout has Data Blinding applied, a blinding icon displays on the domain. This helps identify domains that contain blinded data within the mapping.

4. Domain Properties: Located on the right side of the window (Domain Properties subpanel). Displays details about the domain.
5. Layer / Transformation Properties: Located in the Domain Properties subpanel. Displays details about the currently selected layer or transformation.

Note: Comments entered in Domain Properties display as tooltips containing the comment text when hovering over the transformation. Transformations with no comments display no tooltip. When entering comments, carriage returns display properly, and special characters such as single or double quotes and greater than or less than signs display correctly.

While working in the Domain Editor, the following hotkey shortcuts are available:

• Ctrl Z: Undo
• Ctrl Y: Redo
• Ctrl S: Save and Close
• Delete: Delete current transformation
• Ctrl V: Open the Variables editor for the selected transformation
• Enter: Open the default property editor for the selected transformation

Add a Source Table to the Mapped Domain

1. Click the Select Source drop-down and select the source study or global data store to use.
   
2. In the Tables List, select one of the available data stores. The data store expands to display the list of available tables.
3. Click and drag the desired table into the mapping area to define the data source.
4. A preview of the selected data displays in the Preview area at the bottom of the window.
   

Note: If the same table is added to a mapped domain while using a Domain Transformation, a number displays in the upper corner to distinguish it from the original table.

Important Properties for Source Domains

The properties for each layer vary slightly depending on whether the layer represents source data, or a transformation layer.

Key Properties for Source Data

Schema Name

• Uses a schema token if the source data is part of the current study. The token is converted to the study name in the SQL preview.

• If the source domain is from another study or a global data store, the schema name is hard-coded to the corresponding study or global data store.

• This configuration supports the re-use of mappings between studies through the Global Library or Import / Export capabilities.

Skip Missing

Determines how to handle missing or changed source data. Available options include:

• None: The default selection. If no selection is made, or None is chosen, missing data causes an error.
• Domain: Prevents errors if a domain used in a transformation (Join, Union, etc.) is missing. When re-using mapped domains between studies, missing variables or fields display with null values. In the domain editor, the missing domain displays an error, but the overall transformation still produces results.
• Variables: Ignores missing variables used in the domain and replaces them with null values. When variables are missing, the Variable Count displays in red.
  

Add Custom SQL Code

If the existing transformations available in the Mapper do not meet specific requirements, a custom SQL statement can be added in the SQL code box.

1. Select the domain in the Domain Editor window, then click the </>Code button. An SQL box is added around the domain box.
   
2. Select the SQL box. The Domain Properties subpanel displays on the right side of the window.
3. In the Code field, click the ellipsis to open the Edit SQL window.
   
    

4. Enter the SQL code. If the SQL code defines source data for a domain, data can be referenced by study schema. For example, Select * from DEMO001_Src.DM where DEMO001 is the study, Src (Clinical Data store) is the data store schema, and DM is the table name.
    

   Important: Custom SQL transformations are subject to user privileges and Data Blinding rules. If unblinded data is referenced using an account with the Blinded Data View privilege, sensitive values may be included in derived domains or downstream outputs.
    

   
   Tokens can be used to simplify SQL code referencing within elluminate. Available tokens include:

   • SchemaPrefix: Refers to the study and data store. The format is SchemaPrefix_[data store prefix].[Domain Name]. 
     If no Data Store prefix is entered, the Reporting data store is assumed.
     Example: Select * from {SchemaPrefix}_src.AE selects all fields from the AE domain in the Clinical Data Store.
   • StudyName: Adds a column containing the study name. Commonly used as part of a SELECT statement.
     Example: Select '{StudyName}' as STUDY, * from {SchemaPrefix}_src.AE adds a field named STUDY containing the elluminate Study Name.
   • StudyID: Adds the StudyID from elluminate, which may differ from the StudyID in the EDC. If this field already exists in the results, an alternate name must be used.
     Example: Select '{StudyID}' as STUDYID2, * from {SchemaPrefix}_src.AE adds a field named STUDYID2 containing the elluminate Study ID. 

   • CDR: Refers to the internal table structure of the elluminate Clinical Data Repository. Contact eClinical Solutions for information about available tables for creating customized reports.

     Note: When adding fields with SQL code, ensure field names are unique to prevent SQL errors.

5. Click Save to save the SQL code.

Edit Domain Transformations

Buttons and icons are available at the top of the window to support editing transformations for a mapped domain:

Variable

Enables selection of one of the variable transformations to apply to the selected domain or transformation. See the Edit and Manage Variables in Mapper, Use Pivot and Unpivot to Transpose Data in Mapper, Add a Filter Transformation and Set the Sort Order in Mapper, and Create Aggregate Variables in Mapper articles for more information.

Domain

Allows selection of one of the domain transformations to apply to the selected domain or transformation.

See the Use Join and Unions in Mapper article for more information.  

</>Code

Enables entry of SQL code directly to import data from a table or transform selected domains.

For more information see the Add Custom SQL Code section.

SQL

Copies the SQL code for a selected transformation to the clipboard. The copied code can be pasted into another program or another domain mapping.

1. Select the domain or one of the transformations.
2. Click the Copy SQL button.
3. Open the target program.
4. Paste from the clipboard

Extracts selected transformations and executes them to create a new domain, simplifying the mapped domain.

Export

Exports data from the preview of the currently selected layer.

Undo/Redo

Reverses or reapplies recent actions. For example, if an incorrect transformation is added or a field is removed unintentionally, click Undo to revert the action or Redo to restore it. 

Delete

Removes an existing transformation.

1. Select the box surrounding the transformation to remove.
2. Press Delete on the keyboard or click Delete in the toolbar.

The transformation is removed. This action can also be used to remove selected tables from a Join or Union.

Save

Saves changes made to a mapped domain. Each save creates a new version automatically. Saving also closes the Domain Editor window and returns to the mapping management window.

Close

Closes the Domain Editor window. If unsaved changes exist, a Discard Changes window opens.

• Click Yes to discard changes (a new version is not saved).
• Click No to return to the domain mapping window.

AutoSave

Automatically saves a draft version of the domain mapping whenever changes are made. If connectivity is lost or elluminate is closed unexpectedly, the draft version can be accessed from the mapping management window.

Identify Errors

SQL

When working with domain transformations, errors may occur due to mapping logic issues or misconfigured SQL. When this happens, an error message displays in the Preview area (at the bottom of the window) when SQL (next to Show Data) is selected.

The error message identifies the transformation where the error occurred and the corresponding line in the SQL. These items are clickable links that simplify troubleshooting.

Active domain mapping rules cannot be saved while an error exists. To save a domain mapping rule that contains an error, clear the Active checkbox (in the Domain Properties subpanel on the right), and then click Save.

Use Conformance Data Check - Show Standard Variables

The Show Standard Variables feature allows validation of a mapped domain against a predefined standard or specification without exiting the Mapper.
The display can be toggled between Show Data, SQL, and Show Standard Variables.

When Show Standard Variables is selected, the system displays variables included in the selected standard or specification, indicating whether the mapped domain complies with that structure.
This check verifies only the existence of variables in the mapping output. It does not validate data types, sequence, labels, or controlled terminology.

Perform a Conformance Data Check

1. Click the Show Standard Variables button.
2. The list in the lower window displays the details. 

Variable Types in Standards / Specifications

• Required (Req): Must exist in the domain and cannot contain null values.
• Expected (Exp): Must exist in the domain but can contain null values.
• Permissible (Perm): Optional; does not have to exist in the domain.

Listing Details

The listing provides the following information:

• A list of variables in the corresponding domain defined in the standard or specification.
• A Status column indicates the following:
  • Variables that exist in the mapping domain display a green check mark.
  • Variables missing from the mapping domain but defined as Req or Exp in the standard / specification display Missing in red.
  • Variables not found in the mapping domain and not designated as Req or Exp in the standard / specification display N/A in gray.

Export Data

While developing mapped domains, it is often necessary to review the data produced by a set of transformations. Although this information is available in the Preview area within the Domain Editor, sorting and filtering in Excel can make results easier to validate. The Export button enables exporting data from a selected transformation.

Note: Exported preview data reflects the current user’s privileges and Data Blinding configuration. Users with the Blinded Data View privilege may export unblinded values.

1. Select the transformation for which results are to be viewed.
2. Click the Export icon.
3. Select either Export Current 25 Rows or Export All Rows. An Excel spreadsheet containing the selected data is downloaded to the local computer.