Repository navigation
feat(patient): lab results viewer with abnormal-value highlighting - #132
VeronicDev wants to merge 18 commits into
Conversation
Patient results list + detail per lab order (status, facility, date, summary, abnormality flag), lazy native PDF/image viewer with download, and calm next-steps + acknowledgement status for abnormal/critical. Withheld-pending-review results render as a waiting notice. Assumed contract against docforum-core DocForum#72 documented in ARCHITECTURE_ESSENTIALS.md; ROADMAP.md Phase W2 updated.
|
@VeronicDev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
@VeronicDev pls fix conflicts |
|
@VeronicDev fix CI |
|
CI is red on typecheck: |
|
@VeronicDev Thanks for the PR. It can't be merged yet. To unblock it: CI is failing. Here's what broke:
Please fix these errors and run the same steps locally before pushing ( Merge conflicts: this branch conflicts with Push to this same branch and CI will re-run. Once it's green and conflict-free, it'll be reviewed for merge. |
CI Checks Failed — Action NeededThe continuous integration checks on this pull request are failing. I can't merge until all required checks pass. Failing checks:
What to do: review the failing checks in the "Checks" tab above, fix the issues in your code, and push the changes. |
|
@VeronicDev CI is failing on this branch against the latest Frontend (typecheck + test + build)
|
|
@VeronicDev CI is failing on this branch against the latest Frontend (typecheck + test + build)
|
Fix AppliedRestore LabResult types, results-service methods, routing, and resolve typecheck errors in results feature. |
|
@VeronicDev pls fix CI |
|
@VeronicDev CI is failing on this branch against the latest Browser (journeys + accessibility + visual) Frontend (typecheck + test + build)
|
Fix AppliedRestore missing types (PatientResultsPage, PatientResultDetailPage, SlotGenerationResult, BlockRangeResult, EvaluatedFlags, NotificationChannel, NotificationPreferences, AvailabilitySlot.appointment) in models.ts and App.tsx, fix type safety in useSlotManagement and preferences.test.ts |
|
@VeronicDev CI is failing on this branch against the latest Frontend (typecheck + test + build) The missing-import errors from before are fixed, but your branch's types and tests don't match |
|
@VeronicDev This PR now has merge conflicts with git fetch upstream # upstream = https://github.com/DocForum/docforum-web.git
git rebase upstream/main
# resolve the conflicts, re-run the tests, then:
git push --force-with-leaseThe usual culprits are shared docs like Automated message. It won't repeat unless the PR conflicts again after your next push. |
Closes #24.
Implements PRD §4 patient core flow (results are the end of the book → consult → order → fulfil thread).
What changed and why:
Assumed contract (backend #72 not merged — documented in ARCHITECTURE_ESSENTIALS.md 'Known assumptions'):
Tests:
Screenshots: not attached — no browser tool in this environment, so not visually verified (same disclosed gap as prior UI work here). Please confirm rendered result at the preview URL.
ROADMAP.md Phase W2 + changelog updated; ARCHITECTURE_ESSENTIALS.md Known assumptions added.