Medication Change Verification Workflow for Washington AFHs

A medication change verification workflow for a Washington Adult Family Home should preserve the original order, requested change, date, contact for written verification, verification source, pharmacy receipt, facility review, and activation on the resident's medication profile and MAR.

A phone message, appointment note, pharmacy shipment, and complete written order are not interchangeable. If software updates the active medication before the required information is verified, caregivers can see conflicting directions or administer from an incomplete record.

This guide maps the current Washington medication-log requirements to a safe operational workflow. It was reviewed against official sources on August 8, 2026. Providers should confirm current rules, practitioner authority, pharmacy procedures, nurse-delegation conditions, and facility policy rather than treating this article as clinical or legal advice.

Start with the current Washington rule

WAC 388-76-10475 addresses the resident medication log. For changes or new prescribed medications, the current text includes the change, date, a logged call requesting written verification, a copy of written verification received from the practitioner through listed means or on a new original labeled pharmacy container, and receipt of the changed or new medication from the pharmacy.

WAC 388-76-10430 addresses the medication system, including assessment, negotiated care plan, current log, medication receipt, and current medication records.

Software can organize this evidence and status, but it should not decide clinical validity or practitioner authority.

Identify the resident and facility first

Every change record needs:

• Active facility
• Resident using more than initials or first name
• Current medication and order identifier
• Practitioner
• Connected pharmacy
• Person reporting the change
• Date and time received
• Source channel

If the pharmacy serves several homes, the facility boundary must remain visible through resident search, order entry, message, attachment, acceptance, and report.

Changing the resident during data entry should not silently preserve resident-specific order, allergy, prescriber, or document data. If generic medication lookup data is retained, require review of every resident field.

Before creating a new order, search active, held, discontinued, pending, and duplicate medications for the resident.

Distinguish types of medication change

The workflow should identify whether the information describes:

• New medication
• Dose or strength change
• Dosage-form change
• Route change
• Frequency change
• Administration-time change
• Directions or parameter change
• Start, stop, or end-date change
• Temporary hold
• Resume after hold
• PRN indication or limit change
• Discontinuation
• Replacement product or manufacturer with unchanged order

These changes have different effects. A strength change may require a new supply and end the prior schedule. A timing change may update future slots without changing the prescribed dose.

Do not put the complete difference in a free-text note only. Preserve structured before-and-after values plus the source document.

Capture the initial report without activating it

The first communication may be verbal, a phone message, fax cover, portal message, appointment note, family statement, or pharmacy clarification. Record it as pending verification unless the reviewed source already meets the applicable requirement.

Initial record fields can include:

• Reporter and role
• Reported practitioner
• Received date and time
• Medication
• Reported change
• Effective timing if stated
• Immediate instruction or concern
• Source channel
• Attachment
• Recipient at the home
• Follow-up owner

Label the state clearly: “reported—verification pending.” Do not show it as the current medication direction on the caregiver MAR.

If immediate action is needed, staff follow the facility's practitioner-contact and emergency process. Software should not invent an interim instruction.

Log the request for written verification

WAC 388-76-10475 includes a logged call requesting written verification of the change.

The contact log should preserve:

• Practitioner or authorized office
• Telephone number or contact route used
• Date and time
• Person making the call
• Person reached or voicemail
• Exact change requiring verification
• Requested delivery method
• Response expectation
• Repeat attempts
• Escalation

A “requested” checkbox without time, contact, and user is weak evidence. Show unanswered, message left, reached, promised, received, and unable-to-contact states.

Avoid creating a new task for every retry. One verification request can have a contact-attempt timeline and an assigned owner.

Notifications should be idempotent so a background job does not send the same reminder repeatedly.

Receive and validate written verification

The current rule text recognizes written verification through specified delivery methods or on a new original labeled pharmacy container. The facility should review the actual received evidence.

Capture:

• Source and practitioner identity
• Received date and time
• Receiving user
• Medication name
• Strength and dosage form
• Dose
• Route
• Frequency and administration times
• Exact directions or parameters
• Start, end, hold, resume, or discontinue dates
• Signature or authorization information
• Resident identity
• Verification document or labeled-container evidence

The medication search catalog can populate editable standardized fields, but the received order remains authoritative. Do not add a medication merely because its name exists in RxNorm or an FDA database.

If required information conflicts or is missing, return the record to clarification instead of guessing.

Compare the change with the current active order

Show a side-by-side review of:

• Former value
• Proposed value
• Effective date and time
• Future MAR occurrences affected
• Existing supply and new supply status
• Refill or pharmacy request
• Related delegation or care-plan information
• Allergies and resident-specific warnings

Use clear labels rather than a dense raw-data diff. Highlight only changed fields.

The user should be able to open the former order and received verification. Do not hide discontinued directions after acceptance.

For administration-time changes, explain whether today's already-due or recorded slots will change. Prevent the software from creating a duplicate dose for the same effective period.

Confirm receipt from the pharmacy

WAC 388-76-10475 addresses receipt of the changed or new medication from the pharmacy.

Keep separate states for:

• Pharmacy preparing
• Shipped or out for delivery
• Delivered by pharmacy or courier
• Physically received by the facility
• Quantity and label checked
• Ready for facility activation

The pharmacy can mark delivery; an authorized facility user should mark physical receipt. Those are different facts.

Record resident, medication, strength, form, quantity, lot or expiration when used, received date and time, receiving person, discrepancy, and storage action.

A delivered alert should remain open if the home has not confirmed receipt. Once received, all linked counts should update automatically.

The pharmacy-AFH medication coordination guide explains secure facility authorization, resident-specific orders, acceptance, delivery, and receipt.

Use facility acceptance as a controlled transition

The authorized reviewer should see a single acceptance screen with:

• Resident and facility
• Current order
• Proposed structured change
• Written verification
• Contact history
• Pharmacy receipt
• Effective timing
• Warnings and conflicts
• MAR impact
• Reviewer action

Actions can include accept, reject, request clarification, or hold review. Preserve reviewer, date and time, decision, and reason where appropriate.

Acceptance should atomically create or revise the medication, end or supersede the old order when required, generate future MAR slots, link documents, and resolve the incoming-order task. A partial failure must not leave the profile changed while the MAR remains old.

Use idempotency so repeated clicks cannot activate the change twice.

Preserve the former order and effective period

Never overwrite the old medication record to look as though the new direction always applied. Preserve:

• Former order and schedule
• Active period
• Source and acceptance
• Administration history
• Refusals, holds, and corrections
• Refill and pharmacy events
• Superseding order

The current profile shows the new active state. Historic MARs show the order and instructions that applied at the time.

If the change is later corrected, create another amendment or verified order rather than rewriting both versions.

The audit-trail guide explains additive corrections, before-and-after values, system actors, and medication history.

Handle discontinuation and remaining supply

A discontinuation is a medication-order change and may create disposal or return work for remaining supply.

The workflow should:

• Verify the discontinuation
• Record effective date and time
• Stop future MAR occurrences
• Preserve prior administrations
• Identify remaining medication
• Stop refill requests and pending fulfillment where appropriate
• Create disposal or transfer task
• Notify relevant roles
• Update active medication lists

Do not delete the medication from the resident profile. Mark it discontinued and retain history.

If a pharmacy order is already in transit, route it to clarification or return handling rather than silently accepting it.

Address holds and resumptions explicitly

Temporary holds need start condition or time, scope, source, and review or end condition. Resume instructions require verification through the appropriate process.

Do not treat a hold as discontinuation or mark held doses as refused. The MAR should show held with the linked instruction.

When the hold ends, generate future occurrences from the reviewed resume point without adding missed alerts for the authorized hold period.

Preserve the practitioner communication, written verification, acceptance, and affected dose history.

Align assessment and negotiated care plan

A medication change may affect assistance level, delegation, monitoring, side-effect response, away-from-home management, or resident preference.

The application can flag the assessment or negotiated care plan for review without editing them automatically.

The Washington resident-assessment guide explains medication management, current medication sources, and reconciliation. The plan records how medication services will be provided.

Caregivers should receive the new current instruction and any approved training or handoff before the effective administration, not simply a generic “medication updated” badge.

Keep alerts state-aware

Useful queues include:

• Reported change awaiting verification request
• Practitioner contact attempted
• Written verification pending
• Clarification needed
• Pharmacy fulfillment pending
• Delivered but facility receipt missing
• Ready for acceptance
• Accepted but activation failed
• Disposal or return pending

Each count should open the matching records and identify the next responsible role.

Do not clear the verification alert when a file is uploaded if the structured fields remain incomplete. Do not keep the alert after an authorized acceptance and successful activation.

Report medication changes accurately

Reports can include:

• New and changed orders by date
• Verification requests and response time
• Written verification source
• Clarifications
• Pharmacy delivery and facility receipt
• Acceptance and rejection
• Effective-date history
• Discontinuations and holds
• Activation failures
• Audit events

Filters should include facility, resident, medication, practitioner, pharmacy, change type, status, reported date, verification date, effective date, and acceptance date.

The medication-reporting guide explains filtered PDF, print, structured export, and MAR reconciliation.

Reports should not expose other facilities served by the same pharmacy.

Test the complete change workflow

Use demonstration residents and ask the vendor to:

1. Record a verbal dose change without activating it.
2. Log two practitioner contact attempts.
3. Upload incomplete written verification and request clarification.
4. Receive a complete verified change.
5. Compare it with the current order.
6. Record pharmacy delivery and separate facility receipt.
7. Accept the change and inspect future MAR slots.
8. Verify historic MARs retain the former order.
9. Test a hold, resume, and discontinuation.
10. Attempt duplicate acceptance during a slow response.
11. Switch facilities and test pharmacy resident search.
12. Generate a medication-change and audit report.

Simulate failure between acceptance and MAR generation. The transaction should roll back or show a recoverable unresolved state rather than split truth.

Frequently asked questions

Can a verbal medication change update the MAR immediately?

The facility should follow current Washington requirements and professional instructions. The software should preserve the initial report and required verification workflow rather than treating an incomplete message as a complete order.

What written verification should be stored?

Store the complete received source and structured medication details, including resident, medication, directions, dates, practitioner information, and the source recognized by the applicable rule.

Is pharmacy delivery the same as facility receipt?

No. The pharmacy or courier can report delivery; the home should separately confirm physical receipt and any discrepancy.

Should the old order be deleted?

No. End or supersede it as appropriate and preserve its source, effective period, administration history, and relationship to the new order.

Can medication catalog data verify an order?

No. Catalog data supports standardized entry. The resident-specific practitioner and pharmacy documentation remain the authoritative source.

Verify before changing the active medication

A reliable workflow moves from reported change to logged verification request, received written evidence, pharmacy receipt, facility review, and controlled activation. Every step remains resident- and facility-specific.

AFH Manager can connect medication-change intake, practitioner contact, written verification, pharmacy delivery, facility receipt, side-by-side review, acceptance, MAR activation, alerts, audit history, and reports. Providers can test the full transaction with demonstration medications before rollout.