Complete the setup required to enable DrCloudEHR to provide billing and claims management functionality. The application's Billing Rules engine, Claim Rules engine, and Contract Manager work together with the Billing Manager and Claims Manager to provide efficient claims processing.
You can use DrCloudEHR to generate and submit claims in HCFA or UB-04 format. You can also generate and submit Detailed Financial Transactions (DFT) in HL7 format.
This topic contains the following sections:
Add details for each insurance payer you submit claims to. To submit claims electronically, you must create connections to the medical claims clearinghouses used by the insurance payers to both submit claims and receive payment notifications.
Add details for each insurance company to which you submit claims, including information required to process claims electronically.
You can configure the application track actual charges and adjustments based on your contract with the insurance company. The application uses the amount specified in the Contract Manager to calculate payments and adjustments. For example, assume you submit a claim for $475 for a service, based on the amount specified for the service code. However, per your contract, the company only pays $425, leaving you with a $50 adjustment.
You can configure the application to post the amount the insurance company agrees to pay in the claim details in the customer report. You can also specify that the application posts the adjustment in the system.
The default settings used to process ERA files are set at the practice level. If necessary, you can modify a default setting. Note that the default settings are applied to ERA files received from all insurers, unless you configure custom settings for specific insurance companies as outlined in the Configure Payer-specific Electronic Remittance Advice Processing Settings topic.
Select each setting you want to modify.
Setting | Description |
---|---|
Claim Matching Options | Select criteria to use to match claim identifiers with identifiers in DrCloudEHR. The system matches the original claim identifier by default. |
Service Line Matching Options | You cannot modify the current default settings. |
Denial Adjustment Reason Codes | Specify the status codes that indicate a claim was denied. An ERA file containing the specified codes will be marked as denied. Note that you must also select the Denied Adjustment Reason option from the Denied Service Options menu to enable the denial process. |
Denied Service Options | Specify under what conditions a claim should be considered as denied. Denied claims appear in the Denials Manager. |
Move To Next Responsibility Options | Specify when to move claims to the next level of responsibility, such as to the patient's secondary insurance provider. |
Reversal Claim Options | Specify the status that indicates a reversed claim. |
Denied Claim Options | Specify the status that indicates a denied claim. |
ERA Handling Options | Specify how to process incoming ERA files. |
If the default ERA processing settings do not apply to a specific insurance company, you can configure custom settings that determine how ERA files received from the insurer are processed by DrCloudEHR.
Select each setting you want to apply.
Setting | Description |
---|---|
Setting Name | A unique name for the custom settings. |
Processing From and To dates | Optional date range during which to apply the settings. |
Claim Matching Options | Select criteria to use to match claim identifiers with identifiers in DrCloudEHR. The system matches the original claim identifier by default. |
Service Line Matching Options | You cannot modify the current default settings. |
Denial Adjustment Reason Codes | Specify the status codes that indicate a claim was denied. An ERA file containing the specified codes will be marked as denied. Note that you must also select the Denied Adjustment Reason option from the Denied Service Options menu to enable the denial process. |
Denied Service Options | Specify under what conditions a claim should be considered as denied. Denied claims appear in the Denials Manager. |
Move To Next Responsibility Options | Specify when to move claims to the next level of responsibility, such as to the patient's secondary insurance provider. |
Reversal Claim Options | Specify the status that indicates a reversed claim. |
Denied Claim Options | Specify the status that indicates a denied claim. |
Use the Contract Manager to define details on your contract with each insurance company. Creating a contract defines a fee schedule that shows the actual amounts the insurance company pays you for services based on service code and modifier combinations.
When you post insurance payments manually or electronically, you have the ability to see and flag items that were not paid according to your contract. This allows for more immediate claims follow up, knowledge of potential payer fee changes, and overall better accounts receivable management. DrCloudEHR also provides reports that allow you to analyze claims payments that may be incorrect, based on the actual amounts the insurance company pays as defined in the contract.
To add a contract definition for an insurance company, you add each service code and any applicable modifiers, along with the allowable amount that can be billed for the code/modifier combination.
You must configure connections with each insurance provider you want to interact with electronically.
To submit HCFA or UB-04 claims electronically to an insurance payer, you must configure an EDI connection to the medical claims clearinghouse the payer uses to process claims.
When you configure the connection, you can enter a link to a form describing the services offered by the payers that clearinghouse supports in the Payer Lookup Website field. DrCloudEHR adds a Lookup CMS Payer ID link to the page containing the details for each insurance company.
To submit DFT claims electronically to a processor, you must configure a connection to the processor the payer uses to process claims. When you configure the connection, you specify an upload folder on the processor's server. When you submit a claim, DrCloudEHR uploads the DFT message in HL7 format to the folder.
|
To receive electronic payments from insurance payers, you must configure a connection to the clearinghouse to download the electronic remittance advice (ERA) file containing details on payments and adjustments. As part of the connection configuration you specify a download folder on the clearinghouse server from which DrCloudEHR downloads ERA files on a scheduled basis. The application scans each file for payment and adjustment details, and automatically writes the data to the DrCloudEHR payment system.
Billing rules define how claims are created for closed encounters. Billing rules enable you to use a single service code category to include multiple code, modifier, and billing unit type combinations in a claim. When you close an encounter and generate a claim, the application applies the values set in the billing rule to the claim.
You can set any of the following parameters in a rule to specify claims the rule applies to:
In addition to the service code the rule applies to, you can specify additional service code/modifier/billing unit combinations that are added to claims.
You can add multiple service code/modifier/billing unit combinations to the rule. The combinations are included in claims the rule is applied to.
You can use an existing billing rule as a templates for a new rule. Search for the existing rule at the bottom of the Billing Rules page, make any modifications, and then add the new rule.
Use Claim Rules to automatically populate fields on UB-04 and HCFA claim forms with required values based on insurance payer requirements. The assigned value for a field is taken from existing data within your DrCloudEHR system. You can optionally specify a value for a particular field on a claim form.
The application applies a claim rule when you submit a claim for payment. Until a claim rule is applied, the claim forms created when you generate a claim using Billing Manager are not final, as values set in the form change according to the claim rule.
For each field in a form, you can specify the action to take if the value is missing. You can also specify an error message to send to selected staff members.
Create the claim rule definition, and then configure each claim form field to apply the rule to.