(feat) O3-4363 - Add Visit context header to Order, Visit Note, and F… #2222
Conversation
This file contains 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
chibongho
commented
Jan 30, 2025
| import styles from './start-visit-dialog.scss'; | ||
|
|
||
| interface StartVisitDialogProps { | ||
| patientUuid: string; | ||
| closeModal: () => void; | ||
| visitType: string; |
There was a problem hiding this comment.
Removing this as it doesn't seem to be used. This was brought up before:
https://github.com/openmrs/openmrs-esm-patient-chart/pull/640/files#diff-7e621046e4d227da306880633891cb2d35e4f168f95967ff73f00aa973bc6d06R10
|
Size Change: -267 kB (-1.62%) Total Size: 16.2 MB
ℹ️ View Unchanged
|
|
Hi @chibongho! Thanks for your work on this. I have a suggestion to re-model the entire system. Could we integrate the header context into the workspace system itself? When calling Alternatively, we could create an extension slot based on the property mentioned above (rendered by the workspace system) and attach the RDE visit context extension (from the patient chart). However, I believe it would be better to handle all RDE-related tasks from a separate app (@openmrs/esm-patient-rde-app), as these changes would not only affect the patient chart but also the ward patient workspace. In summary, we have two main points to consider: rendering the extension slot (workspace renderer) and the extension (from the patient chart or the patient RDE app, whichever is more suitable). Please let me know your thoughts on this. Thanks! |
vasharma05
reviewed
Feb 6, 2025
There was a problem hiding this comment.
I am seeing a lot of duplicated work which can be done in the useVisit hook.
Alongside, we should work on the workspace system to render an extension slot if we pass the slot names. Hence we won't have to duplicate our effort in every patient workspace and directly use the workspace system to do out work.
A sample example will be:
import {launchWorkspace} from '@openmrs/esm-framework';
launchPatientWorkspace = (workspaceName, additionalProps) => launchPatientWorkspace(workspaceName, {...additionalProps, renderExtensionSlots: ['visit-context-header-slot']}
| return ( | ||
| <> | ||
| {isRdeEnabled && <ExtensionSlot name="visit-context-header-slot" state={{ patientUuid }} />} |
There was a problem hiding this comment.
This is what I am talking about, why should we go manually into every patient chart workspace and render the extension slot, when we can use the workspace system to do the same?
| return ( | ||
| <div className={styles.container}> | ||
| {isRdeEnabled && <ExtensionSlot name="visit-context-header-slot" state={{ patientUuid }} />} |
| type OpenmrsResource, | ||
| type Privilege, | ||
| type Visit, | ||
| } from '@openmrs/esm-framework'; | ||
| import useSWR, { mutate } from 'swr'; | ||
| import { type ChartConfig } from '../../config-schema'; | ||
|
|
||
| export function useInfiniteVisits(patientUuid: string) { |
There was a problem hiding this comment.
Why re-working on what is already implemented in the useVisit hook
There was a problem hiding this comment.
useVisit() makes a request to fetch active visit(s) for the patient, and another request to fetch the visit currently in the visit context. This function is different; its using useSWRInfinite() to get all the visits of the patient.
| import { getVisitStore, useStoreWithActions, type Visit } from '@openmrs/esm-framework'; | ||
|
|
||
| export function useVisitContextStore() { | ||
| return useStoreWithActions(getVisitStore(), { |
There was a problem hiding this comment.
Shouldn't this be moved into the react utils? Also, isn't this indirectly useVisit?
There was a problem hiding this comment.
It's not useVisit() in that it doesn't make requests to fetch visits, but it's not a bad idea to merge them into the same hook.
And yes, it should be moved to react-utils. I plan to do it in a separate PR. I also have a TODO in VisitContextHeader about moving a useEffect hook into useVisit (in react-utils) as well.
vasharma05
requested changes
Feb 6, 2025
There was a problem hiding this comment.
I’ve noticed a lot of repetitive work that could be handled using the useVisit hook. Additionally, we should improve the workspace system to render an extension slot when we provide the slot names. This way, we won’t have to duplicate our efforts in each patient workspace and can directly use the workspace system to accomplish our tasks.
Here’s a sample example:
import {launchWorkspace} from '@openmrs/esm-framework';
launchPatientWorkspace = (workspaceName, additionalProps) => launchPatientWorkspace(workspaceName, {...additionalProps, renderExtensionSlots: ['visit-context-header-slot']}
Not sure what's duplicated. Can you elaborate?
It only takes 1 extra of of code to render a slot, across 3 different patient chart workspaces. Adding this feature will add more complexity. It also assumes the slot will be placed at the top, which is less flexible than just adding an slot within the workspace wherever we want it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…orms workspaces
Requirements
Summary
This PR adds RDE features: a new visit context header to the patient chart workspaces (order / visit note / clinical forms), and a new visit switcher modal accessible from the visit context header.
The concept of a "Visit Context" when viewing a patient chart is not new; previous RDE work has that when the
rdefeature flag is turned on). Screenshots from before this change:Instead of rendering in the top nav, the visit context header is rendered at the top of the workspace with this change, See the mockups here.
The new changes are behind the existing
rdefeature flag, so they should not be noticeable for most people.Notes:
encounterDatetime), but it doesn't work. See: https://openmrs.atlassian.net/browse/O3-4420encounterDateTimeset to the visit's start time. However the order'sdateActivatedfield is set tonow. Is that expected?now, and is tied to the active visit, instead of the past visit in the visit context.Screenshots
The visit context header in a workspace:
The modal that opens when clicking on "change" in the visit context header. The same modal also shows when the user tries to open the order / visit notes / forms workspace without a visit (active or past) in context.
Related Issue
https://openmrs.atlassian.net/browse/O3-4363
Other