Processing Rules
Translations and Mapping
Because of WEM's nature as Middleware, the WEM software application has a mapping subsystem that powers translations between the MIS and EBT systems.
Error Codes
Error codes are recognized differently among the EBT and MIS systems that route transactions through WEM. Read more about error code mapping.
Realtime Messages
Realtime messages also have similar transformation rules applied to them. In some cases they may need to make multiple calls to get the information in order to fulfill the request.
Batch Files
Batch files are transformed by WEM from one format to another. This represents a great deal of the processing of batch files.
Troubleshooting File Processing Issues
Batch files involve more moving parts than realtime messages do. As a result sometimes those processes can encounter complications.
Assessment
In order to locate where the breakdown occurred, it may be necessary to check a variety of locations. The following steps are a guide, and can be taken in any order.
The expected path reference used below refers to the Proxy Inbox (for Inbound files) or the Inbox (for outbound files)
- Check the Application Error Log in the WEM database. It may provide explicit detail about where the problem took place.
- Check the expected path, if the file is still sitting there and it has been there for more than 10 minutes, it likely means the file processor service is not running or is in a faulted state.
- Check the archive folder for the expected path. If the file is there, it means the file processor picked it up, but it may have not been delivered.
- Check the Outbox folder. if the file is there it indicates that the process that should have removed it failed. For outbound files this is the internal FTP process.
- Check the Outbox archive folder if the file is here the system thinks it delivered it correctly, which indicates a misconfiguration of the FTP site.
Recovery
IF the batch file processing window has closed or manual intervention is needed to provide the files on time, this can be accomplished in a couple of ways. WEM has some issues currently with File Processing Performance, so this should not be done during normal clinic operating hours
- Make sure no files exist in the configured Proxy Inbox for the agency (or agencies if multiples are configured). This path can be found in the configuration file under the appropriate EBT host for the agency.
- Make sure no files exist in the configured Inbox for the agency (or agencies if multiples are configured). This path can be found in the configuration file
- Restart the WEM Services.
- Copy the EBT file from the FTP Server into the proxy Inbox. Due to the performance issue mentioned above, it is ideal to do this one file at a time.
- Watch the Outbox path or the FTP Outbox path as specified in the configuration file for the converted file to appear. Depending on the size of the file this can take several minutes, typically it should be around 3-5 but can take up to 10.
The files can be processed in a non-production environment and delivered manually to the production environment if needed, but this requires the configuration to support the files in the targeted environment.