View raw Markdown
type: resourceresource: ClaimResponse

ClaimResponse

Introduction

Scope and Usage

The ClaimResponse resource provides application level adjudication results, or an application level error, which are the result of processing a submitted Claim resource where that Claim may be the functional corollary of a Claim, Predetermination or a Preauthorization.This resource is the only appropriate response to a Claim which a processing system recognizes as a Claim resource.

This is the adjudicated response to a Claim, Predetermination or Preauthorization. The strength of the payment aspect of the response is matching to the strength of the original request. For a Claim the adjudication indicates payment which is intended to be made. For Preauthorization no payment will actually be made however funds may be reserved to settle a claim submitted later. For Predetermination no payment will actually be made and no assurance is given that the adjudication of a claim submitted later will match the adjudication provided, for example funds may have been exhausted in the interim. Only an actual claim may be expected to result in actual payment.

The ClaimResponse resource may also be returned with the response for the submission of: Re-adjudication and Reversals.

The ClaimResponse resource is an "event" resource from a FHIR workflow perspective - see Workflow Event.

Additional Information

Additional information regarding electronic claims content and usage may be found at:

Boundaries and Relationships

The ClaimResponse resource is used to provide the results of the adjudication and/or authorization of a set of healthcare-related products and services for a patient against the patient's insurance coverages, or to respond with what the adjudication would be for a supplied set of products or services should they be actually supplied to the patient.

The ExplanationOfBenefit resource is for reporting out to patients or transferring data to patient centered applications, such as patient health Record (PHR) application, the ExplanationOfBenefit should be used instead of the Claim and ClaimResponse resources as those resources may contain provider and payer specific information which is not appropriate for sharing with the patient.

When using the resources for reporting and transferring claims data, which may have originated in some standard other than FHIR, the Claim resource is useful if only the request side of the information exchange is of interest. If, however, both the request and the adjudication information is to be reported then the ExplanationOfBenefit should be used instead.

When responding whether the patient's coverage is inforce, whether it is valid at this or a specified date, or returning the benefit details or preauthorization requirements associated with a coverage CoverageEligibilityResponse should be used instead and be the response to a CoverageEligibilityRequest.

The eClaim domain includes a number of related resources

ClaimResponseA payer's adjudication and/or authorization response to the suite of services provided in a Claim. Typically the ClaimResponse references the Claim but does not duplicate the clinical or financial information provided in the claim.
ExplanationOfBenefitThis resource combines the information from the Claim and the ClaimResponse, stripping out any provider or payer proprietary information, into a unified information model suitable for use for: patient reporting; transferring information to a Patient Health Record system; and, supporting complete claim and adjudication information exchange with regulatory and analytics organizations and other parts of the provider's organization.
ClaimA suite of goods and services and insurances coverages under which adjudication or authorization is requested.
CoverageEligibilityResponseThe response to a request to a payer, a CoverageEligibilityRequest, to: ascertain whether a coverage is in-force at the current or at a specified time; list the table of benefits; determine whether coverage is provided for specified categories or specific services; and whether preauthorization is required, and if so what supporting information would be required.

Background and Context

Provides additional detail on exactly how the resource is to be used

Notes

Additional Information

The information presented in different backbone elements, such as .supportingInfo or .adjudication, has a different context based on the .category code presented in each, for example, adjudication occurrence may represent an amount paid by the patient while another may represent the amount paid to the provider.

Additionally, there are several places in the resource which point to other sections of the resource via the use of a .sequence number in the referred-to element and an ._element_Sequence in the referring element. Sequence numbers appear in such element as .careTeam referred to by .careTeamSequence, .diagnosis referred to by .diagnosisSequence, .procedure referred to by .procedureSequence, .supportingInfo referred to by .informationSequence and .item referred to by .itemSequence.

The .noteNumber element, which appears at the .item, .detail and .subDetail levels in the .item and .addItem structures, contains a list of numbers which match the value of the .number element in the .processNote structure. The process notes are indivdual chunks of text describing a situation associated with insurer explanation of adjudication results. Rather than repeating the same text in the adjudication of line item or detail, the insurer can provide the text once in the .processNote structure then include the associated number value in the list of .noteNumbers for each of the appropriate line items or details.

StructureDefinition

Elements (Simplified)

Mappings

Resource Packs

list-ClaimResponse-packs.xml

<?xml version="1.0" encoding="UTF-8"?>

<List xmlns="http://hl7.org/fhir" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://hl7.org/fhir ../../publish/List.xsd">
  <id value="ClaimResponse-packs"/>
  <status value="current"/>
  <mode value="working"/>
</List>

Search Parameters

Full Search Parameters

Examples

Full Examples

Mapping Exceptions

claimresponse-event-mapping-exceptions.xml

Divergent Elements

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. | resource=This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Unmapped Elements

claimresponse-fivews-mapping-exceptions.xml

Unmapped Elements

claimresponse-request-mapping-exceptions.xml

Divergent Elements

Unmapped Elements