A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement.

The Claim resource fulfills three information request requirements: Claim - a request for adjudication for reimbursement for products and/or services provided; Preauthorization - a request to authorize the future provision of products and/or services including an anticipated adjudication; and, Predetermination - a request for a non-bind adjudication of possible future products and/or services.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

Disclaimers the patient should be made aware of regarding the providers estimate

This extension is used to communicate a plain language description of the procedure, product, or service.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A unique identifier assigned to this claim.

Allows claims to be distinguished and referenced.

A unique identifier assigned to this claim.

Allows claims to be distinguished and referenced.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

The status of the resource instance.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A code specifying the state of the resource instance.

Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.

The category of claim, e.g. oral, pharmacy, vision, institutional, professional.

The majority of jurisdictions use: oral, pharmacy, vision, professional and institutional, or variants on those terms, as the general styles of claims. The valueset is extensible to accommodate other jurisdictional requirements.

The type or discipline-style of the claim.

Claim type determine the general sets of business rules applied for information requirements and adjudication.

A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service.

This may contain the local bill type codes, for example the US UB-04 bill type code or the CMS bill type.

A more granular claim typecode.

Some jurisdictions need a finer grained claim type for routing and adjudication.

A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future.

The purpose of the Claim: predetermination, preauthorization, claim.

This element is required to understand the nature of the request for adjudication.

The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought.

The patient must be supplied to the insurer so that confirmation of coverage and service history may be considered as part of the authorization and/or adjudiction.

The period for which charges are being submitted.

Typically this would be today or in the past for a claim, and today or in the future for preauthorizations and predeterminations. Typically line item dates of service should fall within the billing period if one is specified.

A number jurisdictions required the submission of the billing period when submitting claims for example for hospital stays or long-term care.

The date this resource was created.

This field is independent of the date of creation of the resource as it may reflect the creation date of a source document prior to digitization. Typically for claims all services must be completed as of this date.

Need to record a timestamp for use by both the recipient and the issuer.

Individual who created the claim, predetermination or preauthorization.

Some jurisdictions require the contact information for personnel completing claims.

The Insurer who is target of the request.

The provider which is responsible for the claim, predetermination or preauthorization.

Typically this field would be 1..1 where this party is responsible for the claim but not necessarily professionally responsible for the provision of the individual products and services listed below.

An Extension

Provides a reason why the expected value or elements in the element that is extended are missing.

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The provider-required urgency of processing the request. Typical values include: stat, routine deferred.

If a claim processor is unable to complete the processing as per the priority then they should generate and error and not process the request.

The provider may need to indicate their processing requirements so that the processor can indicate if they are unable to comply.

A code to indicate whether and for whom funds are to be reserved for future claims.

This field is only used for preauthorizations.

For whom funds are to be reserved: (Patient, Provider, None).

In the case of a Pre-Determination/Pre-Authorization the provider may request that funds in the amount of the expected Benefit be reserved ('Patient' or 'Provider') to pay for the Benefits determined on the subsequent claim(s). 'None' explicitly indicates no funds reserving is requested.

Prescription to support the dispensing of pharmacy, device or vision products.

Required to authorize the dispensing of controlled substances and devices.

Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products.

For example, a physician may prescribe a medication which the pharmacy determines is contraindicated, or for which the patient has an intolerance, and therefore issues a new prescription for an alternate medication which has the same therapeutic intent. The prescription from the pharmacy becomes the 'prescription' and that from the physician becomes the 'original prescription'.

Often required when a fulfiller varies what is fulfilled from that authorized on the original prescription.

The party to be reimbursed for cost of the products and services according to the terms of the policy.

Often providers agree to receive the benefits payable to reduce the near-term costs to the patient. The insurer may decline to pay the provider and choose to pay the subscriber instead.

The provider needs to specify who they wish to be reimbursed and the claims processor needs express who they will reimburse.

A reference to a referral resource.

The referral resource which lists the date, practitioner, reason and other supporting information.

Some insurers require proof of referral to pay for services or to pay specialist rates for services.

Facility where the services were provided.

Insurance adjudication can be dependant on where services were delivered.

The members of the team who provided the products and services.

Common to identify the responsible and supporting practitioners.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify care team entries.

Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.

Member of the team who provided the product or service.

Often a regulatory requirement to specify the responsible provider.

The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.

Role might not be required when there is only a single provider listed.

When multiple parties are present it is required to distinguish the roles performed by each member.

The qualification of the practitioner which is applicable for this service.

Need to specify which qualification a provider is delivering the product or service under.

The members of the team who provided the products and services.

Common to identify the responsible and supporting practitioners.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify care team entries.

Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.

Member of the team who provided the product or service.

Often a regulatory requirement to specify the responsible provider.

The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.

Role might not be required when there is only a single provider listed.

The role codes for the care team members.

When multiple parties are present it is required to distinguish the roles performed by each member.

The qualification of the practitioner which is applicable for this service.

Provider professional qualifications.

Need to specify which qualification a provider is delivering the product or service under.

The members of the team who provided the products and services.

Common to identify the responsible and supporting practitioners.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify care team entries.

Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.

Member of the team who provided the product or service.

Often a regulatory requirement to specify the responsible provider.

The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.

Role might not be required when there is only a single provider listed.

The role codes for the care team members.

When multiple parties are present it is required to distinguish the roles performed by each member.

The members of the team who provided the products and services.

Common to identify the responsible and supporting practitioners.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify care team entries.

Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.

Member of the team who provided the product or service.

Often a regulatory requirement to specify the responsible provider.

The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.

Role might not be required when there is only a single provider listed.

The role codes for the care team members.

When multiple parties are present it is required to distinguish the roles performed by each member.

The members of the team who provided the products and services.

Common to identify the responsible and supporting practitioners.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify care team entries.

Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.

Member of the team who provided the product or service.

Often a regulatory requirement to specify the responsible provider.

The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.

Role might not be required when there is only a single provider listed.

The role codes for the care team members.

When multiple parties are present it is required to distinguish the roles performed by each member.

Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues.

Often there are multiple jurisdiction specific valuesets which are required.

Typically these information codes are required to support the services rendered or the adjudication of the services rendered.

Information about diagnoses relevant to the claim items.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Example ICD10 Diagnostic codes.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Information about diagnoses relevant to the claim items.

If the Principal Diagnosis code is known, it is important that it be shared in the GFE, particularly when the GFE is being sent to a payer for an insured patient. Payers very often need the diagnosis to be able to provide an estimate. Without the diagnosis, payers may assume the service is diagnostic and thus the patient responsibility may be higher than the diagnosis, such as for preventative services, would otherwise indicate. It is understood that in certain situations, such as scheduled services or GFE requests prior to orders, diagnosis is not needed or may not yet be known. However, when it is known, it is important that this information be shared to ensure the best possible estimate is provided to the patient.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

The type of the diagnosis: admitting, principal, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Information about diagnoses relevant to the claim items.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

The type of the diagnosis: admitting, principal, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Information about diagnoses relevant to the claim items.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

The type of the diagnosis: admitting, principal, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Information about diagnoses relevant to the claim items.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

The type of the diagnosis: admitting, principal, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Information about diagnoses relevant to the claim items.

Required for the adjudication by provided context for the services and product listed.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify diagnosis entries.

Diagnosis are presented in list order to their expected importance: primary, secondary, etc.

Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.

The nature of illness or problem in a coded form or as a reference to an external defined Condition.

Provides health context for the evaluation of the products and/or services.

When the condition was observed or the relative ranking.

For example: admitting, primary, secondary, discharge.

The type of the diagnosis: admitting, principal, discharge.

Often required to capture a particular diagnosis, for example: primary or discharge.

Procedures performed on the patient relevant to the billing items with the claim.

The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service.

An Extension

This extension is used to communicate a plain language description of the procedure, product, or service.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify procedure entries.

Necessary to provide a mechanism to link to claim details.

When the condition was observed or the relative ranking.

For example: primary, secondary.

Often required to capture a particular diagnosis, for example: primary or discharge.

The code or reference to a Procedure resource which identifies the clinical intervention performed.

Example ICD10 Procedure codes.

This identifies the actual clinical procedure.

Procedures performed on the patient relevant to the billing items with the claim.

The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service.

This extension is used to communicate a plain language description of the procedure, product, or service.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify procedure entries.

Necessary to provide a mechanism to link to claim details.

When the condition was observed or the relative ranking.

For example: primary, secondary.

Example procedure type codes.

Often required to capture a particular diagnosis, for example: primary or discharge.

The code or reference to a Procedure resource which identifies the clinical intervention performed.

This identifies the actual clinical procedure.

Procedures performed on the patient relevant to the billing items with the claim.

The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service.

This extension is used to communicate a plain language description of the procedure, product, or service.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify procedure entries.

Necessary to provide a mechanism to link to claim details.

When the condition was observed or the relative ranking.

For example: primary, secondary.

Example procedure type codes.

Often required to capture a particular diagnosis, for example: primary or discharge.

The code or reference to a Procedure resource which identifies the clinical intervention performed.

This identifies the actual clinical procedure.

Procedures performed on the patient relevant to the billing items with the claim.

The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service.

This extension is used to communicate a plain language description of the procedure, product, or service.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify procedure entries.

Necessary to provide a mechanism to link to claim details.

When the condition was observed or the relative ranking.

For example: primary, secondary.

Example procedure type codes.

Often required to capture a particular diagnosis, for example: primary or discharge.

The code or reference to a Procedure resource which identifies the clinical intervention performed.

This identifies the actual clinical procedure.

Financial instruments for reimbursement for the health care products and services specified on the claim.

All insurance coverages for the patient which may be applicable for reimbursement, of the products and services listed in the claim, are typically provided in the claim to allow insurers to confirm the ordering of the insurance coverages relative to local 'coordination of benefit' rules. One coverage (and only one) with 'focal=true' is to be used in the adjudication of this claim. Coverages appearing before the focal Coverage in the list, and where 'Coverage.subrogation=false', should provide a reference to the ClaimResponse containing the adjudication results of the prior claim.

At least one insurer is required for a claim to be a claim.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order.

To maintain order of the coverages.

A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true.

A patient may (will) have multiple insurance policies which provide reimbursement for healthcare services and products. For example a person may also be covered by their spouse's policy and both appear in the list (and may be from the same insurer). This flag will be set to true for only one of the listed policies and that policy will be used for adjudicating this claim. Other claims would be created to request adjudication against the other listed policies.

To identify which coverage in the list is being used to adjudicate this claim.

Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system.

Required to allow the adjudicator to locate the correct policy and history within their information system.

Reference numbers previously provided by the insurer to the provider to be quoted on subsequent claims containing services or products related to the prior authorization.

This value is an alphanumeric string that may be provided over the phone, via text, via paper, or within a ClaimResponse resource and is not a FHIR Identifier.

Providers must quote previously issued authorization reference numbers in order to obtain adjudication as previously advised on the Preauthorization.

A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details.

The items to be processed for adjudication.

The total value of the all the items in the claim.

Used for control total purposes.