When a clinician records a diagnosis via the clinical note — and that diagnosis happens to be a lifelong condition like Type 2 Diabetes or Hypertension — shouldn’t that automatically form part of the patient’s Conditions list? Currently, the system does not support that.
The clinician has to fill in a clinical note, and then separately navigate to the Conditions module to capture the same information again. How can we avoid re-entering information that has already been documented during the visit?
When a qualifying diagnosis is saved, can we have a system prompt to “Add Diagnosis to the patient’s ongoing Conditions"? — with a Yes / No option.
Upon confirmation, the system automatically creates the Condition — sets the status to Active, sets the onset date to the current encounter date, and no additional data capture (in the Conditions module) is needed.
If the condition is already on the patient’s Conditions list, the system skips Condition creation - to avoid duplicate Conditions.
Any Condition promoted from a diagnosis can be updated as needed, i.e., the status and onset date.
I am new to OpenMRS development, but this idea sounds very helpful for users. It would save time because a long‑term diagnosis (like diabetes) could go straight into the patient’s Conditions list instead of typing it again.
I like the confirmation step and the check to avoid duplicates. I am still learning the codebase, but I would be interested to follow how this could be implemented and help where I can.
This goes in both directions: we want to make it easy to populate the condition list from encounter diagnoses and populate encounter diagnoses from the condition list.
My preference would be to have an option next to each diagnosis that isn’t already on the condition list that allows them to add the entry to the condition list. A slightly fancier approach would be an action button that gives choices of “Add to condition list” and “Add to past medical history” where the latter adds it as an inactive condition.
Having the affordance to add things to the condition list from the diagnosis list has a few benefits:
If only available for items not already on the condition list, it becomes a visual cue to distinguish between new & pre-existing diagnoses when looking at the list.
There’s no additional questions when adding a diagnosis. Some might want a checkbox in the diagnosis form to “Also add this to the condition list”, but then you have to deal with the case where it already exists. It could be the same amount of clicks to omit this checkbox and have them use the affordance on the diagnosis list.
No extra popups or dialogs needed.
Extra credit: having an temporary (until you re-render the list) “undo” affordance that lets you undo easily in the moment if you accidentally added the wrong entry to the condition list.
Please don’t do this. The onset date is an optional field and the relevant onset date is not the date diagnosed but the date something started being a problem.
We should maybe avoid adding an active condition, but adding it as historical seems still valid.
I would agree with @burke but also recognize that sometimes the visit Dx and condition are not identical but related (with condition often being somewhat more general). For example, the patient might have COPD, but their visit diagnosis is Exacerbation of COPD. Sometimes the visit Dx is highly specific like “sequelae of CVA” when perhaps it should be CVA on the condition list. I think we can at a minimum have a way to move identical concepts between the two lists, but we might want to add some intelligence particularly when elevating to condition list… (maybe even on using a condition on the visit where the user would be prompted to add specificity if appropriate).