Release 4B 5 Ballot

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-ballot: R5 Ballot - STU see ballot notes ). 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

Operation-chargeitemdefinition-apply

Example OperationDefinition/ChargeItemDefinition-apply (Narrative)

Patient Administration Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format.

Apply OPERATION: Apply The official URL for

Note that this operation is the formal definition is: http://hl7.org/fhir/OperationDefinition/ChargeItemDefinition-apply The for the apply operation applies a definition in a specific context as an OperationDefinition on ChargeItemDefinition. See the Operation documentation

URL: [base]/ChargeItemDefinition/[id]/$apply

Parameters

Use Name Cardinality Type Binding Documentation
IN chargeItem 1..1 Reference

The ChargeItem on which the definition is to ba applies

IN account 0..1 Reference

The account in context, if any

OUT return 1..1 Any Resource

The resource that is the result of applying the definition

The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource. If the ActivityDefinition ChargetItemDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. For a more detailed description, refer to the ActivityDefinition ChargetItemDefinition resource

 

 

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.