Week7

LibreHealth

PROGRESS MADE THIS WEEK:

Hi, As discussed in the last week’s blog , Week 7 was to be used for the following tasks:

  • Complete the visit-nurse workflow (the parts which are not implemented yet.)
  • Complete the visit-provider workflow.
  • Start working on the e-prescription workflow.

This week I was a little busy with some academic work, hence all of the above pointers were not possible, Hence the last 2 pointers will be shifted to the upcoming week. (WEEK 8)

DESCRIPTION:

This week I have mainly worked on completing the visit nurse workflow. As the vitals signs and medication statement components were merged, the react-ehr application was updated to include the screens which use these components in the visit-nurse workflow.

Another interesting thing is that most of these screens are having almost a similar structure, hence there is a possibility that a single component can be created as a layout component for different screens.

NEXT WEEK’s PLAN:

  • Complete the visit-provider workflow.
  • Start working on the e-prescription workflow.
  • fix build fail.

The dosage component seems to cause a build failure, which will be fixed in the coming week.

reiterating the pointers from last week’s blog for the implementation points of the visit-provider workflow:

  • First screen contains a find-patient component to select a patient.
  • After the patient is selected a redux action is triggered which updates redux state and stores the selected patient Id.
  • Another redux action updates the active screen and changes it to that of patient encounters.
  • The patient encounter screens contains all the patient encounters which are fetched using the stored patient Id.
  • On clicking an encounter a redux action updates active page to dashboard.
  • the dashboard page contains 2 tab: physical exams, order.
  • the physical exams tab shows the observations of the patient and contains a component to create any observation.
  • the orders tab will be used to create orders using service request component.
  • the user can log out and select a different patient to repeat the above points.

the pointers for the implementation points of the e-prescription workflow:

  • First screen contains a find-patient component to select a patient.
  • After the patient is selected a redux action is triggered which updates redux state and stores the selected patient Id.
  • Another redux action updates the active screen and changes it to that of patient encounters.
  • The patient encounter screens contains all the patient encounters which are fetched using the stored patient Id.
  • On clicking an encounter a redux action updates active page to dashboard.
  • the dashboard page contains a single screen with a search component for allergies and medications of the patient.
  • the screen also contains a create medication request component.

see you next week 😄.


Author

Shashwat

Posted on

2021-07-27

Updated on

2021-07-27

Licensed under