Sample Decryption and Redirects for Epic #10997
Open
+60
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
/api-legacy/epic/sample/{sampleID}
): takes an encrypted sample ID, decrypts, and redirects to the appropriate sample/api-legacy/epic/patient/{patientID}
): takes an encrypted patient ID, decrypts, and redirects to the appropriate patientapi-legacy/epic/{sampleID}/exists
): takes encrypted sampleID, decrypts, and checks for existence (for determining whether to add a linkout from Epic)mpath.token
): optional, contains api-key for using the decryption servermpath.decryption_url
): optional, contains URL to decryption server