BN-71 | Add. DiagnosesForm To Consultation Pad

[rahu1ramesh]

JIRA → BN-71

This PR introduces the ability to search, select, and manage diagnoses from the consultation pad as part of the patient’s clinical documentation. It lays the groundwork for diagnosis capture in the consultation workflow, in alignment with the FHIR Condition resource model. This implementation is also includes the diagnosis saving functionality.

---

Key Features

• Enables diagnosis search using a terminology source (OpenMRS Dictionary / Snowstorm / CIEL).
• Allows providers to add multiple diagnoses with associated certainty.
• Supports removal of added diagnoses before final submission.
• Displays relevant messages for duplicates or empty results.
• Provides locale-based internationalisation for all visible labels.
• Backend integration for saving diagnoses.
• Storybook for all new components

---

Implementation Details

• Diagnosis Search:

  • Integrated with the OpenMRS REST API via /ws/rest/v1/bahmni/terminologies/concepts.
  • Implements input debouncing to trigger search.
  • Displays a dropdown list of matching results with fallback messaging when no matches are found.
  • Prevents duplicate entries by validating selected diagnoses.

• Certainty Selection:

  • Adds a dropdown for each selected diagnosis with options: Provisional and Confirmed.

• Diagnosis Management:

  • Enables removal of individual diagnoses via a cross icon.

• Internationalisation:

  • Fully integrated with the locale dictionary to support multilingual label rendering.

---

Testing & Type Definitions

• Unit and basic integration tests are included for key components and logic paths.
• TypeScript types are defined for diagnosis entries and verification status options.

---

Screenshots

Search Diagnoses	Add Diagnosis	Add Certainty	Add Duplicate Diagnosis	Missing Certainty	Save Success

---

[mohan-13]

The item selection using keyboard is not working. When I do a down arrow on the filtered items and then hit Enter, always the first item is selected.

[mohan-13]

The searchTerm, diagnosesErrors doesn't need to be a concern / part of consultation pad. This can be controlled within DiagnosisForm. Only the selectedDiagnosis can be part of ConsultationPad, which will be consumed during Consultation Bundle creation.

[rahu1ramesh]

I have addressed this. Thanks for taking a look

[mohan-13]

Same here, this can be moved into DiagnosisForm. The parent (ConsultationPad) component is only interested in selectedDiagnosis, whatever happens before that can be the components action itself.

[rahu1ramesh]

I have addressed this. Thanks for taking a look

[mohan-13]

This method of mocking seems to be inconsistent with how other services are mocked. Can we mock at beforeEach level ?