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

LAB_RESULT_CM transform passes non-standard RESULT_QUAL values from i2b2fact table #19

Open
mprittie opened this issue May 12, 2016 · 2 comments
Assignees

Comments

@mprittie
Copy link

According to the PCORnet CDMv3 spec the expected RESULT_QUAL values in the LAB_RESULT_CM table are:

  • BORDERLINE
  • POSITIVE
  • NEGATIVE
  • UNDETERMINED
  • NI = No information
  • UN = Unknown
  • OT = Other

While running the transform (PCORNetLoader_ora.sql) we get errors on the attempted insertion of non-standard RESULT_QUAL values which are larger than the expected 12 character width (the length of UNDETERMINED). This is due to the fact that TVal_Char values in the i2b2fact table are getting passed directly along as long as they are not NULL. It appears that the transform currently expects that the TVal_Char values of matching records contain the relevant PCORI codes, which our fact table does not.

It also looks like this is on your radar, hence the inline TODO comment, but I wanted to log it here so that it's known that this is impacting others.

@jklann
Copy link
Contributor

jklann commented May 12, 2016

Thanks. Any suggestions on how to do this transparently without making sites change their fact tables? I haven't yet come up with a way.

@mprittie
Copy link
Author

Hi Jeff, if we come up with a generalizable solution before you do, I'll share our approach.

@jklann jklann removed the Oracle label Jul 21, 2016
@jklann jklann self-assigned this Oct 6, 2016
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

3 participants