The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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.

Unique Id for this particular athena-claim-profile.

Who/What Claimed

PID is internal numeric value used in the Chart module and clinical data. This will be the same as the resource id in the Patient resource.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

Patient name for the athena-claim-profile is about.

Internal ID of patient used in non-clinical practice management data.

Patient profile ID

Batch no specific to the patient visit

The batch number of the batch containing this athena-claim-profile

batch no specific to the patient visit

The sum of the charges for this electronic athena-claim-profile.

Charged value of the athena-claim-profile

The sum of the charges for this electronic athena-claim-profile.

Name of the the Currency

The sum of the charges for this electronic athena-claim-profile.

Claim filing type

The ID of the filing method for ths electronic athena-claim-profile. This column should be linked to the MedLists table MedListsId column with a TableName of FilingMethods.

Claim associated filed id

The ID of the EDIClaim that contains this electronic athena-claim-profile.

athena-claim-profileed file name

Edi Claim file name

Claim file created date

The date that this electronic athena-claim-profile file was created.

Person name who filed claim

The name of the user who filed this electronic athena-claim-profile.

Claim file transmission date

Claim file transmission date

Electronic claim submission Number

The reference number for a given claim

Status of claim

The transmission status of this electronic athena-claim-profile file (i.e. 'Ready To Transmit', 'Transmission Failed', 'Transmitted')

Transmission status failure reason

A description of the reason for the unsuccessful transmission of this electronic athena-claim-profile file (applies only to files with TransmissionStatus = 'Transmission Failed')

Claim file data

The actual contents of this electronic claim file.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The maximum line length allowed when this electronic claim file was created by the plug-in.

The maximum record length allowed when this electronic claim file was created by the plug-in.

name of clearing house

clearinghouse for this electronic claim file

Reference to Organization

Reference to Organization

Insurance Carrier Id refering to Organization

Name of the the insurance Carrier

Insurance carrier Name

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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.

Unique Id for this particular athena-claim-profile.

Who/What Claimed

PID is internal numeric value used in the Chart module and clinical data. This will be the same as the resource id in the Patient resource.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

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.

Patient name for the athena-claim-profile is about.

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.

Internal ID of patient used in non-clinical practice management data.

Patient profile ID

Batch no specific to the patient visit

The batch number of the batch containing this athena-claim-profile

batch no specific to the patient visit

The sum of the charges for this electronic athena-claim-profile.

Charged value of the athena-claim-profile

The sum of the charges for this electronic athena-claim-profile.

The amount of the currency. The value includes an implicit precision in the presentation of the value.

Name of the the Currency

The sum of the charges for this electronic athena-claim-profile.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Claim filing type

The ID of the filing method for ths electronic athena-claim-profile. This column should be linked to the MedLists table MedListsId column with a TableName of FilingMethods.

Claim associated filed id

The ID of the EDIClaim that contains this electronic athena-claim-profile.

athena-claim-profileed file name

Edi Claim file name

Claim file created date

The date that this electronic athena-claim-profile file was created.

Person name who filed claim

The name of the user who filed this electronic athena-claim-profile.

Claim file transmission date

Claim file transmission date

Electronic claim submission Number

The reference number for a given claim

Status of claim

The transmission status of this electronic athena-claim-profile file (i.e. 'Ready To Transmit', 'Transmission Failed', 'Transmitted')

Transmission status failure reason

A description of the reason for the unsuccessful transmission of this electronic athena-claim-profile file (applies only to files with TransmissionStatus = 'Transmission Failed')

Claim file data

The actual contents of this electronic claim file.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The maximum line length allowed when this electronic claim file was created by the plug-in.

The maximum record length allowed when this electronic claim file was created by the plug-in.

name of clearing house

clearinghouse for this electronic claim file

Reference to Organization

Reference to Organization

Insurance Carrier Id refering to Organization

Name of the the insurance Carrier

Insurance carrier Name

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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.

Unique Id for this particular athena-claim-profile.

Who/What Claimed

PID is internal numeric value used in the Chart module and clinical data. This will be the same as the resource id in the Patient resource.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. 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.

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.

Who or what the athena-claim-profile is about. The athena-claim-profile can be about a person.

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

Patient name for the athena-claim-profile is about.

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.

Internal ID of patient used in non-clinical practice management data.

Patient profile ID

Batch no specific to the patient visit

The batch number of the batch containing this athena-claim-profile

batch no specific to the patient visit

The sum of the charges for this electronic athena-claim-profile.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. 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.

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.

Charged value of the athena-claim-profile

The sum of the charges for this electronic athena-claim-profile.

The amount of the currency. The value includes an implicit precision in the presentation of the value.

Name of the the Currency

The sum of the charges for this electronic athena-claim-profile.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Claim filing type

The ID of the filing method for ths electronic athena-claim-profile. This column should be linked to the MedLists table MedListsId column with a TableName of FilingMethods.

Claim associated filed id

The ID of the EDIClaim that contains this electronic athena-claim-profile.

athena-claim-profileed file name

Edi Claim file name

Claim file created date

The date that this electronic athena-claim-profile file was created.

Person name who filed claim

The name of the user who filed this electronic athena-claim-profile.

Claim file transmission date

Claim file transmission date

Electronic claim submission Number

The reference number for a given claim

Status of claim

The transmission status of this electronic athena-claim-profile file (i.e. 'Ready To Transmit', 'Transmission Failed', 'Transmitted')

Transmission status failure reason

A description of the reason for the unsuccessful transmission of this electronic athena-claim-profile file (applies only to files with TransmissionStatus = 'Transmission Failed')

Claim file data

The actual contents of this electronic claim file.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The record delimiter used when this electronic claim file was created by the plug-in.

The maximum line length allowed when this electronic claim file was created by the plug-in.

The maximum record length allowed when this electronic claim file was created by the plug-in.

name of clearing house

clearinghouse for this electronic claim file

Reference to Organization

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. 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.

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.

Reference to Organization

Insurance Carrier Id refering to Organization

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

Name of the the insurance Carrier

Insurance carrier Name