pub struct AccountInner {Show 42 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub status: AccountStatus,
pub status_ext: Option<FieldExtension>,
pub billing_status: Option<CodeableConcept>,
pub billing_status_ext: Option<FieldExtension>,
pub type: Option<CodeableConcept>,
pub type_ext: Option<FieldExtension>,
pub name: Option<String>,
pub name_ext: Option<FieldExtension>,
pub subject: Vec<Option<Reference>>,
pub subject_ext: Vec<Option<FieldExtension>>,
pub service_period: Option<Period>,
pub service_period_ext: Option<FieldExtension>,
pub coverage: Vec<Option<AccountCoverage>>,
pub coverage_ext: Vec<Option<FieldExtension>>,
pub owner: Option<Reference>,
pub owner_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub guarantor: Vec<Option<AccountGuarantor>>,
pub guarantor_ext: Vec<Option<FieldExtension>>,
pub diagnosis: Vec<Option<AccountDiagnosis>>,
pub diagnosis_ext: Vec<Option<FieldExtension>>,
pub procedure: Vec<Option<AccountProcedure>>,
pub procedure_ext: Vec<Option<FieldExtension>>,
pub related_account: Vec<Option<AccountRelatedAccount>>,
pub related_account_ext: Vec<Option<FieldExtension>>,
pub currency: Option<CodeableConcept>,
pub currency_ext: Option<FieldExtension>,
pub balance: Vec<Option<AccountBalance>>,
pub balance_ext: Vec<Option<FieldExtension>>,
pub calculated_at: Option<Instant>,
pub calculated_at_ext: Option<FieldExtension>,
/* private fields */
}Expand description
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.
Account v5.0.0
Tracks balance, charges, for patient or cost center
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.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
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.
implicit_rules: Option<String>A set of rules under which this content was created
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 its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
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).
text: Option<Narrative>Text summary of the resource, for human interpretation
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 a 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.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
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 managable, 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.
identifier: Vec<Option<Identifier>>Account number
Unique identifier used to reference the account. Might or might not be intended for human use (e.g. credit card number).
identifier_ext: Vec<Option<FieldExtension>>Extension field.
status: AccountStatusAccountStatus; active | inactive | entered-in-error | on-hold | unknown
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.
status_ext: Option<FieldExtension>Extension field.
billing_status: Option<CodeableConcept>AccountBillingStatus; Tracks the lifecycle of the account through the billing process
The BillingStatus tracks the lifecycle of the account through the billing process. It indicates how transactions are treated when they are allocated to the account.
billing_status_ext: Option<FieldExtension>Extension field.
type: Option<CodeableConcept>AccountType; E.g. patient, expense, depreciation
Categorizes the account for reporting and searching purposes.
type_ext: Option<FieldExtension>Extension field.
name: Option<String>Human-readable label
Name used for the account when displaying it to humans in reports, etc.
name_ext: Option<FieldExtension>Extension field.
subject: Vec<Option<Reference>>The entity that caused the expenses
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.
subject_ext: Vec<Option<FieldExtension>>Extension field.
service_period: Option<Period>Transaction window
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.
service_period_ext: Option<FieldExtension>Extension field.
coverage: Vec<Option<AccountCoverage>>The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account
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.
coverage_ext: Vec<Option<FieldExtension>>Extension field.
owner: Option<Reference>Entity managing the Account
Indicates the service area, hospital, department, etc. with responsibility for managing the Account.
owner_ext: Option<FieldExtension>Extension field.
description: Option<String>Explanation of purpose/use
Provides additional information about what the account tracks and how it is used.
description_ext: Option<FieldExtension>Extension field.
guarantor: Vec<Option<AccountGuarantor>>The parties ultimately responsible for balancing the Account
The parties responsible for balancing the account if other payment options fall short.
guarantor_ext: Vec<Option<FieldExtension>>Extension field.
diagnosis: Vec<Option<AccountDiagnosis>>The list of diagnoses relevant to this account
When using an account for billing a specific Encounter the set of diagnoses that are relevant for billing are stored here on the account where they are able to be sequenced appropriately prior to processing to produce claim(s).
diagnosis_ext: Vec<Option<FieldExtension>>Extension field.
procedure: Vec<Option<AccountProcedure>>The list of procedures relevant to this account
When using an account for billing a specific Encounter the set of procedures that are relevant for billing are stored here on the account where they are able to be sequenced appropriately prior to processing to produce claim(s).
procedure_ext: Vec<Option<FieldExtension>>Extension field.
Other associated accounts related to this account
Other associated accounts related to this account.
Extension field.
currency: Option<CodeableConcept>AccountCurrency; The base or default currency
The default currency for the account.
currency_ext: Option<FieldExtension>Extension field.
balance: Vec<Option<AccountBalance>>Calculated account balance(s)
The calculated account balances - these are calculated and processed by the finance system.
The balances with a term that is not current are usually generated/updated by an invoicing or similar process.
balance_ext: Vec<Option<FieldExtension>>Extension field.
calculated_at: Option<Instant>Time the balance amount was calculated
Time the balance amount was calculated.
The total(s) are not typically updated using the restful API but more often by back-end processes included in a typical finance system.
calculated_at_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for AccountInner
impl Clone for AccountInner
Source§fn clone(&self) -> AccountInner
fn clone(&self) -> AccountInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more