Page History
...
The data requests are configured as breakdowns in the QT_QUERY_RESULT_TYPE table. The values are populated dynamically when the user run user saves the data request querytable definition.
Following values are stored when the query is run.
RESULT_TYPE_ID: <TABLE_INSTANCE_ID>
NAME: Auto generated number: RPDO_<n>
VISUAL_ATTRIBUTE_TYPE_ID is set to LU
USER_ROLE_CD is set to DATA_LDS /NULL?
DISPLAY_TYPE_ID: CATNUM
CLASSNAME:
Example:
| RESULT_TYPE_ID | NAME | DESCRIPTION | DISPLAYTYPE_ID | VISUAL_ATTRIBUTE_TYPE_ID | USER_ROLE_CD | CLASSNAME |
| <TABLE_INSTANCE_ID> | RPDO_78 | User-created Demographics Data Request | CATNUM | LU | DATA_LDS | edu.harvard.i2b2.crc.dao.setfinder.QueryResultPatientRequest |
| Info | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
We recommend data requests be limited to DATA_LDS users (irrespective of Admin path role - admin, user, manager) and data exports be limited to MANAGER users (irrespective of data path role - data_lds, data_agg,data_obf, data_deid). The user role determines if exports/requests are visible and runnable.
|
...
