Enterprise Data Management: Building a Scalable Framework

Data management at enterprise scale is the coordinated practice of governing, architecting, and operating data as a strategic asset across an entire organization. For students, researchers, life-science professionals, and informed general readers, this framework addresses a central question: how does an organization move from fragmented, project-level data handling to a coherent enterprise-wide system that supports decision-making, compliance, and innovation? The practical outcome of this article is a maturity model self-assessment and a governance framework diagram that any organization can adapt to its own context.

The Enterprise Data Management Problem

Organizations across sectors face a common challenge: data accumulates faster than the systems and practices needed to manage it. In clinical and translational research, data science is often integrated with data collection at the point of origin, which contrasts with settings where data scientists work in isolation from those who generate the data. This integration creates both opportunity and complexity, because effective use of data science techniques requires innovation in how data are organized and managed across the enterprise [10].

The stakes are substantial. Drug discovery requires scientists from wide-ranging disciplines to work together in a coordinated fashion, and the success of the entire enterprise depends on the ability to exchange data between functional domains and integrate it in meaningful ways to support the design, execution, and interpretation of experiments [11]. When data management fails, the consequences include documentation deficiencies that trigger regulatory holds, authorization gaps during personnel transitions, fragmentation between regulatory and clinical functions, and reactive compliance postures [14].

The enterprise data management problem is also technical. It involves governance, architecture, operations, and culture. A framework must address all of these dimensions to be scalable and sustainable.

At a Glance: Enterprise Data Management Framework Components

Core Principles of Enterprise Data Management

Data as a Strategic Asset

Organizations that treat data as a strategic asset make different decisions than those that treat data as a byproduct of operations. Data-driven organizations aim to control business decisions based on data, yet many organizations continue to face challenges in fully realizing the benefits of data despite significant investments in digitalization [20]. The gap between investment and benefit often stems from a lack of integrated, systematic, and holistic frameworks to support data stewardship efforts [8].

The strategic view of data requires leadership commitment. Data governance cannot succeed as a bottom-up initiative alone. It requires executive sponsorship, clear accountability, and resources allocated to data management activities. Without this commitment, data management efforts remain fragmented across the data production cycle [7].

Governance Before Technology

Organizations frequently invest in technology before establishing governance, and the results are predictable. Tools without policies, standards, and accountability create new silos instead of solving existing ones. The research on integrated data quality management and information governance emphasizes that there are good theoretical reasons for integrated governance, but there is variable alignment of data quality management, information governance, and organizational objectives across the enterprise [7].

Governance establishes the rules of the road. It defines who can make decisions about data, what standards apply, and how conflicts are resolved. Governance also addresses ethical constraints, particularly in health and research settings where information ecosystems must process data in ways that are aligned with improving health, system efficiency, and patient safety [7].

Architecture Enables Integration

Data architecture determines whether data can flow across the enterprise or whether it remains trapped in departmental silos. The pharmaceutical industry provides instructive examples. One-off solutions built to serve a single purpose for a single set of users create what has been described as a Gordian knot of disconnected systems [11]. A scalable framework requires an architecture that can be extended and leveraged across different application domains.

The Advanced Biological and Chemical Discovery platform at Johnson & Johnson demonstrates this principle. It was designed to bring coherence to how discovery data is collected, annotated, organized, integrated, mined, and visualized. instead of building point solutions, the platform offered a consistent user experience across operational subsystems for managing reagents, reactions, compounds, and assays, with advanced data mining and visualization tools delivered through a common application front-end [11].

Operations Sustain Quality

Data quality is not achieved through architecture alone. It requires ongoing operational attention. The eight practices for data management to enable team data science provide an operational framework that respects how research teams are organized. These practices were applied in a customized version of the open source LabKey platform at the University of Rochester, supporting cohorts that longitudinally track multidomain data from over 3000 subjects. The result was that analytical datasets became more readily available and the bar to interdisciplinary collaboration was lowered [10].

Operations include data quality monitoring, issue tracking, remediation workflows, and performance management. These activities require defined roles and responsibilities, which connects operations back to governance.

Data Governance Framework

Governance Structure and Decision Rights

A governance framework establishes who has authority over data assets and how that authority is exercised. The research on integrated governance identifies the need for alignment between data quality management, information governance, and organizational objectives [7]. This alignment requires a structure that connects executive leadership to operational teams.

The governance structure typically includes several layers. An executive steering committee sets direction and allocates resources. A data governance council develops policies and standards. Domain-specific working groups address the needs of particular business or research areas. Data stewards manage data assets within their domains. This structure ensures that governance decisions are made at the appropriate level and that operational teams have clear guidance.

The centralisation paradox identified in healthcare governance research is relevant here. While decentralization expands formal decision-making authority, the effective exercise of that authority depends on centrally coordinated enabling systems, including digital infrastructure, administrative support, and financial management [16]. Governance frameworks must balance local autonomy with central coordination.

Policies and Standards

Policies translate governance principles into operational requirements. Common policy areas include data classification, data access, data quality, data retention, and data sharing. Standards support policies by defining specific requirements for data formats, metadata, terminology, and quality metrics.

In research settings, standards may align with external requirements. The National Institute of Standards and Technology maintains the Research Data Framework, which addresses the full data lifecycle from planning through preservation and sharing [1]. The EQUATOR Network provides reporting guidelines for health research, which support data quality by ensuring that research methods and results are reported transparently [2]. The NC3Rs Experimental Design Assistant supports researchers in designing experiments that are robust and reproducible [3].

Accountability and Compliance

Governance assigns accountability for data assets. This includes accountability for data quality, data security, data privacy, and regulatory compliance. In regulated industries, governance must support compliance verification and reporting. Recent U.S. federal government directives and scientific organization guidelines have levied specific requirements, increasing the need for a more formal approach to ensuring that stewardship activities support compliance verification and reporting [8].

The Integrated Prospective Regulatory Governance model demonstrates how governance can be embedded as prospective design constraints across the clinical investigation lifecycle. The model includes four components: Prospective Compliance Architecture, Cross-Functional Regulatory Integration, Investigator Lifecycle Management, and Risk-Stratified Submission Strategy. Applied prospectively, the model maintained regulatory authorization continuity across investigator and site transitions, with deviations confined to minor procedural events having no effect on subject safety or data integrity [14].

Data Architecture Framework

Architecture Layers

Enterprise data architecture can be understood in layers. The data source layer includes operational systems, research instruments, and external data feeds. The data integration layer moves data from sources to targets, including extraction, transformation, and loading processes. The data storage layer includes data warehouses, data lakes, and specialized stores. The data access layer provides interfaces for analysts, scientists, and applications. The data governance layer spans all other layers, providing metadata management, data lineage, and policy enforcement.

The architecture must support many different types of scientific technologies generating data of imposing complexity, diversity, and volume [11]. This requires an architecture that is modular and extensible, allowing new data types and sources to be incorporated without disrupting existing capabilities.

Integration Patterns

Integration patterns determine how data flows across the enterprise. Common patterns include point-to-point integration, hub-and-spoke integration, and data virtualization. Point-to-point integration is simple to implement but creates a maintenance burden as the number of connections grows. Hub-and-spoke integration centralizes integration logic but can create a bottleneck. Data virtualization provides real-time access to distributed data without physical movement.

The choice of integration pattern depends on organizational context. The research on enterprise data management frameworks for agile manufacturing emphasizes the need for frameworks that can adapt to changing requirements [27]. Similarly, the unified data management framework for supply chain optimization addresses challenges in enterprise architecture models such as TOGAF, RAMI 4.0, and IBM 4.0 [28]. These models provide different approaches to structuring enterprise architecture, and organizations must select and adapt them to their specific needs.

Metadata and Data Lineage

Metadata is data about data. It includes technical metadata, such as data types and formats, business metadata, such as definitions and ownership, and operational metadata, such as processing history and quality metrics. Metadata management is essential for data discovery, data understanding, and data trust.

Data lineage traces data from its origin through transformations to its final use. Lineage supports impact analysis, troubleshooting, and compliance. When data quality issues are detected, lineage helps identify the source of the problem and the downstream impact.

The research on scientific data stewardship emphasizes the importance of data-centric approaches that support long-term preservation and the use and reuse of digital research data [8]. Metadata and lineage are critical components of stewardship because they enable data to be understood and trusted over time.

Data Operations Framework

Data Quality Management

Data quality management is the operational practice of ensuring that data meets defined quality standards. The research on integrated data quality management and information governance identifies the need for data quality management across the data production cycle [7]. This includes data capture, data processing, data storage, data retrieval, and data sharing.

Data quality dimensions include accuracy, completeness, consistency, timeliness, validity, and uniqueness. Each dimension requires specific measurement approaches. Accuracy measures whether data values are correct. Completeness measures whether all required data are present. Consistency measures whether data values agree across systems. Timeliness measures whether data are current. Validity measures whether data conform to defined formats and ranges. Uniqueness measures whether duplicate records are avoided.

The research on data quality in healthcare settings emphasizes that locally relevant clinical indicators and use of clinical record systems can support clinical governance [7]. This finding supports the importance of context-specific quality measures instead of generic approaches.

Issue Management and Remediation

Data quality issues require systematic management. This includes issue detection, issue logging, issue triage, issue remediation, and issue prevention. Issue detection can occur through automated monitoring, user reports, or periodic audits. Issue logging captures the details of each issue, including the affected data, the nature of the problem, and the impact. Issue triage prioritizes issues based on severity and impact. Issue remediation corrects the data and addresses the root cause. Issue prevention implements controls to avoid recurrence.

The research on process mining in healthcare emphasizes the importance of event data quality for continuous process improvement [22]. Poor event data quality undermines the ability to analyze and improve processes. This finding applies broadly across sectors.

Performance Management

Data operations require performance management to ensure that services meet defined service levels. This includes monitoring data availability, data processing times, and data delivery times. Performance issues can arise from infrastructure constraints, inefficient processing logic, or excessive data volumes.

The research on big data assisted enterprise resource planning emphasizes the importance of efficient resource allocation and use [9]. The Placement-Assisted Resource Management Scheme demonstrated improvements in success rate, reduced switching ratios, smaller resource mitigation ratios, and faster decision times compared to existing approaches [9]. While this research is specific to human resource management, the principle of efficient resource allocation applies to data operations.

Maturity Model Self-Assessment

Maturity Levels

Maturity models provide a structured approach to assessing organizational capabilities and identifying improvement priorities. The Data Management Maturity Model developed using De Bruin's maturity model assessment methodology incorporates key elements of a data-driven organization, emphasizing the interdependencies required to evaluate maturity levels and provide targeted recommendations [20].

Maturity models typically define five levels. Level 1 is initial, where processes are ad hoc and dependent on individual effort. Level 2 is repeatable, where processes are documented and can be repeated. Level 3 is defined, where processes are standardized and integrated. Level 4 is managed, where processes are measured and controlled. Level 5 is optimized, where processes are continuously improved.

The Healthcare Data Management Maturity Model was developed to help healthcare entities determine the as-is state of their healthcare data management and identify components to focus on during improvement endeavors [23]. The model addresses the broad scope of healthcare data management challenges, particularly in developing countries where the challenges are acute.

Assessment Approach

The maturity assessment approach involves several steps. First, define the scope of the assessment, including the organizational units and data domains to be covered. Second, select the maturity model and assessment instrument. Third, collect evidence through interviews, document review, and system inspection. Fourth, score each capability area. Fifth, analyze results to identify strengths and gaps. Sixth, develop an improvement roadmap.

The Master Data Management Maturity Model assessment at the Secretariat of Presidential Advisory Council provides an instructive example. The assessment used a questionnaire filled out by subject matter experts in a group discussion. The result showed that the organization's master data management maturity level was 1, with 61.29 percent of 62 capabilities implemented. This meant that the organization had awareness in the management of master data but could improve to a higher level by implementing the missing capabilities [26].

The spherical fuzzy-based decision model for assessing data management maturity in governmental institutions demonstrates a more sophisticated assessment approach. The study hybridized spherical fuzzy sets with the criteria importance through intercriteria correlation method and the evaluation based on distance from average solution model. The criteria weighting was methodically calculated, and a sensitivity analysis confirmed the robustness of the methodology [21].

Improvement Roadmap

The improvement roadmap translates assessment results into action. It identifies priority improvements based on the gap between current and target maturity levels, the impact of improvements on organizational objectives, and the resources required for implementation.

The Data Management Maturity Model for process mining in healthcare provides an example of how maturity models can be extended to address specific capabilities. The study added a dimension to assess and improve event data quality, presenting different approaches for formal and checkpoint assessments and an embedding of the improvement strategy with examples [22].

The Data Management Maturity Model designed to support digital transformation from an initial level to an optimized one covers organizational structure, systems, data dimensions, and operations. The model includes a maturity scoring system, model architecture, assessment practice, and maturity levels resulting from evaluation. The capabilities are mapped for a data-centric vision, with linkages that bring consistency and traceability [25].

Practical Implementation Steps

Step 1: Establish Governance Foundation

Begin by establishing the governance foundation. This includes securing executive sponsorship, defining the governance structure, and developing initial policies and standards. The governance foundation should address data classification, data access, data quality, and data retention.

The research on integrated prospective regulatory governance demonstrates the value of embedding requirements as prospective design constraints instead of reactive compliance postures [14]. This principle applies broadly. Governance should be designed to prevent issues instead of to respond to them after they occur.

Step 2: Assess Current State

Conduct a maturity assessment to establish the baseline. Use a maturity model that is appropriate for the organizational context. The assessment should cover governance, architecture, operations, and culture.

The maturity assessment should involve subject matter experts from across the organization. The assessment should collect evidence from multiple sources, including interviews, document review, and system inspection. The results should be analyzed to identify strengths and gaps.

Step 3: Design Target Architecture

Design the target architecture based on the assessment results and organizational objectives. The architecture should address data sources, integration, storage, access, and governance. The architecture should be modular and extensible to accommodate future requirements.

The research on enterprise data management frameworks emphasizes the importance of frameworks that can be extended and leveraged across different application domains [11]. The architecture should support this extensibility.

Step 4: Implement Foundational Capabilities

Implement foundational capabilities before expanding to advanced capabilities. Foundational capabilities include metadata management, data quality monitoring, and basic data integration. Advanced capabilities include advanced analytics, data sharing, and automated data quality remediation.

The research on data management practices for team data science emphasizes the importance of making analytical datasets readily available and lowering the bar to interdisciplinary collaboration [10]. Foundational capabilities support this objective.

Step 5: Expand and Optimize

Expand the framework to additional data domains and organizational units. Optimize processes based on performance data and lessons learned. The Plan-Do-Check-Act cycle provides a proven approach to continuous improvement [8].

The research on enterprise risk management frameworks for big data science projects emphasizes the need for risk management in data initiatives [29]. Risk management should be integrated into the framework instead of treated as a separate activity.

Records and Measurements

Key Performance Indicators

Organizations should track key performance indicators to monitor the effectiveness of data management. These indicators should cover data quality, data availability, data usage, and data management efficiency.

Data quality indicators include the percentage of records meeting quality standards, the number of open data quality issues, and the time to resolve data quality issues. Data availability indicators include system uptime, data delivery times, and data access success rates. Data usage indicators include the number of data consumers, the number of data products, and the frequency of data access. Data management efficiency indicators include the cost per data record managed, the time to onboard new data sources, and the percentage of data management tasks automated.

Assessment Records

Maturity assessments should be documented and retained. Assessment records should include the assessment scope, the assessment instrument, the evidence collected, the scores assigned, and the improvement recommendations. These records support progress tracking and provide a basis for future assessments.

The research on data management maturity models emphasizes the importance of quantitative evaluation of how organizations manage their stewardship activities [8]. Assessment records support this quantitative evaluation.

Operational Logs

Data operations should maintain logs of data processing activities, data quality issues, and remediation actions. These logs support troubleshooting, compliance, and continuous improvement.

The research on blockchain integration for data integrity assurance emphasizes the importance of data integrity and access control [13]. Operational logs support data integrity by providing an audit trail of data processing activities.

Common Failure Patterns

Governance on Paper Only

A common failure pattern is governance that exists on paper but is not enforced in daily operations. Policies are developed and approved, but they are not implemented or monitored. This failure pattern often results from insufficient leadership commitment, inadequate resources, or unclear accountability.

The research on integrated governance emphasizes that data quality management and information governance in health services are still fragmented across the data production cycle [7]. This fragmentation reflects the gap between governance on paper and governance in practice.

Architecture Without Governance

Another failure pattern is investing in architecture without establishing governance. Organizations build data platforms and integration systems, but they do not define who is responsible for data quality, who can access data, or what standards apply. The result is that the architecture amplifies existing problems instead of solving them.

The research on enterprise data management frameworks emphasizes the importance of governance in conjunction with architecture [11]. Technology alone does not solve data management problems.

Quality Monitoring Without Remediation

Organizations may implement data quality monitoring but fail to act on the results. Quality issues are detected and logged, but they are not remediated. This failure pattern often results from unclear accountability for remediation or insufficient resources.

The research on data quality management emphasizes the importance of feedback to improve the quality of source data [7]. Monitoring without remediation does not improve data quality.

Maturity Assessment Without Improvement

Organizations may conduct maturity assessments but fail to implement the improvement roadmap. The assessment becomes an end in itself instead of a means to improvement. This failure pattern often results from a lack of ownership for the improvement roadmap or a lack of resources for implementation.

The research on maturity models emphasizes the importance of targeted recommendations for addressing data-related challenges [20]. Recommendations without implementation do not produce improvement.

Limitations and Contextual Considerations

Organizational Size and Resources

The appropriate data management framework depends on organizational size and resources. Small organizations may not have the resources to implement a full enterprise data management framework. They may need to prioritize foundational capabilities and expand over time.

The research on enterprise resource planning emphasizes that the planning of human resources and the management of enterprises consider the organization's size, the amount of effort put into operations, and the level of productivity [9]. This principle applies to data management as well.

Sector-Specific Requirements

Different sectors have different data management requirements. Regulated industries, such as pharmaceuticals and medical devices, have specific compliance requirements. Research organizations have requirements related to data sharing and reproducibility. Government organizations have requirements related to transparency and privacy.

The research on healthcare data management maturity in developing countries emphasizes the need for tailored approaches to data governance given the complexities of balancing public interests with data privacy [21]. This principle applies across sectors.

Technology Constraints

Technology constraints can limit the implementation of data management frameworks. Legacy systems may not support required integration patterns. Data volumes may exceed the capacity of existing infrastructure. Security requirements may limit data sharing.

The research on industrial internet data management emphasizes the challenges of poor data integrity and difficulties in data access [13]. These challenges are often rooted in technology constraints.

Welfare and Safety Context

Data Integrity and Patient Safety

In healthcare and life sciences, data integrity is directly linked to patient safety. Poor data quality can lead to incorrect clinical decisions, delayed treatments, or adverse events. The research on integrated governance emphasizes that ethical constraints exist that require health information ecosystems to process data in ways that are aligned with improving health and system efficiency and ensuring patient safety [7].

Organizations in these sectors must implement data management frameworks that prioritize data integrity. This includes validation of data entry, verification of data processing, and monitoring of data quality.

Regulatory Compliance

Regulatory compliance is a critical driver for data management in regulated industries. The research on integrated prospective regulatory governance identifies documentation deficiencies, authorization gaps, and fragmentation between regulatory and clinical functions as preventable regulatory failures [14]. These failures can trigger clinical holds and delay product development.

Organizations must implement data management frameworks that support regulatory compliance. This includes maintaining accurate records, ensuring data integrity, and providing evidence of compliance.

Research Reproducibility

Data management is essential for research reproducibility. The National Center for Biotechnology Information provides literature resources that support research [4]. PubMed provides access to biomedical literature [5]. These resources support researchers in building on prior work, which requires that data and methods are well documented.

The EQUATOR Network provides reporting guidelines that support transparent reporting of health research [2]. The NC3Rs Experimental Design Assistant supports robust experimental design [3]. These resources support research quality, which depends on data management.

Professional Escalation Criteria

When to Escalate Data Quality Issues

Data quality issues should be escalated when they have significant impact on organizational objectives, when they cannot be resolved within the defined service levels, or when they indicate systemic problems. Escalation criteria should be defined in advance so that operational teams know when to escalate.

Examples of escalation criteria include data quality issues that affect regulatory submissions, data quality issues that affect patient safety, data quality issues that affect financial reporting, and data quality issues that persist despite remediation efforts.

When to Escalate Governance Issues

Governance issues should be escalated when policies are not being followed, when conflicts cannot be resolved at the operational level, or when governance decisions have significant organizational impact. Escalation criteria should be defined in advance so that governance bodies know when to escalate.

Examples of escalation criteria include policy violations that have significant compliance impact, conflicts between organizational units that cannot be resolved, and governance decisions that require executive attention.

When to Escalate Architecture Issues

Architecture issues should be escalated when the architecture cannot support organizational requirements, when integration failures have significant operational impact, or when technology decisions have long-term consequences. Escalation criteria should be defined in advance so that architecture teams know when to escalate.

Examples of escalation criteria include architecture limitations that prevent new data sources from being onboarded, integration failures that affect multiple systems, and technology decisions that require significant investment.

Frequently Asked Questions

What is the difference between data governance and data management?

Data governance establishes decision rights, policies, and accountability for data assets. Data management is the operational practice of implementing governance decisions. Governance defines what should be done, and management does it. Governance without management produces policies that are not implemented, and management without governance produces activities that are not aligned with organizational objectives. The research on integrated governance emphasizes the need for alignment between data quality management, information governance, and organizational objectives [7].

How long does it take to implement an enterprise data management framework?

Implementation time depends on organizational size, complexity, and resources. A foundational framework can be implemented in several months, but full maturity typically requires several years. The maturity assessment provides a baseline, and the improvement roadmap defines the path forward. Organizations should prioritize foundational capabilities first and expand over time. The research on maturity models emphasizes the importance of iterative development phases to refine the model [20].

What is the role of a data steward?

A data steward is responsible for managing data assets within a defined domain. This includes ensuring data quality, managing metadata, supporting data access, and implementing governance policies. Data stewards are the operational link between governance and data management. The research on scientific data stewardship emphasizes that stewardship is critical for ensuring trustworthiness of data, products, and services, which is important for decision-making [8].

How do we measure data quality?

Data quality is measured across multiple dimensions, including accuracy, completeness, consistency, timeliness, validity, and uniqueness. Each dimension requires specific measurement approaches. For example, accuracy is measured by comparing data values to a reference source, completeness is measured by checking for missing values, and consistency is measured by comparing values across systems. The research on data quality management emphasizes the importance of locally relevant indicators [7].

What is the difference between a data warehouse and a data lake?

A data warehouse stores structured, processed data that is optimized for analysis and reporting. A data lake stores raw data in its native format, which supports flexibility but requires more processing before analysis. The choice between a warehouse and a lake depends on organizational requirements. Many organizations use both, with a warehouse for curated data and a lake for exploratory data. The research on data management frameworks emphasizes the need to support many different types of data of imposing complexity, diversity, and volume [11].

How does data management support regulatory compliance?

Data management supports regulatory compliance by ensuring that data are accurate, complete, and traceable. This includes maintaining records of data processing activities, ensuring data integrity, and providing evidence of compliance. The research on integrated prospective regulatory governance demonstrates how regulatory requirements can be embedded as prospective design constraints across the clinical investigation lifecycle [14].

What is a data management maturity model?

A data management maturity model is a structured approach to assessing organizational capabilities and identifying improvement priorities. Maturity models define levels of capability, from initial and ad hoc to optimized and continuously improved. The assessment evaluates current capabilities and identifies gaps. The research on maturity models emphasizes the importance of quantitative evaluation and informed decision-making for continual improvement [8].

How do we get started with enterprise data management?

Start by establishing governance foundation, including executive sponsorship, governance structure, and initial policies. Then conduct a maturity assessment to establish the baseline. Design the target architecture based on assessment results and organizational objectives. Implement foundational capabilities first, then expand and optimize. The research on data management practices emphasizes the importance of making analytical datasets readily available and lowering the bar to interdisciplinary collaboration [10].

Related Articles

• Data Science Careers in Biology: Building a Transferable Evidence Portfolio
• Research Data Management Plan: From File Naming to Long-Term Sharing
• Genomics Building
• Genomics Building
• Genomics Building

References and Further Reading

• Research Data Framework. National Institute of Standards and Technology.
• EQUATOR Network. EQUATOR Network.
• Experimental Design Assistant. NC3Rs.
• NCBI Literature Resources. National Center for Biotechnology Information.
• PubMed. National Library of Medicine.
• Construction of enterprise business management analysis framework based on big data technology.. Heliyon, 2023.
• An integrated organisation-wide data quality management and information governance framework: theoretical underpinnings.. Informatics in primary care, 2014.
• A Conceptual Enterprise Framework for Managing Scientific Data Stewardship.. Data science journal, 2018.
• Development of big data assisted effective enterprise resource planning framework for smart human resource management.. PloS one, 2024.
• Eight practices for data management to enable team data science.. Journal of clinical and translational science, 2020.
• An integrated data management framework for drug discovery--from data capturing to decision support.. Current topics in medicinal chemistry, 2012.
• Harnessing probabilistic neural network with triple tree seed algorithm-based smart enterprise quantitative risk management framework.. Scientific reports, 2024.
• Industrial internet data management framework with blockchain integration for data integrity assurance and access control resolution.. Scientific reports, 2026.
• Integrated Prospective Regulatory Governance: A Quality-by-Design Operating Model for High-Risk Class III Medical Device Clinical Investigations. 2026.
• You Can't Launch This: Trust as Infrastructure in Digital Behavioral Health.. 2026.
• Having and eating the cake? The centralisation paradox in decentralised healthcare governance: a scoping review.. 2026.
• Buddy operating in gynaecological endoscopy: what should this model of surgical practice look like?. 2026.
• Content, controls, audience: contextualizing de-identification as a novel approach to enabling cross-sectoral data linkages
• Safety-Constrained Agentic AI for Autism Screening: A Multimodal, Clinician-Guided Architecture.. 2026.
• Data Management Maturity Model-Process Dimensions and Capabilities to Leverage Data-Driven Organizations Towards Industry 5.0. Applied System Innovation, 2025.
• A novel spherical fuzzy-based decision model for assessing data management maturity in governmental institutions. International Journal of Data Science and Analysis, 2025.
• Extending a Data Management Maturity Model for Process Mining in Healthcare. dHealth, 2023.
• The Healthcare Data Management Maturity Model (HDM3) for the assessment of healthcare data management in developing countries. 2022 IEEE 28th International Conference on Engineering, Technology and Innovation (ICE/ITMC) & 31st International Association For Management of Technology (IAMOT) Joint Conference, 2022.
• MD3M: The master data management maturity model. Computers in Human Behavior, 2015.
• DMMM: Data Management Maturity Model. 2021 International Conference on Advanced Enterprise Information System (AEIS), 2021.
• Master Data Management Maturity Model (MD3M) Assessment: A Case Study in Secretariat of Presidential Advisory Council. International Conference on Information and Communicatiaon Technology, 2021.
• Enterprise data management framework for agile manufacturing. Computer Engineering Division Ced American Society of Mechanical Engineers, 1995.
• Unified Data Management Framework for Supply Chain Optimization: Challenges in Enterprise Architecture Models like TOGAF, RAMI 4.0 and IBM 4.0. Lecture Notes in Information Systems and Organisation, 2025.
• The need for an enterprise risk management framework for big data science projects. Data 2020 Proceedings of the 9th International Conference on Data Science Technology and Applications, 2020.
• Big data-driven enterprise management and market decision-making framework. Service Oriented Computing and Applications, 2025.

This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.