Developers Getting Started With i2b2
Space shortcuts
Space Tools
Developers Getting Started With i2b2 getstarted

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

User RoleCreate Data TableData RequestData Request Manager View DetailsData Export/Generate Data file Change Request Status
ObfuscatedEnabledEnabledEnabledDisabledDisabled
AggregateEnabledEnabledEnabledDisabledDisabled
ProtectedEnabledEnabledEnabledDisabledDisabled
LDSEnabledEnabledEnabledDisabledDisabled
Manager/No LDSDisabled since no LDSDisabledEnabledEnabledEnabled
Manager/LDSEnabledEnabledEnabledEnabledEnabled
Admin/no LDSdisabled since no LDSDisabledEnabledEnabledEnabled
Admin/LDSEnabledEnabledEnabledEnabledEnabled


Database Configuration 

RPDO_TABLE_REQUEST

In order to support the data Table design, a new table RPDO_TABLE_REQUEST is added.  The metadata in Data Table design is stored in the table when the data Table is saved.

...

Info

The default rows insert script is provided in the data install folder of the release 


QT_BREAKDOWN_PATH

QRQT_Breakdown_Path table has been modified to include a new column Group_id. It logs the Project_id value.

Database Updates

RPDO_TABLE_REQUEST 

User created concepts in the data table design will be dynamically logged in the RPDO_TABLE_REQUEST at the time of Table Definition Save.  Below is the list that correspond to values of the User created Data Table 

RPDO_TABLE_REQUEST PARAMETERSDATA TABLE Values
Table_Request_idauto generated incremental value, corresponding to each concept in the data table. Unique for each concept
Table_instance_idunique for each Data table, auto generated incremental value( same value for all the concepts underneath)


QT_QUERY_RESULT_TYPE

The data table definitions are logged as breakdowns in the QT_QUERY_RESULT_TYPE table. The values are populated dynamically when the user saves the data table definition.

...

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. 

 QT_QUERY_RESULT_TYPEuser roleUser-created data requestdata Request ManagerVisibility/Actions

 DATA_LDS

DATA_LDS

Success

Success

Only  user-created requests

MANAGER with

DATA_LDS

DATA_LDS

Success

Success

All user-created requests

MANAGER

without DATA_LDS

MANAGER

?

??

Admin

Admin

?

??


QT_BREAKDOWN_PATH

QT_breakdown_path logs the table_instance_id value and the result_instance_id. to be associated with the ptset. query.

...

NAMEVALUE
RPDO_<Table_instance_id>

EXEC i2b2synthea8.dbo.usp_rpdo2 @TABLE_INSTANCE_ID=<Table_instance_id> @RESULT_INSTANCE_ID={{{RESULT_INSTANCE_ID}}} @MIN_ROW=0 @MAX_ROW=10000


QT_QUERY_RESULT_INSTANCE


QT_XML_RESULT

Data file format/location and Email parameters set-up: HIVE_CELL_PARAMS

...

Developers Getting Started With i2b2 getstarted