... | ... | @@ -19,7 +19,7 @@ Data can be uploaded into the PEP system by means of [the `pepcli store` command |
|
|
/app/pepcli store -p POM162733743006 -c Holter.Visit1 -i ~/holter/49170044-1C98-4A21-886C-A6E18DE1F885.ecg
|
|
|
```
|
|
|
|
|
|
Because of PEP's [pseudonymization](Pseudonymization) goals, uploaders will often not be privy to a participant identifier. Instead they'll usually have a *short pseudonym*, i.e. an identifier for the data sample. Short pseudonyms can be passed to the `pepcli store` command using the `--sp` switch:
|
|
|
Because of PEP's [pseudonymization](Pseudonymization) goals, uploaders will often not be privy to a participant identifier. Instead they'll usually have a *short pseudonym*, i.e. an identifier for the data sample. Short pseudonyms can be passed to the `pepcli store` command using the `--sp` switch, e.g.:
|
|
|
|
|
|
```
|
|
|
/app/pepcli store -sp POM1EC7713461 -c Holter.Visit1 -i ~/holter/49170044-1C98-4A21-886C-A6E18DE1F885.ecg
|
... | ... | @@ -33,9 +33,14 @@ curl https://ecg.ppth.com/49170044-1C98-4A21-886C-A6E18DE1F885/ | /app/pepcli st |
|
|
|
|
|
The `pepcli` utility exits with code `0` (zero) if the `store` command succeeds, or with a different value if it fails. Automated (scripted) invocations of `pepcli store` should check for these values. When the command fails, the utility writes details to the log and/or to the standard error stream `stderr`.
|
|
|
|
|
|
## Identifier pseudonymization
|
|
|
Note that the PEP system can only accommodate a single file in any given cell. If multiple files should be stored together (e.g. because the files would be useless individually, or because the data format requires it), the files must be packaged into a single file (e.g. a `tar` archive) before being `pepcli store`d. Downloaders will then receive the packaged file, which they should process accordingly.
|
|
|
|
|
|
## Data format processing
|
|
|
|
|
|
As [mentioned earlier](#Uploading-data), uploaders will usually specify a short pseudonym to indicate where their data should be stored in PEP. Such short pseudonyms [should not be exposed](#Pseudonymization) to downloaders, since that would provide them with a fixed identifier for the data sample (and hence for the participant). The uploader should therefore ensure that any short pseudonyms (or other identifying information for that matter) are removed from the data before it is uploaded into PEP.
|
|
|
|
|
|
PEP provides built-in facilities to automate pseudonym removal for some data formats @@@ more here @@@
|
|
|
|
|
|
@@@more here@@@
|
|
|
|
|
|
|
|
|
## 2. List data from PEP e.g. to retrieve a short pseudonym
|
... | ... | |