-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement Nick Name Table for DRC Data Pulls (BlueJeans 11.18.19) #145
Comments
Per SOP found here: https://docs.google.com/document/d/15zjSUEF5USpfoQu0TvAevyIIMYpPeTDX3fvDCqSHcGM/edit#heading=h.j97spx63jtdr Ignore, special character differences, nicknames, suffixes, prefixes, hyphens, and character cases for DRC data pulls. |
@OSNorthwestern is this still relevant? |
@ybushmanova Yes still relevant. Basically being able to pull from aliases table in EPIC when comparing OMOP name values and HealthPro values would save lot of time. |
@ybushmanova, are we able to implement this? Basically we are looking to include nicknames in the mismatch process prior to EHR submission. Nicknames/Aliases are what majority of those mismatch list consists of. If DRC data pull can include nicknames/Aliases table in Epic, that would short the list. |
@NiviyaGeorge I'll check with Mike on this and let you know |
@NiviyaGeorge we were looking into this ticket and wanted to know where you would want to see the nicknames? Would it be a column in the mismatch table prior to submission? |
@pshum1, Yes definitely before the submission. I believe we were trying to see the Excel sheet that you provided me to check for mismatch should consider nicknames as well. The step when doing the comparison between OMOP name values and HealthPro values and need to include the nick name values as well. |
Implement nick name table for DRC data pulls to account in common nick names for mismatch lists
The text was updated successfully, but these errors were encountered: