HL7 Terminology
2.0.0 - Publication
This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/v3-ActInvoiceRootGroupCode |
Version: | 2.0.0 |
Name: | ActInvoiceRootGroupCode |
Status: | Active as of 2014-03-26 |
Definition: | Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice. |
OID: | 2.16.840.1.113883.1.11.19399 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
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-ActCode
where concept is-a _ActInvoiceRootGroupCodeThis value set excludes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-ActCode
Code | Display | Definition |
_ActInvoiceRootGroupCode | ActInvoiceRootGroupCode | Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements. Codes from this domain reflect the type of Invoice such as Pharmacy Dispense, Clinical Service and Clinical Product. The domain is only specified for the root (top level) invoice element group for an Invoice. |
This value set contains 15 concepts
Expansion based on ActCode v2.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/v3-ActCode
Code | Display | Definition |
CPINV | clinical product invoice | Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s). For example, a crutch or a wheelchair. |
CP | clinical product invoice | Clinical product invoice where the Invoice Grouping contains one or more billable item and is supported by clinical product(s). For example, a crutch or a wheelchair. |
CSINV | clinical service invoice | Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. \[1\] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). \[2\] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services. The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together. For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. \[3\] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time. For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month). |
CS | clinical service invoice | Clinical Services Invoice which can be used to describe a single service, multiple services or repeated services. \[1\] Single Clinical services invoice where the Invoice Grouping contains one billable item and is supported by one clinical service. For example, a single service for an office visit or simple clinical procedure (e.g. knee mobilization). \[2\] Multiple Clinical services invoice where the Invoice Grouping contains more than one billable item, supported by one or more clinical services. The services can be distinct and over multiple dates, but for the same patient. This type of invoice includes a series of treatments which must be adjudicated together. For example, an adjustment and ultrasound for a chiropractic session where fees are associated for each of the services and adjudicated (invoiced) together. \[3\] Repeated Clinical services invoice where the Invoice Grouping contains one or more billable item, supported by the same clinical service repeated over a period of time. For example, the same Chiropractic adjustment (service or treatment) delivered on 3 separate occasions over a period of time at the discretion of the provider (e.g. month). |
CSPINV | clinical service and product | A clinical Invoice Grouping consisting of one or more services and one or more product. Billing for these service(s) and product(s) are supported by multiple clinical billable events (acts). All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. For example , a brace (product) invoiced together with the fitting (service). |
FININV | financial invoice | Invoice Grouping without clinical justification. These will not require identification of participants and associations from a clinical context such as patient and provider. Examples are interest charges and mileage. |
OHSINV | oral health service | A clinical Invoice Grouping consisting of one or more oral health services. Billing for these service(s) are supported by multiple clinical billable events (acts). All items in the Invoice Grouping must be adjudicated together to be acceptable to the Adjudicator. |
PAINV | preferred accommodation invoice | HealthCare facility preferred accommodation invoice. |
PA | preferred accommodation invoice | HealthCare facility preferred accommodation invoice. |
RXCINV | Rx compound invoice | Pharmacy dispense invoice for a compound. |
RXC | Rx compound invoice | Pharmacy dispense invoice for a compound. |
RXDINV | Rx dispense invoice | Pharmacy dispense invoice not involving a compound |
RXD | Rx dispense invoice | Pharmacy dispense invoice not involving a compound |
SBFINV | sessional or block fee invoice | Clinical services invoice where the Invoice Group contains one billable item for multiple clinical services in one or more sessions. |
VRXINV | vision dispense invoice | Vision dispense invoice for up to 2 lens (left and right), frame and optional discount. Eye exams are invoiced as a clinical service invoice. |
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 |
Source | 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 | Author | Custodian | Comment |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | Vocabulary (Woody Beeler) (no record of original request) | 2014T1_2014-03-26_001283 (RIM release ID) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |