Uploaded image for project: 'i2b2 Core Software'
  1. i2b2 Core Software
  2. CORE-363

bad c_table_cd from search by codes not handled by timeline

    XMLWordPrintable

Details

    • Bug
    • Status: New
    • Major
    • Resolution: Unresolved
    • None
    • TBD
    • None
    • None
    • i2b2 Core Server 1.7.11 Release 3d951c4
      alpine:3.10
      wildfly-14.0.1
      ojdbc8.jar
    • Rank:
      0|s0002o:

    Description

      We built a query with 3 terms and checked "Timeline" in the run query dialog. The timeline got as far as filling in one of the terms and then stopped.

      We discovered the following sequence of events:

      1. The 2nd term in the query came from "search by codes" where the 1st was dragged from the term higherarchy. The SQL used to search by codes included:

      ```
      select c_table_cd
        from blueheronmetadata.table_access
        where c_table_name = 'HERON_TERMS'
          and rownum <= 1
      ```

      This seems to assume each c_table_name corresponds to 1 c_table_cd. That's not the case in our installation. We use the same c_table_name for c_table_cd `i2b2_Procedures` and `i2b2_Diagnoses` etc.

      2. The `c_table_cd` part of the key for that term was `i2b2_Procedures` even though it was a diagnosis concept: `\\i2b2_Procedures\i2b2\Diagnoses\ICD10\...\`

      3. The timeline tried to get term info using that key; the server logs show something like "expected 1 term; found 0"

      4. In the resulting `sdxData.origData`, the `table_name` wasn't present.

      5. We get a js error:

      ```
      TypeError: sdxData.origData.table_name is undefinedTimeline_ctrlr.js:99:6
      ```

      Attachments

        Activity

          People

            mem61 Mike Mendis
            dconnolly Dan Connolly
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: