Add aftercare without creating a competing patient record.

Make a handoff specification

For each item, record its source, destination, purpose, owner, update timing and correction method. Start with patient reference, owner connection, approved plan context and the information the team will document after review. Do not add medication changes or treatment decisions to an automatic transfer merely because a field is technically available.

Work through these acceptance checks

• Identity: demonstrate two similar patient names and confirm the correct owner, patient and clinic location are selected.
• Authorization: show who may approve the plan and who may view or review the episode.
• Transfer method: label manual entry, file export and approved native synchronization accurately; obtain vendor access before relying on the last option.
• Failure: use a deliberately incomplete fictional record and show who sees the problem, how it is corrected and whether retry creates a duplicate.
• Reconciliation: compare a sample of source and destination records after setup; record differences and resolve them before wider use.
• Closure: decide what goes back into the PIMS and who verifies completion of the handoff.

Worked example: a manual start

A clinician approves an aftercare plan. A designated staff member confirms the PIMS patient reference and creates the permitted care context in Vetomo. Another check confirms the correct owner connection before activation. After review, the clinical decision is documented in the PIMS. Write down the actual minutes and correction points in this sequence; do not describe it as automatic synchronization.

Write the exception and rollback procedure

A successful sample transfer does not answer what happens during an outage. Specify the person who pauses new handoffs, where unresolved items are recorded, how staff continue the approved process and who checks the backlog before normal work resumes. Do not overwrite the authoritative clinical record while investigating a mismatch. Use the established PIMS workflow until the responsible team has confirmed the correction.

For example, a retry after an interrupted manual handoff might create a second care context. Test that scenario with fictional data. The team must know how to identify the intended episode and resolve the duplicate through supported controls. The procedure should be understandable to a colleague who did not configure the system.

• List the fields needed for the chosen workflow; avoid an unexplained copy of the entire record.
• Record who approved any vendor access and the actual supported transfer method.
• Check a sample at both ends after corrections, including patient identity and active plan context.
• Reassess the handoff after a configuration change; yesterday’s test does not prove a newly changed workflow.