This page is part of the FHIR Specification (v4.3.0-snapshot1: Release 4B Snapshot #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Patient Administration Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Definition for Code System ChargeItemStatus
<?xml version="1.0" encoding="UTF-8"?> <CodeSystem xmlns="http://hl7.org/fhir"> <id value="chargeitem-status"/> <meta> <lastUpdated value="2021-12-20T14:08:35.086+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> ChargeItemStatus</h2> <div> <p> Codes identifying the lifecycle stage of a ChargeItem.</p> </div> <p> This code system http://hl7.org/fhir/chargeitem-status defines the following codes:</p> <table class="codes"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td style="white-space:nowrap">planned <a name="chargeitem-status-planned"> </a> </td> <td> Planned</td> <td> The charge item has been entered, but the charged service is not yet complete, so it shall not be billed yet but might be used in the context of pre-authorization.</td> </tr> <tr> <td style="white-space:nowrap">billable <a name="chargeitem-status-billable"> </a> </td> <td> Billable</td> <td> The charge item is ready for billing.</td> </tr> <tr> <td style="white-space:nowrap">not-billable <a name="chargeitem-status-not-billable"> </a> </td> <td> Not billable</td> <td> The charge item has been determined to be not billable (e.g. due to rules associated with the billing code).</td> </tr> <tr> <td style="white-space:nowrap">aborted <a name="chargeitem-status-aborted"> </a> </td> <td> Aborted</td> <td> The processing of the charge was aborted.</td> </tr> <tr> <td style="white-space:nowrap">billed <a name="chargeitem-status-billed"> </a> </td> <td> Billed</td> <td> The charge item has been billed (e.g. a billing engine has generated financial transactions by applying the associated ruled for the charge item to the context of the Encounter, and placed them into Claims/Invoices.</td> </tr> <tr> <td style="white-space:nowrap">entered-in-error <a name="chargeitem-status-entered-in-error"> </a> </td> <td> Entered in Error</td> <td> The charge item has been entered in error and should not be processed for billing.</td> </tr> <tr> <td style="white-space:nowrap">unknown <a name="chargeitem-status-unknown"> </a> </td> <td> Unknown</td> <td> The authoring system does not know which of the status values currently applies for this charge item Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, it's just not known which one.</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="pa"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="trial-use"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="0"/> </extension> <url value="http://hl7.org/fhir/chargeitem-status"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.4.847"/> </identifier> <version value="4.3.0-snapshot1"/> <name value="ChargeItemStatus"/> <title value="ChargeItemStatus"/> <status value="draft"/> <experimental value="false"/> <date value="2021-01-17T07:06:13+11:00"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <description value="Codes identifying the lifecycle stage of a ChargeItem."/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/chargeitem-status"/> <content value="complete"/> <concept> <code value="planned"/> <display value="Planned"/> <definition value="The charge item has been entered, but the charged service is not yet complete, so it shall not be billed yet but might be used in the context of pre-authorization."/> </concept> <concept> <code value="billable"/> <display value="Billable"/> <definition value="The charge item is ready for billing."/> </concept> <concept> <code value="not-billable"/> <display value="Not billable"/> <definition value="The charge item has been determined to be not billable (e.g. due to rules associated with the billing code)."/> </concept> <concept> <code value="aborted"/> <display value="Aborted"/> <definition value="The processing of the charge was aborted."/> </concept> <concept> <code value="billed"/> <display value="Billed"/> <definition value="The charge item has been billed (e.g. a billing engine has generated financial transactions by applying the associated ruled for the charge item to the context of the Encounter, and placed them into Claims/Invoices."/> </concept> <concept> <code value="entered-in-error"/> <display value="Entered in Error"/> <definition value="The charge item has been entered in error and should not be processed for billing."/> </concept> <concept> <code value="unknown"/> <display value="Unknown"/> <definition value="The authoring system does not know which of the status values currently applies for this charge item Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, it's just not known which one."/> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.