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

Ingest the Nebraska lexicon into the vocabulary tables. #7

Closed
mgurley opened this issue Nov 29, 2018 · 8 comments
Closed

Ingest the Nebraska lexicon into the vocabulary tables. #7

mgurley opened this issue Nov 29, 2018 · 8 comments

Comments

@mgurley
Copy link
Collaborator

mgurley commented Nov 29, 2018

  • Parse input. Create attribute-value relationship.
  • Link to sites: breast, colon
  • Replace LOINC attribute codes with SNOMED when available
@dimshitc
Copy link
Collaborator

here's the thing:

not all the entries from pdf-protocol exist in release SNOMED-like Nebraska files.
And the first thing is to ingest what's in pdf-protocol rather then what in distribution files, right?
So there will be regular LOINC codes from the protocol with relationship to Site and values from the protocol.
for example:
image
Note, this concept doesnt' have SNOMED equivalent
so we'll have
85331-7 | 'Has site (Nebraska)' | 76752008 | Breast structure
85331-7 | 'Has value (Nebraska)' | 260407003 | Weak
85331-7 | 'Has value (Nebraska)' | 4470001000004101|Moderate
85331-7 | 'Has value (Nebraska)' | 260404005 | Strong

Is this the way you see it?

@dimshitc
Copy link
Collaborator

dimshitc commented Nov 30, 2018

@mgurley
Copy link
Collaborator Author

mgurley commented Nov 30, 2018

@dimshitc Yes, I am a little confused about how the distribution files relate to the protocol PDF. If we can't use the distribution files as the basis for the ingestion and need to scrape the PDF, then we have a problem. This was why I sent the email to Scott Campbell yesterday asking about the latest version. I thought he mentioned at AMIA that LOINC was being removed from the Nebraska Lexicon because of licensing issues. Your layout of the concept relationships look good but we need to talk to Scott about the distribution files.

@dimshitc
Copy link
Collaborator

dimshitc commented Nov 30, 2018

Scrape the PDF is not a problem actually for now, we already copy-pasted this information manually and it can be used in a first version of Nebraska OMOP vocabulary
but later we need to get some automated way of course

@dimshitc
Copy link
Collaborator

dimshitc commented Oct 9, 2019

So, is this still actual?
Is it related somehow to CAP eCC?
Can we talk about this on the one of the vocabulary meetings?

@meerapatelmd
Copy link
Contributor

@mgurley @dimshitc I think Nebraska is key from some of our pathology mappings. What is the status of this effort? I downloaded the Nebraska files, but they weren't as intuitive as I was expecting.

@ekorchmar
Copy link
Collaborator

Currently the SNOMED version of Nebraska Lexicon is being under assessment for inclusion in OMOP CDM Vocabularies. It does not seem to include any crosswalks to PDF protocols.

@sratwani
Copy link
Collaborator

Completed as a part of the 2020 Symposium effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants