Search

Help

Page 17 of 72. Showing 714 results (0.048 seconds)

  1. PROVIDER_DIMENSION Table

    Each record in the PROVIDER_DIMENSION table represents a physician or provider at an institution. The PROVIDER_PATH is the path that describes how the provider fits into the institutional hierarchy. Institution, department, provider name and a code may be included in the path. PROVIDER_DIMENSION
    Server (Cells) Design • Sep 04, 2018

  2. PATIENT_MAPPING Table

    The PATIENT_MAPPING table maps the i2b2 PATIENT_NUM to an encrypted number, PATIENT_IDE, from the source system (the 'e' in "ide" is for encrypted). The PATIENT_IDE_SOURCE contains the name of the source system. The PATIENT_IDE_STATUS gives the status of the patient number in the source system. For example
    Server (Cells) Design • Sep 04, 2018

  3. ENCOUNTER_MAPPING Table

    The ENCOUNTER_MAPPING table maps the i2b2 ENCOUNTER_NUM to an encrypted number, ENCOUNTER_IDE, from the source system (the 'e' in "ide" is for encrypted). The ENCOUNTER_IDE_SOURCE contains the name of the source system. The ENCOUNTER_IDE_STATUS gives the status of the patient number in the source system
    Server (Cells) Design • Sep 04, 2018

  4. PM_CELL_DATA Table

    The PM_CELL_DATA table contains general information about the cells. There is one row for each CELL_ID. A hive may have several cells of the same type, but they will be distributed to the projects according to their PROJECT_PATH. In version 1.x of the Hive software, the XML will only return the cell which
    Server (Cells) Design • Sep 04, 2018

  5. PM_HIVE_DATA Table

    The PM_HIVE_DATA table contains general information about the hive. The DOMAIN_ID column is expected to be highly unique (at least 20 characters in a random sequence). The DOMAIN_ID needs to be unique across multiple enterprises, which is why it should be at least 20 characters in random sequence
    Server (Cells) Design • Sep 04, 2018

  6. PM_PROJECT_DATA Table

    The PM_PROJECT_DATA table contains general information about the project. There is only one row per PROJECT_ID; data with special tags that can occur once per project is also in that row. The PROJECT_ID is a unique identifier. The PROJECT_NAME is a shot human legible name for the project. The PROJECT_KEY
    Server (Cells) Design • Jan 28, 2019

  7. 10.4.4.2.5 Setfinder Query - Temp Table Properties

    A simple setfinder query is one that does not use a temp table during the querying process. The ability to not use a temp table will speed up the process of running a query against your database. The maximum number of items that can be in a query without using a temp table is defined in the CRC setfinder query without
    Developers Getting Started With i2b2 • Jan 03, 2020

  8. Use Case 3_ PATIENT_NUM in mapping table but with a different date

    If the <patient_id> value already exists in the mapping table then compare the UPDATE_DATE to the existing record's update date. If the new record has a more … ">100</patient_map_id> <patient_map_id source="BWH">777</patient_map_id> </patient> The rows in the PATIENT_MAPPING table before the update
    Server (Cells) Design • Sep 04, 2018

  9. PM_PROJECT_PARAMS Table

    Project specific parameters. Each project can have its own set of parameters. PM_PROJECT_PARAMS     PK ID int   PROJECT_ID varchar(50)   PARAM_NAME_CD varchar(50)   VALUE varchar(255)   DATATYPE_CD varchar(50)
    Server (Cells) Design • Sep 04, 2018

  10. Table Usage

    Server (Cells) Design • Sep 04, 2018