Generated Narrative: StructureDefinition ext-R5-SubstanceDefinition.characterization Name Flags Card. Type Description & Constraints Extension 0..* Extension(4.3.0) R5: General specifications for this substance (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:technique 0..1 Extension R5: The method used to find the characterization e.g. HPLC (new) #xD; url 1..1 uri "technique" #xD; value[x] 0..1 CodeableConcept The method used to find the characterization e.g. HPLC Binding: StructureTechnique (example): The method used to elucidate the characterization of the drug substance. #xD; extension:form 0..1 Extension R5: Describes the nature of the chemical entity and explains, for instance, whether this is a base or a salt form (new) #xD; url 1..1 uri "form" #xD; value[x] 0..1 CodeableConcept Describes the nature of the chemical entity and explains, for instance, whether this is a base or a salt form Binding: R5SubstanceFormForR4B (0.1.0) (example) #xD; extension:description 0..1 Extension R5: The description or justification in support of the interpretation of the data file (new) #xD; url 1..1 uri "description" #xD; value[x] 0..1 markdown The description or justification in support of the interpretation of the data file #xD; extension:file 0..* Extension R5: The data produced by the analytical instrument or a pictorial representation of that data. Examples: a JCAMP, JDX, or ADX file, or a chromatogram or spectrum analysis (new) #xD; url 1..1 uri "file" #xD; value[x] 0..1 Attachment The data produced by the analytical instrument or a pictorial representation of that data. Examples: a JCAMP, JDX, or ADX file, or a chromatogram or spectrum analysis #xD; url 1..1 uri "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubstanceDefinition.characterization" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R5: General specifications for this substance (new)
R5: `SubstanceDefinition.characterization` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `SubstanceDefinition.characterization` as defined in FHIR R5 in FHIR R4B. The source element is defined as: `SubstanceDefinition.characterization` 0..* `BackboneElement` Following are the generation technical comments: Element `SubstanceDefinition.characterization` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `SubstanceDefinition.characterization` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children unless an empty Parameters resource
hasValue() or (children().count() > id.count()) or $this is Parameters
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
R5: The method used to find the characterization e.g. HPLC (new)
R5: `SubstanceDefinition.characterization.technique` (new:CodeableConcept)
Element `SubstanceDefinition.characterization.technique` is part of an existing definition because parent element `SubstanceDefinition.characterization` requires a cross-version extension. Element `SubstanceDefinition.characterization.technique` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization.technique` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
The method used to find the characterization e.g. HPLC
The method used to elucidate the characterization of the drug substance. Example: HPLC.
The method used to elucidate the characterization of the drug substance.
R5: Describes the nature of the chemical entity and explains, for instance, whether this is a base or a salt form (new)
R5: `SubstanceDefinition.characterization.form` (new:CodeableConcept)
Element `SubstanceDefinition.characterization.form` is part of an existing definition because parent element `SubstanceDefinition.characterization` requires a cross-version extension. Element `SubstanceDefinition.characterization.form` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization.form` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Describes the nature of the chemical entity and explains, for instance, whether this is a base or a salt form
Describes the nature of the chemical entity and explains, for instance, whether this is a base or a salt form.
R5: The description or justification in support of the interpretation of the data file (new)
R5: `SubstanceDefinition.characterization.description` (new:markdown)
Element `SubstanceDefinition.characterization.description` is part of an existing definition because parent element `SubstanceDefinition.characterization` requires a cross-version extension. Element `SubstanceDefinition.characterization.description` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization.description` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The description or justification in support of the interpretation of the data file
The description or justification in support of the interpretation of the data file.
R5: The data produced by the analytical instrument or a pictorial representation of that data. Examples: a JCAMP, JDX, or ADX file, or a chromatogram or spectrum analysis (new)
R5: `SubstanceDefinition.characterization.file` (new:Attachment)
Element `SubstanceDefinition.characterization.file` is part of an existing definition because parent element `SubstanceDefinition.characterization` requires a cross-version extension. Element `SubstanceDefinition.characterization.file` has a context of SubstanceDefinition based on following the parent source element upwards and mapping to `SubstanceDefinition`. Element `SubstanceDefinition.characterization.file` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The data produced by the analytical instrument or a pictorial representation of that data. Examples: a JCAMP, JDX, or ADX file, or a chromatogram or spectrum analysis
The data produced by the analytical instrument or a pictorial representation of that data. Examples: a JCAMP, JDX, or ADX file, or a chromatogram or spectrum analysis.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4B/extensibility.html) for a list).