Canonical URL: http://fhir.de/StructureDefinition/chargeitem-ebm/0.2
| ChargeItem | 0..* | ChargeItem | Short description Item containing charge code(s) associated with the provision of healthcare provider products DefinitionThe resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation.
| |
| identifier | Σ | 0..1 | Identifier | Short description Business Identifier for item DefinitionIdentifiers assigned to this event performer or other systems. Allows identification of the charge Item as it is known by various participating systems and in a way that remains consistent across servers.
|
| definition | 0..* | uri | Short description Defining information about the code of this charge item DefinitionReferences the source of pricing information, rules of application for the code this ChargeItem uses. Target Resource is yet to be defined as a container that holds information about list prices and rules applicable to the charge item code. Once defined, change type back to Reference(Definition Type).
| |
| status | S Σ ?! | 1..1 | codeBinding | Short description planned | billable | not-billable | aborted | billed | entered-in-error | unknown DefinitionThe current state of the ChargeItem. Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. This element is labeled as a modifier because the status contains the code entered-in-error that marks the charge item as not currently valid.
|
| partOf | 0..* | Reference(ChargeItem) | Short description Part of referenced ChargeItem Alternate namescontainer DefinitionChargeItems can be grouped to larger ChargeItems covering the whole set. E.g. Drug administration as part of a procedure, procedure as part of observation, etc. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |
| code | S Σ | 1..1 | CodeableConcept | Short description A code that identifies the charge, like a billing code Alternate namestype DefinitionA code that identifies the charge, like a billing code. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. chargeitem-billingcodes (example) Constraints
|
| coding | Σ | 0..* | CodingBinding | Short description Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. 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.
|
| system | Σ | 0..1 | uri | Short description Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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 de-reference to some definition that establish the system clearly and unambiguously.
|
| version | Σ | 0..1 | string | Short description Version of the system - if relevant DefinitionThe 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.
|
| code | Σ | 0..1 | code | Short description Symbol in syntax defined by the system DefinitionA 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. Note that FHIR strings may not exceed 1MB in size
|
| display | Σ | 0..1 | string | Short description Representation defined by the system DefinitionA 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. Note that FHIR strings may not exceed 1MB in size
|
| userSelected | Σ | 0..1 | boolean | Short description If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). 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. 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.
|
| text | Σ | 0..1 | string | Short description Plain text representation of the concept DefinitionA 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. 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. Very often the text is the same as a displayName of one of the codings.
|
| subject | S Σ | 1..1 | Reference(Patient | Group) | Short description Individual service was done for/to Alternate namespatient DefinitionThe individual or set of individuals the action is being or was performed on. Links the event to the Patient context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
| context | Σ | 0..1 | Reference(Encounter | EpisodeOfCare) | Short description Encounter / Episode associated with event Alternate namesencounter DefinitionThe encounter or episode of care that establishes the context for this event. Links the request to the Encounter context. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) Constraints
|
| occurrenceDateTime | S Σ | 1..1 | dateTime | Short description When the charged service was applied Alternate namestiming DefinitionDate/time(s) or duration when the charged service was applied. The list of types may be constrained as appropriate for the type of charge item.
|
| participant | 0..* | BackboneElement | Short description Who performed charged service DefinitionIndicates who or what performed or participated in the charged service.
| |
| role | 0..1 | CodeableConcept | Short description What type of performance was done DefinitionDescribes the type of performance or participation(e.g. primary surgeon, anaesthesiologiest, etc.). Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
| |
| actor | 1..1 | Reference(Practitioner | Organization | Patient | Device | RelatedPerson) | Short description Individual who was performing DefinitionThe device, practitioner, etc. who performed or participated in the service. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | Organization | Patient | Device | RelatedPerson) Constraints
| |
| performingOrganization | 0..1 | Reference(Organization) | Short description Organization providing the charged sevice DefinitionThe organization requesting 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.
| |
| requestingOrganization | 0..1 | Reference(Organization) | Short description Organization requesting the charged service DefinitionThe organization performing the service. The rendered Service may not be associated with a Request. It has to be made clear, ob which Organization's Request, the services have been rendered. (In many cases, this may just be the Department associated with the Encounter.location).
| |
| quantity | S Σ | 1..1 | Quantity | Short description Quantity of which the charge item has been serviced DefinitionQuantity of which the charge item has been serviced. In many cases this may just be a value, if the underlying units are implicit in the definition of the charge item code.
|
| value | Σ | 1..1 | decimal | Short description Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
|
| comparator | Σ ?! | 0..1 | codeBinding | Short description < | <= | >= | > - how to understand the value DefinitionHow the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value. quantity-comparator (required) Constraints
|
| unit | Σ | 0..1 | string | Short description Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings may not exceed 1MB in size
|
| system | Σ | 0..1 | uri | Short description System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
| code | Σ | 0..1 | code | Short description Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
|
| bodysite | Σ | 0..* | CodeableConcept | Short description Anatomical location, if relevant DefinitionThe anatomical location where the related service has been applied. Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both.
|
| factorOverride | 0..1 | decimal | Short description Factor overriding the associated rules DefinitionFactor overriding the factor determined by the rules associated with the code. There is no reason to carry the factor in the instance of a ChargeItem unless special circumstances require a manual override. The factors are usually defined by a set of rules 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 overriden.
| |
| priceOverride | 0..1 | Money | Short description Price overriding the associated rules DefinitionTotal price of the charge overriding the list price associated with the code. 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 overriden.
| |
| overrideReason | 0..1 | string | Short description Reason for overriding the list price/factor DefinitionIf the list price or the rule based factor associated with the code is overridden, this attribute can capture a text to indicate the reason for this action. Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.
| |
| enterer | Σ | 0..1 | Reference(Practitioner | Organization | Patient | Device | RelatedPerson) | Short description Individual who was entering DefinitionThe device, practitioner, etc. who entered the charge item. The enterer is also te person considered responsible for factor/priceOverrides if applicable. Reference(Practitioner | Organization | Patient | Device | RelatedPerson) Constraints
|
| enteredDate | Σ | 0..1 | dateTime | Short description Date the charge item was entered DefinitionDate the charge item was entered. The actual date when the service associated with the charge has been rendered is captured in occurrence[x].
|
| reason | 0..* | CodeableConcept | Short description Why was the charged service rendered? DefinitionDescribes why the event occurred in coded or textual form. If the application of the charge item requires a reason to be given, it can be captured here. Textual reasons can be captured using reasonCode.text.
| |
| service | 0..* | Reference(DiagnosticReport | ImagingStudy | Immunization | MedicationAdministration | MedicationDispense | Observation | Procedure | SupplyDelivery) | Short description Which rendered service is being charged? DefinitionIndicated the rendered service that caused this charge. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(DiagnosticReport | ImagingStudy | Immunization | MedicationAdministration | MedicationDispense | Observation | Procedure | SupplyDelivery) Constraints
| |
| account | Σ | 0..* | Reference(Account) | Short description Account to place this charge DefinitionAccount into which this ChargeItems belongs. Systems posting the ChargeItems may 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.
|
| note | 0..* | Annotation | Short description Comments made about the ChargeItem DefinitionComments made about the event by the performer, subject or other participants. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
| supportingInformation | 0..* | Reference(Resource) | Short description Further information supporting the this charge DefinitionFurther information supporting the this charge. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
<ChargeItem> <meta> <profile value="http://fhir.de/StructureDefinition/chargeitem-ebm/0.2" /> </meta> <status value="billable" /> <code> <coding> <system value="http://fhir.de/CodeSystem/kbv/ebm" /> <version value="2017-4" /> <code value="31600" /> <display value="Postoperative Behandlung durch den Hausarzt" /> </coding> </code> <subject> <reference value="Patient/Example-patient-de-basis-address-1" /> </subject> <occurrenceDateTime value="2017-11-07" /> <quantity> <value value="1" /> </quantity> </ChargeItem>
{ "resourceType":"ChargeItem", "meta":{ "profile": [ "http://fhir.de/StructureDefinition/chargeitem-ebm/0.2" ] }, "status":"billable", "code":{ "coding": [ { "system":"http://fhir.de/CodeSystem/kbv/ebm", "version":"2017-4", "code":"31600", "display":"Postoperative Behandlung durch den Hausarzt" } ] }, "subject":{ "reference":"Patient/Example-patient-de-basis-address-1" }, "occurrenceDateTime":"2017-11-07", "quantity":{ "value":"1" } }
Powered by SIMPLIFIER.NET