Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR STU3 - Downloaded Version null See the Directory of published versions

Extension: ExtensionSubstanceAmount_AmountType

Official URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-SubstanceAmount.amountType Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: ExtensionSubstanceAmount_AmountType

R4: SubstanceAmount.amountType (new:CodeableConcept)

This extension is part of the cross-version definitions generated to enable use of the element SubstanceAmount.amountType as defined in FHIR R4 in FHIR STU3.

The source element is defined as: SubstanceAmount.amountType 0..1 CodeableConcept

Following are the generation technical comments: Element SubstanceAmount.amountType is not mapped to FHIR STU3, since FHIR R4 SubstanceAmount is not mapped. Element SubstanceAmount.amountType has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Context of Use

    This extension may be used on the following element(s)

Usage info

Usages:

  • This Extension is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Extension Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Extension

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..1 Extension R4: Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements (new)
... url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-SubstanceAmount.amountType"
... value[x] 0..1 CodeableConcept Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..1 Extension R4: Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements (new)
... id 0..1 string xml:id (or equivalent in JSON)
... extension 0..* Extension Additional Content defined by implementations
Slice: Unordered, Open by value:url
... url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-SubstanceAmount.amountType"

doco Documentation for this format

This structure is derived from Extension

Summary

Simple Extension with the type CodeableConcept: R4: SubstanceAmount.amountType (new:CodeableConcept)

Maturity: 0

Differential View

This structure is derived from Extension

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..1 Extension R4: Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements (new)
... url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-SubstanceAmount.amountType"
... value[x] 0..1 CodeableConcept Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..1 Extension R4: Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements (new)
... id 0..1 string xml:id (or equivalent in JSON)
... extension 0..* Extension Additional Content defined by implementations
Slice: Unordered, Open by value:url
... url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-SubstanceAmount.amountType"

doco Documentation for this format

This structure is derived from Extension

Summary

Simple Extension with the type CodeableConcept: R4: SubstanceAmount.amountType (new:CodeableConcept)

Maturity: 0

 

Other representations of profile: CSV, Excel, Schematron

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() | (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()