Skip to content

(feat) : initial work to bring appointment model to form engine#155

Draft
donaldkibet wants to merge 2 commits intomainfrom
feat/InitialAppointment
Draft

(feat) : initial work to bring appointment model to form engine#155
donaldkibet wants to merge 2 commits intomainfrom
feat/InitialAppointment

Conversation

@donaldkibet
Copy link
Member

Requirements

  • This PR has a title that briefly describes the work done, including the ticket number if there is a ticket.
  • My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
  • My work includes tests or is validated by existing tests.

Summary

This PR forms initial work to bring support of managing appointment. The roadmap includes the following

  • Initial schema enhancement to support creating and editing appointments
  • Add the workload distribution calendar to the form engine
  • Add ability to create re-curing appointments together
  • Unit and e2e test for the feature

Screenshots

Kapture 2024-09-18 at 14 57 31

Related Issue

Other

@ojwanganto
Copy link

With this in the form engine, we can reduce the number of fields one has to fill by providing some defaults i.e. for the appointment type and status fields. We can make those defaults configurable in the form schema.
As a bonus, we can probably show how many appointments are scheduled on a date on change of the appointment date. I think a count will suffice

@ojwanganto
Copy link

How do we want to handle updates to appointments when a form is edited? Do we even want to support this?

@donaldkibet
Copy link
Member Author

donaldkibet commented Sep 19, 2024

At the moment, in edit mode, the form submits the edited fields, we can further enhance the form engine to check if the initial value have changed and submit the new changes

On the distribution calendar, thats the next feature am thinking of adding

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