A logical value set identifier (i.e. ValueSet.identifier). The server must know the value set (e.g. it is defined explicitly in the server's valuesets, 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

A text filter that is applied to restrict the codes that are returned (this is useful in a UI context)

A reference to an external definition that provides additional control information about how the expansion is performed.

At this time, there is no agreed format or funtionality for the target of this URI. The VSAC Documentation provides one example of the use of this parameter. Implementers using this element will need to agree on an appropriate mechanism for use within their interoperability community

The date for which the expansion should be generated. Normally, this 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.

The result of the expansion

Note: as this the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource

The code that is to be validated. If a code is provided, a system must be provided

The system for the code that is to be validated

The version of the system, if one was provided in the source data

A coding to look up

The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information 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.

A display name for the code system

The version that these details are based on

The preferred display for this concept

Whether this code is an abstract concept

Additional representations for this concept

The language this designation is defined for

A code that details how this designation would be used

The text value for this designation

A logical value set identifier (i.e. ValueSet.identifier). The server must know the value set (e.g. it is defined explicitly in the server's valuesets, 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 code that is to be validated. If a code is provided, a system must be provided

The system for the code that is to be validated

The version of the system, if one was provided in the source data

The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return athe recommended display name in an extension in the outcome

A coding to validate

A full codeableConcept to validate. The server returns true if one of the coding values is in the value set, and may also validate that the codings are not in conflict with each other

The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point 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.

if true, then an abstract code is allowed to be used in the context of the code that is being validated. Typically, abstract codes are allowed to be used in value set specifications (e.g. any code that is subsumed by an abstract code). If false (which is the default value), then only concrete codes as defined by the value set are allowed

True if the concept details supplied are valid

Error details, if result = false. If this is provided when result = true, the message carries hints and wanrings

A valid display for the concept if the system wishes to display this to a user

An item to be validated

A codeable concept to be validated. If the source is a coding, or a code/system pair, wrap it in a CodeableConcept

The value set to validate the concept against. This is a logical value set identifier (i.e. ValueSet.identifier). The server must know the value set (e.g. it is defined explicitly in the server's valuesets, or it is defined implicitly by some code system known to the server

The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point 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.

The outcome of validating an item. There must be an entry for every item in the same order

True if the concept details supplied are valid

Error details, if result = false. If this is provided when result = true, the message carries hints and wanrings

A valid display for the concept if the system wishes to display this to a user