(feat) O3-5169: Extend Renew action to Active Medications and standardize Reorder as Renew

[UjjawalPrabhat]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• My work is based on designs, which are linked or shown either in the Jira ticket or the description below. (See also: Styleguide)
• My work includes tests or is validated by existing tests.

Summary

This PR standardizes medication continuation behavior in OpenMRS O3 by unifying Renew as the single action for continuing medications across both Active and Past Medications.

Previously, Renew termed as 'Reorder' was only available for past medications while active medications required manual re-entry, and the overlapping Reorder action caused inconsistent terminology. This change improves clinician workflow and aligns with agreed community behavior.

Screen Recording

Screen.Recording.2026-01-15.190623.mp4

Related Issue

O3-5169

Other

Talk discussion

Related PR

[UjjawalPrabhat]

@denniskigen @VeronicaMuthee Could you please review this PR?

[VeronicaMuthee]

@UjjawalPrabhat, this looks good to me per the video you have shared. Please add Ian and Dennis as your reviewers for the technical details

[UjjawalPrabhat]

@denniskigen @VeronicaMuthee Could you please review this PR?

@ibacher

[VeronicaMuthee]

@UjjawalPrabhat, you haven't added reviewers as yet. Are you able to do that?

[UjjawalPrabhat]

@UjjawalPrabhat, you haven't added reviewers as yet. Are you able to do that?

@VeronicaMuthee, I don't have the required permission to add reviewers. Perhaps you could help me with that? 😅

[denniskigen]

We should add the uuid: order.uuid to line 250 in buildMedicationOrder to fix duplicate order detection in the order basket.

After refactoring to buildMedicationOrder, renew/discontinue basket items no longer get a uuid. The UI still uses uuid for duplicate prevention:

const alreadyInBasket = items.some((x) => x.uuid === medication.uuid);

in the OrderBasketItemActions function.

Previously both handleDiscontinueClick and handleReorderClick set uuid: medication.uuid inline (see pre‑refactor code), so the check worked. Now buildMedicationOrder returns no uuid (see this), so alreadyInBasket always returns false and users can add duplicate renew/discontinue items.

Note that this is a client-side field only; it's not sent to the backend (see prepMedicationOrderPostData). The backend uses previousOrder for order linkage, and it will reject overlapping duplicates anyway via AmbiguousOrderException("Order.cannot.have.more.than.one") in OrderServiceImpl, so preventing duplicates client‑side aligns with backend constraints.

[denniskigen]

Can we also change this line to read "renew" instead of "reorder"?