PEPFAR Data Governance

August 9, 2017

U.S. DEPARTMENT OF STATE

Contents
1. Purpose and Scope .............................................................................................................................. 3
2. Policy Directive and Background ......................................................................................................... 3
2.1 Accountability ............................................................................................................................... 3
2.2 Transparency................................................................................................................................. 3
3. PEPFAR Data Governance Structure ................................................................................................... 3
4. PEPFAR Data ....................................................................................................................................... 4
4.1 PEPFAR data streams .................................................................................................................... 4
4.2 PEPFAR Data Systems .................................................................................................................... 5
5. Data Access ......................................................................................................................................... 6
5.1 Improving access to data for HIV epidemic control....................................................................... 6
5.2 Redaction ...................................................................................................................................... 7
5.3 Geographic masking ...................................................................................................................... 7
5.3.1 Data generated at foreign military sites ..................................................................................... 8
5.3.2 Data on key populations ............................................................................................................ 8
5.3.3 Data on Peace Corps volunteers ................................................................................................ 8
5.4 Data access within PEPFAR ........................................................................................................... 8
5.5 Data access platforms ................................................................................................................... 8
5.6 Data formats ................................................................................................................................. 9
5.7 Data access roles and responsibilities ........................................................................................... 9
6 Data Security ...................................................................................................................................... 10
7 Data Quality and Standards ............................................................................................................... 11
7.1 Objectivity and utility .................................................................................................................. 11
7.2 Integrity....................................................................................................................................... 11
7.3 Requests for corrections ............................................................................................................. 12
7.4 Data quality roles and responsibilities ........................................................................................ 12
7.5 Documentation and metadata .................................................................................................... 12
8 References ......................................................................................................................................... 14
1. Purpose and Scope
Data, and the information derived from data, are assets for the U.S. President’s Emergency Plan for AIDS
Relief (PEPFAR), its partners, the academic and scientific communities, and the public at large. This
document establishes general policy for managing data assets through the PEPFAR program. The
PEPFAR program leverages data to improve our ability to achieve HIV epidemic control and increase
transparency and accountability. The utility of data used for decision-making hinges on the degree to
which data meet established quality criteria and are securely organized and accessible.

This document complements relevant policy directives and existing policy documents and guidance from
the Office of Management and Budget (OMB) and PEPFAR implementing agencies: Department of State
(DoS); U.S. Agency for International Development (USAID); Department of Defense (DoD); Department
of Commerce (DoC); Department of Labor (DoL); Department of Health and Human Services (HHS);
Peace Corps and; Department of the Treasury. The document further outlines roles and responsibilities
for critical data management functions that support the PEPFAR program.

2. Policy Directive and Background

White House Executive Order 13642, OMB Circular A-130, and the OMB Open Data policy M‐13‐13 set
relevant policy for the management of government information.1, 2, 3

2.1 Accountability
PEPFAR meets and exceeds the reporting requirements established by the PEPFAR Stewardship and
Oversight Act of 20134 (Public Law 113-56) the related Senate Foreign Relations Committee’s Report 5 on
those requirements (S. Rept. 113-112) and the Foreign Aid Transparency and Accountability Act. 6, 7

2.2 Transparency
According to OMB Circular A-130, “government information” refers to information “created, collected,
processed, disseminated, or disposed of, by or for the Federal Government.” This directive and data
policy set the guiding principles of PEPFAR to value privacy, transparency and openness.

3. PEPFAR Data Governance Structure

The U.S. Global AIDS Coordinator & U.S. Special Representative for Global Health Diplomacy authorizes
PEPFAR data governance policy.

1 White House Executive Order 13642, Making Open and Machine Readable the New Default for Government Information.
http://www.gpo.gov/fdsys/pkg/FR-2013-05-14/pdf/2013-11533.pdf
2 Office of Management and Budget. OMB Circular A-130, Revised. Management of Federal Information Resources,

https://www.whitehouse.gov/omb/circulars_a130_a130trans4
3 Executive Office of the President. OMB Memorandum M-13-13 Open Data Policy-Managing Information as an Asset.

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2013/m-13-13.pdf
4 PEPFAR STEWARDSHIP AND OVERSIGHT ACT OF 2013, 127 STAT. 648 PUBLIC LAW 113–56—DEC. 2, 2013.

https://www.congress.gov/113/plaws/publ56/PLAW-113publ56.pdf
5 PEPFAR STEWARDSHIP AND OVERSIGHT ACT OF 2013 (S. 1545). https://www.congress.gov/113/crpt/srpt112/CRPT-

113srpt112.pdf
6
“H.R.3766 — 114th Congress: Foreign Aid Transparency and Accountability Act of 2016.”
https://www.congress.gov/bill/114th-congress/house-bill/3766/
7
"S.2184 — 114th Congress: Foreign Aid Transparency and Accountability Act of 2015", https://www.congress.gov/bill/114th-
congress/senate-bill/2184
The All Things Data Steering Committee (ATDSC) consists of representatives from the implementing
agencies and is chaired by the Deputy Coordinator for Program Results and Impact Monitoring for
Epidemic Control (PRIME) at the U.S. Department of State’s Office of the U.S. Global AIDS Coordinator
and Health Diplomacy (S/GAC). ATDSC provides strategic direction and guidance for all PEPFAR data
collection efforts. The committee chair advises the Coordinator.

ATDSC develops, reviews, and approves data governance policies, processes, and standards, which data
stewards implement. The term “data steward” refers to a role assigned to staff under their existing
position that ensures adherence to data management policies. PEPFAR data stewardship encompasses a
set of roles that a variety of individuals occupy in relation to data at different points in data lifecycles.
Each data stream has its own lifecycle and is subject to data governance policy and data stream-specific
supplementary guidance that is authored by a primary data steward, which is a designated team or
working group. Questions about PEPFAR Data Governance policy should first go to the primary data
steward, described below, and then be posed to ATDSC as necessary.

4. PEPFAR Data
The main focus of this document is on the dissemination of substantive information (i.e., data sets,
reports, studies, and summaries) generated with PEPFAR support rather than information prepared for
the management and operations of PEPFAR. This policy does not apply to press releases or similar
communications. This policy does not cover data curated or owned by other entities outside of PEPFAR,
such as data shared with PEPFAR but owned by a partner government.

4.1 PEPFAR data streams

Listed below are the primary PEPFAR data streams, sources of data stream-specific documentation, and
the respective primary data stewards. Additional documentation catalogs specific, detailed data
governance considerations, such as data approval processes, access and roles and responsibilities
pertaining to these data streams.

 Monitoring, Evaluation, and Reporting Indicators (MER): PEPFAR program indicators for targets
and results.
o Primary Data Steward: PRIME
o Documentation: Annual Program Reporting Guidance, PEPFAR Monitoring, Evaluation,
and Reporting Indicator Reference Guide8, and MER Data Life Cycle
 Site Improvement Through Monitoring System (SIMS): data from standardized tools that assess
adherence to PEPFAR standards of care and service delivery.
o Primary Data Steward: Program Quality
o Documentation: SIMS Data Life Cycle
 Expenditure Analysis: the amount of funds spent by PEPFAR implementing partners via
Country/Regional Operational Plans.
o Primary Data Steward: PRIME
o Documentation: Expenditure Analysis of PEPFAR Programs Guidance

8
PEPFAR Guidance. https://www.pepfar.gov/reports/guidance/
  Budget: initial planned funding levels approved each year in the PEPFAR Country Operational
Plans (COP) and Region Operational Plans (ROP). A COP/ROP is the vehicle for documenting U.S.
government annual investments and program activities in HIV/AIDS for each PEPFAR operating
unit (country or region).
o Primary Data Steward: Country Oversight and Accountability
o Documentation: Country Operational Plan Guidance9
 Organization unit (OU) hierarchy: geographic relationships, in tabular form, that define the
arrangement of administrative units and health facilities in DATIM, which is PEPFAR’s instance of
DHIS2. 10
o Primary Data Steward: PRIME
 Spatial Data: points lines and polygons that capture the geometry of administrative units and
health facilities.
o Primary Data Steward: PRIME
o Documentation: Spatial Data Lifecycle Guidance
 Sustainability Index and Dashboard (SID): a tool completed periodically by PEPFAR teams and
partner stakeholders to sharpen the understanding of each country’s sustainability landscape
and to assist PEPFAR and others in making informed HIV/AIDS investment decisions.
o Primary Data Steward: Financial and Programmatic Sustainability
 Surveys and Surveillance: data on epidemic features such as HIV prevalence; national HIV
incidence; pediatric HIV prevalence; HIV viral load suppression; behavioral prevalence in the
general population; behavioral prevalence among high-risk populations; and transmission of
drug resistant HIV strains.
o Primary Data Steward: Agency-specific
o Documentation: Agency-specific guidance governs these data streams.
 Implementation Science: research that informs delivery and scale-up of efficacious
interventions to improve HIV prevention, care, and treatment
o Primary Data Steward: Agency-specific
o Documentation: Agency-specific guidance governs these data streams.
 Evaluations: the systematic collection and analysis of information about the characteristics,
outcomes, and impact of programs and projects
o Primary Data Steward: Agency-specific
o Documentation: Evaluations Standards of Practice11

4.2 PEPFAR Data Systems

Most PEPFAR data stream lifecycles originate in transactional systems such as PEPFAR's health
information system, Data for Accountability, Transparency and Impact (DATIM). These systems are
optimized for data collection and data entry. The PEPFAR Data Hub (PDH) is the data warehouse, or

9
PEPFAR Guidance. https://www.pepfar.gov/reports/guidance/
10
DHIS2 Documentation. Organisation units. https://docs.dhis2.org/2.22/en/user/html/ch04.html
11
PEPFAR Guidance. https://www.pepfar.gov/reports/guidance/
repository, for data collected by transactional systems across the PEPFAR program. PDH consolidates,
stores, and packages PEPFAR data for internal analysis and review as well as public dissemination.

Figure 1 briefly describes the purpose of each of PEPFAR’s information systems and depicts their
interrelationship.

Figure 1. The PEPFAR Data Hub, transactional systems, business intelligence, and analytic tools.

5. Data Access
5.1 Improving access to data for HIV epidemic control
The PEPFAR program makes data accessible to maintain transparency and improve our ability to achieve
HIV epidemic control. Data access policy allows the PEPFAR community to take full advantage of its data
resources and responsibly expand public access to valuable information. PEPFAR encourages its
partners, the academic and scientific communities, and the public at large to make broad use of PEPFAR
data for innovative scientific, technological, analytical, and other applications.

A key feature of data accessibility is whether data are releasable to the public or must remain internal to
the United States Government. PEPFAR uses the OMB categorization that describes data as public,
restricted public, or non-public.12

 Public: Data asset is or could be made publicly available to all without restrictions.

12
Chief Information Officer. Supplemental Guidance on the Implementation of M-13-13 “Open Data Policy – Managing
Information as an Asset”. https://project-open-data.cio.gov/implementation-guide/
  Restricted Public: Data asset is available under certain use restrictions (e.g. made available to
select researchers under certain conditions).
 Non-public: Data asset is not available to members of the public and is only available for internal
use by the Federal Government.

5.2 Redaction
PEPFAR publishes country operations plans with redaction of procurement-sensitive funding
information for awards that have not yet been made. Procurement-sensitive data become open when
the decision is announced.

5.3 Geographic masking

The Open Government Directive and Freedom of Information Act (FOIA) provide exceptions to this
presumption of openness. There are valid legal, privacy, confidentiality, and security considerations
related to some data that PEPFAR curates - such as patient-level data, data concerning foreign militaries,
or the exact locations where vulnerable populations congregate – that are inappropriate for wide
circulation. To accommodate exceptions to open data, authoritative versions of PEPFAR data streams
are published at different levels of granularity for internal and external consumers.

Some data that PEPFAR collects and manages are sensitive and not appropriately releasable to the
public. PEPFAR attenuates risks associated with personally identifiable information (PII) and other
sensitive data through geographic aggregation. The most granular data used for routine planning and
monitoring are deidentified through aggregation to the site level, which is either a clinical site or a low-
level administrative unit (e.g. a district).13 All data below this level are non-public or restricted public and
should be shared only with groups identified in data use agreements or an ethics board-approved
protocol. Table 1 describes for the primary data streams the level of data granularity associated with
each access level.

Table 1. Access categories and the primary PEPFAR data streams

13
National Institute of Standards and Technology. Guide to Protecting the Confidentiality of Personally Identifiable Information
(PII). Special Publication (NIST SP) - 800-122, https://www.nist.gov/publications/guide-protecting-confidentiality-personally-
identifiable-information-pii
5.3.1 Data generated at foreign military sites
A portion of PEPFAR data relates to foreign militaries. PEPFAR supports military-to-military (mil-mil),
civilian-to-military (civ-mil), and military-to-civilian (mil-civ) activities.

 Military-military (mil-mil) are DoD programs with a primary focus to serve military populations
at military site locations. Beneficiaries may include civilians who are provided with services at
military sites.
 Civilian – military (civ – mil) are non-DoD programs serving military populations at military sites.
Beneficiaries may include civilians who are provided with services at military sites.
 Military-civilian (mil-civ) have a primary focus to serve civilian populations at civilian site
locations. These may be DOD or non-DOD managed program activities.

PEPFAR records data on mil-civ activities at the level of granularity specified by the data stream with no
special exception. All mil-mil and civ-mil data, at any level of aggregation, is non-public.

5.3.2 Data on key populations

Key populations are especially vulnerable to stigma, harassment, abuse, and discrimination and
sometimes subject to criminalization. These groups include gay men and other men who have sex with
men, people who inject drugs, sex workers, and transgender persons. All data collection and publication
related to key populations is subject to heightened attention to privacy, confidentiality, and security.
PEPFAR does not make public site level data on key populations. All PEPFAR data products are reviewed
for key population security.

5.3.3 Data on Peace Corps volunteers

PEPFAR does not make public data that can link Peace Corps volunteers to a specific site or geographic
area that may identify a volunteer.

5.4 Data access within PEPFAR

PEPFAR promotes access to authoritative versions of data throughout the program. Prior to reaching an
authoritative state, internal access to data is defined by roles. Data providers have access to data that
they enter into PEPFAR systems. As data move from through the approval process within a given data
stream, the number of people with access to the data increases, but always in relation to a defined
stewardship role, such as implementing partner data clerk, GIS Specialist, DATIM Site Administrator,
Strategic Information Liaison, or Strategic Information or Expenditure Analysis Advisor. Access to several
data streams is governed by the PEPFAR Data Calendar. 14

5.5 Data access platforms

PEPFAR implements open data policy through the Panorama Spotlight, PEPFAR.gov, and Data.gov.
Panorama Spotlight is the primary platform for making authoritative PEPFAR data available to the
public.15 Unless otherwise noted, data that appear on the public dashboard are in the public domain
worldwide through the CC0 1.0 Universal Public Domain Dedication.16 PEPFAR data sets should have a

14 PEPFAR Data Calendar, https://www.pepfarii.net/

15 PEPFAR Dashboards, https://data.pepfar.net/
16 CC0 1.0 Universal Public Domain Dedication, http://creativecommons.org/publicdomain/zero/1.0
metadata record on Data.gov. Other tools and platforms used within the program include DATIM, FACTS
Info, PROMIS, and ArcGIS Online. Specific data are sometimes available in more than one place.

5.6 Data formats

Open data formats support the widest array of potential users. In keeping with open data principles,
PEPFAR publishes data sets in machine readable, non-proprietary formats (e.g. comma-separated values
(csv), shapefile (shp), etc.) for all data streams.17 , 18

5.7 Data access roles and responsibilities

5.7.1 The All Things Data Steering Committee

The All Things Data Steering Committee advises the chair on the state of data access, including which
PEPFAR data can responsibly and legally be made available to the public. This involves processing of
agency, implementing partner, or other data access requests using data sharing agreements, data
security categorization, and cybersecurity mechanism reviews. This group considers possible
justifications for exemptions and documents reasons why specific data assets or components of a data
asset should not be made public. The group also prioritizes data for release. Other issues the group
addresses are update schedules and additional data beyond the primary data streams. Finally, this group
works to see that PEPFAR data, cleared for public release, reside on open platforms such as Data.gov.

5.7.2 Program Results and Impact Monitoring for Epidemic Control (PRIME)
S/GAC’s PRIME Team is responsible for maintaining systems that assure role-based access to PEPFAR
data. These systems, tools, repositories, and business intelligence platforms include The PEPFAR Data
Hub, Panorama Spotlight, Panorama, DATIM, and ArcGIS Online.

5.7.3 Agencies
Implementing agencies should ensure that PEPFAR-supported contracts, grants, cooperative
agreements, and other instruments include existing agency-specific data access-related guidance and
that recipients fulfill those requirements. Where applicable (e.g. SIMS, evaluations, implementation
science, surveillance) agencies submit, in machine readable format, complete and approved data
according to the calendar for each data stream.

5.7.4 Country teams

PEPFAR Country Teams submit complete, approved data according to the calendar for each data stream,
including evaluation. Country Teams confirm that mil-mil, civ-mil and key population data are
appropriately reported. Teams should also monitor site lists for explicit reference to key populations
(e.g. Sex Worker Friendly Clinic #8), work with implementing partners to identify the true site name, and
update DATIM accordingly.

17
Project Open Data, Principles. https://project-open-data.cio.gov/principles/
18
Data.gov. A Primer on Machine Readability for Online Documents and Data. https://www.data.gov/developers/blog/primer-
machine-readability-online-documents-and-data
5.7.5 Implementing partners/grantees
PEPFAR fund recipients provide quality data in machine readable formats according to the required
reporting calendar and data definitions for each data stream.

6 Data Security
Data security ensures appropriate access to data through the implementation of risk-based security
requirements.19 Security addresses physical, electronic, and procedural aspects of protecting
information. Security protects data from inadvertent or malicious inappropriate disclosure and non-
availability of data due to system failure and user error.

PEPFAR adheres to standards for categorizing information and information system security according to
a range of risk levels. PEPFAR also adheres to information security requirements (i.e., management,
operational, and technical security controls) for information and information systems in each such
category.20 , 21, 22

Data stream-specific documentation traces the chain of custody from data generation to the data’s state
of rest and should address the following data security components:

 Responsibilities
 Data collection and use
 Data sharing and release
 Physical security
 Electronic data security
 Audit and monitoring
 Retention23

An Interagency System Security Forum (ISSF) reviews PEPFAR technology as it pertains to security and
privacy implementations and makes recommendations to the ATDSC on technology configuration, data
security standards, policy, and procedures. The ISSF will be chaired by the Health Information System
Lead at S/GAC, with representation from each agency, plus additional members including the agencies’

19 UNAIDS. 2006. Guidelines on Protecting the Confidentiality and Security of HIV Information.
http://data.unaids.org/pub/manual/2007/confidentiality_security_interim_guidelines_15may2007_en.pdf
20 National Institute of Standards and Technology. Standards for Security Categorization of Federal Information and Information

Systems (Federal Information Processing Standard [FIPS] 199). http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-

final.pdf
21 National Institute of Standards and Technology. Special Publication SP 800-60 Vol. I Rev. 1, Guide for Mapping Types of

Information and Information Systems to Security Categories (August 2008). http://dx.doi.org/10.6028/NIST.SP.800-60v1r1

22 National Institute of Standards and Technology. Special Publication SP 800-60 Vol. II Rev. 1, Appendices to Guide for Mapping

Types of Information and Information Systems to Security Categories (August 2008). http://dx.doi.org/10.6028/NIST.SP.800-
60v2r1
23 Executive Office of the President. OMB Memorandum M-12-18 Managing Government Records Directive.

https://www.archives.gov/records-mgmt/m-12-18.pdf
Chief Information Security Officers and others with relevant security or privacy expertise. The ISSF meets
monthly or as needed.

7 Data Quality and Standards

A data driven approach requires quality data. PEPFAR is committed to the collection and dissemination
of accurate, reliable, and unbiased information in a clear, complete, and unbiased manner. PEPFAR
adopts the OMB Guidelines for Ensuring and Maximizing the Quality, Objectivity, Utility, and Integrity of
Information Disseminated by Federal Agencies.24 OMB Guidelines require basic information quality
standards and note that the more important the information, the higher the standard to which it should
be held. PEPFAR weighs the costs and benefits of information quality in all of its data streams and is
committed to creating and managing data that have objectivity, utility, and integrity.

PEPFAR data that are influential scientific, financial, or statistical information should be reproducible
according to commonly accepted scientific, financial, or statistical standards. PEPFAR data that are for
internal use only should undergo rigorous, documented robustness checks. Quality standards for
PEPFAR data appear in data stream-specific documentation.

7.1 Objectivity and utility

Primary data stewards take the following steps prior to data dissemination to assure objectivity and
utility of PEPFAR data:

 Prepare a draft of the data set or document after consulting the necessary parties, including
government and non-government sources, as appropriate;
 Determine and assure the accuracy and completeness of source data;
 Determine the expected uses by the government and public;
 Determine necessary clearance points;
 Determine where the final clearance decision shall be made;
 Determine whether peer review would be appropriate and, if necessary, coordinating such
review;
 Obtain clearances; and
 Overcome delays and, if necessary, present the matter to higher authority.

7.2 Integrity
Several administrative layers ensure the integrity of PEPFAR data against unauthorized, unanticipated,
or unintentional modification. Together these controls protect the security of PEPFAR information (see
Data Security above).

PEPFAR data systems employ role-based access to prevent unauthorized modification of data. Several
key data streams are governed by the PEPFAR Data Calendar (see Data Access above), which promotes
integrity by setting clear expectations for when systems are open or closed for data entry and revision.25

24 OMB, Guidelines for Ensuring and Maximizing the Quality, Objectivity, Utility, and Integrity of Information Disseminated by
Federal Agencies, https://www.gpo.gov/fdsys/pkg/FR-2002-02-22/pdf/R2-59.pdf
25 PEPFAR Data Calendar, https://www.pepfarii.net/
7.3 Requests for corrections
When PEPFAR receives information from the public that raises questions about the quality of the
information it has disseminated, PEPFAR duly considers corrective action. The purpose of this corrective
action is to serve the genuine and valid needs of PEPFAR without disrupting PEPFAR processes, and to
deal with information quality matters, not to resolve underlying substantive policy or legal issues.
“Affected” persons are those who may benefit or be harmed by the disseminated information. This
includes both: (a) persons seeking to address information about themselves or about other persons to
which they are related or associated; and (b) persons who use the information.

Persons seeking to correct information affecting them that was publicly disseminated by PEPFAR may
submit a Petition for Correction addressed to SGACPublicAffairs@state.gov or:

Office of the U.S. Global AIDS Coordinator and Health Diplomacy

U.S. Department of State
SA-22, Room 10300
Washington, DC 20522-2210

7.4 Data quality roles and responsibilities

7.4.1 The All Things Data Steering Committee

The All Things Data Steering Committee provides strategic guidance on data quality.

7.4.2 Program Results and Impact Monitoring for Epidemic Control

PRIME authors PEPFAR-specific data quality guidance and manages the administration of the PEPFAR
Data Hub, DATIM, Panorama, and the Data Hub.

7.4.4 Agencies
Agencies implement PEPFAR-specific and their respective information quality guidelines.26 27

7.4.5 Country teams

Country teams are responsible for following pre-dissemination review procedures.

7.4.6 Implementing partners/grantees

PEPFAR fund recipients provide accurate data in machine readable formats according to the required
reporting calendar for each data stream. PEPFAR fund recipients also perform data quality audits to
ensure compliance with data quality guidance.

7.5 Documentation and metadata

Per OMB guidance, PEPFAR implementing agencies maintain an enterprise data inventory that includes
data assets created, collected, and managed through PEPFAR.28 Data stream-specific documentation

26 USAID. ADS 578, Information Quality Guidelines. https://www.usaid.gov/sites/default/files/documents/1868/578.pdf

27
U.S. Department of Health and Human Services (HHS). Guidelines for Ensuring and Maximizing the Quality, Objectivity,
Utility, and Integrity of Information Disseminated to the Public. https://aspe.hhs.gov/report/hhs-guidelines-ensuring-and-
maximizing-quality-objectivity-utility-and-integrity-information-disseminated-public
28
Executive Office of the President. OMB Memorandum M-13-13 Open Data Policy-Managing Information as an Asset.
https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2013/m-13-13.pdf
should include introductory materials that orient consumers to each of the data streams. Authoritative
data set should have accompanying metadata. Metadata should include the following elements: Title,
Description, Tags (Keywords), Last Update, Publisher, Contact Name, Unique identifier, Public Access
Level, License, and Theme. 29

Known issues are documented in data release notes that accompany data sets. A data dictionary should
accompany data sets to support appropriate use of PEPFAR data.

29U.S. Chief Information Officer. Project Open Data. Metadata Resources for Schema v1.1. https://project-open-
data.cio.gov/v1.1/metadata-resources/
8 References
U.S. Department of Health and Human Services (HHS). Guidelines for Ensuring and Maximizing the
Quality, Objectivity, Utility, and Integrity of Information Disseminated to the Public,
https://aspe.hhs.gov/report/hhs-guidelines-ensuring-and-maximizing-quality-objectivity-utility-and-
integrity-information-disseminated-public

Office of Management and Budget. OMB Circular A-130, Revised. Management of Federal Information
Resources, https://www.whitehouse.gov/omb/circulars_a130_a130trans4

Office of Management and Budget. OMB Memorandum M-13-13 Open Data Policy-Managing
Information as an Asset.
https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2013/m-13-13.pdf

Office of Management and Budget. Guidelines for Ensuring and Maximizing the Quality, Objectivity,
Utility, and Integrity of Information Disseminated by Federal Agencies. Federal Register / Vol. 67, No. 36
/ Friday, February 22, 2002 / Notices. https://www.gpo.gov/fdsys/pkg/FR-2002-02-22/pdf/R2-59.pdf

UNAIDS. 2006. Guidelines on Protecting the Confidentiality and Security of HIV Information.
http://data.unaids.org/pub/manual/2007/confidentiality_security_interim_guidelines_15may2007_en.p
df

U.S. Chief Information Officer. Project Open Data. Metadata Resources for Schema v1.1. https://project-
open-data.cio.gov/v1.1/metadata-resources/

U.S. Chief Information Officer. Project Open Data. Open Data Principles. https://project-open-
data.cio.gov/principles/

U.S. Department of State Open Data Plan, IRM. November 12, 2013.
http://www.state.gov/documents/organization/217997.pdf

USAID. ADS 578, Information Quality Guidelines,

https://www.usaid.gov/sites/default/files/documents/1868/578.pdf

White House Executive Order 13642, Making Open and Machine Readable the New Default for
Government Information. http://www.gpo.gov/fdsys/pkg/FR-2013-05-14/pdf/2013-11533.pdf