Generated Narrative: StructureDefinition DebtPortalInvoice Name Flags Card. Type Description & Constraints Invoice 0..* Invoice(4.0.1) Invoice containing ChargeItems from an Account #xD; identifier S 0..* Identifier Business Identifier for item #xD; status S 1..1 code draft | issued | balanced | cancelled | entered-in-error Binding: ARBillStatus FHIR (required): see mapping VF_ARBillStatus #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:alternate-codes S 0..1 (Complex) Alternate code/original text for this code URL: http://hl7.org/fhir/StructureDefinition/alternate-codes #xD; value[x] #xD; coding S 0..* Coding Code defined by a terminology system #xD; system S 0..1 uri Identity of the terminology system Required Pattern: http://va.gov/fhir/CodeSystem/430.3 #xD; code S 0..1 code Symbol in syntax defined by the system #xD; display S 0..1 string Representation defined by the system #xD; subject S 0..1 Reference(VAPatient) Recipient(s) of goods and services #xD; recipient SC 0..1 Reference(Debt Portal Patient) Recipient of this invoice Constraints: 340-.01)" class="constraint">dpi-17-1818 #xD; date S 0..1 dateTime Invoice date / posting date #xD; issuer S 0..1 Reference(VAOrganization) Issuing Organization of Invoice #xD; account S 0..1 Reference(Debt Portal Account) Account that is being balanced #xD; Slices for lineItem 0..* BackboneElement Line items of this Invoice Slice: Unordered, Open by value:$this #xD; lineItem:va-charges S 0..1 BackboneElement Line items of this Invoice #xD; Slices for chargeItem[x] 1..1 Reference(ChargeItem), CodeableConcept Reference to ChargeItem containing details of this line item or an inline billing code Slice: Unordered, Open by type:$this #xD; chargeItem[x]:chargeItemReference S<a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( dpi-17-1834, dpi-17-2220 )">C 0..1 Reference(Debt Portal ChargeItem[charges] | Debt Portal ChargeItem[removed]) Reference to ChargeItem containing details of this line item or an inline billing code Constraints: dpi-17-1834, <span style="font-weight:bold" title="If INTEGRATED BILLING ACTION - PARENT CHARGE <> INTEGRATED BILLING ACTION - IEN then reference ChargeItemremoved based on (null)" class="constraint">dpi-17-2220 #xD; priceComponent #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: base #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Total Charge #xD; amount S 0..1 Money Monetary amount associated with this component #xD; lineItem:va-interest S 0..1 BackboneElement Line items of this Invoice #xD; Slices for chargeItem[x] 1..1 Reference(ChargeItem), CodeableConcept Reference to ChargeItem containing details of this line item or an inline billing code Slice: Unordered, Open by type:$this #xD; chargeItem[x]:chargeItemReference S 0..1 Reference(Debt Portal ChargeItem[interest]) Reference to ChargeItem containing details of this line item or an inline billing code #xD; Slices for priceComponent 0..* BackboneElement Components of total line item price Slice: Unordered, Open by value:$this #xD; priceComponent:va-marshal-fee-charged 0..1 BackboneElement Components of total line item price #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Marshal Fee Charged #xD; amount S 0..1 Money Monetary amount associated with this component #xD; priceComponent:va-court-cost-charged 0..1 BackboneElement Components of total line item price #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Court Cost Charged #xD; amount S 0..1 Money Monetary amount associated with this component #xD; priceComponent:va-interest-charged 0..1 BackboneElement Components of total line item price #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Interest Charged #xD; amount S 0..1 Money Monetary amount associated with this component #xD; priceComponent:va-admin-charged 0..1 BackboneElement Components of total line item price #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Administrative Charged #xD; amount S 0..1 Money Monetary amount associated with this component #xD; Slices for totalPriceComponent 0..* Components of Invoice total Slice: Unordered, Open by value:$this #xD; totalPriceComponent:va-orig-amt S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: informational #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Original Amount #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-curr-bal S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: base #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Current Balance #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-amend-amt S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: base #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Amended Amount #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-principal-bal S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: base #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Principal Balance #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-interest-bal S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Interest Balance #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-admin-cost-bal S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Administrative Cost Balance #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-marsh-fee S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Marshal Fee #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-court-cost S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Court Cost #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-principal-paid S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: base #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Principal Paid #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-interest-paid S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Interest Paid #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-admin-cost-paid S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Administrative Cost Paid #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-marsh-fee-paid S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Marshal Fee Paid #xD; amount S 0..1 Money Monetary amount associated with this component #xD; totalPriceComponent:va-court-cost-paid S 0..1 BackboneElement Components of Invoice total #xD; type S 1..1 code base | surcharge | deduction | discount | tax | informational Required Pattern: surcharge #xD; code #xD; text S 0..1 string Plain text representation of the concept Required Pattern: Court Cost Paid #xD; amount S 0..1 Money Monetary amount associated with this component #xD; Documentation for this format
This StructureDefinition contains the maps for VistA file ACCOUNTS RECEIVABLE (430) to Invoice.
Veterans Health Information Systems Technology and Architecture (VistA)
Invoice containing ChargeItems from an Account
Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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 it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
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 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 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.
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 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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
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).
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identifier of this Invoice, often used for reference in correspondence about this invoice or for tracking of payments.
Allows Identification of this Invoice instance.
1975: source value based on ACCOUNTS RECEIVABLE - BILL NO. (430-.01)
IB.AccountsReceivable.BillNumber IB.AccountsReceivableTCSP.BillNumber
draft | issued | balanced | cancelled | entered-in-error
This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
see mapping [VF_ARBillStatus](ConceptMap-VF-ARBillStatus.html)
1843: terminologyMaps using VF_ARBillStatus on ACCOUNTS RECEIVABLE - CURRENT STATUS > ACCOUNTS RECEIVABLE TRANS.TYPE - NAME (430-8 > 430.3-.01)
IB.AccountsReceivable.ARTransactionTypeIEN Dim.ARTransactionType.ARTransactionType
unique id for the element within a resource (for internal references)
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Alternate code/original text for this code
Indicates alternate codings and/or original text for the concept represented by the code. Codings or text provided SHALL convey equivalent meaning to the meaning of the code being extended (though with potential differences in level of detail conveyed).
Used when the FHIR specification requires a code, but the writing application wants or needs to preseve it's own underlying code, possibly for use for other applications reading the content
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).
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.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
2236: source value based on ACCOUNTS RECEIVABLE - CURRENT STATUS > ACCOUNTS RECEIVABLE TRANS.TYPE - (430-8 > 430.3-)
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
2236c: fixed value = http://va.gov/fhir/CodeSystem/430.3
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
2236a: source value based on ACCOUNTS RECEIVABLE - CURRENT STATUS > ACCOUNTS RECEIVABLE TRANS.TYPE - TRANSACTION TYPE IEN (430-8 > 430.3-.001)
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
2236b: source value based on ACCOUNTS RECEIVABLE - CURRENT STATUS > ACCOUNTS RECEIVABLE TRANS.TYPE - NAME (430-8 > 430.3-.01)
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
In case of Invoice cancellation a reason must be given (entered in error, superseded by corrected invoice etc.).
Derived Profiles may choose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.
Type of Invoice depending on domain, realm an usage (e.g. internal/external, dental, preliminary).
The individual or set of individuals receiving the goods and services billed in this invoice.
1976: reference based on ACCOUNTS RECEIVABLE - PATIENT (430-7)
The data in CDW does not support Invoice.recipient and Invoice.subject being different. It is assumed that the recipient will always be the subject and to avoid having duplicate patient references, it is recommended to use Invoice.recipient for the reference to the patient.
IB.AccountsReceivable.PatientIEN IB.AccountsReceivableComment.PatientIEN IB.AccountsReceivableDescription.PatientIEN IB.AccountsReceivableFiscalYear.PatientIEN IB.AccountsReceivableRepayDate.PatientIEN IB.AccountsReceivableTCSP.PatientIEN IB.AccountsReceivableTCSP.PatientSID
The individual or Organization responsible for balancing of this invoice.
If type is PATIENT (#2) then reference Patient based on (430-9 > 340-.01)
1818: reference based on ACCOUNTS RECEIVABLE - DEBTOR > AR DEBTOR - DEBTOR (430-9 > 340-.01) is type is PATIENT (#2)
IB.AccountsReceivable.ARDebtorIEN Dim.ARDebtor.InstitutionIEN Dim.ARDebtor.InsuranceCompanyIEN Dim.ARDebtor.PatientIEN Dim.ARDebtor.StaffIEN Dim.ARDebtor.VendorIEN
.inboundRelationship(typeCode=COMP].source[classCode<=PCPR, moodCode=EVN]
Date/time(s) of when this Invoice was posted.
The list of types may be constrained as appropriate for the type of charge item.
1977: source value based on ACCOUNTS RECEIVABLE - DATE BILL PREPARED (430-10)
IB.AccountsReceivable.BillPreparedDateTime IB.AccountsReceivableComment.BillPreparedDateTime IB.AccountsReceivableDescription.BillPreparedDateTime IB.AccountsReceivableFiscalYear.BillPreparedDateTime IB.AccountsReceivableRepayDate.BillPreparedDateTime IB.AccountsReceivableTCSP.BillPreparedDateTime
Indicates who or what performed or participated in the charged service.
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Type of involvement in creation of this Invoice
Describes the type of involvement (e.g. transcriptionist, creator etc.). If the invoice has been created automatically, the Participant may be a billing engine or another kind of device.
The device, practitioner, etc. who performed or participated in the service.
Practitioners and Devices can be associated with multiple organizations. It has to be made clear, on behalf of which Organization the services have been rendered.
2007: reference based on ACCOUNTS RECEIVABLE - SITE (430-12)
Account which is supposed to be balanced with this Invoice.
Systems posting the ChargeItems might not always be able to determine, which accounts the Items need to be places into. It is up to the potprocessing Financial System to apply internal rules to decide based on the Encounter/EpisodeOfCare/Patient/Coverage context and the type of ChargeItem, which Account is appropriate.
Each line item represents one charge for goods and services rendered. Details such as date, code and amount are found in the referenced ChargeItem resource.
Sequence in which the items appear on the invoice.
Reference to ChargeItem containing details of this line item or an inline billing code
The ChargeItem contains information such as the billing code, date, amount etc. If no further details are required for the lineItem, inline billing codes can be added using the CodeableConcept data type instead of the Reference.
The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated.
base | surcharge | deduction | discount | tax | informational
This code identifies the type of the component.
Codes indicating the kind of the price component.
A code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.
Factor used for calculating this component
The factor that has been applied on the base price for calculating this component.
There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.
Monetary amount associated with this component
The amount calculated for this component.
If INTEGRATED BILLING ACTION - PARENT CHARGE = INTEGRATED BILLING ACTION - IEN then reference ChargeItemcharges based on (null)
If INTEGRATED BILLING ACTION - PARENT CHARGE <> INTEGRATED BILLING ACTION - IEN then reference ChargeItemremoved based on (null)
1834: reference is INTEGRATED BILLING ACTION - PARENT CHARGE = INTEGRATED BILLING ACTION - IEN
INTEGRATED BILLING ACTION - AR BILL NUMBER (350-.11) = Accounts Receivable - Bill Number (430-.01)
2220: reference is INTEGRATED BILLING ACTION - PARENT CHARGE <> INTEGRATED BILLING ACTION - IEN
1840: source value based on INTEGRATED BILLING ACTION - TOTAL CHARGE (350-.07)
1999b: fixed value = Marshal Fee Charged
1999: source value based on AR TRANSACTION - MARSHAL FEE (433-25)
2000: source value based on AR TRANSACTION - COURT COST (433-26)
2001: source value based on AR TRANSACTION - INT.CHARGE (433-27)
2002b: fixed value = Administrative Charged
2002: source value based on AR TRANSACTION - ADM.CHARGE (433-28)
The total amount for the Invoice may be calculated as the sum of the line items with surcharges/deductions that apply in certain conditions. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the total price was calculated.
1828: source value based on ACCOUNTS RECEIVABLE - ORIGINAL AMOUNT (430-3)
1829: source value based on ACCOUNTS RECEIVABLE - CURRENT BALANCE (430-11)
1830: source value based on ACCOUNTS RECEIVABLE - AMENDED AMOUNT (430-35)
1831: source value based on ACCOUNTS RECEIVABLE - PRINCIPAL BALANCE (430-71)
1832: source value based on ACCOUNTS RECEIVABLE - INTEREST BALANCE (430-72)
1866b: fixed value = Administrative Cost Balance
1866: source value based on ACCOUNTS RECEIVABLE - ADMINISTRATIVE COST BALANCE (430-73)
1867: source value based on ACCOUNTS RECEIVABLE - MARSHAL FEE (430-74)
1868: source value based on ACCOUNTS RECEIVABLE - COURT COST (430-75)
1869: source value based on ACCOUNTS RECEIVABLE - TOTAL PAID PRINCIPAL (430-77)
1870: source value based on ACCOUNTS RECEIVABLE - TOTAL PAID INTEREST (430-78)
1871b: fixed value = Administrative Cost Paid
1871: source value based on ACCOUNTS RECEIVABLE - TOTAL PAID ADMINISTRATIVE COST (430-79)
1872: source value based on ACCOUNTS RECEIVABLE - TOTAL PAID MARSHAL FEE (430-79.1)
1873: source value based on ACCOUNTS RECEIVABLE - TOTAL PAID COURT COST (430-79.2)
Payment details such as banking details, period of payment, deductibles, methods of payment.
Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.
Comments made about the invoice by the issuer, subject, or other participants.
.inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST]