You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The pull request updates the frontend code to use the encounter_date field instead of the admission_date field in the consultation model and form. This is to support different types of encounters and suggestions for the consultation, and to align with the changes in the backend. The pull request also refactors the suggestion field to use a new type and filter out deprecated options. The pull request affects several components that display or use the consultation data, such as ConsultationCard, ConsultationDetails, ConsultationForm, DischargeModal, ShiftDetails, DeathReport, TreatmentSummary, and PatientInfoCard. The pull request also updates the patient list API query parameters and the UI labels to use the encounter date instead of the admission date. The pull request also adds a new type called ConsultationSuggestionValue to the constants.tsx file to restrict the possible values of the suggestion field.
Add as const to CONSULTATION_SUGGESTION array and define ConsultationSuggestionValue type to restrict the possible values of the suggestion field in consultation model and form (link)
Change the type of the suggestion field from string to ConsultationSuggestionValue in consultation model and form (link, link)
Filter out the deprecated options from the CONSULTATION_SUGGESTION array when rendering the select field for the suggestion field in consultation form (link)
Add a new input field for the encounter_date field in consultation form and make it required for all suggestions (link)
Use the ConsultationModel interface defined in the Facility folder to type the consultation data in the Patient and Shifting folders (link, link, link)
@rithviknishad We truly appreciate your efforts. Thank you for taking the time to contribute; this is a very valuable contribution to us 🥇. We always welcome your contribution 🙂, so feel free to contribute to anything anytime, and never lose that spirit of innovation 🙌.
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.
rithviknishad
added
Backend
and removed
waiting for backend
merge conflict
WHAT
🤖[deprecated] Generated by Copilot at b4c8de2
The pull request updates the frontend code to use the
encounter_datefield instead of theadmission_datefield in the consultation model and form. This is to support different types of encounters and suggestions for the consultation, and to align with the changes in the backend. The pull request also refactors thesuggestionfield to use a new type and filter out deprecated options. The pull request affects several components that display or use the consultation data, such asConsultationCard,ConsultationDetails,ConsultationForm,DischargeModal,ShiftDetails,DeathReport,TreatmentSummary, andPatientInfoCard. The pull request also updates the patient list API query parameters and the UI labels to use the encounter date instead of the admission date. The pull request also adds a new type calledConsultationSuggestionValueto theconstants.tsxfile to restrict the possible values of thesuggestionfield.Required Backends
admission_datetoencounter_dateand clean column care#1728Proposed Changes
admission_datetoencounter_dateand white label the field based on decision after consultation choice #6668admission_datebased on consultation suggestion #6669@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers
Merge Checklist
HOW
🤖[deprecated] Generated by Copilot at b4c8de2
admission_datefield toencounter_datein consultation model, form, and UI components to reflect the fact that it can also represent the date of domiciliary care, out-patient visit, or encounter for other suggestions (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)as consttoCONSULTATION_SUGGESTIONarray and defineConsultationSuggestionValuetype to restrict the possible values of thesuggestionfield in consultation model and form (link)suggestionfield fromstringtoConsultationSuggestionValuein consultation model and form (link, link)CONSULTATION_SUGGESTIONarray when rendering the select field for thesuggestionfield in consultation form (link)encounter_datefield in consultation form and make it required for all suggestions (link)ConsultationModelinterface defined in theFacilityfolder to type the consultation data in thePatientandShiftingfolders (link, link, link)