Resource to define constraints on the Expansion of a FHIR ValueSet.

An absolute URL that is used to identify this expansion profile when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this expansion profile is (or will be) published.

Formal identifier that is used to identify this expansion profile when it is represented in other formats, or referenced in a specification, model, design or an instance.

Used to identify this version of the expansion profile when it is referenced in a specification, model, design or instance.

There may be multiple resource versions of the expansion profile that have the same identifier.

A free text natural language name for the expansion profile.

Support human navigation.

The name is not expected to be unique. A name should be provided unless the expansion profile is a contained resource (e.g. an anonymous expansion profile in a FHIR profile). Most registries will require a name.

The status of the expansion profile.

Identify when/if the expansion profile should be used.

Allows filtering of expansion instances that are appropriate (or not) for use.

This expansion profile was authored for testing purposes (or education/evaluation/marketing), and is not intended for genuine production usage.

This expansion profile was authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.

Allows filtering of expansion instances that are appropriate (or not) for use.

The name of the individual or organization that published the expansion profile.

Helps establish the "authority/credibility" of the expansion profile.

Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.

Contacts to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

The name of an individual to contact regarding the expansion profile.

If there is no named individual, the telecom is for the organization as a whole.

Contact details for individual (if a name was provided) or the publisher.

The date that the expansion profile status was last changed. The date must change when the business version changes, if it does, and it must change if the status code changes.

Need to know when an expansion profile was first legal for use or became withdrawn or replaced.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the expansion profile. Additional specific dates may be added as extensions.

A free text natural language description of the use of the expansion profile - reason for definition, conditions of use, etc. The description may include a list of expected usages for the expansion profile and can also describe the approach taken to build the expansion profile.

Human understandability.

The description is not intended to describe the semantics of the expansion profile. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the expansion profile is a contained resource (e.g. an anonymous expansion profile in a FHIR profile). Most registries will require a description.

A set of criteria that provide the constraints imposed on the value set expansion by including or excluding codes from specific code systems (or versions).

Code systems to be included in value set expansions.

A data group for each code system to be included.

An absolute URI which is the code system to be included.

See ''Coding.system'' for further documentation.

The version of the code system from which codes in the expansion should be included.

This is used to apply version specifc inclusion contraints. If no version is specified, then all codes from the code system present in the expansion (prior to application of the expansion profile) will be retained.

Code systems to be excluded from value set expansions.

A data group for each code system to be excluded.

An absolute URI which is the code system to be excluded.

See ''Coding.system'' for further documentation.

The version of the code system from which codes in the expansion should be excluded.

This is used to apply version specifc exclusion contraints. If no version is specified, then all codes from the code system present in the expansion (prior to application of the expansion profile) will be excluded.

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

ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are only evaluated if includeDesignations is present and set to "true". If includeDesignations is present with a value of "true" and both ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are absent, then all designations are returned in the expansion.

A set of criteria that provide the constraints imposed on the value set expansion by including or excluding designations.

Designations to be included.

A data group for each designation to be included.

At least one of designation.language or designation.use must be provided for each include.designation element.

The language this designation is defined for.

In the absence of a language, all designations are retained which match the designation.use parameter for this include.designation.

Designation uses for inclusion in the expansion.

In the absence of a use, all designations are retained which match the designation.language parameter for this include.designation element.

Designations to be excluded.

A data group for each designation to be excluded.

At least one of designation.language or designation.use must be provided for each exclude.designation element.

The language this designation is defined for.

In the absence of a language, all designations are excluded which match the designation.use parameter for this exclude.designation element.

Designation uses for exclusion in the expansion.

In the absence of a use, all designations are retained which match the designation.language parameter for this exclude.designation element.

Controls whether the value set definition is included or excluded in value set expansions.

The ValueSet defintion refers to all fields in the ValueSet definition apart from ValueSet.contains. The definition is only included if includeDefinition is present and has a value of "true".

Controls whether inactive concepts are included or excluded in value set expansions.

Inactive codes are included if includeInactive is present and has a value of "true".

Controls whether or not the value set expansion includes nested codes (i.e. ValueSet.expansion.contains.contains).

Nested codes excluded if excludeNested is present and has a value of "true".

Controls whether or not the value set expansion includes codes which cannot be displayed in user interfaces.

Codes which cannot be used in user interfaces will be excluded if excludeNotForUI is present and has a value of "true".

Controls whether or not the value set expansion includes post coordinated codes.

Post coordinated codes are excluded if excludePostCoordinated is present and has a value of "true".

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

If the value set being expanded is incomplete (because it is too big to expand), return a limited expansion (a subset) with an indicator that expansion is incomplete.

This field overides the default behaviour (which is to return an error). This does not apply to expansions which are unbounded.