You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There ist a problem with required VS-bindings in slices
Conditions for slicing in the specification:
.coding ist sliced
slicing closed --> Only the options that can be specified via the slices should be available
discriminator $this(pattern) or $this(value)
required VS-binding for each slice. The required VS-bindings contain different CodeSystems for each slice. The distinction can be made on .system
Slicing closed and dicriminator:
Required VS-binding first slice
Required VS-binding second slice
Relevant section from the Example
If the value set of the VS binding only uses codes from one code system, a pattern for .system can be stored to fix the error. If the value set uses codes from multiple code systems, this is not possible.
If you validate examples against such a profile, you will receive an error message that the involved element doesn‘t match any known slice defined in the profile although a required binding exists.
The entire profile and example can be found in the zip file requiredBinding.zip
The text was updated successfully, but these errors were encountered:
There ist a problem with required VS-bindings in slices
Conditions for slicing in the specification:
Slicing closed and dicriminator:
Required VS-binding first slice
Required VS-binding second slice
Relevant section from the Example
If the value set of the VS binding only uses codes from one code system, a pattern for .system can be stored to fix the error. If the value set uses codes from multiple code systems, this is not possible.
If you validate examples against such a profile, you will receive an error message that the involved element doesn‘t match any known slice defined in the profile although a required binding exists.
The entire profile and example can be found in the zip file
requiredBinding.zip
The text was updated successfully, but these errors were encountered: