R6 Ballot (1st Draft)

This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions

13.7 Resource ClaimResponse - Content

Financial Management icon Work GroupMaturity Level: 2 Trial UseSecurity Category: Patient Compartments: Patient, Practitioner

This resource provides the adjudication details from the processing of a Claim resource.

13.7.1 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.

13.7.1.1 Additional Information

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

  • Financial Resource Status Lifecycle: how .status is used in the financial resources.
  • Secondary Use of Resources: how resources such as Claim, ClaimResponse and ExplanationOfBenefit may be used for reporting and data exchange for analytics, not just for eClaims exchange between providers and payors.
  • Subrogation: how eClaims may handle patient insurance coverages when another insurer rather than the provider will settle the claim and potentially recover costs against specified coverages.
  • Coordination of Benefit: how eClaims may handle multiple patient insurance coverages.
  • RealTime Exchange and Obtaining Deferred Responsess: ClaimResponses may be obtained using Polling or FHIR REST (SEARCH).
  • Attachments and Supporting Information: how eClaims may handle the provision of supporting information, whether provided by content or reference, within the eClaim resource when submitted to the payor or later in a resource which refers to the subject eClaim resource. This also includes how payors may request additional supporting information from providers.
  • 3-Tier Line Item Hierarchy: 3-tier hierarchy of Goods, products, and Services, to support simple to complex billing.
  • Tax: Tax handling of Goods, products, and Services.

13.7.2 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
ClaimResponse A payor'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.
ExplanationOfBenefit This resource combines the information from the Claim and the ClaimResponse, stripping out any provider or payor 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.
Claim A suite of goods and services and insurances coverages under which adjudication or authorization is requested.
CoverageEligibilityResponse The response to a request to a payor, 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.

13.7.3 References to this Resource

13.7.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ClaimResponse TUDomainResourceResponse to a claim predetermination or preauthorization

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier 0..*IdentifierBusiness Identifier for a claim response

... traceNumber 0..*IdentifierNumber for tracking

... status ?!Σ1..1codeactive | cancelled | draft | entered-in-error
Binding: Financial Resource Status Codes (Required)
... type Σ1..1CodeableConceptMore granular claim type
Binding: Claim Type Codes (Extensible)
... subType 0..1CodeableConceptMore granular claim type
Binding: Example Claim SubType Codes (Example)
... use Σ1..1codeclaim | preauthorization | predetermination
Binding: Use (Required)
... patient Σ1..1Reference(Patient)The recipient of the products and services
... created Σ1..1dateTimeResponse creation date
... insurer Σ0..1Reference(Organization)Party responsible for reimbursement
... requestor 0..1Reference(Practitioner | PractitionerRole | Organization)Party responsible for the claim
... request Σ0..1Reference(Claim)Id of resource triggering adjudication
... outcome Σ1..1codequeued | complete | error | partial
Binding: Claim Processing Codes (Required)
... decision Σ0..1CodeableConceptResult of the adjudication
Binding: Claim Adjudication Decision Codes (Example)
... disposition 0..1stringDisposition Message
... preAuthRef 0..1stringPreauthorization reference
... preAuthPeriod 0..1PeriodPreauthorization reference effective period
... event 0..*BackboneElementEvent information

.... type 1..1CodeableConceptSpecific event
Binding: Dates Type Codes (Example)
.... when[x] 1..1Occurance date or period
..... whenDateTimedateTime
..... whenPeriodPeriod
... payeeType 0..1CodeableConceptParty to be paid any benefits payable
Binding: Claim Payee Type Codes (Example)
... encounter 0..*Reference(Encounter)Encounters associated with the listed treatments

... diagnosisRelatedGroup 0..1CodeableConceptPackage billing code
Binding: Example Diagnosis Related Group Codes (Example)
... item 0..*BackboneElementAdjudication for claim line items

.... itemSequence 1..1positiveIntClaim item instance identifier
.... traceNumber 0..*IdentifierNumber for tracking

.... noteNumber 0..*positiveIntApplicable note numbers

.... reviewOutcome 0..1BackboneElementAdjudication results
..... decision 0..1CodeableConceptResult of the adjudication
Binding: Claim Adjudication Decision Codes (Example)
..... reason 0..*CodeableConceptReason for result of the adjudication
Binding: Claim Adjudication Decision Reason Codes (Example)

..... preAuthRef 0..1stringPreauthorization reference
..... preAuthPeriod 0..1PeriodPreauthorization reference effective period
.... adjudication 0..*BackboneElementAdjudication details

..... category 1..1CodeableConceptType of adjudication information
Binding: Adjudication Value Codes (Example)
..... reason 0..1CodeableConceptExplanation of adjudication outcome
Binding: Adjudication Reason Codes (Example)
..... amount 0..1MoneyMonetary amount
..... quantity 0..1QuantityNon-monetary value
.... detail 0..*BackboneElementAdjudication for claim details

..... detailSequence 1..1positiveIntClaim detail instance identifier
..... traceNumber 0..*IdentifierNumber for tracking

..... noteNumber 0..*positiveIntApplicable note numbers

..... reviewOutcome 0..1see reviewOutcomeDetail level adjudication results
..... adjudication 0..*see adjudicationDetail level adjudication details

..... subDetail 0..*BackboneElementAdjudication for claim sub-details

...... subDetailSequence 1..1positiveIntClaim sub-detail instance identifier
...... traceNumber 0..*IdentifierNumber for tracking

...... noteNumber 0..*positiveIntApplicable note numbers

...... reviewOutcome 0..1see reviewOutcomeSubdetail level adjudication results
...... adjudication 0..*see adjudicationSubdetail level adjudication details

... addItem 0..*BackboneElementInsurer added line items

.... itemSequence 0..*positiveIntItem sequence number

.... detailSequence 0..*positiveIntDetail sequence number

.... subdetailSequence 0..*positiveIntSubdetail sequence number

.... traceNumber 0..*IdentifierNumber for tracking

.... provider 0..*Reference(Practitioner | PractitionerRole | Organization)Authorized providers

.... revenue 0..1CodeableConceptRevenue or cost center code
Binding: Example Revenue Center Codes (Example)
.... productOrService 0..1CodeableConceptBilling, service, product, or drug code
Binding: USCLS Codes (Example)
.... productOrServiceEnd 0..1CodeableConceptEnd of a range of codes
Binding: USCLS Codes (Example)
.... request 0..*Reference(DeviceRequest | MedicationRequest | NutritionOrder | ServiceRequest | SupplyRequest | VisionPrescription)Request or Referral for Service

.... modifier 0..*CodeableConceptService/Product billing modifiers
Binding: Modifier type Codes (Example)

.... programCode 0..*CodeableConceptProgram the product or service is provided under
Binding: Example Program Reason Codes (Example)

.... serviced[x] 0..1Date or dates of service or product delivery
..... servicedDatedate
..... servicedPeriodPeriod
.... location[x] 0..1Place of service or where product was supplied
Binding: Example Service Place Codes (Example)
..... locationCodeableConceptCodeableConcept
..... locationAddressAddress
..... locationReferenceReference(Location)
.... quantity 0..1SimpleQuantityCount of products or services
.... unitPrice 0..1MoneyFee, charge or cost per item
.... factor 0..1decimalPrice scaling factor
.... tax 0..1MoneyTotal tax
.... net 0..1MoneyTotal item cost
.... bodySite 0..*BackboneElementAnatomical location

..... site 1..*CodeableReference(BodyStructure)Location
Binding: Oral Site Codes (Example)

..... subSite 0..*CodeableConceptSub-location
Binding: Surface Codes (Example)

.... noteNumber 0..*positiveIntApplicable note numbers

.... reviewOutcome 0..1see reviewOutcomeAdded items adjudication results
.... adjudication 0..*see adjudicationAdded items adjudication

.... detail 0..*BackboneElementInsurer added line details

..... traceNumber 0..*IdentifierNumber for tracking

..... revenue 0..1CodeableConceptRevenue or cost center code
Binding: Example Revenue Center Codes (Example)
..... productOrService 0..1CodeableConceptBilling, service, product, or drug code
Binding: USCLS Codes (Example)
..... productOrServiceEnd 0..1CodeableConceptEnd of a range of codes
Binding: USCLS Codes (Example)
..... modifier 0..*CodeableConceptService/Product billing modifiers
Binding: Modifier type Codes (Example)

..... quantity 0..1SimpleQuantityCount of products or services
..... unitPrice 0..1MoneyFee, charge or cost per item
..... factor 0..1decimalPrice scaling factor
..... tax 0..1MoneyTotal tax
..... net 0..1MoneyTotal item cost
..... noteNumber 0..*positiveIntApplicable note numbers

..... reviewOutcome 0..1see reviewOutcomeAdded items detail level adjudication results
..... adjudication 0..*see adjudicationAdded items detail adjudication

..... subDetail 0..*BackboneElementInsurer added line items

...... traceNumber 0..*IdentifierNumber for tracking

...... revenue 0..1CodeableConceptRevenue or cost center code
Binding: Example Revenue Center Codes (Example)
...... productOrService 0..1CodeableConceptBilling, service, product, or drug code
Binding: USCLS Codes (Example)
...... productOrServiceEnd 0..1CodeableConceptEnd of a range of codes
Binding: USCLS Codes (Example)
...... modifier 0..*CodeableConceptService/Product billing modifiers
Binding: Modifier type Codes (Example)

...... quantity 0..1SimpleQuantityCount of products or services
...... unitPrice 0..1MoneyFee, charge or cost per item
...... factor 0..1decimalPrice scaling factor
...... tax 0..1MoneyTotal tax
...... net 0..1MoneyTotal item cost
...... noteNumber 0..*positiveIntApplicable note numbers

...... reviewOutcome 0..1see reviewOutcomeAdded items subdetail level adjudication results
...... adjudication 0..*see adjudicationAdded items subdetail adjudication

... adjudication 0..*see adjudicationHeader-level adjudication

... total Σ0..*BackboneElementAdjudication totals

.... category Σ1..1CodeableConceptType of adjudication information
Binding: Adjudication Value Codes (Example)
.... amount Σ1..1MoneyFinancial total for the category
... payment 0..1BackboneElementPayment Details
.... type 1..1CodeableConceptPartial or complete payment
Binding: Example Payment Type Codes (Example)
.... adjustment 0..1MoneyPayment adjustment for non-claim issues
.... adjustmentReason 0..1CodeableConceptExplanation for the adjustment
Binding: Payment Adjustment Reason Codes (Example)
.... date 0..1dateExpected date of payment
.... amount 1..1MoneyPayable amount after adjustment
.... identifier 0..1IdentifierBusiness identifier for the payment
... fundsReserve 0..1CodeableConceptFunds reserved status
Binding: Funds Reservation Codes (Example)
... formCode 0..1CodeableConceptPrinted form identifier
Binding: Form Codes (Example)
... form 0..1AttachmentPrinted reference or actual form
... processNote 0..*BackboneElementNote concerning adjudication

.... number 0..1positiveIntNote instance identifier