Skip to main content

Part of Introduction to the Secure Data Environment

Accessing the SDE and the desktop

Current Chapter

Current chapter – Accessing the SDE and the desktop


Overview

This chapter covers the NHS England’s Secure Data Environment (SDE) desktop, how to use GitLab and your data sets.

The safe setting of the SDE is a series of virtual machines run in the cloud which has access to Databricks, RStudio and other software which you can use to access and analyse patient data securely. To ensure the security of this patient data, the SDE has limitations on what you can output from the environment and what you can bring in. For example, there are rules around which packages can be installed and how code can be copied and pasted into the SDE. These are explained in more detail in the following sections.


Accessing the SDE

You must have a user account to access the SDE. You will need to sign into the SDE with your existing credentials and two-factor authenticator method. For more information about setting up your account, visit the SDE set-up guide.

Secure Data Environment sign in window

After you have signed in, you will need to select the Data Sharing Agreement (DSA), or project, you would like to work under. If you only have one DSA, you will skip this step.

You will now see the SDE Portal page. There are a number of options here, including the Import reference data service, which will be covered in a later chapter. Select Launch the virtual desktop.

You will see the session preparation progress indicator screen.

SDE portal session preparation progress indicator screen

After a short wait, your virtual desktop will be displayed.


Desktop and Gitlab video

This video covers using the desktop area of the SDE and gives a brief introduction to using GitLab within the SDE.

You can use the desktop area for editing files, accessing GitLab and sending files to the safe output service.

If you are unfamiliar with version control or GitLab, we would recommend that you watch the video 'Version control in the SDE' which will help familiarise you with version control and how it works in the SDE.
 

Transcript for desktop and Gitlab video

Slide 1

In this video, I will give a quick demo of the desktop area and GitLab of the NHS England Secure Data Environment or SDE. Please be aware that the interface of some of the tools mentioned may have changed slightly since this video was recorded.

Slide 2

Once you log into the SDE, you will land on the virtual desktop which contains shortcuts to the tools you will use in the environment.

Slide 3

Any files you want to be available the next time you log in should be placed in either the home folder or the collab storage drive.

Slide 4

From the desktop you can access the tooling available for analysis such as Databricks, RStudio and Gitlab.

Slide 5

Using the Output your results portal you can submit your analysis to output checkers to be brought out of the SDE.

Slide 6

The Quick Start Guide provides a summary of all the information you need to get started in the SDE.

Slide 7

Slide 8

Gitlab is the chosen method for version control in the SDE enabling you too view previous versions of your code, track changes and work collaboratively with others. Once you have created a personal access token you can connect to your tool of choice. To create a personal access token, follow the steps on the page, Using GitLab in the NHS England Secure Data Environment.

Slide 9

That brings us to the end of this video.

Glossary

Persistent storage

The concept of saving files in a location where they will be available once your SDE sessions has timed out. Persistent storage locations in the SDE are the home folder within the virtual desktop, the collab storage drive, GitLab and Databricks. Files or code stored in these locations will remain and be accessible next time you log in to the SDE. Files stored in other locations are destroyed when your session on the SDE closes.

GitLab

The SDE uses GitLab, which is a platform built around Git. Git is a powerful, collaborative version control system that tracks changes to files and code. GitHub is a similar platform that uses the Git system.

Access token

An access token, or personal access token, is a 20 character code that can be used to link your SDE GitLab account with other software, such as Databricks or RStudio.  You can generate these within your GitLab profile. When creating an access token you must select an expiration date, after which you will need to create another token.  

Optional useful resources for Gitlab and the virtual desktop.

Last edited: 15 November 2024 4:08 pm