Service Workbench
  • General User Guide
    • Introduction
    • Studies
      • Open Data Studies
      • Controlled Data Studies
        • Human Connectome
        • TCGA (The Cancer Genome Atlas)
        • EMory BrEast Imaging Dataset (EMBED)
      • Organization Studies
    • Research workspaces
      • Workspace statuses
      • Workspace configurations
      • How can I create a workspace linked to a study?
      • How can I create a workspace WITHOUT a study?
      • Installing packages into workspaces
      • Using custom Jupyter Notebook kernels
      • Uploading data into SWB
    • Instances
    • Example Analyses & Notebooks
    • FAQ
      • Why was my workspace stopped when I was working on it?
      • How can I install devtools in R/Rstudio?
      • I don't see a 'studies' folder in my workspace?
      • Error: 'Forbidden' or 'Unable to connect'
      • Error: 'We have a problem! null is not an object'...
      • 403 error page
      • Error provisioning environment sagemaker
      • Workspace in Unknown status
      • Cannot connect to SageMaker workspace
      • I can't get through to the log-in page on SWB.
    • Help / Contact Us
    • Release Notes
  • AIM-AHEAD
    • Accessing OCHIN Data
      • Phase 1: Regulatory Requirements
      • Phase 2: Data Exploration
      • Phase 3: Data Analysis
      • Example Researcher Workflow
    • Understanding the OCHIN Data
      • i2b2 Common Data Model
      • Example Queries
      • Additional information
  • Harvard Medical School
    • Introduction
    • Activating your account
    • Creating your workspace
  • LEAP-DEV
    • Workspace Configurations
Powered by GitBook
On this page
  1. AIM-AHEAD
  2. Understanding the OCHIN Data

Additional information

Note that the “race_cd” field of the PATIENT_DIMENSION table contains a set of race codes. A description for these are in the “FellowsSample.common.i2b2” table. In the i2b2 table, the “c_name” field contains the name of each race; and, the “c_operator” and “c_dimcode” fields indicate the corresponding code(s).

For diagnoses, the “tval_char” field in the OBSERVATION_FACT table contains the values “Encounter Diagnosis”, “Problem List”, or “Medical History” to indicate the source of the diagnoses.

For medications, the “tval_char” field in the OBSERVATION_FACT table contains the values “DISPENSING” or “PRESCRIBING” to indicate the source of the medications.

For laboratory tests with a numeric test result, the value of the result is stored in the “nval_num” field of the OBSERVATION_FACT table.

For medications, the “tval_char”, “nval_num”, “valueflag_cd”, and “quantity_num” fields are used in the following way, based on the source of the medication data:

TVAL_CHAR

NVAL_NUM

VALUEFLAG_CD

QUANTITY_NUM

PRESCRIBING

Number of refills ordered (not including the original prescription). If no refills are ordered, the value is zero. For historical prescriptions, the value is Null.

Dose of a given mediation, as ordered by the provider

Quantity ordered.

DISPENSING

Days supply. Number of days that the medication supports based on the number of doses.

Dose of a given mediation, as dispensed.

Number of units (pills, tablets, vials) dispensed.

PreviousExample QueriesNextIntroduction

Last updated 1 year ago