cbioportal icon indicating copy to clipboard operation
cbioportal copied to clipboard

Sample Decryption and Redirects for Epic

Open averyniceday opened this issue 5 months ago • 1 comments

Fix # (see https://help.github.com/en/articles/closing-issues-using-keywords)

Describe changes proposed in this pull request: Add support for new endpoints that handle redirects from Epic. Includes calls to Mpath server for decrypting IDs before generating redirects. Includes the following additions:

  • Endpoint (/api-legacy/epic/sample/{sampleID}): takes an encrypted sample ID, decrypts, and redirects to the appropriate sample
  • Endpoint (/api-legacy/epic/patient/{patientID}): takes an encrypted patient ID, decrypts, and redirects to the appropriate patient
  • Endpoint (api-legacy/epic/{sampleID}/exists): takes encrypted sampleID, decrypts, and checks for existence (for determining whether to add a linkout from Epic)
  • Property (mpath.token): optional, contains api-key for using the decryption server
  • Property (mpath.decryption_url): optional, contains URL to decryption server

Checks

  • [ ] The commit log is comprehensible. It follows 7 rules of great commit messages. We can fix this during merge by using a squash+merge if necessary
  • [ ] Has tests or has a separate issue that describes the types of test that should be created. If no test is included it should explicitly be mentioned in the PR why there is no test.
  • [ ] Is this PR adding logic based on one or more clinical attributes? If yes, please make sure validation for this attribute is also present in the data validation / data loading layers (in backend repo) and documented in File-Formats Clinical data section!
  • [ ] Make sure your PR has one of the labels defined in https://github.com/cBioPortal/cbioportal/blob/master/.github/release-drafter.yml

Any screenshots or GIFs?

If this is a new visual feature please add a before/after screenshot or gif here with e.g. Giphy CAPTURE or Peek

Notify reviewers

Read our Pull request merging policy. It can help to figure out who worked on the file before you. Please use git blame <filename> to determine that and notify them either through slack or by assigning them as a reviewer on the PR

averyniceday avatar Sep 17 '24 19:09 averyniceday