Encrypt Patient Id for EGASP upload. #321
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anagperal
reviewed
Feb 7, 2025
| @@ -0,0 +1,9 @@ | |||
| import { FutureData } from "../entities/Future"; | |||
|
|
|||
| export type EncryptionData = { | |||
There was a problem hiding this comment.
This is not a domain entity?
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
📌 References
📝 Implementation
IMPORTANT NOTE
The following changes have to released with metadata changes to migrate AMR_GLASS_EGASP_PRE_ENCRYPTION_KEY program and also we need to create an event with secret key and nonce values.
📹 Screenshots/Screen capture
encryption-1.mov
encryption-3.mov
encryption-2.mov
🔥 Testing