A high-speed connection with Window's Internet Explorer is recommended for use on the i-Plexus Website for file submissions, report retrievals, web reporting and claim editing.

FTP with PGP encryption or FTPs is recommended for submitting files and retrieving reports through File Transfer Protocols.

Billing managers should have working knowledge of the Windows environment including use of Explorer, copy/paste and renaming functions.

Billing managers should have working knowledge of their billing system and a working relationship with their billing system vendor.

Billing managers should have working knowledge of their file format. i-Plexus accepts print image (Click here to view sample), NSF (Click here to view sample) and 837 (Click here to view sample) formats as well as proprietary formats from billing system vendor partners. Other proprietary formats may require a custom parsing fee.

To obtain the 837 Implementation Guide, go to www.wpc-edi.com and click on HIPAA on the left toolbar. It it will take you to a list of available HIPAA EDI implementation guides.

Billing managers should have general working knowledge of EDI and payer responses including ERA.

Practices must have unique tax IDs or must be able to use tax ID extensions in order to make them unique. NPI may be used to identify sites that share a single tax ID; however, some limitations apply.

File naming conventions only apply to the extension at the end of the file name. The name before the period ("dot") is up to user discretion; however, the extension of the file (e.g. .txt, .clm, .837, etc) must remain consistent for each type of file submitted. If claims and patient statements are submitted to i-Plexus for processing, each uses its own inbound process which is called up by the file extension.

Claims are expected to be batched in files as opposed to single submissions; file formats are expected to remain consistent. Map changes and multiple maps are subject to additional fees.