Desk briefpolicy

HTI-5 gives certified software more ways to reconcile medication lists

Starting December 28, a revised federal certification criterion gives health IT developers more latitude in how they display incoming data during reconciliation. Before a facility’s next software update, walk through what a pharmacist can see, confirm, and find again.

Two people looking at a laptop together
A joint walkthrough can show what the receiving team sees at each step of a medication handoff.

What changes in December

The Office of the National Coordinator for Health Information Technology (ONC) published the HTI-5 final rule on October 28. The proposed rule would have removed the clinical information reconciliation and incorporation criterion at 45 CFR § 170.315(b)(2). The final rule keeps it and changes how a module can demonstrate that it meets the criterion, effective December 28, 2026.

The prior criterion called for a simultaneous view of data from at least two sources. The revised criterion removes that display requirement and its references to specified exchange formats for incoming data. It allows a module to demonstrate reconciliation in workflows beyond receipt of a transfer or referral summary, such as an internal transfer or information supplied by a patient. That flexibility leaves room for different screen designs and data paths across products and versions.

ONC expects modules that already conform to meet the revised criterion as implemented. If a facility and its supplier already use a side-by-side view, ask whether they plan to keep that view in the installed version. For a new purchase, ask the supplier which module and version were certified and which exchange workflow it can demonstrate with the facility’s partners. A test of an internal transfer answers a different question from a transfer arriving from another organization.

The confirmation step remains

The revised text still calls for matching received data to the correct patient and creating a reconciled list of medications, allergies and intolerances, and problems. The user must be able to review and validate the final data. After the user confirms, the module must be able to update the list automatically and incorporate the data using at least the applicable version of the standard specified in § 170.213.

The two dates to keep straight apply to different criteria. The reconciliation changes take effect in December. Under the separate transitions-of-care criterion, specified Direct edge-protocol and clinical document creation and display requirements expire January 1, 2030. That later date applies to certification requirements. Ask the facility or developer for the release schedule and exchange options that apply to the version the care team uses.

Follow one transfer with the receiving team

An independent consultant pharmacist can ask the facility’s clinical lead and software contact for a short walkthrough in a test environment. Start with two synthetic lists for a hospital return, with one difference that someone must resolve. Use the route the facility expects to use in practice, then have each person open the screen their role would normally see.

First, find the sending organization and the date of each list, if the system presents them. Follow the difference from the incoming material to the review screen. If staff need to open a second view or document for context, count that step and ask who has access. Show where a question can stay visible if the decision is deferred, and who can see it at the next shift change.

Then follow the confirmation through to the current list. Ask the covering pharmacist to find the source material, the updated list, and any unresolved question using their usual permissions. Write down which steps the team demonstrated and who owns the gaps. These are local workflow and purchasing questions. The outcomes will depend on the module, interface, configuration, and access each facility has in place.

If the facility relies on more than one hospital, record which connection the team actually tested. Use that record when planning the next test after a software release or a change in the sending partner.

Keep the monthly review on its own schedule

The rule changes health IT certification. The nursing-facility pharmacy-services regulation at 42 CFR § 483.45(c) continues to govern the monthly pharmacist review and reporting of irregularities. A confirmed list can be an input to that review. The pharmacist still needs to know which record reflects the facility’s current list and where the facility keeps the review and any follow-up.

About the author

Lena Ortiz

Lena covers events, workplace conversations, and the practical questions surfacing across the consultant-pharmacy community, using public discussions as leads rather than proof.

Read Lena Ortiz's editorial profile