Page | 2
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Table of Contents
User Guides ................................................................................................................................................... 3
Data Flow ...................................................................................................................................................... 3
What credentials are required for fulfilling the different roles for MPOG Participation? ........................... 4
Anesthesia CPT Prediction Tool .................................................................................................................... 5
Downloading the MPOG App Suite ............................................................................................................... 6
Variable Mapping .......................................................................................................................................... 7
Concept Browser ........................................................................................................................................... 8
Location Mapping ......................................................................................................................................... 9
Case Viewer ................................................................................................................................................. 10
Data Diagnostics.......................................................................................................................................... 11
Case Validation............................................................................................................................................ 13
Transfer to MPOG Central .......................................................................................................................... 16
Maintenance Schedule ............................................................................................................................... 19
Upgrades ..................................................................................................................................................... 20
Appendix A – Database Roles ..................................................................................................................... 21
Appendix B – MPOG Role Assignments ...................................................................................................... 22
Glossary ....................................................................................................................................................... 26
Page | 3
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
User Guides
The user guides for the MPOG Applicaon Suite can be found on our website. They are updated
as needed during each MPOG upgrade, biannually in the Spring and Fall.
Data Flow
How does the data get from our Electronic Health Record (EHR) to MPOG?
Files are generated by extracng data from its source system and placed into a file share that is
accessible by the MPOG Import Ulity (extract). This includes data from the EHR, Anesthesia
Reporng Server, the Billing Vendor, and any supplemental extracts that the site is using. Those
files are removed from the file share and inserted directly into the Import Manager Database
(import). The files stored in Import Manager are parsed into tabular data and inserted into
staging tables (consume). This generates metadata regarding variable usage that is used in
Variable Mapping. The tabular data is then inserted into the designated MPOG_MAS database
(handoff).
All data up to this point is stored on the site’s local servers, MPOG does not have access to this
data. Once the data has been cleaned and validated by the local team (ACQR, Quality Champion,
Anesthesia IT Champion, etc.), the data can be transferred to the MPOG Central Repository by
using the transfer ulity within the MPOG Applicaon Suite (upload).
What do I do when the file is too big to import? Should I split it into mulple files?
You cannot “split” files. All that does is overwrite data since the system assumes the date you are
imporng is complete. You will need to re-extract the affected dates into smaller ranges, keeping
individual files under 2GB in size.
• Target Date Completeness: Files cannot contain updates for only a few cases or paents
at a me. Whenever data for a parcular target date and module is extracted, all data for
Page | 4
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
that date must be present in the file. Any data that was extracted previously but is not
present in a new file will be interpreted as deleted and will be purged from Import
Manager. (see MPOG Import Manager File Spec, page 5).
What credenals are required for fulfilling the different roles for MPOG
Parcipaon?
See Appendix B – MPOG Role Assignments for a breakdown of role responsibilies and
requirements.
Page | 5
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Anesthesia CPT Predicon Tool
The Anesthesia CPT Predicon tool is a machine learning algorithm that takes procedure text
and predicts the top 3 anesthesia CPT codes based on cases that have submied CPT codes.
Some of the most common reasons for using the CPT predictor are:
(a) Billing was not completed at the me of transfer to MPOG – MPOG allows a 3-
month grace period for billing to be completed and submied
(b) No billing data available for a case
(c) A site is experiencing issues with their billing files – can be due to errors
encountered during the import-consume-handoff process, errors in the billing file
received from the vendor, or missing billing files
Sites sll need to submit CPT codes once they are available. This tool is beer than having no
CPT codes but is not perfect. The tool ‘learns’ from the submied codes to improve its
predicons. Using the predicted codes will allow MPOG to send more accurate measure
feedback while the site is working through the issues with the billing data.
Algorithm for Selecng from Top 3 Predicted Codes:
• If difference in predicted confidence interval is >1.6x between 1
st
and 2
nd
code, Use 1
st
code only For example: (01922: 70%, 00700: 20%, 01936: 10%)
• If difference between predicted 1
st
and 3
rd
code is >1.6x, use 1
st
and 2
nd
code only
• For labor epidural and c-secons, use 1
st
predicted code only
• Machine connues to ‘learn‘ as codes are submied – Sites will provide us feedback that
will allow us to manually improve the algorithms.
Page | 6
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Downloading the MPOG App Suite
Instrucons for downloading the MPOG App Suite can be found on our website. It is not
compable with Macs and is only available for PCs. However, if you have remote access to a PC,
you can download the MPOG App Suite to the PC and then connect remotely via Mac.
How do I know what informaon to put in to the ‘Connecon Profile’?
Contact your local technical team for the server and database connecon informaon.
What do I do if my connecon fails?
− First, double check the server connecon informaon with your local technical team
− Next, verify that you have been granted the appropriate access. See Appendix A – Database
Roles. The MPOG technical team can provide instrucons on which database roles should be
granted. Your local technical team grants the correct roles.
Why don’t I have access to all of the buons? I believe I need access to some more of the
apps.
− App access is done through assigning ‘Database Roles.’ These are assigned by your local technical
team with some guidance from the MPOG Coordinang Center.
− Your technical team may need to grant addional ‘database roles’ if current access is not sufficient.
Page | 7
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Variable Mapping
Is there a recommended order for compleng Variable Mapping?
− We recommend mapping variable in these categories first: Race, Gender, Ethnicity, Procedure
Service, Admission Type, Staff Type. These categories typically have less variables and can be
mapped quickly.
− Next, we recommend mapping variables in the Lab Type and Administraon Type
(Inputs/Outputs/Meds) categories.
o There are 3 steps in compleng Lab Type mapping.
Start with mapping labs that are important to surgical/anesthesia care (Hgb, Hct,
Creanine, Glucose, Troponin, potassium).
Next, map microbiology and virology labs that we have concepts for (i.e.,
coronavirus, COVID Anbody tesng, blood cultures, wound cultures, etc.)
Finally, map any remaining labs that we have concepts for (i.e., WBC, blood
gases) .
If we do not have a concept for a variable, it is okay to leave it unmapped or
skipped.
o The Administraon Type (Inputs/Outputs/Meds) category includes IN’s and OUT’s such
as fluids, medicaons, blood products, EBL, emesis, and urine output. Exclude all
physiologic and gas flow variables from this mapping group. Epic sites, exclude all
“volume (mL)” medicaon variables, as they are duplicates.
− The bigger categories, Administraon Route, Units of Measurement (Administraon),
Observaon Type, and Observaon Detail Type should be mapped last.
o When mapping Administraon Route, map unspecified concepts to “Other” or leave
unmapped. Focus on compleng mapping for variables with a row count greater than
100. Units of Measurement (Administraon), leave those variables without a
corresponding MPOG concept unmapped. Observaon Type includes the events,
physiologic, and outcomes variables (i.e., intubaon). This category should be mapped
before Observaon Details Type, which includes variables that are the details of the
events (i.e., ETT type). For both Observaon Type and Observaon Details Type, we
recommend starng mapping by focusing on variables with a row count greater than
1000, then focusing on any that are specific to anesthesia and surgical care.
What is Premapping?
Premapping is completed by the MPOG Coordinang Center for Epic sites only, since Epic oen
uses similar variables across their sites. MPOG will review the common Epic AIMS IDs and
update the pre-mapping for these variables. This occurs automacally when a new Epic site
starts onboarding with MPOG. Aer onboarding is completed, premapping updates can sll be
applied and reviewed by clicking on the Premappings buon in Variable Mapping. The ‘Variable
Mapping Tips - Epic Sites’ user guide on our website has more informaon about the
premapping process.
Page | 8
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
What if there are mulple variables with similar names?
If duplicate variables exist for crical mes such as anesthesia start/end, surgery start/end, etc.,
anesthesia documentaon is preferred but you can also map nursing documentaon if
anesthesia documentaon is not available for crical mes/events.
How do I know what types of variables should be mapped to the concepts that have
similar names?
We have added definions to some of our concepts to clarify their intended use. These concepts
will have a blue icon next to it on the right side of the Variable Mapping tool. Hover over the
icon, and it will give you more informaon about that concept. If you have a queson about a
concept that does not have an icon, contact the MPOG help desk
(support@mpog.zendesk.com).
Concept Browser
Why do concepts not come up when I search by concept ID?
To search by concept ID, type ‘id:’ before the numbers
Page | 9
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Locaon Mapping
How do you determine what the Health System name is?
For instuons within the United States, we use the American Hospital Associaon (AHA) website to
determine Health System names for all MPOG parcipang sites. This allows for standardizaon in
aggregate reporng and enables future analysis for research projects at the hospital and/or health
system level. If a hospital is not part of a larger health system, then the hospital name is assigned as
the health system name also. This is done during Clinical Onboarding, and the MPOG Clinical
Informacs Specialist will assist with assigning locaon names and types.
If your instuon changes names, contact the MPOG help desk (support@mpog.zendesk.com), and
we will work with you to update the names together.
For instuons located outside of the United States, we will determine this together to ensure
standardizaon in naming across parcipang sites.
How do you determine if a locaon is a hospital or subsidiary hospital?
For instuons within the United States, we also use the American Hospital Associaon (AHA)
website to determine if a locaon is a hospital or subsidiary hospital. This is done during Clinical
Onboarding, and the MPOG Clinical Informacs Specialist working with you will help with the
locaon names and types.
For instuons located outside of the United States, we will determine this together using the
informaon that is available.
Can we add locaons to MPOG that were previously not included?
Yes, you can add more locaons aer you are in MPOG producon, however addional validaon is
required before upload. Please contact the Coordinang Center for guidance as you consider adding
new locaons to ensure the following steps are addressed:
• Fill out the MPOG Applicaon for exisng sites adding new locaons
o The applicaon does not allow you to save and return later and must be completed
in one session.
o For sites outside of Michigan, addional fees may apply. For more informaon
regarding fees, please visit the MPOG Website: hps://mpog.org/funding-outside-
michigan/
• Once we receive the applicaon, MPOG will follow up via email with the next steps.
• Do NOT enable any new locaons unl aer you receive instrucons from MPOG.
Page | 10
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Case Viewer
I can see informaon in my EHR (Epic, Cerner, etc.) that I do not see in Case Viewer.
Where did the informaon go?
− First, try searching for the variable in ‘Record Search.’ If it appears, look to see what the original
variable is mapped to. Fix any incorrect mapping in ‘Variable Mapper.’
− If unable to find in ‘Record Search,’ check table view for the variable. Again, see if there is any
mapping that needs to be corrected.
− If variable is not in ‘Table View,’ check Variable Mapper. The variable may have been
inappropriately excluded. Correct any mapping issues found.
− If variable is not in Case Viewer or Variable Mapper, contact your local technical team with a case
example, screenshots of the data in your EHR, and any other relevant informaon. The data may
not be part of the data geng extracted from your EHR.
Page | 11
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Data Diagnoscs
How is Data Diagnoscs Used?
Data Diagnoscs is used to help verify data completeness, variable mapping, and accuracy. Two
separate strategies are employed to improve data quality and ensure data accuracy. Technical and
clinical staff use this tool to detect systemac errors with data extracon, transformaon, or
mappings. Diagnosc visualizaons represent specific pass/failure thresholds to determine
compliance at a macro level. If one (or more) diagnoscs for your site fall in either the Borderline or
Poor areas, complete a data drill down to determine what is causing the result. Borderline or Poor
results tend to be related to any combinaon of the following issues:
− Data missing and not included in the extract
− Errors somewhere in the Import Manager Data Flow process
− Handoff has not finished
− Variable Mapping: mis-mapped variables, unmapped/skipped/excluded variables, recent
mapping changes
− Documentaon at the site (i.e., Train of Four is not rounely documented)
Billing Diagnoscs
Some diagnoscs are required for all sites, some are oponal, and one is only required for Epic sites. The
chart below breaks this down.
My case has billing codes, why is it failing the billing diagnosc?
Hospital Discharge data is linked to the paent. The diagnosc requires the associated billing code to
align with the case me. (The billing code start and end mes must include the case me period).
Professional fee diagnoscs require the codes be case linked. If you are seeing codes for the date of the
procedure, but they are not marked as case-linked, do your pro fee codes have a me component? You
can set an import manager handoff seng that increases the tolerance for case linking. This can be set in
the Import Manager Assistant app, contact support@mpog.zendesk.com for assistance.
Page | 12
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
How oen should I review Data Diagnoscs?
Data Diagnosc review and aestaon are required for all sites before uploading to the Central
MPOG database. All funded sites are required to conduct this aestaon process on a monthly
basis. Non-funded sites are required to complete aestaon before each upload to MPOG Central.
If submission is on a monthly basis, then aestaon should also occur on a monthly basis.
How do I drill down on a diagnosc?
See Data Diagnoscs Troubleshoong guide.
What can cause a sudden dip or spike in the Data Diagnoscs scores?
There are mulple reasons why you see sudden dips or spikes in your data. Some of the most
common reasons are:
− Possibility 1: Changes in clinical pracce that are accurately reflected in the data.
o In this example, an iniave was rolled out at a site in May/June 2019 to improve
EBL documentaon.
o As expected, the percentage of cases with EBL documentaon increased aer the
iniave.
o This diagnosc is reflecve of pracce at the instuon and can be aested as
accurate.
− Possibility 2: Mapping changes
− Possibility 3: New concepts that need mapping
− Possibility 4: Extract changes
− Possibility 5: Locaon name changes in the Extract
What does it mean to complete ‘Data Diagnosc Aestaons?’
In the Aestaon secon, the site Anesthesia Clinical Quality Reviewer (ACQR) or Quality Champion
can review the diagnosc and determine if the data accurately represents the documentaon
present at the site (either in the EHR or billing soware). You can aest to the accuracy of your data
mulple mes throughout the month, but Aestaon is required to be completed for all
diagnoscs labeled as High Priority and Medium Priority at least once per month prior to
upload to MPOG Central.
Page | 13
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Case Validaon
Why does the queson ask if the paent was 90 years old when they were older?
MPOG cuts age off at 90 years old to decrease the chance that the paent could be idenfied,
since most of the paents are younger than 90. When you see a queson asking if the paent
was 90 years old, but they were actually older, you should answer ‘Correct’.
Why does the date and me of operaon show up as 01/01/0001 - 00:00?
The data for this case has not yet finished handoff. You can either choose another case to
validate or save the MPOG Case ID and try to validate the case again in a few days aer handoff
is complete. Check Import Manager Assistant to assess the handoff queue (see Module: Data
Review – IM Assistant.
*Case Validaon uses Anesthesia Start Date/Time as the Date of Operaon in the banner for all
unreviewed cases. If a case is reviewed that has Anesthesia Start Date/Time missing, it will
default to Scheduled Time as the Date of Operaon unl the issue causing the missing
anesthesia start me is resolved.
Why does it say, ‘Was surgical incision NOT FOUND’ and the line highlighted in red?
There are different scenarios that may result in ‘surgical incision not found’:
1) If you are reviewing a procedure where there is no incision (i.e., labor epidural), this is expected,
and you can skip the queson.
2) If you are reviewing a case where you would expect to see an incision (i.e., CABG) and it is
highlighted red
a. First, check Variable Mapping. The incision me may be unmapped, or it may be
mapped to a different concept. This queson looks for variables mapped to either
50006 AACD Procedure Start Date/Time or 50235 Surgical Incision Time.
b. If the mapping is correct, then review Import Manager Assistant to verify that
handoff has completed. Rever to the Import Manager Assistant user guide for
Page | 14
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
instrucons on how to check handoff status. If it has completed, review Import
Manager Assistant for missing days and contact your local Technical Support person
to help troubleshoot. Contact the MPOG help desk (support@mpog.zendesk.com) if
further assistance is needed.
Where does MPOG get the admission informaon from?
Case Validaon Queson: ‘Is the admission type correctly mapped as ___?’
This queson pulls data from the preop admission status, or what the admission status was
when the case was booked. We have developed a specificaon for an oponal supplemental
extract for ADT (Admission/Discharge/Transfer) data that can be used to show admission status
changes. Contact the MPOG help desk (support@mpog.zendesk.com) if you are interested in
subming this oponal extract.
Case Validaon says that the paent had a block, but it is from a prior procedure.
Sites that use Epic have seen this issue. Usually this is due to documentaon, where the block is
documented as an LDA during a prior procedure but is never documented as removed. Since it
was not removed, it looks like the paent sll has it. We have phenotypes that can address this
issue once you transfer to MPOG Central, however we cannot apply phenotypes on your local
database. The way to fix this issue is to address the documentaon. Otherwise, you can answer
this queson as ‘Correct’ because it accurately reflects the documentaon in your EHR.
How does MPOG determine if a medicaon is a bolus or an infusion?
This is determined by site documentaon, but the medicaons that MPOG typically expects to
see as boluses or infusions are listed in the table below.
If an end me is not populated, infusion dose will connue unl the start me of the next
administraon for the same medicaon. If an end me is not populated and there is not an
addional administraon, the infusion will connue unl anesthesia end me. If the infusion
start me is aer anesthesia end, the end me will default to 5 minutes aer infusion start.
Page | 15
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Why does Case Validaon ask the same intraop medicaon queson mulple mes?
Case Validaon is used to confirm your site’s variable mapping. Intraop medicaon queson
logic is as follows:
• The first medicaon alphabecally
• The last medicaon alphabecally
• The heaviest medicaon by mass
• The lightest medicaon by mass
If the same medicaon queson is repeated, it’s likely due to one of the following reasons:
• The case was a small/short case with only a few medicaons administered and therefore
that one medicaon meets the criteria for the quesons listed above.
• There may be unmapped medicaons that were administered in the EHR but do not
show up in Case Viewer. Please review variable mapping if this is the case.
How is the infusion end me determined if it wasn’t documented in the EHR?
Case Validaon defaults infusion end me to 6 hours aer anesthesia end if it was not
documented or if it was documented later than 6 hours aer anesthesia end. The standard
extract meframe for MPOG data is limited to 4 hours before anesthesia start through 6 hours
aer anesthesia end. Some sites may have modified their extract meframe – contact your
technical team if you have quesons regarding the extract.
My paent had many labs resulted in the me frame asked, but the quesons only ask
about hemoglobin, hematocrit, and glucose. Is that right?
The quesons under the labs secon are looking for only hemoglobin, hematocrit, and glucose
labs from the day before through the day aer the procedure. It will not look at any other labs
during this me frame.
What do I do when Case Validaon doesn’t match what I see in the EHR?
See Case Validaon Troubleshoong guide.
Page | 16
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Transfer to MPOG Central
How long aer I transfer my data will it be updated on the dashboard?
On the 1
st
, 2
nd
, and 4
th
week of each month, data is processed at MPOG Central in the order it is received.
During transfer week, which is the 3
rd
week of the month (2
nd
week in December), the data is processed
so that the newer cases are completed first. This is to allow for the most recent data to be completed
and ready for provider feedback emails to be sent the following Wednesday.
Page | 17
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
What is Privacy Preserving Record Linkage (PPRL)?
Privacy Preserving Record Linkage is the new term for the Blinded Record Index (BRI). It is a
process through which paents can be matched to each other without directly using protected
idenfiers. This ability to match paents from different data sources is useful for (1) idenfying
records that belong to the same paent and (2) finding dates of death.
While described in more detail elsewhere, the process of adding paents to the PPRL is
summarized in the following steps:
1. Paent idenfiers (e.g., name, date of birth, SSN) are hashed many mes using a
local-side key with the hospital firewall.
2. These hashes are encrypted and sent over HTTP to a central service. Messages are
authencated using both client and server cerficates.
3. The central service hashes them many more mes using a central-side key.
4. These hashes are then stored in a database at University of Michigan with the
associated MPOG paent idenfier.
Aer this process, it is computaonally infeasible to transform the hashed data back into the
original paent idenfiers. Doing so by brute force would take a period of me measured in
millions of years. In addion to this technical hurdle, data use agreements spulate that no party
including MPOG itself is to aempt re-idenfying paents.
It uses US Naonal Instutes of Standards and Technology Secure Hashing Algorithm and
incorporates RSA secure key. The hashed codes are kept centrally with no source idenfiers.
These hashed codes can be linked across data sources This Public domain hashing algorithm has
been “blessed” by US federal government in registries manual as non-PHI and is approved by
IRBs and DUAs at all MPOG instuons. See the Privacy Preserving Record Linkage presentaon
for more informaon.
**If you are experiencing errors when transferring older data, you can uncheck the box next to
‘Create/update the blinded record index for this paent.’
Page | 18
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
What do the presets include?
There are three presets for transferring to MPOG – Recommended, Previous Month, and
Historical. You do not need to specify a date range when using these presets, it will automacally
populate when you choose a seng.
• Recommended – This seng includes cases for the previous month and any historical
cases that have been updated (i.e., mapping changes, new billing data, or new data
that wasn’t included previously). Use this for your regular monthly transfers. This
seng could contain a lot of data and may take some me to complete.
• Previous Month – This seng only includes data for the previous month. Use this if
you are short on me for your regular monthly transfer, as this seng contains only
one month of data. Any older cases that have new data or mapping changes will not
be sent to MPOG Central and will not be updated. You will need to complete a
Historical (see below) transfer when you have me in order to update the older data.
• Historical - This seng only includes your historical data and does not include the
previous month. Use this if you have historical data that needs to be updated at
MPOG Central outside of the monthly upload schedule. This transfer can take some
me, as it includes any historical cases that either have new data or have updated
mapping. You can transfer historical data any me throughout the month.
*If your site receives Provider Feedback Emails, you must use either the Recommended seng or the
Previous Month seng to transfer data before the monthly deadline. Historical data is not reflected in
those emails but is used in the QI Reporng Tool (Dashboard) measure scores.
Page | 19
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Maintenance Schedule
What is the Maintenance Schedule?
The Maintenance Schedule is the recommended cadence to complete monthly tasks, and to
ensure that data is uploaded by the deadline. Tasks are broken down into which week they
should be completed during. Week 1 is the first week of the month with a Wednesday.
It also includes dates for the monthly data transfer deadline, and dates for when Provider
Feedback Emails will be sent.
It also includes the dates of the Transfer Deadline, QI Reporng Tool (Dashboard) Update, and
when Provider Feedback Emails will be sent.
When should data be uploaded?
Data is uploaded for the previous month on the 3
rd
Wednesday. This gives enough me for the
data to process so we can send Provider Feedback Emails on the 4
th
Wednesday.
**The only excepon is in December, where the transfer deadline is the 2
nd
Wednesday and
Provider Feedback Emails are sent on the 3
rd
Wednesday.
Where can I find it?
The maintenance schedule is under the Resources page under the Quality secon on the MPOG
website, hps://mpog.org/
How oen is it updated?
It is updated every year and is typically available on the MPOG website starng in November or
December.
Page | 20
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Upgrades
When is the MPOG App Suite Upgraded?
The MPOG App Suite is upgraded twice per year, in the spring and in the fall. There are two parts
to each upgrade: the database upgrade and the app (workstaon) upgrade. The database
upgrade is completed with assistance from the MPOG Technical team. The app (workstaon)
upgrade is the part that you see in the MPOG App Suite. There are different ways to apply the
app upgrade, depending on your site. Your technical team will give you instrucons when it is
me.
How do we apply the upgrade?
The upgrade package will be sent to each site’s IT contact.
− For sites using Desktop Virtualizaon (e.g., Citrix), your IT team will upgrade the App
Suite.
− For sites where the App Suite is installed on PCs, your IT team will distribute the installer
to all individuals aer the database upgrade has been applied. Once you have received
the installer from your IT team, follow the install instrucons here.
Can we skip an upgrade?
No, you cannot skip an upgrade. Oen, the changes made during one upgrade are built upon
changes made during previous upgrades.
Can I submit a request for an upgrade?
Yes, if you have a request that you would like included in a future MPOG App Suite upgrade,
contact the MPOG help desk (support@mpog.zendesk.com) with your request.
Page | 21
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Appendix A – Database Roles
The following table shows the database roles needed for access to the applicaons within the MPOG Suite. No addional permissions are needed
to use these applicaons.
Please grant MPOG_Researcher to everyone who needs to use the MPOG Suite. It acts as a base role.
Case
Viewer
Concept
Browser
Variable
Mapping
1
STS
Import
2
NSQIP
Import
2
PHI
Scrubber
Data
Diagnostics
Case
Validation
Transfer
to MPOG
Central
Batch
MRN
Lookup
Content
Synchronization
Research
Data
Cleaning
3
Location
Mapping
Provider
Contacts
Import
Manager
Assistant
4
MPOG_Assistant
App
MPOG_CaseVali
dator
MPOG_Content
Downloader
MPOG_Exporter
MPOG_Exporter
Restricted
MPOG_Importer
MPOG_MRNBat
cher
MPOG_PhiScrub
ber
MPOG_QueryWr
iter
MPOG_Research
er
MPOG_Variable
Mapper
db_owner
1
A config connection is required for this application unless the configuration type is Epic Legacy.
2
Either db_owner or both MPOG_Importer and MPOG_ContentDownloader is required to use the registry import applications (NSQIP and STS). Just MPOG_ContentDownloader or MPOG_Importer
will not be enough to use either of these applications.
3
A research connection is required for this application.
4
This application is only available for Import Manager configurations.
Last updated May 7, 2019
Page | 22
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Appendix B – MPOG Role Assignments
What credenals are required for fulfilling the different roles for MPOG Parcipaon?
Role/Task
Responsibilies
Notes
IT Lead
Oversees the development,
maintenance, and opmizaon of
the IT infrastructure supporng
MPOG's diverse iniaves. This
role involves managing a team of
IT professionals, ensuring data
security and integrity,
coordinang with clinical teams,
and implemenng technology
soluons to facilitate efficient
data collecon, analysis, and
reporng.
IT Support
Responsible for providing
technical assistance and
troubleshoong for systems used
in local sites efforts with MPOG
iniaves.
Can also help with Data
Uploader role.
Anesthesia IT
Champion
Works with the local technical
and clinical teams to assist with
implemenng the IT
infrastructure necessary to
support MPOG parcipaon. This
role requires an understanding of
concept mapping and local EHR
documentaon.
The Quality Champion, PI,
and IT Champion roles can be
fulfilled by one individual or
mulple. We defer to the
instuon to determine who
will be best suited for each
role.
Quality
Champion
Parcipates in the MPOG Quality
Commiee on behalf of the site.
They are responsible for
reviewing site performance on
MPOG QI measures and
disseminang best pracces
locally
The Quality Champion, PI,
and IT Champion roles can be
fulfilled by one individual or
mulple. We defer to the
instuon to determine who
will be best suited for each
role.
Principal
Invesgator
Leads research efforts for the site
and parcipate in the MPOG
Perioperave Clinical Research
Commiee (PCRC).
The Quality Champion, PI,
and IT Champion roles can be
fulfilled by one individual or
mulple. We defer to the
instuon to determine who
will be best suited for each
role.
Page | 23
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Role/Task
Responsibilies
Notes
Cardiac
Champion
Expert in cardiac anesthesia who
leads efforts to improve cardiac
care and outcomes within MPOG.
This role involves advocang for
best pracces, analyzing
performance metrics, guiding
quality improvement iniaves,
and collaborang with both
clinical and technical teams to
implement evidence-based
protocols and contribute to
MPOG's research efforts in
cardiac anesthesia.
OB
Champion
An expert in obstetric anesthesia
who leads iniaves to improve
care quality and outcomes for
pregnant paents. This role
involves advocang for best
pracces, analyzing performance
metrics, guiding quality
improvement projects, and
collaborang with clinical and
technical teams to implement
evidence-based protocols and
contribute to MPOG's research
efforts in obstetric anesthesia.
Pediatric
Chair
Pediatric Chair at local site who
oversees iniaves aimed at
improving care quality and
outcomes for pediatric paents.
This role involves seng clinical
guidelines, analyzing performance
data, driving quality improvement
projects, and collaborang with
muldisciplinary teams to
implement evidence-based
pracces, while also contribung
to MPOG's broader research and
educaonal goals in pediatric
anesthesia.
Page | 24
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Role/Task
Responsibilies
Notes
Pediatric
Champion
Expert in pediatric anesthesia
dedicated to enhancing the
quality and outcomes of care for
pediatric paents. This role
involves advocang for best
pracces, analyzing performance
metrics, leading quality
improvement iniaves, and
collaborang with clinical and
technical teams to implement
evidence-based protocols that
align with MPOG's research and
quality improvement goals in
pediatric anesthesia.
Variable
Mapper
CRNA,
Anesthesia
Assistant, RN
Responsible for accurately
mapping local electronic health
record (EHR) data to MPOG's
standardized variables. This role
requires a deep understanding of
both local EHR documentaon
and MPOG's data definions,
ensuring data integrity and
consistency to support
meaningful research and quality
improvement efforts. The
Variable Mapper should be
someone with clinical experience
(Anesthesiologist, CRNA, RN,
etc.).
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their technical support,
Anesthesia IT Champion, or
Quality Champion fill this role.
Although not recommended,
this role can be filled by
someone without clinical
experience (i.e., IT Lead), as
long as they have a clinical
person to help as needed
Locaon
Mapper
This person should have a
working knowledge of the site’s
campus (i.e., OR rooms, Non-OR
Areas, etc.)
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their technical support,
Anesthesia IT Champion, or
Quality Champion fill this role.
Case
Validator
CRNA,
Anesthesia
Assistant, RN
Completes Case Validaons prior
to monthly Transfer to MPOG.
Current requirements are to
complete a minimum of 5
validaons per month.
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their Anesthesia IT
Champion or Quality
Champion fill this role.
Page | 25
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Role/Task
Responsibilies
Notes
Data
Uploader
(PHI Scrub
and Transfer
to MPOG)
Responsible for the mely and
accurate upload of clinical data to
the MPOG database. This role
entails managing data extracon
from local electronic health
records, ensuring data quality,
and troubleshoong any issues
that arise during the upload
process to support the ongoing
research and quality
improvement iniaves within
the organizaon.
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their technical support,
Anesthesia IT Champion, or
Quality Champion fill this role.
Data
Diagnoscs
Reviewer
CRNA,
Anesthesia
Assistant, RN
Prior to monthly Transfer to
MPOG, completes Review and
Aestaon of Data Diagnoscs for
accuracy. Works with site’s IT
Support to troubleshoot issues.
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their Anesthesia IT
Champion or Quality
Champion fill this role.
Provider
Contacts
Management
Michigan sites have an RN or
CRNA in this posion. Sites
outside Michigan will have
either their technical support,
Anesthesia IT Champion, or
Quality Champion fill this role.
Anesthesia
Clinical
Quality
Reviewer
(ACQR)
ASPIRE is the quality
improvement (QI) arm of the
MPOG, that improves outcomes
by empowering perioperave
teams to explore variaon in
pracce and idenfy
opportunies for change. Funding
provided by Blue Cross Blue
Shield of Michigan (BCBSM)
supports ASPIRE acvies within
the state of Michigan and
requires each site to hire an
ACQR. The ACQR’s primary
funcon is to facilitate the
implementaon of the ASPIRE
program within their instuon.
Page | 26
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Glossary
ACQR – Anesthesia Clinical Quality Reviewer. This is a role that is required for instuons parcipang in
MPOG/ASPIRE within the State of Michigan. Instuons will receive yearly funding for the ACQR.
This role is typically filled by a Registered Nurse with operang room experience but can be filled
by other clinical staff (i.e., CRNA). The ACQR’s primary funcon is to facilitate the
implementaon of the ASPIRE program within their instuon. Funding for the ACQR is based on
annual case volumes.
AIMS – Anesthesia Informaon Management System
AIMS Variables – These are the variables that are found in the site’s EHR. The variable names are
assigned in the extract.
ASPIRE – The Anesthesiology Performance Improvement and Reporng Exchange (ASPIRE) is the quality
improvement (QI) arm of the Mulcenter Perioperave Outcomes Group (MPOG). ASPIRE
improves outcomes by empowering perioperave teams to explore variaon in pracce and
idenfy opportunies for change.
Blinded Record Index (BRI) – A system that creates a blinded record index by merging datasets across
sites without PHI. It uses a hashing algorithm that is encrypted and cannot be decrypted. This
was now referred to as Privacy Preserving Record Linkage (PPRL). The name is changed, but the
process is the same.
Consume – Files stored within the Import Manager Database are parsed into tabular data and inserted
into staging tables. Addionally, metadata regarding variable usage is generated for later
mapping.
Extract – Files are generated by extracng data from its source system (i.e., Epic, Cerner, CompuRecord,
etc.). These files are then placed into a file share accessible by the MPOG import ulity. The site
technical team completes this process. Epic has a standard MPOG Extract that they use for their
sites. All other EHRs require the site technical team to write their own MPOG Extract.
Funded Sites – Sites parcipang in MPOG that are located within the State of Michigan (USA) that also
parcipate in the ASPIRE CQI. These sites receive funding from Blue Cross Blue Shield of
Michigan and must meet specific yearly requirements.
Handoff – The tabular data is inserted into the designated LOCAL MPOG_MAS database. The data within
this database is accessible to the clinical team through the MPOG App Suite (Workstaon). Aer
this step, you will see the data in the different tools of the MPOG App Suite – Variable Mapping,
Case Viewer, Case Validaon, Data Diagnoscs.
Import – Files are removed from the file share and inserted directly into the Import Manager Database,
which is located on the site’s LOCAL MPOG Database Server.
MPOG – The Mulcenter Perioperave Outcomes Group
Non-Funded sites – Sites parcipang in MPOG that are located outside the State of Michigan (USA).
Page | 27
MPOG help desk (support@mpog.zendesk.com) Last Updated: 7/28/2026
Privacy Preserving Record Linkage (PPRL) - A system that creates a blinded record index by merging
datasets across sites without PHI. It uses a hashing algorithm that is encrypted and cannot be
decrypted. This was previously referred to as Blinded Record Index (BRI). The name is changed,
but the process is the same.
Transfer to MPOG – Using the transfer ulity within the MPOG applicaon suite, surgical cases are
uploaded to the central repository. This step is completed by the designated person (i.e., ACQR,
QI Champion, technical team member), and is completed AFTER data has been validated, PHI
Scrubbed and aested. This step transfers the data from the Local MPOG Database to the
Central MPOG Database.
Upload – Using the transfer ulity within the MPOG applicaon suite, surgical cases are uploaded to the
central repository. This step is completed by the designated person (i.e., ACQR, QI Champion,
technical team member), and is completed AFTER data has been validated, PHI Scrubbed and
aested. This step transfers the data from the Local MPOG Database to the Central MPOG
Database.
Variable Mapping - This process of standardizing terms across mulple EHRs and across mulple sites
allows for common data elements to be used for research or quality improvement purposes.
Think of this as the process of translang the site’s AIMS Variables into the same language as all
other MPOG Sites (i.e., Clinician is the same thing as Anesthesiologist). The Variable Mapper
should be someone with clinical experience (Anesthesiologist, CRNA, RN, etc.). Although not
recommended, this role can be filled by someone without clinical experience (i.e., IT Lead), as
long as they have a clinical person to help as needed.