Difference between revisions of "Outbound Interface Filtering"
Jump to navigation
Jump to search
(Created page with '=Overview= *It is desirable to prevent some transactions from being sent to a particular target system (and consequently vendor systems). **For instance, one certainly would not…') |
John.Buckley (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | =Overview= | + | [[Category:ConnectR]] |
| + | ==Overview== | ||
*It is desirable to prevent some transactions from being sent to a particular target system (and consequently vendor systems). | *It is desirable to prevent some transactions from being sent to a particular target system (and consequently vendor systems). | ||
**For instance, one certainly would not desire a charge message to be sent to the lab. | **For instance, one certainly would not desire a charge message to be sent to the lab. | ||
| Line 10: | Line 11: | ||
**Message type | **Message type | ||
**Document type | **Document type | ||
| − | =Example= | + | ==Example== |
[[Image:ConnectR Filtering.jpg]] | [[Image:ConnectR Filtering.jpg]] | ||
Revision as of 14:29, 16 November 2012
Overview
- It is desirable to prevent some transactions from being sent to a particular target system (and consequently vendor systems).
- For instance, one certainly would not desire a charge message to be sent to the lab.
- Also, it may be that there are two lab vendors and as such, messages should be routed properly based upon requested performing location.
- In this regard, blocking logic in ConnectR can be deployed in order to achieve the aforementioned objectives.
- Typically charges and prevented from going to lab systems and orders are prevented from going to practice management systems by inspecting the message type sent from the superset source and blocking based upon that value.
- There are limitless flavors of filtering that take place
- Provider
- Requested performing location
- Message type
- Document type
Example
