A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.

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

R5: Account.billingStatus (new:CodeableConcept)

Element Account.billingStatus has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.billingStatus has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.diagnosis (new:BackboneElement)

Element Account.diagnosis has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.diagnosis has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.procedure (new:BackboneElement)

Element Account.procedure has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.procedure has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.relatedAccount (new:BackboneElement)

Element Account.relatedAccount has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.relatedAccount has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.currency (new:CodeableConcept)

Element Account.currency has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.currency has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.balance (new:BackboneElement)

Element Account.balance has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.balance has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.calculatedAt (new:instant)

Element Account.calculatedAt has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.calculatedAt has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.

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.

Indicates whether the account is presently used/usable or not.

This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid.

Indicates whether the account is available to be used.

R5: Account.billingStatus (new:CodeableConcept)

Element Account.billingStatus has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.billingStatus has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.diagnosis (new:BackboneElement)

Element Account.diagnosis has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.diagnosis has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.procedure (new:BackboneElement)

Element Account.procedure has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.procedure has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.relatedAccount (new:BackboneElement)

Element Account.relatedAccount has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.relatedAccount has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.currency (new:CodeableConcept)

Element Account.currency has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.currency has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.balance (new:BackboneElement)

Element Account.balance has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.balance has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.calculatedAt (new:instant)

Element Account.calculatedAt has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.calculatedAt has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.

A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc.

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.

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.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

The codes SHOULD be taken from CommonLanguages
(preferred to http://hl7.org/fhir/ValueSet/languages|4.0.1)

A human language.

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

R5: Account.billingStatus (new:CodeableConcept)

Element Account.billingStatus has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.billingStatus has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.diagnosis (new:BackboneElement)

Element Account.diagnosis has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.diagnosis has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.procedure (new:BackboneElement)

Element Account.procedure has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.procedure has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.relatedAccount (new:BackboneElement)

Element Account.relatedAccount has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.relatedAccount has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.currency (new:CodeableConcept)

Element Account.currency has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.currency has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.balance (new:BackboneElement)

Element Account.balance has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.balance has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: Account.calculatedAt (new:instant)

Element Account.calculatedAt has a context of Account based on following the parent source element upwards and mapping to Account. Element Account.calculatedAt has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.

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.

Unique identifier used to reference the account. Might or might not be intended for human use (e.g. credit card number).

Indicates whether the account is presently used/usable or not.

This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the Account as not currently valid.

Indicates whether the account is available to be used.

Categorizes the account for reporting and searching purposes.

The usage type of this account, permits categorization of accounts.

Name used for the account when displaying it to humans in reports, etc.

Identifies the entity which incurs the expenses. While the immediate recipients of services or goods might be entities related to the subject, the expenses were ultimately incurred by the subject of the Account.

Accounts can be applied to non-patients for tracking other non-patient related activities, such as group services (patients not tracked, and costs charged to another body), or might not be allocated.

The date range of services associated with this account.

It is possible for transactions to be posted outside the service period, as long as the service was provided within the defined service period.

The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account.

Typically. this may be some form of insurance, internal charges, or self-pay.

Local or jurisdictional business rules may determine which coverage covers which types of billable items charged to the account, and in which order. Where the order is important, a local/jurisdictional extension may be defined to specify the order for the type of charge.

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.

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.

The party(s) that contribute to payment (or part of) of the charges applied to this account (including self-pay).

A coverage may only be responsible for specific types of charges, and the sequence of the coverages in the account could be important when processing billing.

The priority of the coverage in the context of this account.

It is common in some jurisdictions for there to be multiple coverages allocated to an account, and a sequence is required to order the settling of the account (often with insurance claiming).

Indicates the service area, hospital, department, etc. with responsibility for managing the Account.

Provides additional information about what the account tracks and how it is used.

The parties responsible for balancing the account if other payment options fall short.

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.

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.

The entity who is responsible.

A guarantor may be placed on credit hold or otherwise have their role temporarily suspended.

The timeframe during which the guarantor accepts responsibility for the account.

Reference to a parent Account.