A reference to the canonical url for URL of a value set. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server

The value set is provided directly as part of the request. Servers may choose not to accept value sets in this fashion

The identifier that is used to identify a specific version of the value set to be used when generating the expansion. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.

The context of the value set, so that the server can resolve this to a value set to expand. The recommended format for this URI is [Structure Definition URL]#[name or path into structure definition] e.g. http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation. Other forms may be used but are not defined. This form is only usable if the terminology server also has access to the profile conformance registry that the server is using, but can be used to delegate the mapping from an application context to a binding at run-time

If a context is provided, a context direction may also be provided. Valid values are:

• 'incoming': the codes a client can use for PUT/POST operations, and
• 'outgoing', the codes a client might receive from the server.

The purpose is to inform the server whether to use the value set associated with the context for reading or writing purposes (note: for most elements, this is the same value set, but there are a few elements where the reading and writing value sets are different)

A text filter that is applied to restrict the codes that are returned (this is useful in a UI context). The interpretation of this is delegated to the server in order to allow to determine the most optimal search approach for the context context. The server can document the way this parameter works in TerminologyCapabilities ..expansion.textFilter. Typical usage of this parameter includes functionality like:

• using left matching e.g. "acut ast"
• allowing for wild cards such as %, &, ?
• searching on definition, designations and display(s)
• allowing for search conditions (and / or / exclusions)

Text Search engines such as Lucene or Solr, long with their considerable functionality, might also be used. The optional text search might also be code system specific, and servers might have different implementations for different code systems

A reference Properties to an external definition that provides additional control information about how the expansion is performed. At this time, there is no agreed format or functionality for be considered when matching against the target of this URI. filter text in addition to display, definition and designations, etc. The VSAC Documentation provides one example of properties must have a string representation, e.g. string, code, or url, though the use search is always text based irrespective of this parameter. Implementers using this element will need to agree on an appropriate mechanism for use within their interoperability community. Known uses for profile include: * whether to return the value set content logical definition with the expansion * whether to include inactive concepts property type.

The date for which the expansion should be generated. if a date is provided, it means that the server should use the value set / code system definitions as they were on the given date, or return an error if this is not possible. Normally, the date is the current conditions (which is the default value) but under some circumstances, systems need to generate an expansion as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.

Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)

Paging support - how many codes should be provided in a partial page view. Paging only applies to flat expansions - servers ignore paging if the expansion is not flat. If count = 0, the client is asking how large the expansion is. Servers SHOULD honor this request for hierarchical expansions as well, and simply return the overall count

Controls whether concept designations are to be included or excluded in value set expansions. Overrides the value expansions

A token that specifies a system+code that is either a use or a language. Designations that match by language or use are included in the expansion profile if there expansion. If no designation is one specified, it is at the server discretion which designations to return

Controls whether the value set definition is included or excluded in value set expansions. Overrides This includes all elements of the ValueSet, including extensions, with the exception that the id and meta elements would be specific to the expansion, not to the definition value in set, and the expansion profile if there itself is one filled out.

Controls whether inactive concepts are included or excluded in value set expansions. Overrides the value in the expansion profile if there is one. Note that if the value set explicitly specifies that inactive codes are included, this parameter can still remove them from a specific expansion, but this parameter cannot include them if the value set excludes them

The supplement must be used when performing an expansion. Use of this parameter should result in $expand behaving the same way as if the supplements were included in the value set definition using the http://hl7.org/fhir/StructureDefinition/valueset-supplement

Controls whether or not the value set expansion nests may nest codes or not (i.e. ValueSet.expansion.contains.contains). Overrides the value in If excludeNested is set to true, the expansion profile if there MUST be flat (no nesting). If excludeNested is one set to false (default), however, nesting is possible but not required

Controls whether or not the value set expansion includes might include

• codes which cannot be displayed from the CodeSystem with a notSelectable property set to true as specified in status and in Concept Properties
• nested contains with no code (see Contains )
• nested contains in the ValueSet with abstract = true

One purpose of such concepts is helping a user interfaces. Overrides navigate through the value in list efficiently. If excludeNotForUI is set to true, the expansion profile if there concepts as described above will be excluded from the expansion. If excludeNotForUI is one set to false (default), all concepts as described above may be part of the expansion. In the FHIR Specification itself, the value set expansions are generated with excludeNotForUI = false, and the expansions used when generating schema / code etc., or performing validation, are all excludeNotForUI = true.

Controls whether or not the value set expansion includes post coordinated codes. Overrides the value in the expansion profile if there is one codes

Specifies the language to be used for description in the expansions i.e. the language to be used for ValueSet.expansion.contains.display. Overrides ValueSet.expansion.contains.display

A request to return a particular property in the expansion. The returned property may include subproperties. May be either a code from the code system definition (convenient) or a the formal URI that refers to the property. Note that property names can clash, so using a URI is recommended. The special value in '*' means all properties and their sub-properties known to the server

If true this asserts that you will correctly handle an unclosed expansion and the returned expansion profile SHALL include the valueset-unclosed extension if there the value set is one unclosed. If handle-unclosed-expansion is set to false the server SHALL return an error if the value set is unclosed.

Code system, or a particular version of a code system to be excluded from the value set expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56

Specifies a version to use for a system, if the value set does not specify which one to use. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56

Edge Case: Specifies a version to use for a system. If the a value set being expanded specifies a different version, an error is incomplete (because it returned instead of the expansion. The format is too big the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56

Edge Case: Specifies a version to expand), return use for a limited system. This parameter overrides any specified version in the value set (and any it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56. Note that this has obvious safety issues, in that it may result in a value set expansion (a subset) giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the value is overridden, the version used SHALL explicitly be represented in the expansion parameters

Specifies a version to use for a valueset, if the reference to the value set does not specify which version to use. The format is the same as a canonical URL: [system]|[version] - e.g. http://example.org/ValueSet/example|1.0.0. Note that this is similar to the force-system-version parameter but applied to valuesets

Edge Case: Specifies a version to use for a valueset. If a reference to a value set specifies a different version, an indicator error is returned instead of the expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://example.org/ValueSet/example|1.0.0. Note that this is similar to the force-system-version parameter but applied to valuesets

Edge Case: Specifies a version to use for a valueset. This parameter overrides any specified version in the reference to the value set (and any it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://example.org/ValueSet/example|1.0.0. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is incomplete. Overrides both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the value is overridden, the version used SHALL explicitly be represented in the expansion profile if there parameters. Note that this is one similar to the force-system-version parameter but applied to valuesets.

Specifies an library that provides expansion rules for the operation. The library has an extension expansionParameters that references a contained Parameters resource that contains additional $expand parameters. See the [CRMI specification description of manifests]https://hl7.org/fhir/uv/crmi/STU1/StructureDefinition-crmi-manifestlibrary.html) and CRMI expansion rules for a complete description of how manifest values are used to provide defaults for expansion parameters. Parameters specified directly in an $expand operation override behaviors specified by the manifest parameter.

One or more additional resources that are referred to from the value set provided with the $expand or $validate-code invocation. These may be additional value sets or code systems that the client believes will or may be necessary to perform the operation. Resources provided in this fashion are used preferentially to those known to the system, though servers may return an error if these resources are already known to the server (by URL and version) but differ from that information on the server.

The result of the expansion. Servers generating expansions SHOULD ensure that all the parameters that affect the contents of the expansion are recorded in the ValueSet.expansion.parameter list