MPOG Config Database
Tables and Their Uses
Introduction
The MPOG configuration database (MPOG_MAS_CONFIG) is used to store data and procedures relevant to ETL
processes that pull data out of an AIMS and into MPOG.
These data pulls are divided into two steps. First, “concept extracts” are used to scan the source database for
variables. The results of this scan are then inserted into the MPOG config database for later mapping. Once the
mapping is complete, “data extracts” are run to pull data from the source database, apply the mappings from the
config database, and finally inserting into the main MPOG database (MPOG_MAS).
Note that because each institution can have very different ETL processes, the config database is not coupled to the
main MPOG database. Aside from being compatible with the variable mapping utility, the config database tables
are used largely as a convention.
Mapping Tables
The mapping tables, those prefixed with “Configuration_”, are used to map the relationship between variables
found in an institution’s AIMS and MPOG concepts. Creating this relationship is important as it establishes a
standard data dictionary across multiple contributing centers.
As an example, a systolic blood pressure measured from an arterial line could be represented with an internal type
identifier of 3245. The MPOG equivalent concept is “BP Sys Arterial Line (Invasive, Peripheral)”, represented in
MPOG as 3030. In order to create this relationship, the internal identifier of 3245, an appropriate description, and
an estimated row count are inserted into the Configuration_PhysiologicVariableTranslation. An individual with
clinical knowledge can then use the variable mapping utility provided to map the two identifiers together based
upon the provided description. Once mapped, the extract that will pull vital sign monitor data can then join to this
mapping table to transform variable 3245 to MPOG concept 3030.
1
Figure 1: Screenshot of the variable mapping utility
Configuration_IntraopMedication
This table is used to store variable mappings for both medications and fluids. This applies to two locations in the
main MPOG database:
Associated Columns in Main Database
AIMS_IntraopInputOutputs
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_IO_Concept_ID
MPOG_IO_Concept_ID
AIMS_IntraopMedications
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Med_Concept_ID
MPOG_Med_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for medication or fluid type
AIMS_Concept_Desc
Readable description for medication or fluid type (e.g. “Propofol” or “Urine Output”)
AIMS_Usage
The estimated row count for this identifier. This is important as it lets the individual using the utility know how
relevant a particular variable is.
2
Incremental_Running_Total
Indicates if a particular concept is documented as a running total or if each record is a separate measurement
 True = 100 mL, 200 mL, 300 mL -> 300 mL total was documented
 False = 100 mL, 200 mL, 300 mL -> 600 mL total was documented
Source_Table
The table from which this variable originated from. This can be useful for telling the mapping user the context of a
particular variable.
Active_From
The starting date for when this description was valid for this identifier. This is useful only if your institution reuses
variable identifiers. If not, please insert a dummy value such as “Jan 1, 1900”. This was made part of the primary
key as medication definitions can change more often than other variable types.
Active_To
The ending date for when this description was valid for this identifier. This is useful only if your institution reuses
variable identifiers. If not, please insert a dummy value such as “Jan 1, 2100”. This was made part of the primary
key as medication definitions can change more often than other variable types.
MPOG_Concept_id
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
3
Configuration_IntraopNoteDetails
Please read the documentation for Configuration_IntraopNotes first as this table is dependent on it. Furthermore,
AIMS_IntraopNoteDetails is an optional table and therefore this mapping table may not be used. Also be aware
that if variables are shared between parent and child notes i.e. there is only one set of concepts, only
Configuration_IntraopNotes should be used.
Associated Columns in Main Database
AIMS_IntraopNoteDetails
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Component_Concept_ID
MPOG_Component_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
Exclude_From_Extract
Whether or not to exclude this variable from being extracted into MPOG
This commonly is applied to variables considered sensitive and should not be imported into MPOG
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
4
Configuration_IntraopNotes
This table stores variable mappings used in intraoperative notes, which is essentially a catch-all for any
intraoperative documentation that does fit into the other categories.
Associated Columns in Main Database
AIMS_IntraopNotes
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Note_Concept_ID
MPOG_Note_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Concept_Type
Can be used to group variables together. If not applicable, leave NULL.
AIMS_Concept_Additional_Info
Any additional information can be placed into this field.
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Source_Table
The table from which this variable originated from.
This can be useful for telling the mapping user the context of a particular variable.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
Exclude_From_Extract
Whether or not to exclude this variable from being extracted into MPOG
This commonly is applied to variables considered sensitive and should not be imported into MPOG
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
5
Configuration_LaboratoryFlags
This table is a legacy component and can be ignored.
6
Configuration_LaboratoryVariables
Associated Columns in Main Database
AIMS_LabValues
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Lab_Concept_ID
MPOG_Lab_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Source_Table
The table from which this variable originated from.
This can be useful for telling the mapping user the context of a particular variable.
Source_Form
If applicable, the form in the AIMS on which the variable is found.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900”
This was made part of the primary key as lab definitions can change more often than other variable types.
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100”
This was made part of the primary key as lab definitions can change more often than other variable types.
Exclude_From_Extract
Whether or not to exclude this variable from being extracted into MPOG
This commonly is applied to variables considered sensitive and should not be imported into MPOG
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
7
Configuration_MedicationUnits
This table stores variable mappings relevant to units of measure such as milliliters and kilograms.
Associated Columns in Main Database
AIMS_IntraopInputOutputs
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_IO_UOM
MPOG_UOM_Concept_ID
AIMS_IntraopMedications
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Med_UOM
MPOG_UOM_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Unit_Of_Measure_Detail
Any additional information about the unit of measure
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
8
Configuration_Outcomes
Associated Columns in Main Database
AIMS_Outcomes
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Outcome_Concept_ID
MPOG_Outcomes_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
Source_Form
If applicable, the form in the AIMS on which the variable is found.
Source_Table
The table from which this variable originated from.
This can be useful for telling the mapping user the context of a particular variable.
Centricity_Case_Linked
A Centricity specific option for stating the outcome variable is linked to an operation or not.
Postoperative_Days_Limit
The maximum number of days after an operation to look for this variable. This is useful for when outcome data is
linked to patients and not operations.
Centricity_Observation_Date_Var_Type_Sys
Centricity specific column, please ignore.
AIMS_Detail_Concept_ID
Used in the event an outcome is in a well-structured hierarchy e.g. an outcome note has a parent row and multiple
children in the source database, this can be used to store the identifier of the child’s variable identifier. If not
applicable, insert “N/A”.
AIMS_Detail_Concept_Desc
The readable description for the identifier in AIMS_Detail_Concept_ID.
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
Exclude_From_Extract
Whether or not to exclude this variable from being extracted into MPOG
This commonly is applied to variables considered sensitive and should not be imported into MPOG
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
9
10
Configuration_PhysiologicVariableTranslation
Associated Columns in Main Database
AIMS_IntraopPhysiologic
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Physiologic_Concept_ID
MPOG_Physiologic_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Source_Table
The table from which this variable originated from.
This can be useful for telling the mapping user the context of a particular variable.
Manual_Entry_CD
Whether this variable is meant to be manually entered by the provider or captured by a monitor.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
11
Configuration_PreoperativeConcepts
Associated Columns in Main Database
AIMS_Preop
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Preop_Concept_ID
MPOG_Preop_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Source_Form
If applicable, the form in the AIMS on which the variable is found.
Source_Table
The table from which this variable originated from.
This can be useful for telling the mapping user the context of a particular variable.
Centricity_Case_Linked
A Centricity specific option for stating the outcome variable is lined to an operation or not.
Preoperative_Days_Limit
The maximum number of days before an operation to look for this variable. This is useful for when preop data is
linked to patients and not operations.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
Exclude_From_Extract
Whether or not to exclude this variable from being extracted into MPOG
This commonly is applied to variables considered sensitive and should not be imported into MPOG
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
12
13
Configuration_ProcedureNotes
This table is a component specific to the Centricity AIMS only. Please ignore.
14
Configuration_ProcedureRoomTypes
This table stores the mappings for the types of operating rooms used at your institution.
Associated Columns in Main Database
AIMS_IntraopCaseInfo
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Procedure_Room_Name
MPOG_Procedure_Room_Type_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable.
Procedure rooms are typically not classified by type in an AIMS, so this is often the room’s identifier or name.
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
15
Configuration_ProcedureServices
This table stores the mappings for cases’ primary service, such as cardiac, general, and orthopedics.
Associated Columns in Main Database
AIMS_IntraopCaseInfo
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Primary_Procedural_Service
MPOG_Primary_Procedural_Service_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
16
Configuration_Races
This table stores the mappings for patient race.
Associated Columns in Main Database
AIMS_Patients
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Race_Text
MPOG_Race_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
Race is often stored directly as a string in most AIMS. If this is the case, duplicate the string for both ID and
description.
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
17
Configuration_Routes
This table is used to store the types of routes used for medications and fluids such as IV and epidural.
Associated Columns in Main Database
AIMS_IntraopInputOutputs
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_IO_Route
MPOG_Route_Concept_ID
AIMS_IntraopMedications
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Med_Route
MPOG_Route_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Route_Detail
Any additional information about the route can be placed in this field
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
18
Configuration_Sites
This table stores the mappings for access sites. This table is unique among the mapping tables as it maps to MPOG
concepts of different types. The concept type determines how the concept can be mapped, so this will need to be
inserted prior to using the utility.
It is not uncommon for the same variable to be mapped multiple times. For example, “Left Hand IV” would need to
be mapped for side, location, and type (MPOG concept IDs 13, 15, and 16). In these cases, the same AIMS variable
would have multiple rows with different concept types.
Associated Columns in Main Database
AIMS_Sites
MPOG_Concept_Type_ID = 13
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Site_Location_CD
MPOG_Site_Location_ID
MPOG_Concept_Type_ID = 14
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Site_Size_CD
MPOG_Site_Size_ID
MPOG_Concept_Type_ID = 15
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Site_Type_CD
MPOG_Site_Type_ID
MPOG_Concept_Type_ID = 16
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Site_Side_CD
MPOG_Site_Side_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
MPOG_Concept_Type_ID
Used to differentiate the attributes of an access site.
 13
Access Location
 14
Access Size
 15
Access Type
 16
Access Side
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
AIMS_Detail_Concept_ID
19
Used in the event a site is in a well-structured hierarchy e.g. a site has a parent row and multiple children in the
source database, this can be used to store the identifier of the child’s variable identifier. If not applicable, insert
“N/A”.
AIMS_Detail_Concept_Desc
The readable description for the identifier in AIMS_Detail_Concept_ID.
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
20
Configuration_Staff
This table stores the mappings for staff roles such as anesthesia attending, anesthesia resident, CRNA, or surgery
attending.
Associated Columns in Main Database
AIMS_IntraopStaff
Column for Original Identifier:
Column for Mapped Identifier:
AIMS_Staff_Role
MPOG_Staff_Role_Concept_ID
Columns
AIMS_Concept_ID
Internal identifier for the variable
AIMS_Concept_Desc
Readable description for the variable
AIMS_Usage
How often this variable is found in the database. This can be either a row count or a case count.
AIMS_Seniority_Level
Applicable only to residents. Useful for differing the years of each resident (years 1 – 3)
If not applicable, use the value “N/A”
Active_From
The starting date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
1900” or null
Active_To
The ending date for when this description was valid for this identifier.
This is useful only if your institution reuses variable identifiers. If not, please insert a dummy value such as “Jan 1,
2100” or null
MPOG_Concept_ID
The equivalent MPOG concept identifier for this variable. Use the value 0 for this field when inserting new rows.
21
Misc. Tables
Config_Extraction_History
This table contains a log of all extraction execution. MPOG supplies procedures to interact with this table.
To illustrate, let’s say the extract notes for cases that occurred between Jan 1 and Jan 5, 2010 was executed
starting at Dec 25, 2013 12:00AM and finished at 12:10AM. The corresponding record in this table would have the
values given as examples for each column.
Columns
Extraction_Start_Time
When the module started execution
Value for above scenario: Dec 25, 2013 12:00AM
Extraction_End_Time
When the module finished execution
Value for above scenario: Dec 25, 2013 12:10AM
Extraction_Module
The module being reference in this record e.g. physiologic, labs, notes, etc.
Value for above scenario: Notes
Extraction_Range_Start
The start of the date range that is being extracted for this module
Value for above scenario: Jan 1, 2010
Extraction_Range_End
The end of the date range that is being extracted for this module
Value for above scenario: Jan 5, 2010
Had_Error
The SQL error code encountered during execution. If none, this field is null.
Config_Extraction_Preferences
This table contains various settings and preferences for the extracts. A common value used in this table is the date
to start extraction from.
Columns
MPOG_Concept_ID
The MPOG concept for this value. All preference concepts are found under MPOG Concept Type ID 18.
Preference_Value
The value of this setting. This column’s data type is varchar to support any type of value.
Config_PatientsTest
22
This table can be used to store all patients considered as test records and therefore should be excluded from the
extract. This table provides two ways of recording the patient identifiers to exclude, reg_num (or MRN) or
patient_sys (or the internal patient identifier in the AIMS). Either or both can be used, whatever makes it easiest
for your institution.
Columns
reg_num
Reg number or MRN of the patient to be excluded
patient_sys
Internal patient identifier of the patient to be excluded
23
Additional Tables
If you find that the above tables do not fully support the needs of your institution’s MPOG extract, you are free to
create your own tables in the config database. If you choose to do so however, it is strongly encouraged that any
tables you add are used to supplement the existing ones rather than replace them.
24