What's New
Documentation
FAQ
Getting Started
QuickStart Guide Daily Workflow Guide

SFTP

16 Aug 2024
4 Minutes to read

Print
Dark

Light
PDF

SFTP

Updated on 16 Aug 2024
4 Minutes to read

Print
Dark

Light
PDF

Article summary

Did you find this summary helpful?

Thank you for your feedback

Important

SFTP/API setup can only be performed by an Administrative user.

Navigate to Settings on left-hand navigation bar > Account Settings and scroll down to the SFTP section.

Click the SFTP Active dropdown and select YES
Click a pop-up box will display on the screen with the following credentials:
SFTP Password, Username, Password, Hostname, Port, Upload Claim Folder, and Download Responses/ERA folder.
The credentials in this pop-up will have to be applied to the Practice Management System's SFTP settings.

More Information

Some PMS and billing systems may ask for an MD5 Fingerprint to validate that their system is in fact connecting with the Claim.MD server. This fingerprint is located at the bottom of the SFTP credential pop-up (see image below).

Contact the PMS support for assistance in configuring these credentials.

Copy and Paste

We recommend copying and pasting the information and entering into the Practice Management software (or securely sharing information to the PMS support contact person).

	SFTP Settings
SFTP Active	Select YES in dropdown.
SFTP Username	This is used in the SFTP configuration in your SFTP client. This will display when clicking Save
SFTP Password	This is used in the SFTP configuration in your SFTP configuration page. This is hidden until you click Save.
SFTP Host	This is the hostname to configure in your SFTP client.
SFTP Port	This is the SSH/SFTP port to configure in your SFTP client.
Send Files Folder	/SendFiles This is the folder your SFTP client should use to upload claim and eligibility files into CLAIM.MD.
Receive Files Folder	This is the folder your SFTP client should use to download claim status, ERA and other files from CLAIM.MD.
File Acknowledgment	Available file level acknowledgement formats to download via the SFTP server.
Claim Status Format	Available claim status formats to download via the SFTP server.
Receive ERA/835	Generally, this will be 835 which is the standard format, but other options are available depending on how systems are setup.
TaxID Subfolders	Separate claim status and ERA files into sub folders by Tax ID. i.e. /ReceiveFiles/741111111/60054_1234567893_11741672.835. *Your software must be properly configured if you activate this setting.

File Acknowledgements

When you upload a batch file via SFTP and select "File Acknowledgement" or "Claim Status Format" options in the SFTP Settings under Settings > Account Settings, the system returns files in specific formats. Below are the details of the possible file formats you may receive.

.result Format:

The '.result' format provides a file-level acknowledgment in plain text, confirming whether a file was received and successfully loaded by Claim.MD.

Valid Processed File Example:

Received 220 claims in file: file123.txt

Any acknowledgment starting with "Received n claims" indicates successful processing of the specified number of claims.

Error Example:

ERROR File:

'file123.txt' is a duplicate of 'file122.txt'. Processing Aborted!

If the response does not begin with "Received n claims," it signifies an error. The complete text of the response should be reviewed to identify the issue.

No Claims Loaded Example:

Received 0 claims in file:

file123.txt

If the acknowledgment indicates that no claims were loaded, it is essential to review the situation, as this may also represent an issue requiring attention.

Important Considerations

Always review the full content of the '.result' file to ensure that the batch file was processed as expected.
In case of errors or unexpected results, further investigation is recommended to identify and resolve any underlying issues.

Claim Status Format

The available claim status formats for download via the SFTP server are XML, 277, CSV, and EPIC.

XML

Response Sample

</claim>

</claim>

</claim>

</claim>

</result>

RESPONSE SCHEMA: application/xml

Result: object (response)

last_responseid: string

claim: array of objects

batchid	string Value sent as "remote_batchid" or the X12 Loop BHT03
bill_npi	string Billing provider NPI
bill_taxid	string Billing provider Tax ID
claimid	string Users claim identifier. (Value sent in remote_claimid field or REF*D9)
remote_claimid	string Users claim identifier. (Value sent in remote_claimid field or REF*D9)
claimmd_id	string Claim.MD unique claim identifier. This will equal a previous returned value if Claim.MD updated a previous claim.
fdos	string Earliest date of service on a 1500 claim. Statement from date on a UB claim.
fileid	string Users unique file ID from ISA13 or 'fileid'.
filename	string Users file name.
ins_number	string Insured policy number.
payerid	string Payer ID
pcn	string Users unique patient control number.
sender_icn	string Sender of this status message, claim identifier.
sender_name	string Sender of this status message.
senderid	string ID Code of this sender.
status	any A = Claim Acknowledgment R = Claim Rejection Enum: "A" "R"
total_charge	string Total billed amount on the claim.
response_time	string Response status timestamp YYYY-MM-DD HH:MM:SSaa (MST/MDT)
messages	Array of objects

error: Array of objects (error)
error_code
string

error_message
string

What's Next

Table of contents

File Acknowledgements
Claim Status Format

error_code	string
error_message	string