Name the source of truth
For each object, document the authoritative system, its identifier, and the person or service allowed to change it. Include the visit, patient report, review, and handoff state.
Map the fields
Define required, optional, excluded, and redacted fields. Agree on what the destination needs and how unknown or missing information is represented.
Define identity and access
Specify the role and access scope needed to read or update each object. Verify that patient-facing information excludes staff-only reasoning.
Separate sent from delivered
Specify how the destination acknowledges receipt and how failures, retries, duplicates, and delays are handled. A local success state does not prove destination acceptance.
Rehearse before launch
Use synthetic records to validate mapping, audit history, recovery, and rollback. Compatibility and acceptance remain site-specific until the real destination has been tested.