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

Feature/patient info #110

Merged
merged 32 commits into from
Jan 17, 2024
Merged

Feature/patient info #110

merged 32 commits into from
Jan 17, 2024

Conversation

CourtneyGosselin
Copy link
Member

@CourtneyGosselin CourtneyGosselin commented Dec 23, 2023

Ticket(s)

DIG-1276

Description

Introduce a detailed Patient Info exploration page, empowering users to effortlessly visualize patient JSON data in a concise table format. On the left, a user-friendly folder hierarchy provides easy navigation, complemented by the inclusion of ancestry table IDs seamlessly integrated into the specific table currently in view.

Expected Behaviour

When interacting with the clinical table, users can seamlessly delve into patient clinical information by simply clicking on a row, providing an intuitive deep-dive experience.

Screenshot PR

image

To do/Tickets before Merging Branch

Implement a user-friendly search functionality enabling users to efficiently navigate patient or patient table data.

Types of Change(s)
🪲 Bug fix (non-breaking change addressing an issue)
✨ New feature (non-breaking change introducing enhanced functionality)
💥 Breaking change (modification that would alter existing functionality)

Has it been tested for:

  • Prettier linter doesn't return errors
  • Production branch PR browser testing: Chrome, Firefox, Edge, etc.
  • Locally tested
  • Dev server tested
  • Production tested before merging into the stable/production branch

Copy link
Contributor

@OrdiNeu OrdiNeu left a comment

Choose a reason for hiding this comment

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

A few formatting & code changes

src/views/clinicalGenomic/clinicalPatientView.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/useClinicalPatientData.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/widgets/patientSidebar.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/clinicalPatientView.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/useClinicalPatientData.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/widgets/patientSidebar.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/widgets/patientSidebar.js Outdated Show resolved Hide resolved
src/views/clinicalGenomic/widgets/patientSidebar.js Outdated Show resolved Hide resolved
@OrdiNeu
Copy link
Contributor

OrdiNeu commented Jan 15, 2024

Can you rebase this off develop? There's a few merge conflicts

@CourtneyGosselin
Copy link
Member Author

CourtneyGosselin commented Jan 15, 2024

@OrdiNeu I started working on rebasing right after your PR got merged in, and I'm addressing both the merge conflicts and incorporating the styled changes for patient-info. I should have it sorted out soon

Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Signed-off-by: Courtney Gosselin <[email protected]>
Copy link
Contributor

@OrdiNeu OrdiNeu 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!

@CourtneyGosselin CourtneyGosselin merged commit f701116 into develop Jan 17, 2024
4 checks passed
@CourtneyGosselin CourtneyGosselin deleted the feature/patient-info branch January 17, 2024 22:54
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.

3 participants