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

Consider making obviously necessary elements mandatory #37

Open
vadi2 opened this issue Dec 19, 2022 · 0 comments
Open

Consider making obviously necessary elements mandatory #37

vadi2 opened this issue Dec 19, 2022 · 0 comments
Labels
QA stage This work should be done after the modelling and IG creation are mostly ready

Comments

@vadi2
Copy link
Owner

vadi2 commented Dec 19, 2022

The IG has been built with as little mandatory cardinalities as possible - 1) since we don't know what kind of data exactly will we be able to get, and 2) we'd like to get all of the data possible, even if it is not 100% complete.

Some elements however can be made mandatory as without them, our data collection simply would not function. This list should be kept as minimal as possible. Some candidates include:

  • form 17 number
  • claimresponse.request
  • appointment.slot
  • claimresponse.adjudication

This work is slotted for the QA stage hopefully we'll have more clarity by then.

@vadi2 vadi2 added the QA stage This work should be done after the modelling and IG creation are mostly ready label Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA stage This work should be done after the modelling and IG creation are mostly ready
Projects
None yet
Development

No branches or pull requests

1 participant