contact | login | register | home
news tools training documents Call us today at: 919-434-5399
	Two approaches to a 5010 solution using WTX Step Up/Step Down vs. Parallel Processing The two approaches to a 5010 solution using WTX are Step Up/Step Down and Parallel Processing. The Step Up/Step Down approach involves Stepping Up from 4010 to 5010 & Step Down from 5010 to 4010. The advantage of this is that your backend systems should remain largely unchanged, however, 5010 differences wouldn't be seen in the backend. The second approach is to create a new parallel process that handles 5010 by, for example, using new copybooks, WTX maps, and WMB flows to send 5010 transactions down another path and process. This does involve backend changes to your adjudication system which may take more time to implement. We can provide consulting services for either approach. More Information Click here for more information about our 5010 Step Up, Step Down approach using WTX. Click here to send us an email or call us at 919-434-5399 Three reasons for WTX 5010 Step Up & Step Down Maps Three reasons for WTX 5010 Step Up & Step Down Maps: Production runtime solution where inbound 5010 data is stepped down to 4010 before sending to your adjudication system (aka mainframe, claims team) and 4010 data from your adjudication system is stepped up to 5010 before being sent out the door ensuring HIPAA compliancy. Creating test data to test either approach. Some internal, third party tools such as practice management may not be ready for 5010 so the only solution is to Step Down the 5010 to 4010 until they are ready. More Information Click here for more information about our 5010 Step Up, Step Down approach using WTX. Click here to send us an email or call us at 919-434-5399 WebSphere TX 8.2 map to 8.1 map backwards convertion tool Finally a simple tool to convert WTX 8.2 map to WTX 8.1 maps. Export you map to an XML file, upload here, and import into WTX 8.1. Convert WTX 8.2 maps to WTX 8.1 maps Can a 1+ gig file be processed on the broker? The answer is yes and, in fact, over 2 gigs is possible. Have you hit the 100 meg limitation on the FileInput Node within WebSphere Message Broker and then been told by IBM that 80+ meg files are not recommended? We were told that anything over 80 megs could start causing issues. After a couple days of trying different ideas we went with the approach of gzipping the file using a shell script to let it pass through the FileInput node and then using the GZIP adapter on a card within a WTX map. How to process large files on WebSphere Message Broker   No Drag & Drop's for your WTX Map & Wrap maps To develop a HIPAA map & wrap solution using WTX was going to take several days of dragging and dropping until this tool was developed. In the case of the 837's, thousands of mappings and days of development will be avoided using this tool. Use this tools after a free registration. 4010 vs 5010? Having trouble figuring out what the differences between 4010A1 and 5010 HIPAA transactions will be? Download the FREE Edifecs5010™ Comparison Manuals. Click here to register and download the FREE comparison PDF's. Another excellent resource is the CMS side-by-side comparison of the 4010 vs 5010 transactions on their website. Click here to read more about the comparisons and download the comparison PDF's.   TOOLS UPDATE Our NPI calculator and our File Unwrapping tools have been updated and are available for use. MIGRATION TOOLS We can help your migration from WTX to BizTalk go a lot smoother. Sign up today to take a look at our WTX Tree to BTS schema migration tool. WMB 6.1 VISIO STENCIL Click here to download our WebSphere Message Broker version 6.1 Visio Stencil. (NOTE: Save as a .VSS file not .DOC) For Visio 2002 users download a 2002 version here. DOCUMENTATION TOOLS We now have 14 documentation tools to help you document WTX and BizTalk. Sign up today to take a look at our documentation tools. Finally... an easier way to read WTX Trace Files The number one complaint about WTX is reading the trace (MTR) files. The trace files have always been hard to read and have changed very little in the 15 years of Mercator's existence. Download the WTX map that writes reports from MTR files. WebSphere Message Broker to Visio Under development now is a new tool that takes WMB message flows and converts them into Visio diagrams. The Visio diagrams will use the WMB stencil (available for download here) and will allow users the ability to provide a "birds eye view" of all their flows by creating and combining multiple Visio diagrams from all flows. It will give architects and developers more flexibility than using the jpg's or bmp's created by taking screen shots or using IBM's WMB documentation tool. WMB Message Flow backward convertion tool (WTX 8.2 to 8.1 node) The WTX 8.1 and WTX 8.2 nodes can not live together in harmony in the WebSphere Message Broker toolkit. IBM has a conversion tool to migrate from your flows that contain an WTX 8.1 node to the new WTX 8.2 node format. However, if you've opened a flow that uses a WTX 8.1 node in the WMB toolkit that has WTX 8.2 for integration servers installed it will automatically convert it to an WTX 8.2 node flow. Click here to try the tool. Registration is free. This tool removes all the WTX node flow's 8.2 xml elements and attributes from a message flow solving the issue of accidently opening a flow containing the WTX 8.1 node after you've installed WTX 8.2 for integration servers into the WMB toolkit.
DeBruin Consulting,    All rights reserved © resume