Data Access NOTE Please refer to the "Authorized Access" section below for information about how access to the data from this accession. Access differs from many other dbGaP accessions.ObjectivesShock: To determine if prehospital administration of 7.5% hypertonic saline with 6% Dextran-70 (HSD) or 7.5% hypertonic saline alone (HS), compared to current standard therapy with normal saline (NS), as an initial resuscitation fluid, affects survival following traumatic injury with hypovolemic shock.TBI: To determine whether out-of-hospital administration of hypertonic fluids improves neurologic outcome following severe traumatic brain injury (TBI).Background Trauma is the leading cause of death among North Americans between the ages of 1 and 44 years. The majority of these deaths result from hypovolemic shock or severe brain injury. Participants in hypovolemic shock develop a state of systemic tissue ischemia then a subsequent reperfusion injury at the time of fluid resuscitation. Conventional resuscitation involves the IV administration of a large volume of isotonic or slightly hypotonic (lactated ringers, LR) solutions beginning in the prehospital setting. Although not conclusive, prior studies have suggested that alternative resuscitation with hypertonic saline (7.5%) solutions may reduce morbidity or mortality in these participants. Furthermore, hypertonic fluids may have specific advantages in the brain-injured participant, as they may aid in the rapid restoration of cerebral perfusion and prevent extravascular fluid sequestration, thereby limiting secondary brain injury. In addition, recent studies have demonstrated that hypertonicity significantly alters the activation of inflammatory cells, an effect that may reduce subsequent organ injury from ischemia-reperfusion and decrease nosocomial infection. The majority of previous clinical trials have focused on the use of HSD. The potential for 7.5% saline alone (HS) to have similar effects has not been well studied. Removal of the dextran component may enhance the anti-inflammatory effects of this solution, which could improve secondary outcomes such as acute respiratory distress syndrome (ARDS), multiple organ failure syndrome (MOFS) and rates of nosocomial infections. Participants Shock: There were 893 participants that were randomized (853 enrolled).TBI: There were 1282 participants enrolled and 6-month outcomes data were available for 1087 (85%).Design Shock: Multicenter, randomized, blinded clinical trials involving 114 emergency medical services agencies in North America within the Resuscitation Outcomes Consortium were conducted from May 2006 to August 2008. Initial resuscitation fluid, 250 mL of either 7.5% saline per 6% dextran 70 (hypertonic saline/dextran, HSD), 7.5% saline (hypertonic saline, HS), or 0.9% saline (normal saline, NS) administered by out-of-hospital providers. Primary outcome was 28-day survival. On the recommendation of the data and safety monitoring board, the study was stopped early (23% of proposed sample size) for futility and potential safety concern.TBI: Multicenter, double-blind, randomized, placebo-controlled clinical trials involving 114 North American emergency medical services agencies within the Resuscitation Outcomes Consortium were conducted between May 2006 and May 2009. A single 250-mL bolus of 7.5% saline/6% dextran 70 (HSD), 7.5% saline (HS), or 0.9% saline (NS) initiated in the out-of-hospital setting. The main outcome measure was a six-month neurologic outcome based on the Extended Glasgow Outcome Scale (GOSE) (dichotomized as >4 or ≤4). The study was terminated by the data and safety monitoring board after randomization of 1331 participants, having met prespecified futility criteria.Conclusions Shock: Among injured participants with hypovolemic shock, initial resuscitation fluid treatment with either HS or HSD, compared with NS, did not result in superior 28-day survival. However, interpretation of these findings is limited by the early stopping of the trial (PMID: 21178763).TBI: Among participants with severe TBI not in hypovolemic shock, initial resuscitation with either HS or HSD, compared with normal saline, did not result in superior 6-month neurologic outcome or survival (PMID: 20924011).
Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal
