Features

When it runs the FSPM will begin a process cycle every 5 seconds. During each process cycle it will do the following in the order stated.

If you have added any Message Collection Folders, it will look in each one for HL7 data files (files that have the file extension entered in the main window) which are at least 3 seconds old and contain data (ie zero byte files are ignored). It will then MOVE (using a safe copy and delete method) each of those files into the Central Distribution Folder.

It will then poll the Central Distribution Folder looking for HL7 data files (files that have the file extension entered in the main window). If found it will process them IN ORDER BY THE FILE DATE/TIME so that files (and thus messages) are processed in a 'first-in-first-out' manner. As with item 1, files less than 3 seconds old and files with no data are ignored.

3.	For each HL7 data file encountered, it will first analyze the file for HL7 messages. If a file contains NO HL7 messages, it will be moved to the PM-ErrorFiles sub-folder underneath the Central Distribution Folder. If the file is determined to contain HL7 messages, then it will proceed to step 4.

For each HL7 message within a data file, the FSPM will evaluate the contents against the matching instructions of Rubbish Bins. If you haven't configured any rubbish bin destinations then it will proceed to step 5. Rubbish Bins will always be evaluated FIRST, if there is more than one rubbish bin, they will be evaluated in alphabetical order. If the message is found to match the matching instructions in a rubbish bin then the message will NOT proceed any further. If the rubbish bin has a destination folder configured the message will be saved into that folder (after any Transformation Instructions have been applied). If there is no destination folder, the message is simply internally purged.

HL7 messages which DID NOT match any rubbish bins will then be evaluated against the matching instructions for every Message Destination you have created. If the message is found to match the instructions of a destination, then the message is modified with any Transformation Instructions (if applicable) and will then be saved into the message destination folder with a filename convention of <datetimestamp><4digitsequentialnumber>.<FileExtension defined in destination instructions>.

ANY HL7 message which matches NONE of your destination matching instructions (regular destinations and rubbish bins) will be saved into the PM-Undeliverable sub-folder of the Central Distribution Folder with the same filename convention described in step 5 (but using the File Extension you entered in the main window).