In this section: How to: |
The inbound channel configuration that is described in this section transforms 4010 and 5010 versions of HIPAA inbound messages. The channel produces an XML output representation of the HIPAA inbound messages. It generates a functional acknowledgement (997) document, an XML validation report, and routes transformed XML to a designated folder based on the success or failure of the HIPAA validation. The output files are routed to the following defined directories:
The transformed XML document will reside in the good or bad directory, depending on the validation rules that are specified.
The following are required in order to create the HIPAA inbound processing channel:
A working knowledge of iWay Service Manager.
The archived channel .zip file (HIPAAToXML_IB_QS_AckRpt_Pflow_Channel.zip)
Note: For your convenience, the HIPAAToXML_IB_QS_AckRpt_Pflow_Channel.zip file is attached to this PDF.
For PDF-compatibility purposes, the file extension of the HIPAAToXML_IB_QS_AckRpt_Pflow_Channel.zip file is temporarily renamed to .zap. After saving this file to your file system, you must rename this extension back to .zip before it can be imported to iWay Service Manager.
The input data files representing valid and invalid data (HIPAA_276_5010x212_good_sample.data and HIPAA_276_5010x212_bad_sample.data).
The following archived channel (Hipaa_IB_Split_Version_Channel.zip) can be used to split inbound 4010 and 5010 HIPAA. This channel will read the inbound HIPAA data and determine its version. The EDI will be written to either a 4010 or 5010 folder.
Note: For your convenience, the Hipaa_IB_Split_Version_Channel.zip file is attached to thisPDF. For PDF-compatibility purposes, the file extension of theHipaa_IB_Split_Version_Channel.zip file is temporarily renamed to .zap. After saving thisfile to your file system, you must rename this extension back to .zip before it can be importedto iWay Service Manager.
Another channel can be started to listen on a specific version folder and process the information accordingly. For example, if the attached HipaatoXML_IB_QS_AckRpt_pflow_Channel listens on the 5010 version folder, then another channel containing 4010 ebixes can listen on the 4010 version folder to process HIPAA 4010 data.
In order to download and save the HIPAA Ebix:
http://techsupport.informationbuilders.com
A logon window is displayed.
Note: If you do not have a Global ID and password, you must contact iWay Technical support.
<iWaySMHOME>\etc\manager\packages
where:
Is the directory where iWay Service Manager is installed (for example, C:\Program Files\iWay61).
<iWAYSMHOME>\etc\repository\manager\archives
where:
Is the directory where iWay Service Manager is installed (for example, C:\Program Files\iWay61).
For example:
In this example, the HIPAA output directory structure was created on the local C drive.
To import components from a repository archive:
A pane telling you whether the import was a success or not appears.
If your HIPAA output directory structure was created on a local drive other than C, then you must update the inbound registers. To update the inbound registers:
To upload the Ebix to iWay Service Manager:
The New Ebix pane is displayed, as shown in the following image.
The New Ebix pane is displayed, as shown in the following image.
Note: HIPAA Version 5010 may require multiple Ebix attachements to channels that are dependent on the transactions that are being processed. If this is the case, then you must repeat steps 2 through 6.
To add the Ebix components to a channel:
To build, deploy, and test your channel:
The following pane appears.
A green check mark appears under the Status column as shown in the following image.
The channel is ready to accept inbound data.
C:\Hipaa\inputdir\hipaa_xml
The HIPAA XML output files are copied to the corresponding subdirectories in the HIPAA output directory structure, as shown in the following image.
iWay Software |