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

Determine how multi-cardinality question population should be handled. #31

Open
dmuylwyk opened this issue Sep 9, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@dmuylwyk
Copy link
Contributor

dmuylwyk commented Sep 9, 2024

Determine how multi-cardinality question population should be handled.

  1. Must support repeating questions as well as repeating groups of questions.
  2. Favour sdc-questionnaire-initialExpression over sdc-questionnaire-itemPopulationContext if possible.
  3. May require using sdc-questionnaire-itemPopulationContext extensions; however, this needs to be reconciled with implementation.
@dmuylwyk dmuylwyk added the documentation Improvements or additions to documentation label Sep 9, 2024
@dmuylwyk dmuylwyk self-assigned this Sep 9, 2024
@dmuylwyk
Copy link
Contributor Author

Start with highlighting basic Questionnaire/QuestionnaireResponse examples of such questions (i.e. add appropriate extensions later). Including but not necessarily limited to:

  • Single-cardinality item
  • Multi-cardinality item
  • Group item with single-cardinality children
  • Group item with multi-cardinality item among single-cardinality children
  • Multi-cardinality group item with single-cardinality children
  • Multi-cardinality group item with multi-cardinality item among single-cardinality children
  • etc?

Ultimately, we'll want an example Questionnaire with extensions + Library to illustrate above, alongside an example QuestionnaireResponse to complete the picture, as well as any helpful narrative.

@dmuylwyk dmuylwyk removed their assignment Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

No branches or pull requests

1 participant