Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 HIPAA Transaction Configuration : Transaction Configuration Files

Transaction Configuration Files
When you configure a HIPAA transaction in the Operations Editor, the following files are needed for each transaction:
The HIPAA transaction guidelines contain rules which are used to validate HIPAA X12 transactions according to the HIPAA Implementation Guides (IGs) or Type 3 Technical Reports (TR3s). The HIPAA transaction guidelines are shipped with TIBCO BusinessConnect EDI Protocol HIPAA Edition powered by Instream in the directory BC_HOME/protocols/tibedi/samples/sampleDocs/guidelines.
The HIPAA transaction schemas contain the definition of the XML that can be used by your backend process for handling HIPAA transaction data. The schemas associated with the HIPAA transaction guidelines shipped by TIBCO BusinessConnect EDI Protocol HIPAA Edition powered by Instream can be found in the following directory: BC_HOME/protocols/tibedi/samples/sampleDocs/schemas
The HIPAA transaction map files are used by the EDI conversion engine to convert HIPAA transaction EDI data into XML and the reverse. The HIPAA transaction map files can also be used to convert HIPAA transaction EDI data into textual data.
The map files associated with the HIPAA transaction schemas shipped by TIBCO BusinessConnect EDI Protocol HIPAA Edition powered by Instream are located in the directory BC_HOME/protocols/tibedi/samples/sampleDocs/maps.
The map files which contain the mapping for converting from XML to EDI data have file names of the form schema_name_XE.map. The map files used for converting inbound EDI data into XML data have file names of the form schema_name_EX.map.
You will notice that the names of the HIPAA transaction schemas and maps files are similar to each other but they are not similar to the names of the HIPAA transaction guidelines. This is because the HIPAA transaction schemas and maps files are created using TIBCO EDISIM Standards Editor which cannot read the HIPAA transaction guidelines because the rules in the guidelines are encrypted. So to create the HIPAA transaction schemas and maps files, you must use the unencrypted guideline from TIBCO EDISIM which only contains level 1 and 2 syntax checks but not the level 3 and above HIPAA validation rules.
The following table contains information on the name of the TIBCO EDISIM guideline used to generate the schemas and map files for each HIPAA transaction.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved