Back to the library

Key question New

AI-processed · Author-approved

How can data governance rules stay attached to sensitive health data as it moves across different healthcare providers?

Governing Sensitive Health Data Journeys: Toward Multi-Level Data Contracts for Portability of Data Governance
Jan Maschewski, Kenneth Richter · International Conference on Information Systems (ICIS) · 2026
Illustration for: How can data governance rules stay attached to sensitive health data as it moves across different healthcare providers?

Loads Spotify's player; Spotify may set cookies. This device remembers your choice.

Key findings

  • Proposes an architecture structured across journey-level defaults, data-level contract refinements, and derived-data-level constraints.
  • Conceptualizes a data governance wrapper that packages descriptive metadata, role- and purpose-based permissions, consent status, and audit logs alongside health data.
  • Defines inheritance rules ensuring newly generated or transformed health data maintains governance continuity from its source data object rather than falling back to generic journey defaults.
  • Identifies six design requirements for portable governance to facilitate movement, clarification, or refusal decisions at care checkpoints without full operational automation.

What it means for you

CIO / IT Executive

Initiate a pilot program to evaluate a multi-level data contract architecture, ensuring that incoming and outgoing patient datasets include a governance wrapper bundling metadata, consent status, and purpose-based permissions rather than relying solely on local system policies.

IT Manager

Audit current health data integration pipelines to identify where data transformations and derived outputs (such as AI recommendations) occur, and verify that inheritance rules are configured so that generated data retains the governance constraints of its source object.

Business Strategist

Map out the multi-organizational orthopedic care pathway to identify critical checkpoints where governance friction or legal ambiguity occurs, and draft standardized data-level contract refinements to streamline cross-organizational data sharing agreements.

Researcher

Extend the design science research demonstrator by testing the six newly identified portable governance requirements against complex clinical edge cases, specifically focusing on how data movement, clarification, and refusal decisions operate without full operational automation.

Policymaker

Review existing health data portability regulations to incorporate standards for journey-level defaults and data-level contract wrappers, ensuring legal frameworks support automated governance continuity when patient records cross organizational boundaries.

Summary

This research-in-progress study proposes a multi-level data contract architecture to ensure that governance rules remain portable, interpretable, and actionable throughout patient data journeys. Grounded in data governance and boundary resources literature, the authors apply a Design Science Research methodology to conceptualize the architecture and instantiate it in an interactive demonstrator simulating an orthopedic care pathway.

Problem

While patient health records frequently move across healthcare organizations, systems, and clinical roles, the governance rules dictating authorized use remain locked in local policies, systems, or manual clarification processes. This disconnect creates governance friction and legal ambiguity, particularly when data is interpreted, aggregated, or transformed into derived outputs such as AI recommendations or clinical summaries.

Transcript
Host: Welcome to A.I.S. Insights — powered by Living Knowledge. I am Anna Ivy Summers. Today, we examine a study titled "Governing Sensitive Health Data Journeys: Toward Multi-Level Data Contracts for Portability of Data Governance." It is authored by Jan Maschewski and Kenneth Richter and presented at the International Conference on Information Systems in 2026. Alex, this study addresses how sensitive healthcare data travels across providers while keeping governance rules attached.

Expert: Hello Anna. In modern healthcare, patient care spans multiple providers, including general practitioners, hospitals, rehabilitation centers, and insurers. As patients move through care episodes, their data moves with them. However, while data moves across these technical and organizational boundaries, the governance conditions—specifying authorized roles, legitimate processing purposes, consent status, and retention limits—often remain trapped in local policies, proprietary systems, or manual clarification processes.

Host: So we have mobile data paired with stationary governance. What practical difficulties does this mismatch cause across care settings?

Expert: It creates operational friction and ambiguity. When data arrives at a subsequent checkpoint, personnel must either engage in time-consuming clarification work or risk using the data outside legitimate bounds. The challenge intensifies when data is interpreted, aggregated, or transformed into derived outputs, such as AI-generated risk scores or discharge summaries. These new outputs depend on original data, yet often lose the associated consent constraints and provenance records.

Host: How did the authors approach this problem in their research?

Expert: The authors employed a Design Science Research approach, utilizing the Baustein framework to structure their process. Rather than treating governance as an abstract policy exercise, they designed an artifact: a multi-level data contract architecture. They evaluated representational adequacy by instantiating the artifact in a demonstrator that models a patient journey covering hip osteoarthritis, surgery, rehabilitation, and follow-up across five contracting actors.

Host: Let us break down the architecture. How do these multi-level contracts function together?

Expert: The study organizes governance across three distinct tiers. First, journey-level contracts define baseline defaults for an entire episode of care, anchoring governance in longitudinal treatment continuity. Second, data-level contracts refine those defaults for specific objects; for example, restricting an insurer's access strictly to billing fields while withholding clinical narratives. Third, derived-data-level contracts govern newly generated assets, such as clinical interpretations or computational analyses.

Host: And how do those conditions remain attached to the information as it moves?

Expert: Through what the study terms a data governance wrapper. Conceptualized as a boundary resource, the wrapper bundles descriptive metadata—like data type and originating institution—with governance metadata, including authorized roles, legal basis, consent status, and audit logs. A key mechanism is inheritance: derived data inherits constraints directly from the source object it was generated from, rather than defaulting to broad journey permissions. For instance, if research consent for an initial diagnostic image is withdrawn, a derived analytical record cannot inherit permission for secondary research use.

Host: Meaning that at each care checkpoint, the system or professional has clear parameters.

Expert: Exactly. At each checkpoint where data is transferred or transformed, the wrapper supports one of three outcomes: movement, clarification, or refusal. The wrapper does not execute automated legal authority or replace clinical judgment; instead, it provides a machine-readable, interpretable representation that informs human decision-makers and technical systems.

Host: Looking at the business and operational impact, what can healthcare organizations and health IT leaders take away from this study?

Expert: For healthcare providers and platform architects, this approach offers a model for managing data in motion. By attaching explicit governance parameters to data objects, organizations can reduce administrative clarification work, maintain regulatory accountability across fragmented care networks, and establish verifiable provenance for derived data and AI assets. It helps ensure health data is neither unnecessarily withheld nor used beyond legitimate care purposes.

Host: A structured foundation for maintaining governance continuity throughout complex care pathways. Thank you, Alex, for breaking down this study, and thank you to our listeners. Join us next time on A.I.S. Insights — powered by Living Knowledge.
Artificial Intelligence & Automation Information Systems & Management Human-Computer Interaction Data Analytics & Big Data Digital Transformation & Strategy Cybersecurity & Privacy Cloud & Infrastructure E-Commerce & Digital Platforms Operations & Supply Chain Sustainability & Green IS

Data Governance, Data Contract, Patient Journey, Data Portability, Health Information Systems, Design Science Research