Skip to content
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

Enabling the Patient to Add to their Data via the LLM Assistant #58

Merged
merged 7 commits into from
Mar 7, 2024

Conversation

kcallon
Copy link
Contributor

@kcallon kcallon commented Mar 7, 2024

Enabling the Patient to Add to their Data via the LLM Assistant

♻️ Current situation & Problem

Currently, the patient is only able to ask about what their current data is and ask questions about it. They are unable to update their data using the LLM Assistant.

⚙️ Release Notes

-This update allows for the patient to add to their list for surgery, allergies and medical history. Currently these LLM Assistants are being kept separate to ensure all functionality works and because medications does not allow for a live update.
-It does this by using an LLM function call to collect variables dependent on the view (so for allergies it collects allergy name and reaction type), and then adding this data to the global data variable. The changes persist so that the user can then see their updated data when they go back to their view page.

📚 Documentation

Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.
You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.

✅ Testing

Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.
This section describes important information about the tests and why some elements might not be testable.

📝 Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

Copy link

codecov bot commented Mar 7, 2024

Codecov Report

Attention: Patch coverage is 0% with 80 lines in your changes are missing coverage. Please review.

Project coverage is 13.97%. Comparing base (426d67b) to head (d77db53).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
- Coverage   14.29%   13.97%   -0.31%     
==========================================
  Files          55       55              
  Lines        2591     2671      +80     
==========================================
+ Hits          370      373       +3     
- Misses       2221     2298      +77     
Files Coverage Δ
Intake/Medical History/MedicalHistoryView.swift 0.00% <ø> (ø)
Intake/Surgery/SurgeryView.swift 0.00% <ø> (ø)
...ntake/Medication View/MedicationLLMAssistant.swift 0.00% <0.00%> (ø)
Intake/Allergy Records/AllergyRecords.swift 0.00% <0.00%> (ø)
Intake/Allergy Records/AllergyLLMAssistant.swift 0.00% <0.00%> (ø)
Intake/Surgery/SurgeryLLMAssistant.swift 0.00% <0.00%> (ø)
...e/Medical History/MedicalHistoryLLMAssistant.swift 0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 426d67b...d77db53. Read the comment docs.

@kcallon kcallon requested a review from nriedman March 7, 2024 06:58
Copy link
Contributor

@nriedman nriedman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@kcallon kcallon merged commit 897bd71 into main Mar 7, 2024
7 checks passed
@kcallon kcallon deleted the llm-assistant branch March 7, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants