The Period.start date corresponds with the date the beneficiary was admitted to a facility and the onset of services. May precede the Statement From Date if this claim is for a beneficiary who has been continuously under care. The Period.end date corresponds with the date beneficiary was discharged from the facility, or died. Matches the final Statement Thru Date. When there is a discharge date, the Patient Discharge Status Code indicates the final disposition of the patient after discharge. (18, 19)

The date the claim was received by the payer (88)

UB04 (Form Locator 4) type of bill code provides specific information for payer purposes. The first digit of the three-digit number denotes the type of institution, the second digit classifies the type of care being billed, and the third digit identifies the frequency of the bill for a specific course of treatment or inpatient confinement. (17)

Identifies the place where the patient was identified as needing admission to an institution. This is a two position code mapped from the standard values for the UB-04 Source of Admission code (FL-15). (13)

Priority of the admission. Information located on (UB04 Form Locator 14). For example, an admission type of elective indicates that the patient's condition permitted time for medical services to be scheduled. (14)

Patient’s status as of the discharge date for a facility stay. Information located on UB04. (Form Locator 17). (117)

Claim diagnosis related group (DRG). DRGs require the DRG system; i.e., MS-DRG / AP-DRG / APR-DRG, the DRG version and the code value (32, 33. 113)

Provider submitted medical record number that can be included on the claim. (109)

Provider assigned patient account number that can be included on the claim. (109)

Diagnosis codes describe an individual's disease or medical condition. (6, 7, 8, 21, 22, 23, 30)

Diagnosis.sequence values do not necessarily indicate any order in which the diagnosis was reported or identified. client app implementations should not assign any significance to the sequence values. client app implementations should use the values of diagnosis.type to identify primary, secondary, etc.

Indicates if the inpatient institutional diagnosis is admitting, principal, other or an external cause of injury. (21, 22, 23)

Used to capture whether a diagnosis was present at time of a patient's admission. (28)

Medical procedure a patient received during inpatient stay. Current coding methods include: International Classification of Diseases Surgical Procedures (ICD-9). Information located on UB04 (Form Locator 74). (25, 27, 10, 12)

procedure.sequence values do not necessarily indicate any order in which the procedure occurred. client app implementations should not assign any significance to the sequence values. client app implementations should use the values of procedure.type to identify primary and secondary procedures

Indicates if the inpatient institutional procedure (ICD-PCS) is the principal procedure or another procedure. (186)

Code used on the UB-04 (Form Locator 42) to identify a specific accommodation, ancillary service, or billing calculation related to the service being billed (86)

Medical procedure a patient received from a health care provider. Current coding methods include: CPT-4 and HCFA Common Procedure Coding System Level II - (HCPCSII). (40)

Modifier(s) for the procedure represented on this line. Identifies special circumstances related to the performance of the service. (41)

The quantity of units, times, days, visits, services, or treatments for the service described by the HCPCS code, revenue code or procedure code, submitted by the provider. (42)

Reason codes used to interpret the Non-Covered Amount that are provided to the Provider. (92)

The quantity of units, times, days, visits, services, or treatments allowed for the service described by the HCPCS code, revenue code or procedure code, submitted by the provider. (149)

Indicates that the Billing Provider has a contract with the Plan (regardless of the network) as of the effective date of service or admission. (101)

Indicates the in network or out of network payment status of the claim. (142)

Reason codes used to interpret the Non-Covered Amount that are provided to the Provider. (92)

Reason codes used to interpret the Non-Covered Amount that are provided to the Provider. (92)

This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

When the resource last changed - e.g. when the version changed.

Defines the date the Resource was created or updated, whichever comes last (163). Payers SHALL provide the last time the data was updated or the date of creation in the payer’s system of record, whichever comes last

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

meta.profile is required as a matter of convenience of receiving systems. The meta.profile should be used by the Server to hint/assert/declare that this instance conforms to one (or more) stated profiles (with business versions). meta.profile does not capture any business logic, processing directives, or semantics (for example, inpatient or outpatient). Clients should not assume that the Server will exhaustively indicate all profiles with all versions that this instance conforms to. Clients can (and should) perform their own validation of conformance to the indicated profile(s) and to any other profiles of interest. CPCDS data element (190)

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.

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 explanation of benefit.

Identifier assigned by a payer for a claim received from a provider or subscriber. It is not the same identifier as that assigned by a provider. (35)

Allows EOBs to be distinguished and referenced.

A unique identifier assigned to this explanation of benefit.

Allows EOBs 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 portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

The status of the resource instance.

Claim processing status code (140). Expected values are active or cancelled. To comply with the CMS rule, draft EOBs are not required

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.

Specifies the type of claim. (e.g., inpatient institutional, outpatient institutional, physician, etc.) (16). Defines the Claims profiles. Values from Claim Type Codes are required; a data absent reason is not allowed

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 such as the US UB-04 bill type code.

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.

Expected value is claim. The CMS rule applies to adjudicated claims; it does not require preauthorizations or predeterminations

Complete, proposed, exploratory, other.

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 for forecast reimbursement is sought.

Identifier for a member assigned by the Payer. If members receive ID cards, that is the identifier that should be provided. (1). 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 adjudication. Additional required path:EOB.insurance.coverage(Coverage).beneficiary(Patient).identifier

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 prodeterminations. 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 start of the period. The boundary is inclusive.

The first day on the billing statement covering services rendered to the beneficiary (i.e. 'Statement Covers From Date’). (177)

The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

The last day on the billing statement covering services rendered to the beneficiary (i.e. 'Statement Covers Thru Date’). (178)

The date this resource was created.

Date the claim was adjudicated (179)

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

The party responsible for authorization, adjudication and reimbursement.

Code of the payer responsible for the claim (2, 5). Same as insurance.coverage.organization. Party responsible for reimbursing the provider

To be a valid claim, preauthorization or predetermination there must be a party who is responsible for adjudicating the contents against a policy which provides benefits for the patient.

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

The identifier assigned to the Billing Provider. (94)

Other claims which are related to this claim such as prior submissions or claims for related services or for the same event.

If the current claim represents a claim that has been adjusted and was given a prior claim number, this field represents the prior claim number. If the current claim has been adjusted; i.e., replaced by or merged to another claim number, this data element represents that new number.(111, 112)

For workplace or other accidents it is common to relate separate claims arising from the same event.

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 code to convey how the claims are related.

For example, prior claim or umbrella.

Some insurers need a declaration of the type of relationship.

An alternate organizational reference to the case or file to which this particular claim pertains.

For example, Property/Casualty insurer claim number or Workers Compensation case number.

In cases where an event-triggered claim is being submitted to an insurer which requires a reference number to be specified on all exchanges.

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

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.

Type of Party to be reimbursed: Subscriber, provider, other.

Identifies the type of recipient of the adjudication amount; i.e., provider, subscriber, beneficiary or another recipient. (120)

Need to know who should receive payment with the most common situations being the Provider (assignment of benefits) or the Subscriber.

Reference to the individual or organization to whom any payment will be made.

Recipient reference (121)

Need to provide demographics if the payee is not 'subscriber' nor 'provider'.

The outcome of the claim, predetermination, or preauthorization processing.

Expected value is complete

The result of the claim processing.

To advise the requestor of an overall processing outcome.

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.

careTeam.sequence values uniquely identify careTeam members. They do not necessarily indicate any order in which the patient was seen by the careTeam or identify any level of significance of the careTeam to the patient, etc. Client app implementations should not assign any significance to the sequence values

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.

The identifier assigned to the care team. (varies depending on the profile)

Often a regulatory requirement to specify the responsible provider.

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

The functional role of a provider on a claim. (165)

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.

Defines data elements not available in the base EOB resource

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

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

The Period.start date corresponds with the date the beneficiary was admitted to a facility and the onset of services. May precede the Statement From Date if this claim is for a beneficiary who has been continuously under care. The Period.end date corresponds with the date beneficiary was discharged from the facility, or died. Matches the final Statement Thru Date. When there is a discharge date, the Patient Discharge Status Code indicates the final disposition of the patient after discharge. (18, 19)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

The date when or period to which this information refers.

The date when or period to which this information refers.

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

The date the claim was received by the payer (88)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

The date when or period to which this information refers.

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

UB04 (Form Locator 4) type of bill code provides specific information for payer purposes. The first digit of the three-digit number denotes the type of institution, the second digit classifies the type of care being billed, and the third digit identifies the frequency of the bill for a specific course of treatment or inpatient confinement. (17)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.

This may contain the local bill type codes such as the US UB-04 bill type code.

Required to identify the kind of additional information.

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

Identifies the place where the patient was identified as needing admission to an institution. This is a two position code mapped from the standard values for the UB-04 Source of Admission code (FL-15). (13)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.

This may contain the local bill type codes such as the US UB-04 bill type code.

Required to identify the kind of additional information.

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

Priority of the admission. Information located on (UB04 Form Locator 14). For example, an admission type of elective indicates that the patient's condition permitted time for medical services to be scheduled. (14)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.

This may contain the local bill type codes such as the US UB-04 bill type code.

Required to identify the kind of additional information.

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

Patient’s status as of the discharge date for a facility stay. Information located on UB04. (Form Locator 17). (117)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.

This may contain the local bill type codes such as the US UB-04 bill type code.

Required to identify the kind of additional information.

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

Claim diagnosis related group (DRG). DRGs require the DRG system; i.e., MS-DRG / AP-DRG / APR-DRG, the DRG version and the code value (32, 33. 113)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.

This may contain the local bill type codes such as the US UB-04 bill type code.

Required to identify the kind of additional information.

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

Provider submitted medical record number that can be included on the claim. (109)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data.

Could be used to provide references to other resources, document. For example, could contain a PDF in an Attachment of the Police Report for an Accident.

To convey the data content to be provided when the information is more than a simple code or period.

Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data.

Could be used to provide references to other resources, document. For example, could contain a PDF in an Attachment of the Police Report for an Accident.

To convey the data content to be provided when the information is more than a simple code or period.

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

Provider assigned patient account number that can be included on the claim. (109)

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

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 supporting information entries.

Client app implementations should look-up supportingInfo elements based on category values instead of sequence values

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

The general class of the information supplied: information; exception; accident, employment; onset, etc.

This may contain a category for the local bill type codes.

Required to group or associate information items with common characteristics. For example: admission information or prior treatments.

Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data.

Could be used to provide references to other resources, document. For example, could contain a PDF in an Attachment of the Police Report for an Accident.

To convey the data content to be provided when the information is more than a simple code or period.

Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data.

Could be used to provide references to other resources, document. For example, could contain a PDF in an Attachment of the Police Report for an Accident.

To convey the data content to be provided when the information is more than a simple code or period.

Information about diagnoses relevant to the claim items.

Diagnosis codes describe an individual's disease or medical condition. (6, 7, 8, 21, 22, 23, 30)

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.sequence values do not necessarily indicate any order in which the diagnosis was reported or identified. client app implementations should not assign any significance to the sequence values. client app implementations should use the values of diagnosis.type to identify 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.

Indicates if the inpatient institutional diagnosis is admitting, principal, other or an external cause of injury. (21, 22, 23)

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

Indication of whether the diagnosis was present on admission to a facility.

Used to capture whether a diagnosis was present at time of a patient's admission. (28)