Bill
S 34
Establishes a Massachusetts Open Data Standard and portal; state/municipal agencies publish public data in machine-readable formats with APIs, improving transparency and innovation.
Status: Introduced January 8, 2025. Referred to committee (records show referral to Elections and to Advanced Information Technology, the Internet and Cybersecurity); hearing scheduled 7/10/2025; later reported favorably and referred to Senate Ways & Means (record contains some inconsistent/duplicated actions — see Procedural Notes).
Purpose
- Establish a statewide open data standard and an open data portal so state and municipal agencies publish public data in machine-readable, standardized formats that support public access, analysis, and reuse.
- Improve government transparency, agency accountability, public knowledge, and economic opportunities created by accessible government data.
Key definitions (selected)
- “Public data”: data collected by a public agency that is otherwise subject to disclosure under existing public records law.
- “Open data”: public data made readily available online using best-practice structures and formats.
- “Open data portal”: Internet site maintained by/for the Commonwealth to publish data.
- “Chief data officer”: the Commonwealth officer established under chapter 7D, §4A (charged with implementation).
Major provisions and requirements
- Chief data officer responsibilities
- Create an inventory of public data held by state and municipal agencies.
- Establish and maintain an open data portal (may reuse existing portals).
- Appoint at least two open-data/IT experts within the Executive Office of Technology Services and Security as needed.
- Develop the Massachusetts Open Data Standard, a technical standards manual, and data-security standards.
- Maintain a public online forum for feedback.
- Massachusetts Open Data Standard requirements (high level)
- Agencies must publish public data on the designated portal in standardized, machine-readable formats that permit analysis and aggregation across datasets.
- Data should be updated as often as necessary to preserve integrity and usefulness.
- Support for APIs, searchable access (including via third-party tools), and public notification of updates where possible.
- Data should be available without registration or licensing wherever feasible.
- Emphasis on user-centered design, agile management, open standards, and protection of personally identifying information.
- Agency reporting and planning
- If an agency cannot publish certain public data, it must report what data, why it cannot be made available, and an expected date for posting.
- Annually (by December 1) each state agency must submit and publish a strategic plan (up to 5 years) describing its public data holdings and how IT/telecom projects, budgets, contracts and capital plans support the Open Data Standard and related efficiencies.
- Municipal assistance
- Chief data officer may work with municipal agencies to help adopt the standard and share data.
Limits and interactions with existing law
- The bill explicitly preserves existing obligations under chapter 4 §7 and chapter 66 (public records law); it does not alter those disclosure duties.
- Includes provisions to protect personal identifying information and create data-security standards.
Who would be affected
- Directly: State agencies and municipal agencies required to inventory, standardize, and publish public data.
- Indirectly: Residents, journalists, researchers, developers, private-sector firms using government data, and vendors providing data/IT services.
- Potential resource impact: agencies may need staff time, technical work, and possible funding to inventory, convert, secure, and maintain datasets and APIs.
Procedural notes and data limits
- The provided bill text is complete through Section 5; Section 6 is truncated in the supplied document, so downstream provisions (if any) could not be summarized.
- Legislative action records provided include multiple, sometimes conflicting entries (duplicate referrals, a “House concurred” entry for a Senate bill, and sponsor listings that appear inconsistent with Massachusetts state practice). These discrepancies should be checked against the official legislative website for current status and sponsor accuracy.
Potential impacts (summary)
- Benefits: greater transparency, easier public access to government data, potential for innovation and economic activity.
- Costs/risks: implementation costs for agencies, need for sustained technical capacity, and careful management of privacy/security and exemptions for data that cannot/should not be published.
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.
