Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Policy index / Open data policy index
Open data policy index

Tulsa Executive Order 2015-07: Open Data Program and Advisory Board (2015)

Tulsa Executive Order 2015-07: Open Data Program and Advisory Board (2015)

Tulsa's Executive Order 2015-07 created an open data program and an Open Data Advisory Board chaired by the CIO, defined open data to include city software source code, and set criteria for choosing datasets, building on the city's 2013 open data resolution.

What the order does

The order builds on Resolution 7991, which Tulsa adopted in May 2013 to support open data, open standards and open source software. It moves from statement to structure: it defines open data, confirms the city's existing portal as the authoritative source, and creates an Open Data Advisory Board (ODAB) to write an implementation plan.

One unusual feature is that the order defines "data" to include software source code developed or maintained by or for the city, which puts open source releases inside the open data program.

Key provisions

  • Definitions. Separate definitions for protected and sensitive information. Open data must be free of legal limits on reuse and published in open formats.
  • Portal. The city's existing portal, run by IT under the CIO, is the authoritative source.
  • Advisory board. The ODAB is chaired by the CIO and made up of department data coordinators. It sets timetables and drafts an implementation plan for the mayor's approval.
  • Selection criteria. The board considers whether a dataset is reliable, often requested under the Open Records Act, useful for accountability or service delivery, informative about city operations, or likely to create economic opportunity.
  • Updates. Departments make reasonable efforts to update their datasets regularly.

Which guidelines it reflects

The annotated text covers twenty guidelines, including prioritization, thoughtful formats, open code, archival material, real-time updates, funding and future review.

Why this matters for your business data

Tulsa's selection criteria, which favor data that is reliable, in demand and capable of creating economic opportunity, are close to how buyers judge private datasets. Before you share operational data, ask the same questions. Our guide from open data policy to data value expands on them, and the valuation calculator gives a first estimate.

We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

What is Tulsa's Open Data Advisory Board?

A board created by Executive Order 2015-07, chaired by the city's Chief Information Officer, whose members are data coordinators from each department. It advises on the open data portal, sets timetables and prepares an implementation plan with detailed policies for the mayor to approve.

Does Tulsa treat source code as open data?

Yes. The order's definition of data explicitly includes software source code developed or maintained by or for the city, and its definition of open data covers source code published online. That ties the program to the city's earlier commitment to open source software.

How does Tulsa decide which datasets to publish?

The advisory board weighs whether a proposed dataset is reliable and accurate, often requested under the Oklahoma Open Records Act, supportive of accountability or service delivery, helpful to public understanding of the city, and likely to create economic opportunity.

Guidelines this policy reflects

Sources

  1. Original executive order (historical; may no longer resolve)
  2. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.