VieCure 4.0’s Obsolete Drug Management workflow helps system administrators replace medications in treatment plans and rules flagged by the monthly First Databank update feed, remove obsolete products from the customer Medication List, and update user ordering favorites. Existing patient activation plans require separate clinical follow-up because they are not automatically changed. After replacement, users must manually remove the obsolete products through System Configuration > Orders > Medication List. The system admin must also review and update impacted rules as needed.
About This Guide
- Audience – Clinical / System Administrators
- Applies to – VieCure 4.0
- Verified against – 22 Oct 2026 teach-back
Before You Begin
- Work from System Configuration > Clinical > Obsolete Drug Management.
- Start with Active plans. Inactive plans can be displayed for reference, but the demonstrated workflow does not update them.
- Confirm the obsolete medication details before selecting a replacement: drug, strength/concentration, dosage form, route, status, and Generic Med ID when available.
- Choose the closest clinically appropriate replacement. A matching Generic Med ID can help identify a close match, but it is not required in every case.
- Confirm the replacement is enabled on the customer drug list. If needed, add/enable it before completing the replacement.
Replace an Obsolete Medication in Plans
- 1. Open Obsolete Drug Management – Go to System Configuration > Clinical > Obsolete Drug Management, select Plans, and filter Plan Status to Active.
- 2. Review impact – Expand the obsolete medication to see the active plans that contain it. Only plans containing a medication flagged obsolete by FDB appear in this list.
- 3. Select Edit Drug – Review the obsolete product details and the plans that will be updated.
- 4. Search for the replacement – Search by medication name and use filters such as Route to narrow the list. Match route, formulation, concentration/strength where possible, active status, and other medication identifiers.
- 5. Confirm the replacement is usable – Verify the product is enabled in the customer drug list. For medications where billing configuration is relevant, verify billing units/UOM are configured appropriately.
- 6. Select and review – Choose the replacement and review all displayed changes before continuing. The platform identifies the plans that will be affected.
- 7. Update – Select Update/Continue to complete the replacement. The processed obsolete medication is removed from the obsolete list for the addressed area.
- 8. Verify in Workbench – Open an affected plan in Workbench and confirm the new medication is present with the expected configuration.
Special Handling for Oral Medications
- A product swap may require manual prescription changes when dosage form or strength changes. In the teach-back example, zanubrutinib changed from an 80 mg capsule to a 160 mg tablet. The plan replacement succeeded, but prescription quantity and directions still required manual review and update.
- Review the prescribed dose against the intended regimen/reference content.
- Update quantity, tablet/capsule count, directions (SIG), cycle duration, and refill information as applicable.
- Repeat the prescription review for every impacted plan. Do not assume the medication replacement alone updates all prescription instructions.
Remove the Obsolete Product from the Customer Drug List
- 1. Open Medication List – Go to System Configuration > Orders > Medication List.
- 2. Locate the obsolete product – Search by medication name and verify the exact product using the displayed identifiers, including the FDB identifier when helpful.
- 3. Remove it – Select the obsolete item and choose Delete Selected Drug.
- Complete this after the replacement so the obsolete product is no longer available on the customer drug list.
Rules and Favorites
- Rules: use the Rules section of Obsolete Drug Management. The replacement interaction is similar to Plans, and replacing the drug updates impacted rules.
- Favorites: VieCure 4.0 displays users whose favorites contain the obsolete medication and supports replacing the medication in Favorites. This is an important 4.0 workflow improvement.
Verify Before You Finish
- Replacement – Correct medication, route, formulation and strength/concentration selected.
- Plan update – Affected active plans show the intended replacement in Workbench.
- Prescription – For oral products or strength/form changes, quantity and SIG/directions were manually reviewed and corrected.
- Customer drug list – Obsolete product was removed after replacement.
- Rules / Favorites – Impacted rules and favorites were reviewed and updated as needed.
- Patient impact – Existing patient activation plans were identified for separate follow-up because this workflow does not automatically change them.
Important Workflow Gap / Follow-Up
- Patient activation plans are not automatically updated. The demonstrated workflow does not provide a built-in report listing all patients whose active activation plans contain the obsolete drug. The team described this as a current manual/process gap. Coordinate with client clinical leadership, such as the lead pharmacist, to identify affected patients and update patient-specific plans before the obsolete product causes a downstream ordering issue.
- Do not assume removal from the customer drug list resolves existing patient plans. Patient-specific medication changes may require clinical review and additional edits, particularly when strength, dosage form, quantity, or directions change.
Example Replacement Patterns from the Teach-Back
- IV example: dexamethasone 4 mg/mL injection solution was replaced with an active product matching concentration, dosage form, route, and Generic Med ID. A 10 mg/mL option existed, but the same-concentration product was the closer match.
- Oral oncology example: zanubrutinib 80 mg capsule was replaced with a 160 mg tablet. The prescription then required manual adjustment to reflect one 160 mg tablet twice daily and the corresponding quantity.
Comments
0 comments
Article is closed for comments.