Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove workaround for split dosage cardinality of bounds element #83

Open
dvribeira opened this issue Dec 18, 2024 · 0 comments
Open

Remove workaround for split dosage cardinality of bounds element #83

dvribeira opened this issue Dec 18, 2024 · 0 comments
Assignees
Labels
bug Something isn't working resource A resource definition is involved

Comments

@dvribeira
Copy link
Contributor

dvribeira commented Dec 18, 2024

Since today, building of the IG is not working because of the slicing of the boundsPeriod element.

Sushi will complain already that the rule to allow only Period slicing for bounds[x] cannot be applied because Period is not a valid type. This comes from the fact that in the dosage split resource definition upstream (CH EMED), the boundsPeriod slice is not allowed, but the other slices are. How come this was not an issue before and now it is, remains a bit of a mistery but it is in any case irrelevant since the main issue in the end is the cardinality of the bounds[x] element as a whole in the split dosage profile. See hl7ch/ch-emed#309

This forces us to split the enforcement of the Period type so that it is not applied to split dosage and to also enforce the 0..0 cardinality on the whole element for the split dosage ourselves until this is applied upstream. Once this is applied upstream, we should remove the redundant cardinality rule on the split dosage profile.

@dvribeira dvribeira added bug Something isn't working resource A resource definition is involved labels Dec 18, 2024
@dvribeira dvribeira self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resource A resource definition is involved
Projects
None yet
Development

No branches or pull requests

1 participant