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

Move MedReq and Allergy references to end of table #295

Merged
merged 1 commit into from
Sep 6, 2024
Merged

Conversation

mikix
Copy link
Contributor

@mikix mikix commented Sep 6, 2024

Checklist

  • Consider if documentation in docs/ needs to be updated
    • If you've changed the structure of a table, you may need to run generate-md
    • If you've added/removed core study fields that not in US Core, update our list of those in core-study-details.md
  • Consider if tests should be added
  • Update template repo if there are changes to study configuration in manifest.toml

@mikix mikix changed the title Move MedReq and Allerty references to end of table Move MedReq and Allergy references to end of table Sep 6, 2024
mr.authoredOn,
mr.authoredOn_month,

concat('MedicationRequest/', mr.id) AS medicationrequest_ref,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a little hard to see because I rearranged how this table gets generated (to more easily inject the code triplet in the middle of the list). But this line here is new - I added it because it seems standard for core tables to have this kind of field (and it makes sense).

@mikix mikix force-pushed the mikix/table-order branch from 9fff4c6 to 1bf4f27 Compare September 6, 2024 13:49
@mikix mikix marked this pull request as ready for review September 6, 2024 13:50
Comment on lines -585 to +586
BOOL_OR(ec.table_name = 'condition')
BOOL_OR(ec.table_name = 'allergyintolerance')
AND BOOL_OR(ec.table_name = 'condition')
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is from a previous PR where I forgot to regenerate SQL after making a change.

Since the current flow is to generate SQL from test data, we could add a check in the CI to regenerate SQL and see if there are any changes - failing the PR if so... Just a thought for later

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#182 - it's been hanging around for a bit, but it remains a good idea.

Copy link

github-actions bot commented Sep 6, 2024

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
2013 2000 99% 90% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 1bf4f27 by action🐍

@mikix mikix merged commit 71a8884 into main Sep 6, 2024
3 checks passed
@mikix mikix deleted the mikix/table-order branch September 6, 2024 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants