Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 12 Next »

NACHC has invested in building informatics infrastructure and developing services to support a growing body of data-related work. External partners are sharing their clinical and administrative data with NACHC through an array of informatics projects. As NACHC’s informatics portfolio has reached a critical mass, the next step is to implement a data governance structure to build trust among data partners and ensure the highest quality work products.

NACHC convened a data governance council in the fall of 2021 as part of developing and implementing a governance infrastructure for informatics project work. The data governance council will:

  • review and discuss internal and external requests for data or data-related project participation;
  • approve or deny data requests from external partners;
  • approve or deny requests for access to data stored within the NACHC environment;
  • make recommendations regarding data-related project participation;
  • define, discuss, approve, document and track new policies and procedures to meet emerging data governance needs;
  • oversee and manage the NACHC response to data breaches or vulnerabilities;
  • ensure NACHC data governance policies and processes do not infringe on stakeholder policies, agreements, and processes; and
  • ensure long-term, broadly representative data governance for NACHC.


Governance Council Members

The current GC members are:

  1. Ronald Yee (chair)
  2. Julia Skapik
  3. Gervean Williams
  4. Meg Meador
  5. Jennie McLaurin
  6. External: Carolyn Neal (CDC)
  7. External: Andrew Hamilton (Alliance Chicago)

Governance Council Materials

Key Data Governance Issues

The priority issues that the Data Governance Council will address in its first year are:

  • Developing and implementing a systematic process to respond to data requests
  • Policy and procedures around IRB
  • Security and privacy policies, procedures, and communications to staff
  • Revision of the DUA templates and expansion of agreement types to accommodate diverse projects


  • No labels