Expand VS for Conditions #144
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dtphelan1
requested review from
dmendelowitz,
jafeltra,
julianxcarter and
mgramigna
as code owners
dmendelowitz
approved these changes
Aug 2, 2021
Contributor
dmendelowitz
left a comment
dmendelowitz
left a comment
There was a problem hiding this comment.
This looks good to me!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses STEAM-423. CT Matching task is using snomed condition codes. MEF looks to see if condition codes are in primary or secondary value set in order to properly add category.coding values to conform to mCODE cancer condition profiles. However, because our VS files are not expanded, we don't properly satisfy the 'isCancerCondition' check, so we don't add the necessary category codings.
This PR expands all mCODE VS's that have
includeobjects which define codes intensionally with afilterobject.New behavior
No new behavior, just new codes against which we match for
isCancerConditionfunction callsCode changes
None.
Testing guidance
Before checking out this PR, run the extraction tool and inspect the Condition resource and confirm that the condition's do not have a category code with value "64572001" (this category code gets added when the condition is recognized as a Cancer condition).
Afterwards, checkout the branch and run extraction again. Confirm that this category code, "64572001", is now showing up on condition resources.
NOTE: Before merging, we should remove the old VS's in the
valuesets/originaldir. I've left them in so people can see the change that's taken place in expansion.