Forge

https://docs.fire.ly/projects/Forge/
Admin
Forge is a user-friendly graphical editor for creating and managing FHIR Conformance Resources...
Tokens:5,894
Snippets:59
Trust Score:9
Update:1 year ago
Show doc for...
Tokens:
Raw
### Wildcard Matching Examples

Source: https://docs.fire.ly/projects/Forge/features/IntegrationwithSimplifier

Demonstrates various uses of wildcards for matching files and directories based on their names and locations.

```pattern
*.txt
*.*
*
.*
*word*
readme.*
styles/*.css
scripts/*/*
images*/*
```

--------------------------------

### Forge Proxy Whitelisting IPs

Source: https://docs.fire.ly/projects/Forge/_sources/InstallingForge

This snippet lists the IP addresses that need to be whitelisted by an administrator to allow Forge installation and usage behind a proxy server. It specifies the IPs for simplifier.net and downloads.simplifier.net.

```text
simplifier.net              IP 40.68.205.178
downloads.simplifier.net    IP 40.114.243.70 
```

--------------------------------

### Directory Depth Matching Examples

Source: https://docs.fire.ly/projects/Forge/features/IntegrationwithSimplifier

Illustrates patterns for matching files across arbitrary directory depths, including specific subdirectories and all subdirectories.

```pattern
**/*
dir/
dir/**/*
```

--------------------------------

### Launching Forge STU3 via Command Line

Source: https://docs.fire.ly/projects/Forge/LaunchingForge

Demonstrates how to launch the Forge application for STU3 using the dotnet executable and the specific DLL. This method requires navigating to the application's installation folder.

```batch
"C:\Program Files\dotnet\dotnet.exe" Forge.UI-R3.dll
```

--------------------------------

### Include File Patterns

Source: https://docs.fire.ly/projects/Forge/features/IntegrationwithSimplifier

Examples of patterns used to include specific files or file types during synchronization. Patterns starting with a file name or wildcard are treated as inclusions.

```pattern
FHIR/IG/*
*.xml
```

--------------------------------

### Whitelisting IP Addresses for Proxy Installation

Source: https://docs.fire.ly/projects/Forge/InstallingForge

This snippet lists the IP addresses that need to be whitelisted by a network administrator to allow Forge to connect behind a proxy server. It specifies the domains and their corresponding IP addresses for the simplifier.net service.

```text
simplifier.net              IP 40.68.205.178
downloads.simplifier.net    IP 40.114.243.70
```

--------------------------------

### Forge STU3 Start Menu Shortcut Location

Source: https://docs.fire.ly/projects/Forge/LaunchingForge

Provides the default path to the `.appref-ms` shortcut for Forge STU3 in the Windows Start Menu. This path is used to launch Forge indirectly from code.

```text
%APPDATA%\Microsoft\Windows\Start Menu\Programs\Firely\Firely FHIR Tools\Forge for HL7 FHIR STU3.appref-ms
```

--------------------------------

### Exclude File Patterns

Source: https://docs.fire.ly/projects/Forge/features/IntegrationwithSimplifier

Examples of patterns used to exclude specific files or file types during synchronization. Patterns starting with '!' are treated as exclusions.

```pattern
!FHIR/*.img
!*.cs
!FHIR/examples/*
```

--------------------------------

### R4B Upgrade Wizard Log Example

Source: https://docs.fire.ly/projects/Forge/features/R4BUpgradeWizard

This log snippet demonstrates the output of the R4B Upgrade Wizard after processing FHIR project files. It shows version updates and minor changes detected during the upgrade process for various resource definitions.

```text
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbaseObservationLab.StructureDefinition.xml
    VersionUpdated
        4.0.1 > 4.3.0
    MinorChanges
        Observation.subject > New target types available for type reference: Organization, Procedure, Practitioner, Medication, Substance
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbaseOrganization.xml
    VersionUpdated
            4.0.1 > 4.3.0
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbasePatient.StructureDefinition.xml
    VersionUpdated
            4.0.1 > 4.3.0
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbasePractitioner.StructureDefinition.xml
    VersionUpdated
            4.0.1 > 4.3.0
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMECoreSmokingStatusProfile.xml
    VersionUpdated
            4.0.1 > 4.3.0

```

--------------------------------

### Forge Upload Ignore Patterns (.simplifierupload)

Source: https://docs.fire.ly/projects/Forge/_sources/features/IntegrationwithSimplifier

Specifies files and folders to be ignored during Forge uploads. Lines starting with '#' are comments, blank lines are separators. Patterns starting with '*' include files, and patterns starting with '!' exclude files. By default, if inclusion patterns exist, all non-matching files are excluded.

```plaintext
# This is a comment

# Include all .xml files
*.xml

# Exclude all .img files in FHIR directory
!FHIR/*.img

# Include all files in FHIR/IG directory
FHIR/IG/*

# Include all files with .txt extension
*.txt

# Exclude all .cs files
!*.cs

# Exclude all files in FHIR/examples directory
!FHIR/examples/*
```

--------------------------------

### Element ID Scheme Example

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Illustrates the FHIR-defined scheme for generating element IDs based on element paths and slice names. This is used in Forge for managing element identifiers.

```text
For example, "Patient.identifier:SSN.system"
```

--------------------------------

### Slice Name Validation Rules in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Verifies correct usage of forward slashes in slice names, allowing them only for reslices and not at the start, end, or repeating. It also checks if the base of reslices matches the parent slice name and accepts '@default' for unsticed instance data.

```regex
Verify correct use of forward slashes; only valid for reslices; may not occur at start, end or repeating
```

```regex
For reslices, verify that the base (everything before the last ‘/’ character) matches the parent slice name
```

```regex
Accept special name “@default”, to indicate the default slice
```

--------------------------------

### Launching Forge with Documents via Command Line

Source: https://docs.fire.ly/projects/Forge/LaunchingForge

Illustrates how to launch Forge and automatically open one or more specified files using command line arguments. The file paths must be fully qualified absolute paths.

```batch
"C:\Program Files\dotnet\dotnet.exe" Forge.UI-R3.dll [filePath] [filePath] [...]
```

--------------------------------

### Execute Forge with Command Line Arguments

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Allows users to specify file paths directly on the command line when launching Forge. Forge will then attempt to open each specified file upon startup. File paths with spaces should be enclosed in quotes.

```shell
Forge.exe "path/to/file1.json" "path/to/another file.xml"
```

--------------------------------

### ImplementationGuide Resource Updates in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Details improvements to the ImplementationGuide resource editing in Forge, including support for re-ordering package resources, automatic synchronization of resource names, and editing of dependency, contact, and page components.

```text
Support re-ordering of ImplementationGuide package resources
Automatically synchronize ImplementationGuide.package.resource.name property with name of the associated target resource.
Support for editing ImplementationGuide.dependency components
Support for editing ImplementationGuide.contact components
Basic support for editing ImplementationGuide.page components
```

--------------------------------

### Forge STU3 Application Shortcut Content

Source: https://docs.fire.ly/projects/Forge/LaunchingForge

Shows the content of an `.appref-ms` shortcut file for Forge STU3. This can be used to create or generate a shortcut in a known location.

```text
http://downloads.simplifier.net/forge/stu3/Forge-R3.application#Forge-R3.application, Culture=neutral, PublicKeyToken=ac5f0d017c71eb2e, processorArchitecture=msil
```

--------------------------------

### Specify File Paths via Command Line Arguments

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Allows users to specify one or more file paths as command-line arguments when launching Forge. The application will attempt to open each specified file.

```bash
Forge.exe [file] [file] [file] ...
```

--------------------------------

### Forge Executable DLLs for Different Versions

Source: https://docs.fire.ly/projects/Forge/LaunchingForge

Lists the main DLL files for Forge corresponding to different FHIR versions (STU3, R4, R4B, R5). These are used to identify the correct executable for launching Forge.

```text
STU3: Forge.UI-R3.dll
R4  : Forge.UI-R4.dll
R4B : Forge.UI-R4B.dll
R5  : Forge.UI-R5.dll
```

--------------------------------

### Handling Complex Extensions in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

This snippet describes how Forge manages complex extensions, including the visibility of Extension.url and Extension.value[x] elements. It details the 'Add' and 'Extend' toolbar commands for managing extension elements.

```text
The Extension.url child element is hidden in the UI and automatically generated behind the scenes.
The Extension.value[x] child element is only visible for simple extension elements that do not contain nested child extension elements. Forge automatically hides the value[x] element when you add a complex extension element to the same parent. If you remove all child extension elements from a complex extension element, the value[x] child element becomes visible again.

Toolbar commands:
  * Add => Add extension element; applies to complex extension root element and custom extension child elements
  * Extend => Extend selected element; applies to standard value[x] and (hidden) url child elements
```

--------------------------------

### Forge Type Initialization for Reference Types

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Correctly initializes type profiles for Forge. For value types, it assigns the compatible profile URL to type.profile. For resource references, it assigns the URL to type.targetProfile, fixing an issue where type.profile was incorrectly used.

```json
Value types: { Code = "<type>", Profile = "<url>" }
```

```json
Resource references: { Code = Reference, TargetProfile = "<url>"}
```

--------------------------------

### Integer Type Handling

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Demonstrates precise handling and serialization of specialized integer types (Integer, UnsignedInt, PositiveInt). It includes sanitizing input and managing value constraints.

```text
More precise handling and serialization of specialized integer types: Integer | UnsignedInt | PositiveInt
Sanitize input, (dis)allow negative values
```

--------------------------------

### Create New Extension Shortcut

Source: https://docs.fire.ly/projects/Forge/features/DefineExtensions

This shortcut allows for the quick creation of a new extension, typically used for string or markdown properties. It provides a streamlined way to add basic extensions.

```Forge
Ctrl+E
```

--------------------------------

### Display Package Versions Descending

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

The Package Manager now displays available versions for each package in a dropdown combobox, sorted in descending order with the latest version at the top. This provides users with an immediate view of the most recent package versions.

```text
The package versions are now sorted in descending order, with the highest (latest) version on top.
```

--------------------------------

### File Globbing Patterns for Matching Files and Directories

Source: https://docs.fire.ly/projects/Forge/_sources/features/IntegrationwithSimplifier

Demonstrates various globbing patterns for matching files and directories. Supports exact names, wildcards like '*' for zero or more characters (excluding separators), and '**/' for arbitrary directory depth.

```plaintext
# Exact file name
some-file.txt
path/to/file.txt

# Wildcards
*.txt         # All files with .txt extension
*.*           # All files with an extension
*             # All files in top-level directory
.*            # File names beginning with '.'
*word*        # All files with 'word' in the filename
readme.*      # All files named 'readme' with any extension
styles/*.css  # All .css files in the 'styles/' directory
scripts/*/*   # All files in 'scripts/' or one level of subdirectory
images*/*     # All files in a folder starting with 'images'

# Arbitrary directory depth
**/*          # All files in any subdirectory
dir/          # All files in any subdirectory under 'dir/'
dir/**/*      # All files in any subdirectory under 'dir/'
```

--------------------------------

### Handle Copy to Clipboard Exceptions

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Addresses an issue where copying validation messages to the clipboard could cause application freezes or crashes, possibly due to clipboard unavailability. Forge now includes exception handling for these scenarios to improve stability.

```text
Forge now catches unexpected exceptions while copying.
```

--------------------------------

### Date/Time Type Handling

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Shows the improved handling and serialization of specialized date/time types (Instant, DateTime, Date, Time) according to FHIR rules. It also details UI elements like DatePicker and TextBox for input.

```text
More precise handling and serialization of specialized date/time types: Instant | DateTime | Date | Time
Ensure proper formatting of date/time values according to FHIR serialization rules.
Present DateTime and Date with DatePicker controls.
Present Time and Instant values with TextBox controls that show an input hint describing the expected format
```

--------------------------------

### Save XML Declaration Options

Source: https://docs.fire.ly/projects/Forge/features/ForgeOptions

Specifies how XML declarations are saved to a resource. Options include 'Same as source', 'Include', and 'Omit'. Newly created, duplicated, or upgraded resources will include the declaration unless 'Omit' is selected.

```text
Forge has three options that allow you to specify when Xml declarations are saved to a resource:
    * Same as source
    * Include
    * Omit
Note that when saving resources that are newly created, duplicated or upgraded, the Xml declaration is included when the option is set to **Same as source** or **Include** and omitted when set to **Omit**.
```

--------------------------------

### Forge File Name Handling

Source: https://docs.fire.ly/projects/Forge/_sources/ReleaseNotes

Fixes an issue where Forge incorrectly processed files containing an ampersand character (%) in their file names. This ensures that files like 'MyPatient_%C3%A9.xml' are handled correctly.

```bash
MyPatient_%C3%A9.xml
```

--------------------------------

### XML Declaration Options in Forge

Source: https://docs.fire.ly/projects/Forge/_sources/features/ForgeOptions

This section describes the three options available in Forge for controlling the saving of XML declarations within resources: 'Same as source', 'Include', and 'Omit'. It also notes the behavior for newly created, duplicated, or upgraded resources.

```text
<?xml version="1.0" encoding="utf-8"?>

```

--------------------------------

### Forge XML/JSON Serialization Fix

Source: https://docs.fire.ly/projects/Forge/_sources/ReleaseNotes

Addresses an issue where complex child elements in extension definitions were serialized to XML/JSON in the wrong order, causing errors when saving and reopening. This fix ensures correct serialization order.

```xml
<Element 'Extension.extension.extension' is not available in the corresponding resource>
```

```json
{"error": "Element 'Extension.extension.extension' is not available in the corresponding resource"}
```

--------------------------------

### FHIR .NET API Snapshot Generator Improvements

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

The FHIR .NET API, specifically version 1.4.0-forge4, includes several improvements to the Snapshot Generator. These changes focus on deriving type constraints, normalizing type slices, handling default slicing components, initializing sliceNames, fixing element expansion, and supporting logical models.

```csharp
#1074 Derive implicit type constraint from renamed choice type element.
    Example: "valueString" implies element type constrained to String
    #1051 Normalize type slices in snapshot
    Transform renamed choice type elements ("valueString") in differential
    to fully expanded type slice ("value[x]:valueString") in snapshot
    (generated snapshot will never contain renamed elements, making it easier to process & compare)
    #1051 Generate default Slicing component for slice entry of type slice to snapshot, even if missing from differential
    #1051 Initialize default sliceNames for renamed choice type elements, if missing from differential
    Example: value[x] constrained to "Quantity" implies sliceName "valueQuantity"
    #1051 Fix incorrect expansion of resliced elements
    #1051 Implement official HL7 FHIR Snapshot Generator unit tests
    https://github.com/hapifhir/org.hl7.fhir.core/tree/master/org.hl7.fhir.r5/src/test/resources/snapshot-generation
    #1052 Initialize ElementDefinition.constraint.source
    #1067 Fix incorrect base for profile extension root element
    #1090 SnapshotGenerator supports Logical Models
    #1101 Handle element constraint without a path
```

--------------------------------

### Forge Date/Time Serialization Fix

Source: https://docs.fire.ly/projects/Forge/_sources/ReleaseNotes

Corrects a bug where Forge did not serialize date/time information in a region/language independent way when caching resource and summary information. This prevented parsing of timestamps in specific regional settings, like Finnish.

```csharp
/* Forge did not serialize date/time information in a region/language independent way when caching resource and summary information on disk. This would result in an error message similar to: "2024-04-22T08.41.08.303414+00:00" cannot be parsed as an instant. It only affects Windows users that have a regional date/time setting that is incompatible with the FHIR standard (e.g. Finish). */
```

--------------------------------

### Forge Bug Fix: FOR-334 Extension Definition Selector

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Fixes the behavior of the "Open..." button for extension definition selectors. The button is now hidden for complex extension child elements where the type.profile is empty, as these cannot be directly opened. The button remains visible only for the root element of a referenced external extension.

```csharp
// Forge now hides the Open... button for complex extension child elements (type.profile is empty),
// as you cannot directly open a single child element of a structure.
// The Open... button is only visible on the root element of the referenced external extension.
// This addresses FOR-334.
```

--------------------------------

### FHIR Upgrade Log Analysis

Source: https://docs.fire.ly/projects/Forge/_sources/features/R4BUpgradeWizard

This snippet shows a typical upgrade log generated by the R4B Upgrade Wizard. It details version updates and minor changes made to FHIR resources during the upgrade process, highlighting specific modifications like target type additions for references.

```text
Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbaseObservationLab.StructureDefinition.xml
        VersionUpdated
	    4.0.1 > 4.3.0
        MinorChanges
	    Observation.subject > New target types available for type reference: Organization, Procedure, Practitioner, Medication, Substance
    Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbaseOrganization.xml
	    VersionUpdated
		4.0.1 > 4.3.0
    Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbasePatient.StructureDefinition.xml
	    VersionUpdated
		4.0.1 > 4.3.0
    Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMEbasePractitioner.StructureDefinition.xml
	    VersionUpdated
		4.0.1 > 4.3.0
    Upgrade log for C:\Users\Rob\Documents\FHIR\ACMEBaseProfilesR4-R4B\ACMECoreSmokingStatusProfile.xml
	    VersionUpdated
		4.0.1 > 4.3.0
```

--------------------------------

### Forge UI Element Visibility Logic for Complex Extensions

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Explains how the Forge UI dynamically hides or shows the Extension.value[x] child element based on the presence of nested complex extension elements within a parent. It also details the 'Add' and 'Extend' toolbar commands for managing extension elements.

--------------------------------

### Fixing Invalid System URI

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Details a correction made to an invalid system URI in the default list of system identifiers, specifically changing 'urn:std:iso:11073:10101' to 'urn:iso:std:iso:11073:10101'.

```text
Correct invalid system uri (reported by Brian Reinhold)
The default list of system identifiers contained an invalid URI.
Correction: "urn:std:iso:11073:10101" => "urn:iso:std:iso:11073:10101"
```

--------------------------------

### Update FHIR R4 .NET API

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

This snippet indicates a required update to the .NET API version for FHIR R4. It lists specific bug fixes related to the Snapshot Generator, including initialization of extensions and handling of ElementDefinition.base for contentReference children.

```text
Update to .NET API 1.4.0 for FHIR R4 (official build)
Provides bug fixes for the Snapshot Generator:

  - #1116 initialize [...].extension.url fixed value, if missing
  - #1123 ElementDefinition.base empty for contentReference children
```

--------------------------------

### Configuration for Narrative Elements in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

This describes a configuration option in Forge that allows users to include or discard Narrative elements when creating or opening StructureDefinitions. The option defaults to discarding elements to save memory, but can be enabled to restore the original behavior.

```text
Configuration option to include or discard Narrative elements

This behavior is now configurable through the menu option “Discard all Narrative elements” and has been disabled by default. You can enable this option in order to restore the original behavior and discard Narrative elements when loading StructureDefinitions.
```

--------------------------------

### Forge Bug Fix: FOR-196 Ctrl+C Freeze

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Addresses an issue where pressing Ctrl+C on a validation warning could cause Forge to freeze. This fix implements exception handling for unexpected errors that might occur when copying data to the clipboard, likely due to clipboard unavailability.

```csharp
// Forge now catches unexpected exceptions while copying.
// This addresses FOR-196 where Ctrl+C on validation warning may cause freeze.
```

--------------------------------

### Use FhirPath Expression

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

This feature allows using FhirPath expressions as an alternative to XPath for defining property values. It's a newer, experimental feature.

```text
This property accepts a FhirPath expression, as an alternative to the existing .xpath property.
```

--------------------------------

### Validate ValueSet Binding URLs in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Ensures correct validation of valueset binding URLs based on element type. Supports http/https for ValueSetReference and http/https/urn for ValueSetUri.

```regex
.binding.valueSetReference => accept http | https
```

```regex
.binding.valueSetUri => accept http | https | urn
```

--------------------------------

### Define Custom Rulesets with YAML in Firely Forge

Source: https://docs.fire.ly/projects/Forge/features/QualityControl

Learn how to create your own rulesets for Quality Control in Firely Forge by defining a YAML file. Forge automatically recognizes these files and adds them as new menu items to the Quality Control dropdown.

```yaml
# Example: <your_ruleset_name>.rules.yaml
# Define your custom validation rules here.
# For example:
- rule: "ExampleRule"
  description: "This is an example rule."
  severity: "warning"
  expression: "Patient.gender.exists()"

```

--------------------------------

### XML Entity Rendering in Forge

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

The XML view in Forge now renders encoded XML entities (&amp;, &quot;, &apos;, &lt;, &gt;) as-is without decoding. Previously, these were decoded, potentially causing issues when copying to the clipboard.

```html
The XML view now renders encoded XML entities (&amp; &quot; &apos; &lt; &gt;) in attribute values as-is, without decoding.
```

--------------------------------

### Forge Feature: Editable StructureDefinition.type for Logical Models

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Enables the `StructureDefinition.type` field to be editable for logical models. For logical models, this field should contain a fully-qualified URI identifying the logical type, similar to a canonical URL. This contrasts with constraining profiles and extensions, where Forge auto-generates a read-only structure type code.

```csharp
// For logical models, StructureDefinition.type should specify a fully-qualified Uri
// that uniquely identifies the logical type (similar to canonical url).
// This addresses FOR-337.
```

--------------------------------

### FHIR.NET API Upgrade for DSTU2

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Details on the upgrade to FHIR.NET API v0.95-alpha1 for DSTU2 1.0.2. This version introduces stricter deserialization for coded values, mapping them to C# Enum types, which may cause runtime Parse exceptions for invalid values.

```csharp
ElementDefinition.Type.Code : FHIRDefinedType
Conformance.resource.type : ResourceType
```

--------------------------------

### FHIR STU3 Element Definition ID Generation Logic

Source: https://docs.fire.ly/projects/Forge/OldReleaseNotes

Details the logic Forge uses to automatically generate and serialize element IDs for constrained element definitions in FHIR STU3. It outlines the structure of generated IDs and notes that user overrides are not permitted. A known issue with slice names in ID generation is also mentioned.

```text
Forge automatically generates element id values for all (constrained) element definitions
Forge always serializes the generated ids for all (constrained) element definitions in the differential component
Forge generates each element id from the element names and slice names of parent elements: elementName[:sliceName].elementName[:sliceName]…
User cannot override the generated element ids
Forge automatically updates element ids when necessary, e.g. if you rename a parent slice
```

--------------------------------

### Forge Bug Fix: FOR-335 Choice Type Renaming

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Solves an issue where Forge sometimes failed to rename choice type elements when they were constrained. This fix is linked to issue #1123, which addresses the `ElementDefinition.base` field being empty for `contentReference` children.

```csharp
// This issue has been solved by #1123 (ElementDefinition.base empty for contentReference children)
// This addresses FOR-335.
```

--------------------------------

### DateTime Value Limitations

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Highlights limitations in editing time and timezone parts of DateTime values due to WPF DatePicker constraints. Partial date support is also not yet implemented.

```text
Editing time and timezone part of a DateTime value is not yet supported
Due to limitations of the WPF DatePicker control, you can only specify the date part of a DateTime value.
Partial dates are not yet supported
FHIR DateTime allows partial values, e.g. year or year-month.
Forge does not yet support this, due to limitations of the WPF DatePicker control.
```

--------------------------------

### Forge Bug Fix: FOR-316 Complex Type Expansion

Source: https://docs.fire.ly/projects/Forge/_sources/OldReleaseNotes

Resolves a problem where child elements of complex types were not always expanded. This includes cases like Extension.extension.value[x] constrained to CodeableConcept. The fix improves cycle detection logic to prevent infinite recursion while allowing necessary element expansion.

```csharp
// The cycle detection logic has been improved to allow child element expansion whenever applicable.
// Also, Forge now dynamically expands the child elements of a type choice element ("value[x]") when constrained
// to a single complex type - unless the type choice element is (type) sliced.
// This addresses FOR-316.
```
Tokens:
Raw