-
Notifications
You must be signed in to change notification settings - Fork 115
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
Feature add cornerstone adapters #225
Feature add cornerstone adapters #225
Conversation
@wayfarer3130 how does the work here relate to #197 ? Are they complementary and consistent? |
They are mostly complementary - there are a small number of overlapping changes, although this change makes #197 smaller because it puts a bunch of the work for #197 into a single location where it can just be done consistently. |
204128c
to
879775e
Compare
@wayfarer3130 @swederik @JamesAPetts @igoroctaviano @galelis I noticed that the SR measurements code is checking CodeValue without checking CodingSchemeDesignator (e.g., contentSequenceArr.find(group => group.ConceptNameCodeSequence.CodeValue === FINDING) where FINDING_SITE = "G-C0E3". This is bad practice - one should always check both value and scheme, since there is no guarantee that the same code will not be used in different schemes for different concepts (and indeed one should check for SRT, SNM3 and 99SDM if you want to be really robust). Further, you should be using SCT not SRT codes on writing (but checking for either on reading for legacy support), e.g., SCT: 363698007 should be written rather than SCT: G-C0E3, in order to be compliant with CP 1850 and to keep the SNOMED licensing folks happy. |
Thanks @dclunie , |
Accidentally hit close instead of comment |
…/group in the same way
The point TID300 normally takes 1 point, but seems to be ok if an extra one is added for the source of the indicator.
9827214
to
b1da082
Compare
@pieper tested against OHIF, LGTM. |
🎉 This PR is included in version 0.19.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This change adds cornerstone adapters for a number of missing versions:
Some of these previously had code with "todo" in it, but no actual functionality.
The change also makes additional items bi-direction, in specific, the finding and findingSite values are now used to generate description and location values in cornerstone.