Skip to content

Set Up a Connection

A connection is where files come from - a folder, an SFTP drop, or an S3 bucket - or where paper goes: a printer. One connection serves every run from that source.

  1. In the sidebar, select Connections.
  2. Select Create.
  3. Choose the transport and enter its details. For SFTP, paste the server’s Host Key, which the clearinghouse can give you; ClaimPod will not save an SFTP connection without it. Files are picked up from the input/ subfolder of the folder you name.
  4. Select Test Connection. A working connection reports how many files it can see, such as Connected · 4 files visible. An address on a network ClaimPod is not allowed to reach is refused; ask your administrator to allow it.
  5. Select Create. The connection appears in the list and is available to schedules.

Result: the connection is available to schedules and to manual browsing.

The connection takes whatever is in its input/ folder. To limit a run to certain files, set the Files parameter on the Import Data schedule that reads it: pick files, or type a wildcard such as *.edi, which is matched at run time so it keeps working as new files land with new names. See Schedule a Recurring Task.

  1. Select Create and choose the Printer transport.
  2. Enter the Printer Address (optional) if ClaimPod should send jobs to it, or leave it blank for a printer billers print to from their browser. The address starts with ipp:// or ipps://. If the printer needs a login, enter it in Username (optional) and Password (optional), never in the address.
  3. With an address, name the Form Tray (optional) that holds the red forms and select Test Connection.
  4. Select Print Test Page, hold the page over a red CMS-1500 form against a light, and nudge the Alignment until the text sits inside the boxes. Repeat as needed; nothing has to be saved between tries.
  5. Select Create.

Result: billers can pick the printer when they print claims. Alignment lives on the printer, so fixing it here fixes every batch that prints there.

Connection credentials are stored encrypted. Editing a connection does not display them back to you, and leaving a password or secret blank keeps the saved one. If you change where the connection points, such as the host, username, host key, bucket or printer address, enter the password or secret again.

Related: Connections · Build a Mapping Template · Import Batches