Import a subscription data release

To import a data release that is available to you, perform the following steps.

  1. In the left navigation pane, click the Settings icon (Settings icon).
  2. In the Configure System section, click Manage Subscription Data Releases.
  3. Click a data offering's Row Action menu (Row Action menu), and click Import.
  4. Choose whether you want to create Standard Runs and Report Outputs. You may receive one or more choices depending on the data offering. See the Release Notes for the particular data release for more details.

    Note:

    The report outputs that can be created along with the data release import are summary reports for use by Drug Profiles.
  5. Choose whether to notify All users or Selected users when the release is available.
    If you chose Selected users, choose them from a list of available users. Then click OK.
  6. Click Submit.
    • Oracle Empirica Signal runs the import job in the background.
    • You can track the progress of the import by hovering on the background processing indicator (Background processing icon).
    • The Status column on the Manage Subscription Data Releases table updates to Running or In Queue.
    • If an issue is encountered during the import, the Status column displays Error Occurred.
  7. When the import completes, view the objects associated with the imported data release.
    • The Status of the data release is updated to Loaded.
    • The Imported column updates with the date and time of the import.
    • Configurations for the imported data release are available on the Manage Configurations page. All the imported configurations will be of Type Managed.
    • Standard runs, if requested, will be available on the Data Mining Runs page. The runs will be published to all login groups.
    • If report outputs were requested, then the jobs for the summary reports are submitted. Once finished, the report outputs will be published to all currently available login groups.
    • If the data release specifies aliases and aliases did not already exist, then aliases are created. Existing aliases are updated only if the data offering is for a later date then the current alias.
    • Email notifications are sent to users as requested in the import request.