A mapping is a collection of domains and their associated rules that define how data is mapped from a staging area to a specified data mart.

The mapping defines the Standard or Specification and the target Data Store for all included mapped domains.

Important: Mapper transformations and domain execution respect user privileges and configured Data Blinding rules. If the execution account has the Blinded Data View privilege, unblinded values may be used in transformations and written to derived domains or downstream data stores. Verify that execution account 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 data is handled during transformation and help prevent unblinded values from being written to derived domains or downstream data stores.

Create a Mapping

1. From the Platform Menu, select Mapper under Data Mapping & Computing, then select the study or global data store. The Mapper window opens.
   
2. In the Mappings section, click New to create a custom mapping. The Custom Mapping window opens. 
   
3. In the Name field, enter a descriptive name for the mapping.
4. In the Standard field, click the drop-down and select the intended Standard or Specification for the mapping.

   • Selecting a Standard or Specification allows Mapper to suggest variable naming conventions and controlled terminology for any domains defined in the standard or specification.

     Tip: The icon to the left of each standard or specification name indicates the type. Standards are listed first, followed by specifications. Scroll to view all available selections.
     

5. The Controlled Terminology field is only used when a Standard is selected. Controlled terminology does not apply to the DMOD standard.
   • When a specification is selected, Controlled Terminology is built in.
   • To select a version of the controlled terminology for a standard, click the drop-down and select the desired version.
   • If no version or date is selected, the most recent controlled terminology version is applied.
6. Select the Active checkbox to make the mapping active. Inactive mappings are not executed automatically when data is imported. 

7. In the Map To field, click the drop-down and select the destination for the mapped domains. Any existing data marts or staging areas can be selected.

   Note: Multiple mappings can be created per data store, but the names of the mapped domains must be unique. See Create a New Mapped Domain below for details.

8. In the Description field, enter a brief description for the custom mapping.

   Note: Data Blinding is not configured at the mapping level. It is applied at the domain level and during execution based on user privileges and configured Data Blinding rules.

9. Click Save to save the mapping.

Create a Mapped Domain

Each domain results in a new table, or dataset, in the database when the domain or mapping is executed.

Domains marked active execute automatically when their source data is imported.

A domain can also be executed manually to update its output table by clicking Execute.
Note: Domain execution applies configured Data Blinding rules based on execution account privileges. Review both settings before executing domains that include sensitive data.

In addition to the steps below, mapped domains can also be created in several other ways:

• Automatically by Dynamic Mapping Templates. These automatically created domains do not appear until an import that matches the template is run.
• Manually based on one of the Dynamic Mapping Templates, by manually associating the dynamic template with a study, rather than using the default dynamic template behavior.
• Imported from an XML file.
• Imported from the Global Library.

Tip: For details on using Dynamic Mapping Templates, see the article Create a Domain from a Dynamic Mapping Template in Mapper.
For details on importing from a file or from the Global Library, see the article Manage a Mapped Domain in Mapper.

1. In the Domains section, click New. The New Domain window opens.
   
    
2. In the Name field, enter the name of the domain to be created. Names must be unique within the target data store of the mapping.

   • A domain named AE cannot be created in two different mappings that point to the same data store.

     Tip: If the domain name matches one defined in the selected mapping’s standard or specification (for example, DM, AE, etc.), the system suggests field names based on that standard or specification and adds the table name to the description automatically.

3. Select the Active checkbox to allow the domain to execute automatically when data is imported.
   • Domains are typically left inactive during development to prevent automatic execution.
4. Select the Intermediate checkbox to make the mapping available as a source for further mapping.
   • Intermediate mappings are not exported but are available for reuse in other mappings (for example, when creating Joins or Unions).
   • After execution, the resulting table displays in the target data store with a list icon instead of a table icon. This indicates that the mapping can be reused.
     
5. In the Description field, enter a brief summary describing the domain being created.
   • If the Name is a recognized table or panel name, the full table name displays in the description automatically.
6. In the Blinded Data Settings field, select one of the following options: Default, Restrict Blinded Data, or Map Blinded Data. These settings control how blinded data is handled for the domain during transformation and execution. Depending on user privileges, some options may be unavailable or disabled.
   • Default: Uses the system-configured Data Blinding rules without applying additional restrictions at the domain level.
     • Blinded values remain masked according to the study’s Data Blinding configuration.
     • If the execution account has the Blinded Data View privilege, unblinded values may be used during transformation and written to downstream outputs.
   • Restrict Blinded Data: Prevents the use of unblinded values during transformation, regardless of user privileges.
     • Blinded values remain masked and are not exposed in transformations or outputs.
     • Ensures that sensitive data is not written to derived domains or downstream data stores.
     • Recommended when strict enforcement of blinding is required.
   • Map Blinded Data: Allows the use of blinded values during transformation while maintaining masking in outputs.
     • Transformations can reference underlying values during processing.
     • Output values remain masked according to the study’s Data Blinding rules.
     • Useful when calculations require full data context but outputs must remain blinded.
7. Click Save. The Domain Editor opens.

Best Practices for Creating a Mapped Domain

• Link to a standard or specification first. Selecting a CDISC or DMOD standard, custom standard, or specification allows for the auto-completion of field names, labels, and code lists, which helps prevent downstream mapping errors.
• Use unique domain names. Assign a unique table name to each mapped domain. When selecting source tables (including those created from previous mappings), be cautious not to select a table that the mapping is designed to recreate, as this may result in the system blocking execution.
• Use Intermediate domains. Break complex transformations into smaller intermediate domains to create the final mapped domain. This approach simplifies troubleshooting and allows for the reuse of baseline or first-entry logic in other mappings. For example, create an intermediate domain that calculates each subject's baseline visit date, which can then be used in downstream mappings.
• Promote mapped domains to the Global Library. Promoting to the Global Library allows the mapped domain to be imported into other studies without re-coding, ensuring consistency and saving programming time.
• Use the Extract button in the Domain Editor. Extract complex transformation logic from an existing mapped domain into a reusable intermediate domain. This allows the same transformation to be referenced in other mappings without the need to rebuild it.
• Apply Blinded Data Settings appropriately to each domain. Select the appropriate Blinded Data Settings option for each domain and confirm Data Blinding configuration before execution to ensure sensitive data is handled according to the study’s blinding strategy.