TARBA — Arnab Roy

PROJECT / 02 · HEALTHCARE RESEARCH DATA GOVERNANCE · 2024

TARBA

A healthcare research platform for changing study structures without losing approval or traceability.

UX + PRODUCT DESIGN

INGESTION · VALIDATION · GOVERNANCE · REPORTING

2024

HEALTHCARE RESEARCH DATA GOVERNANCE

CONTEXT / WHY THE SYSTEM EXISTED

THE GOVERNANCE MODEL HAD TO SURVIVE CHANGES IN STUDY STRUCTURE.

Different studies could require different fields, dependencies, contributors and outputs. The platform still had to preserve ownership, evidence, validation and approval as that structure changed.

01 / CONFIGURABLE BY STUDY

Forms, fields, dependencies, contributors and output formats could vary with each research programme.

FORMS · FIELDS · DEPENDENCIES · CONTRIBUTORS · OUTPUT

02 / NON-NEGOTIABLE TRUST

Ownership, evidence, validation and approval had to remain explicit no matter how the research structure changed.

OWNERSHIP · EVIDENCE · VALIDATION · APPROVAL · TRACEABILITY

03 / VERIFY · APPROVE · REPORT

Evidence · completeness · checks → Hierarchy · groups · sign-off → Controlled formal output

PERMISSIONS · USER HIERARCHY · APPROVAL GROUPS · TRACEABILITY

DESIGN QUESTION

How could flexible study structures preserve fixed governance rules?

STUDY TEAMS NEEDED TO CHANGE THE STRUCTURE THEMSELVES.

01 / COMPOSE THE SCHEMA

Headings, dates, lists, media, tabular data and custom fields became building blocks that could be assembled around a study.

02 / ENCODE RELATIONSHIPS

Dependencies were authored with the form, so capture logic could change with the research structure instead of forcing a new interface.

03 / CARRY GOVERNANCE FORWARD

Approval-group assignment was part of authoring, linking flexible capture directly to the governance model that follows.

WORKFLOW PROOF / 01

APPROVAL RULES STARTED AT ADMIN LEVEL AND FOLLOWED THE FORM.

Admin levels, permissions and the default approval path were set once, then reused by forms and adjusted when a study needed something different.

01 / ADMIN SETTINGS / CONFIGURE

02 / USER HIERARCHY / MAP AUTHORITY

03 / ALL FORMS / EXECUTE

The configured path became the live workflow.

DESIGN DECISION / TRUSTED OUTPUT

THE REPORT COULD BE TRUSTED BECAUSE THE WORKFLOW PRESERVED ITS EVIDENCE.

Approved fields, evidence and provenance stayed attached to the research record, then resolved into a structured report ready to review, print or download.

01 / APPROVED RESEARCH RECORD

PROVENANCE STAYED WITH THE DATA

Verified fields, approval context, media, tables and citations remained attached to the approved record.

02 / TRUSTED REPORT

APPROVED CONTENT BECAME A REPORT PEOPLE COULD REVIEW AND EXPORT

Approved research content was reorganised into structured sections with patient/report metadata and print or download actions.

03 / GOVERNED OUTPUT

APPROVED FIELDS BECAME EXPORTABLE OUTPUT

Evidence and citations stayed attached as the research record resolved into a structured report ready to review, print or download.

Trust was inherited from the workflow, not added at the end.

OUTCOMES / REFLECTION / 02

TARBA COULD CHANGE BY STUDY AND KEEP ITS GOVERNANCE RULES.

Research structures could vary without breaking validation, approvals or traceability.

01 / FLEXIBILITY

LET THE STUDY DEFINE THE STRUCTURE

02 / GOVERNANCE

CARRY GOVERNANCE INTO EVERY FORM

03 / TRACEABILITY

KEEP PROVENANCE WITH THE OUTPUT

MY ROLE

INFORMATION ARCHITECTURE CONFIGURABLE FORM LOGIC PERMISSIONS APPROVAL WORKFLOWS REPORTING UX

REFLECTION

Configurability only worked because the governance rules stayed explicit underneath it. I’d treat those rules as the product’s starting structure, then let each study flex around them.

PREVIOUS PROJECT /

ONEVIEW

ENTERPRISE OPERATIONS

2026

VIEW PROJECT →

NEXT PROJECT /

TREATMENT.HOSPITAL

MEDICAL TOURISM + HEALTHCARE OPERATIONS

2024

VIEW PROJECT →