[PRMP-827] Review - API Integration for Review #964
Conversation
This file contains hidden or 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
lillie-dae
force-pushed
the
PRMP-827
branch
4 times, most recently
from
10e8f29 to
d24947f
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Overview
This ticket covers implementing the API calls for review.
Jira ticket: PRMP-827
Description
API calls required
Search Patient GET call
Review GET by ID call
Retrieve presigned URL
Display demographics (patient GET)
Preview or download
If PDF, preview document without download
If not PDF, no preview, just download
Accept is patient or not patient
If details match, upload journey
If canBeDiscarded is true and 1-1 document relationship is true
document exists -> append journey
document DOES NOT exist -> add journey
If canBeDiscarded is true and 1-1 document relationship is false, switch to accept/reject screen
If canBeDiscarded is false, move to upload process on accept click
If details don't match, go to transfer to correct patient
In instance a data controller can discard, Based on document type config attribute
canBeDiscarded attribute means that the data controller has the ability to reject a file / document without saving it in the NDR
Checklist
Tasks for all changes:
I have run git pre-commits.(WIP)Deploy - Sandbox- workflow run - TBCSANDBOX Full- Deploy feature branch to sandbox- workflow run - TBCAdditional tasks for UI changes (delete if not applicable):
SANDBOX - UI Smoke Test- workflow run - TBC