eObjects

This version of the HCX specification defines the domain model specifications required for the following eObjects:

  • Coverage Eligibility Request and Coverage Eligibility Response

  • Claim Request and Claim Response: These objects will be used for both Pre-Authorization and Claim use cases (and for Pre-Determination also in future).

  • Payment Notice and Payment Reconciliation

As mentioned in the design considerations for domain specification, the eObjects leverage HL7/FHIR4 specification and extend it, wherever required.

Coverage Eligibility Request

As per the design considerations and guidelines listed in the previous sections, the coverage eligibility request payload has to be created as an FHIR document bundle. The bundle should have the following resources:

Resource

Description

Composition

type: should be a code representing Coverage Eligibility Request document type.

section: The document shall have one section with a single entry having reference to CoverageEligibilityRequest resource.

structure definition: CoverageEligibilityRequest Documentarrow-up-right

CoverageEligibilityRequest

The document must contain a CoverageEligibilityRequest resource.

FHIR Profile: linkarrow-up-right

structure definition: CoverageEligibilityRequestarrow-up-right

Patient

The document should contain a Patient resource with minimal required information about the patient (refer to rows #38-42 in the “Coverage eligibility checkarrow-up-right” sheet).

FHIR Profile details:

  1. Patient resources should mandatorily have an NDHM identifier.

  2. Patient resources can also have a hospital Id (Medical record number).

  3. Patient resources can also have an insurance id (PMJAY ID).

  4. Patient resources can also have employee IDs and other business identifiers.

structure definition: Patientarrow-up-right

Coverage

The document should contain one or more Coverage resources with minimal information of the policy about which the information is requested (refer to row#30 in the “Coverage eligibility checkarrow-up-right” sheet).

FHIR Profile details:

  • Coverage resources should mandatorily have an identifier for the policy ID issued by the insurer.

structure definition: Coveragearrow-up-right

Domain Headers:

Key

Description

Search Parameters:

Key

Description

Coverage Eligibility Response

Resource

Description

Composition

type: should be a code representing Coverage Eligibility Response document type.

section: The document shall have one section with a single entry having reference to CoverageEligibilityResponse resource.

structure definition: CoverageEligibilityResponse Documentarrow-up-right

CoverageEligibilityResponse

The document must contain a CoverageEligibilityResponse resource.

FHIR Profile: linkarrow-up-right

structure definition: CoverageEligibilityResponsearrow-up-right

Coverage

The document should contain one or more Coverage resources with minimal information of the policy about which the information is being returned.

FHIR Profile details:

  • Coverage resources should mandatorily have an identifier for the policy ID issued by the insurer.

structure definition: Coveragearrow-up-right

Domain Headers:

Key

Description

Search Parameters:

Key

Description

Claim Request

Claim object is used by providers to submit pre-authorization and claim requests to the payers. The same eObject can be used for both these use cases and the usage can be differentiated by the value of “claim.use” element. The value of this element should be set as “preauthorization” for Pre-Authorization requests and as “claim” for Claim requests.

Resource

Description

Composition

type: should be a code representing Claim Request document type.

section: The document shall have one section with multiple entries having references to Claim and Signature resources.

structure definition: ClaimRequest Documentarrow-up-right

Claim

The document must contain a Claim resource.

FHIR Profile: linkarrow-up-right

structure definition: Claimarrow-up-right

Coverage

The document should contain one or more Coverage resources with minimal information on the policy about which the information is being returned.

FHIR Profile details:

  • Coverage resources should mandatorily have an identifier for the policy ID issued by the insurer.

structure definition: Coveragearrow-up-right

Encounter

Details of the Encounters during which this Claim was created or to which the creation of this Claim is associated.

FHIR Profile: linkarrow-up-right

structure definition: Encounterarrow-up-right

Condition

Details of the health conditions relevant to this Claim request.

FHIR Profile: linkarrow-up-right

structure definition: Conditionarrow-up-right

Signature resources

List of signatures by Hospital, Doctor and Patient associated with this Claim request.

structure definition: Signaturearrow-up-right

Domain Headers:

Key

Description

usage

“preauthorization” or “claim”, to indicate the use case this eObject is being used for.

Search Parameters:

Key

Description

Claim Response

ClaimResponse object is used by payers to send the response for pre-authorization and claim requests to the providers. The same eObject can be used for both these use cases and the usage can be differentiated by the value of “ClaimResponse.use” element. The value of this element should be set as “preauthorization” for Pre-Authorization responses and as “claim” for Claim responses.

Resource

Description

Composition

type: should be a code representing Claim Response document type.

section: The document shall have one section with a single entry having reference to ClaimResponse resource.

structure definition: ClaimResponse Documentarrow-up-right

ClaimResponse

The document must contain a ClaimResponse resource.

FHIR Profile: linkarrow-up-right

structure definition: ClaimResponsearrow-up-right

Domain Headers:

Key

Description

usage

“preauthorization” or “claim”, to indicate the use case this eObject is being used for.

Search Parameters:

Key

Description

Payment Notice

Resource

Description

Composition

type: should be a code representing Payment Notice document type.

section: The document shall have one section with a single entry having reference to PaymentNotice resource.

PaymentNotice

The document must contain a PaymentNotice resource.

FHIR Profile: linkarrow-up-right

structure definition: PaymentNoticearrow-up-right

PaymentReconciliation

The document should contain a PaymentReconciliation resource with information about the payment related to this payment notice.

FHIR Profile: linkarrow-up-right

structure definition: PaymentReconciliationarrow-up-right

Domain Headers:

Key

Description

Search Parameters:

Key

Description

Last updated