Release 5 Preview #3

This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). 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

Codesystem-chargeitem-status.json

Patient Administration Work GroupMaturity Level: N/AStandards Status: Informative

Raw JSON (canonical form + also see JSON Format Specification)

Definition for Code System ChargeItemStatus

{
  "resourceType" : "CodeSystem",
  "id" : "chargeitem-status",
  "meta" : {
    "lastUpdated" : "2020-08-20T17:41:31.970+10:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "pa"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 0
  }],
  "url" : "http://hl7.org/fhir/chargeitem-status",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.1.847"
  }],
  "version" : "4.5.0",
  "name" : "ChargeItemStatus",
  "title" : "ChargeItemStatus",
  "status" : "draft",
  "experimental" : false,
  "date" : "2020-08-20T17:41:31+10:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "Codes identifying the lifecycle stage of a ChargeItem.",
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/chargeitem-status",
  "content" : "complete",
  "concept" : [{
    "code" : "planned",
    "display" : "Planned",
    "definition" : "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."
  },
  {
    "code" : "billable",
    "display" : "Billable",
    "definition" : "The charge item is ready for billing."
  },
  {
    "code" : "not-billable",
    "display" : "Not billable",
    "definition" : "The charge item has been determined to be not billable (e.g. due to rules associated with the billing code)."
  },
  {
    "code" : "aborted",
    "display" : "Aborted",
    "definition" : "The processing of the charge was aborted."
  },
  {
    "code" : "billed",
    "display" : "Billed",
    "definition" : "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."
  },
  {
    "code" : "entered-in-error",
    "display" : "Entered in Error",
    "definition" : "The charge item has been entered in error and should not be processed for billing."
  },
  {
    "code" : "unknown",
    "display" : "Unknown",
    "definition" : "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."
  }]
}

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.