HL7 Terminology (THO)
5.3.0 - Publication
This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v3-ActRelationshipAccounting | Version: 2.0.0 | |||
Active as of 2014-03-26 | Computable Name: ActRelationshipAccounting | |||
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.14900 |
Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
where concept is-a _ActRelationshipAccountingThis value set excludes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
Code | Display | Definition |
_ActRelationshipAccounting | ActRelationshipAccounting | Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. |
This value set contains 4 concepts
Expansion based on codesystem ActRelationshipType v3.1.0 (CodeSystem)
Code | System | Display | Definition |
_ActRelationshipCostTracking | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | ActRelationshipCostTracking | Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. |
CHRG | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has charge | A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. The financial transaction will define the charge (bill) for delivery or performance of the service. Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. |
COST | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has cost | A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. The financial transaction will define the cost of delivery or performance of the service. Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. |
_ActRelationshipPosting | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | ActRelationshipPosting | Expresses values for describing the relationship between a FinancialTransaction and an Account. |
CREDIT | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has credit | A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance. |
DEBIT | http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType | has debit | A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |
History
Date | Action | Custodian | Author | Comment |
2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | 2014T1_2014-03-26_001283 (RIM release ID) | Vocabulary (Woody Beeler) (no record of original request) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |