-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track previous consultation consultations #1806
Comments
Adding this raises a concern, if a patient is readmitted to a different facility, the newer facility should not be able to access this information |
If the pre-readmission consultation's facility is not the same as the current consultation, the serializer should redact the consultation object. |
@rithviknishad why don't we just return the external_id of the previous consultation and let the use navigate to the consultation? This would take care of the access control and would also avoid nested serialization |
Yup! That's much simpler and cleaner! |
(Possible since we now have the |
Hey @rithviknishad I am working on this issue !! Please assign me. |
As discussed, let's add a field called:
cc: @Bhavik-ag @sainak |
readmission
consultations
Please assign me |
@Bhavik-ag unassigning due to no activity |
@rithviknishad Yup go ahead !! |
@Omkar76 If you aren't currently working on this issue , can I work on it? |
Hi @DraKen0009, I'm done implementing the requirements. I was just verifying the migrations locally. I will be sending a PR for this one in few minutes. |
Required Changes
last_consultation
(null if no previous consultation present)last_consultation
field and add logic to fill this field for existing data.The text was updated successfully, but these errors were encountered: