Scenarios

Real World Scenarios

When would I need the FSPM

Consider some of the following scenarios as to when you might need the Filesystem Postmaster. We've broken it into two parts, Inbound Scenarios (covering receiving HL7 messages) and Outbound Scenarios (related to sending HL7 messages).

INBOUND SCENARIOS

Scenario 1 - (1 HL7 message to multiple recipients) : The client receives HL7 messages over 1 TCP/IP connection and needs to deliver instances of the same message to multiple destinations (see the reverse in OUTBOUND SCENARIOS). Examples could be:

•	Every message needs to go to the EMR (Electronic Medical Record software)

•	1 Copy of each ADT (Patient Demographics) message needs to go to 1 or more HL7-capable medical devices

Scenario 2 - (The Sender sends too much): This happens much more often than you might think. The trading partner sending HL7 messages sends you far more messages than you need or want. Examples could be:

•

Your application(s) are receiving Patient Demographic (ADT), Schedule (SIU), and Results (ORU) HL7 messages and all that you need are patient demographic add or update messages (Type=ADT; Event=A04,A08). Use the FSPM to filter the messages for you by creating a Rubbish Bin to eat all of the messages you don't need.

•	OR your application receives Lab or Radiology results (ORU) messages BUT you only want to import FINAL results.

•	OR you're receiving a major feed from a large trading partner (a Hospital) and need to filter out messages for specific physicians.

OUTBOUND SCENARIOS

Scenario 1 - (Use 1 Interface to send to multiple recipients): Your application is producing HL7 messages and you need to send them to your client. Your client is the same client described in INBOUND SCENARIOS #1. They would like for your application to send copies of each message to a different TCP/IP connection based on some rules. You need a solution that's fast, clean, affordable and won't require any modifications to your existing product. You could do the following:

1.	Configure your HL7 interface to place write all HL7 messages into the FSPM Central Distribution Folder.

2.	Create 2 destinations. 1 for ALL messages and 1 for ADT messages only (see Creating Destinations).

3.	The FSPM will handle dispatching the messages appropriately to each destination folder.

4.	If you now need to send the HL7 messages placed into each destination folder via TCP/IP you will need an HL7 sending application. An excellent choice is the EasyHL7 Mailbox Router which allows you to create an unlimited number of outbound TCP/IP connections!

Scenario 2 - (Creating Test Messages): If your application produces HL7 messages, you will invariably be asked to produce example or test messages. Sometimes you might even need to create large volumes of test messages for stress testing scenarios. This is usually a difficult and tedious process where you must always be cautious not to violate any patient privacy guidelines by inadvertently using live patient data. With the FSPM you can easily create a destination which uses transformation instructions to make messages completely anonymous! Complete with Random names, message control IDs the works.