Become a Member

To become a member of MPOG, you must follow the steps below.  

  • Steps 1 - 5: Regulatory / Legal Documentation
  • Steps 6 - 8: Technical Implemenation and upload to MPOG Central Repository

Please Note, institutions are required to obtain a Business Associate Agreement (BAA) Step 2 prior to starting the technical implementation of MPOG, Step 6.  The rest of the regulatory and legal documentation can be done in conjunction with the technical implementation, but must be done before upload to Central Repository, Step 8.


Step 1: Organize Institutional Support, Identify Key Personnel & Apply for Membership

Must occur prior to starting Step 7: Obtain Server / Develop / Configure Data Interfaces to Transfer Data

Any anesthesiology department can apply for membership in MPOG / ASPIRE as long s they have an anesthesiology information system (AIMS). 

  1. Organize institutional support
    1. Implementation of MPOG requires a high level of technical expertise to create the technical infrastructure needed to submit data to MPOG.  An institution must ensure that the department chair or head of practice is aware of the financial and FTE requirements of MPOG implementation and supports joining MPOG.  Click on the following link for FTE Requirments and Cost
  2. Identify Key Personnel at your institution, click on the following link for a complete list of key personnel
  3. Submit the MPOG Membership Application from the MPOG Membership Downloads to Tory Lacca at

Please note: There are two separate applications:

  1. Funded Blue Cross Blue Shield Michigan institutions
  2. Non-funded sites outside the State of Michigan.


Step 2: Complete a Business Associate Agreement (BAA)

Must occur prior to starting Step 7: Obtain Server / Develop / Configure Data Interfaces to Transfer Data

A Business Associate Agreement (BAA) is a legal document that must be put in place between the Regents of the University of Michigan and your institution.

This is normally done through a grants/contracts office at each institution but may vary depending on the site. This agreement is put in place because during the technical implementation and training phases.  MPOG developers and clinical staff may be exposed to protected health information (PHI) from your site.  This document is put in place to allow MPOG staff to properly train staff.

Please see the Membership Downloads section for the University of Michigan BAA template.


Step 3: Complete a Data Use Agreement (DUA)

Can occur concurrently with Steps 1 and 2

Data use agreements (DUA) are drafted between the University of Michigan's and your institutional attorneys. This is normally done through a grants/contracts office at each institution but may vary depending on the site. Understand that these agreements are at the institutional level (not departmental or individual level) and will therefore require signatures from institutional representatives.

Please see the Membership Downloads section for the MPOG DUA template.
The DUA must be in place before data submission to MPOG Central Repository.


Step 4: Submit Performance IRB Application for Approval


Can occur concurrently with Steps 1, 2, and 3 and must be in place before Step 8

  1. A Performance Site IRB must be obtained prior to data submission, Step 8.
    1. An IRB can take weeks / months to obtain depending on your institutional IRB process.  
    2. For detailed information on how to obtain an IRB, see the following website:

Please note: If you institution does not have an onsite IRB, FDA regulations permit an institution without an IRB to arrange for an 'outside' IRB to be reponsible for intitial and contiuing review of studies conducted at the non-IRB institution.  The University of Michigan can accept oversite for non-exempt research.  Please contact Tory Lacca to initiate the process.


Step 5: Review MPOG Bylaws and Terms of Membership Participation

Can occur concurrently with Steps 1 - 4 and must be in place prior to MPOG Submission, Step 8

Review the MPOG Bylaws document, sign and date agreement to the terms of membership participation. E-mail a signed copy of your MPOG Bylaws to Tory Lacca



Step 6: Obtain Server for Local MPOG Data

Dependent on Steps 1 - 2: Identfying Key Perfonnel at Your Institution and Submit MPOG Application and Obtaining a Business Associate Agreement (BAA)

The first step in MPOG implementation is to obtain a local server that will house your local MPOG data.  This must be a separate server and can be a stand alone or virtual server, see Server Requirements in the MPOG Technical Download Section

Please note, an institution may purchase the server before the BAA is completed, but MPOG developers will not move onto the next steps of setting up the server until the BAA is complete.


Step 7: Develop / Configure Data Interfaces to Transfer Data

Dependent on Step 6

After you have obtained a server, you can start the data configuration.  Depending on your institution’s anesthesia information management system (AIMS), your institution or department may need to develop and/or configure the data interfaces necessary to transfer your institution’s data to the central MPOG database.

  1. MPOG and / or vendor programmers have already developed configurable data interfaces for several AIMS and the ACS-NSQIP data structure. Note that provided adapters may need additional development to account for institutional-specific practices.
    1. Centricity
    2. MetaVision
    3. CompuRecord
    4. Picis
    5. Epic
  2. If your institution uses an AIMS that has data interface capabilities already developed by MPOG, the technical effort required to contribute data to MPOG is markedly reduced. Your institution will simply need to configure the data interface (licensed free of charge from MPOG) to manage its institution-specific AIMS content.
  3. If your institution uses an AIMS that does not have an existing MPOG data interface, your institution or department will have to develop the data interface and content mapping routines.
  4. In many situations, some of the elements requested by the standard MPOG data transfer do not reside in your institution’s AIMS. Examples of such data include: laboratory values, demographic data, and preoperative anesthesia history and physical discrete data. These data will necessitate a custom interface developed by your department or institution. Although MPOG staff can provide technical consultation for these efforts, they cannot be the primary developers for these interfaces


Step 8: Submit Limited Dataset to the Central MPOG Database

Dependent on Steps 7

Once the data from your institution’s AIMS, institutional data sources, and surgical outcome registries are extracted into your local MPOG database, they are almost ready for submission to the central MPOG database. Note that MPOG provides utilities to help automate the following processes:

  1. Although patient identifiers are used at your institution to aggregate data across disparate data sources, these identifiers are NOT sent to the central MPOG database. Prior to their removal, they are converted into hashed identifiers in accordance with the National Security Agency’s Secure Hashing Algorithm-256 (SHA-256). This hashing process eliminates the ability to re-identify the patient once the data is sent to the central MPOG database.
  2. Remove all protected health information (PHI) other than date of service / surgery prior to data transfer. This includes name, date of birth, address, social security number, etc. For a complete list, please refer to HIPAA’s official PHI elements list.
  3. Remove all public provider identifiers such as doctor name, doctor number (i.e. NPI), pager number, etc. However, all AIMS-generated system identifiers that are not publicly visible can and should be transmitted.
  4. Transfer limited dataset to the central MPOG database using the provided transfer utility.