Data governance vs data management: who decides and who does
The difference between setting the rules for an organization's data and carrying them out, the roles involved, and what "good data" means.
What are data governance and data management?
In DAMA's body of knowledge, data governance is the exercise of authority and control (planning, monitoring and enforcement) over the management of data assets. Data management is the development, execution and supervision of the plans, policies, programs and practices that deliver, control, protect and enhance the value of data throughout its life. Governance sits in the middle of DAMA's framework, with the areas of data management around it: architecture, modelling, storage and operations, security, integration, documents and content, reference and master data, warehousing and business intelligence, metadata and data quality.
In healthcare the wider term information governance is also used (AHIMA), covering all information and records, including their retention, legal hold and disposal, not only structured data.
How do data governance and data management differ?
| Data governance | Data management | |
|---|---|---|
| Purpose | Decide the rules and who may make which decisions about data | Carry out those rules in systems and daily work |
| Main question | What should be done, and who decides? | How is it done? |
| Outputs | Policies, standards, agreed definitions, decision rights, quality targets, issue resolution | Databases, interfaces, backups, access controls, data quality checks, reports |
| Who | A governance council or committee led by the business and clinical leaders, data owners and stewards | IT and data teams: database administrators, integration and reporting analysts, data custodians |
| Example | The committee agrees one definition of a "30-day readmission" for every report | The reporting team builds that definition into the data warehouse and every report that uses it |
The two need each other: governance without management is policy on paper, and management without governance builds systems in which each department defines the same thing differently.
What are the data owner, the data steward and the data custodian?
- Data owner: a senior business or clinical leader who is accountable for a data domain (for example patient demographics or laboratory results), approves who may access it and for what, and decides its policies.
- Data steward: a person close to the data's use who is responsible for its definitions, quality and correct use day to day: maintaining the definitions, resolving quality issues, answering questions about what a field means.
- Data custodian: usually IT, responsible for the technical safekeeping of the data: storage, security controls, backup and recovery, applying the access the owner approved.
A common pattern is that the owner decides, the steward looks after the meaning and quality, and the custodian looks after the systems that hold it. Organizations name these roles differently; the separation of decision, meaning and safekeeping is what matters.
What makes data "good quality"?
Data quality is fitness for its intended use, usually measured on several dimensions:
- Accuracy: it matches reality (the right allergy, the right weight).
- Completeness: required values are present.
- Consistency: the same fact agrees across systems.
- Timeliness: it is available when needed and up to date.
- Validity: it follows the agreed format and allowed values.
- Uniqueness: one real thing is recorded once (no duplicate patient records).
Quality problems are cheapest to fix at the point of capture: structured fields, validation rules, pick lists bound to standard codes, and training are better than cleaning data afterwards.
Which tools support data governance?
- Data dictionary: each data element with its name, definition, format, allowed values, source and owner.
- Business glossary: the agreed meaning of business and clinical terms, in plain language.
- Metadata management: data about the data: where it comes from, how it is transformed (lineage), who uses it.
- Master data management (MDM): one trusted version of core entities shared across systems, such as patients (the master patient index), providers and locations.
- Data quality monitoring: measures and dashboards against the agreed targets, with a process for resolving issues.
What do candidates get wrong?
- Treating data governance as an IT project. It is led by the business and clinical owners of the data; IT carries out much of the management.
- Confusing owner and custodian. The owner decides who may use the data; the custodian keeps it safe in the systems.
- Equating governance with security. Security is one area governance sets rules for, beside definitions, quality, retention and use.
- Fixing quality only downstream. Cleaning reports leaves the source wrong; quality is built in at capture.
- Leaving definitions to each department. Different definitions of the same measure produce reports that cannot be compared.
Summary for revision
- Governance sets the rules and decision rights; management carries them out.
- Owner is accountable and decides access; steward looks after definitions and quality; custodian keeps the data safe technically.
- Quality dimensions: accuracy, completeness, consistency, timeliness, validity, uniqueness.
- Tools: data dictionary, business glossary, metadata, master data management, quality monitoring.
- Information governance (AHIMA) is wider: all information, including retention and disposal.
Sources
- DAMA International, DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (2017).
- AHIMA, Information Governance Principles for Healthcare (IGPHC).
- ISO/IEC 38505-1, Governance of IT: governance of data.
The site files this concept under the domain Management and Leadership.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.