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 GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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

Resource ChargeItemDefinition "device"

StructureDefinition Work Group: pa

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

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:

description: Financial details for custom made device

UseContexts

-CodeValue[x]
*Clinical Venue (Details: http://terminology.hl7.org/CodeSystem/usage-context-type code venue = 'Clinical Venue', stated as 'null')Outpatient environment (SNOMED CT#440655000)
*Age Range (Details: http://terminology.hl7.org/CodeSystem/usage-context-type code age = 'Age Range', stated as 'null')>18 yrs (Details: UCUM code a = 'a')

jurisdiction: World (m49.htm#001)

instance: Device/example

applicability

Conditions

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

propertyGroup

priceComponent

type: base

code: Verkaufspreis (netto) (billing-attributes#VK)

amount

€67.44 (EUR)

propertyGroup

applicability

condition

%context.occurenceDateTime > '2018-04-01'("Gültigkeit Steuersatz")

PriceComponents

-TypeCodeFactor
*taxMehrwersteuersatz (billing-attributes#MWST)1.19

propertyGroup

applicability

condition

%context.occurenceDateTime <= '2018-04-01'("Gültigkeit Steuersatz")

PriceComponents

-TypeCodeFactor
*taxMehrwersteuersatz (billing-attributes#MWST)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.