Chargeitemdefinition-device-example

FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example ChargeItemDefinition/device (Narrative)

Patient Administration Work Group

Maturity Level: N/A

Standards Status: Informative

Compartments: No defined compartments

This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile ChargeItemDefinition.

Generated Narrative: ChargeItemDefinition device

StructureDefinition Work Group: pa

url: http://sap.org/ChargeItemDefinition/device-123

identifier: Uniform Resource Identifier (URI)/urn:oid:2.16.840.1.113883.4.642.29.2

name: CustomDevice345675

title: Financial details for custom made device (345675)

status: active

date: 2023-02

publisher: HL7 International / Patient Administration

contact: http://www.hl7.org/Special/committees/pafm

description:

Financial details for custom made device

UseContexts

Code

Value[x]

UsageContextType venue: Clinical Venue

Outpatient environment

UsageContextType age: Age Range

>18 yrs (Details: UCUM codea = 'a')

jurisdiction: World

instance: Device: identifier = http://goodcare.org/devices/id#345675

applicability
Conditions

- Description Language Expression

* Verify ChargeItem pertains to Device 12345 text/fhirpath %context.service.suppliedItem.reference='Device/12345'

propertyGroup
priceComponent
type: base
code: Verkaufspreis (netto)
Amounts

- Value Currency

* 67.44 EUR

propertyGroup
applicability
Conditions

- Description Language Expression

* Gültigkeit Steuersatz text/fhirpath %context.occurenceDateTime > '2018-04-01'
PriceComponents

- Type Code Factor

* tax Mehrwersteuersatz 1.19

propertyGroup
applicability
Conditions

- Description Language Expression

* Gültigkeit Steuersatz text/fhirpath %context.occurenceDateTime <= '2018-04-01'
PriceComponents

- Type Code Factor

* tax Mehrwersteuersatz 1.07

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.