The Integrated Rules Professional API requires the use of the Professional Claims API for submission of claims to the payer. If you have another workflow for claims submissions, you may use that instead.
See the API Examples section on the left panel in the developer portal.
The input is a complete professional claim that you submit as the request body, as you would with a standard professional claim submission. Please see example in Integrated Rules Professional Request & Response.
After the Integrated Rules Professional
/professionalclaims/advanced/v1/validation endpoint successfully evaluates a professional claim, you will get a summary message stating so, with core claim reference and a Metadata for troubleshooting information. Please see example in Integrated Rules Professional Request & Response.
When the validation API encounters issues in the claim evaluation, it will list each in the reply. Please see example in Validation Endpoint Issue.
Please see example in Submit Edited Claims.
Please see example in X12 EDI 270 Request & 271 Response.
For all Integrated Rules Institutional API applications, be familiar with the term Edits, which has a specific meaning in this context.
Payers control their own claims edit specifications. Edit specifications govern how medical practices must submit correct claims information for payer processing and claim adjudication. Claims Edits can change at any time, and these changes may or may not reach you before you submit an institutional claim, much less be integrated into your claims submission software.
Because of this likelihood, you may encounter unexpected errors and incur delays when filing claims, even when you think your software and processes are up to date.
These issues can occur at any time. Some medical practices may subscribe to continuous payer updates and submission edits. They receive their Claim edits notifications from the payer. Others may not do so, finding the costs prohibitive. The Integrated Rules Services team monitors regulatory requirements from Medicare and from industry organizations of many different types, and develops the Integrated Rules Knowledge Packs based upon the Packs' medical disciplines and the Rules/Edits that apply to them.
We continuously track and follow the Rules/Edits changes so you do not have to. Using the Knowledge Packs that you order as a match for your business, we tailor your Institutional Claims Integrated Rules API to your specific needs.
Currently available Knowledge Packs for Institutional Claims include the following:
- General Billing
- Dialysis/End Stage Renal Disease (ESRD) (Institutional claims only)
- Post Acute Care
- Prior Authorization
- Institutional claims from Rural Health Clinics and Federally Qualified Health Centers (Rural FQHC)
- Medical Necessity
- National Correct Coding Initiative (NCCI)
- Therapy (Institutional claims with Therapy Revenue Code, HCPCS/CPT-4 codes)
- Validation Codes
Providers of each of the various Edit/Rule types select the Knowledge Packs that fits their needs. Rules within each category also may apply to specific Payers. For example, rules within the Durable Medical Equipment pack may be applicable for Aetna or for Medicare.
Another benefit: not all fields in an Institutional Claim request will be applicable for every service. A single claim may be a very substantial request body. Our Rules and Knowledge Packs enable you to narrow your claims down to the bodies of information that are only necessary for your claim type.
Edits are directly comparable to individual validation rules in our API, hence we use the term Integrated Rules for our API.
The majority of Integrated Rules Claims Edit categories support both Professional and Institutional claims. Some Edit/Rule categories are supported only through Institutional claims; others are supported only by Professional claims and hence are not listed here.
Our Institutional Claims Integrated Rules EDI supports the following Edit Types and compliance checking for HIPAA Types 1 through 7:
|Type 1 EDI Standard Integrity Testing
|Validate basic syntactical integrity of the EDI submission.
|Type 2 HIPAA Implementation Guide Requirement Testing
|Validate HIPAA requirement-guide-specific syntax requirement by checking limits on repeat counts, used or not used qualifiers, code, elements, and segments.
|Type 3 HIPAA Balance Testing
|Validate that claim line items amounts are equal to total claim amount.
|Type 4 HIPAA Inter-Segment Situation Testing
|Validate inter-segment relationship. For example, if element A exists, element B must be populated.
|Type 5 HIPAA External Code Set Testing
|Validate specific code set values for HIPAA standards.
|Type 6 Product Type/Type of Service Testing
|Validate that segments that differ based on certain Healthcare services are properly created and processed.
|Type 7 Trading Partner-Specific Testing
|Compliance with payer specific requirement.
Updated about 20 hours ago