When a unit is already recorded but staff copy its data again
An operator sends pre-advice and staff search for service, unit and reference before registration. Amendments arrive later and movements are reported elsewhere. Edichemy scopes the connection to your TOS so available information supports agreed exchanges and discrepancies remain visible.
Plans and movements need different triggers
Pre-advice receipt does not confirm physical entry. Identify the fact authorising each response and keys linking visit, service and unit. Agree review for unmatched events instead of inventing another operation merely to finish processing.
Define the SIMPLE workflow separately
Identify documentation and sources for your terminal’s required SIMPLE exchange. TOS information may be reused, but an operator message does not establish another destination’s requirements. Separate terminal registration, outbound events and acceptance tests.
Before buying
Provide initial pre-advice, an amendment and an unknown reference. Check the TOS record, response and exception owners. State interface functions and maintainer work. This assesses the actual scope without promising every platform or software version.