Define the record before asking for an export
List residents and facilities, medication-review history, recommendations, responses, status history, users and authorship, timestamps, report artifacts, attachments, configuration, and source identifiers. Mark which elements are clinically or operationally necessary after termination.
This is not a claim that every system must export every internal field. It is a way to expose the buyer's continuity requirement before contract language fixes the available options.
Request both human and machine tests
Open a sample PDF or archive as a future reviewer would. Separately inspect structured files for stable identifiers, field definitions, dates, encoding, relationships, and missing values.
A CSV can be structured yet unusable if status codes are unexplained or resident relationships are lost. A polished PDF can preserve reading context yet be difficult to migrate into the next workflow.
Put the exit path in the commercial review
Confirm who may request export, available formats, delivery method, preparation time, cost, post-termination access, correction handling, vendor retention, and deletion or return commitments. Obtain qualified contract and privacy review.
For RxPertise or any other migration, do not assume perfect parity. Test representative history, attachments, recommendations, dates, and reports, and record what will not transfer.