Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Building a Better MDR
.jpg?version=1&modificationDate=1747312334450&cacheVersion=1&api=v2)
| Project Scope |
|---|
Identify use cases (e.g. standards librarian versus data manager versus programmer) for MDRs (focused on cross-study data standards), functions and features and best practices of an “ideal” vendor-neutral MDR so organisations can align services, systems, and tools accordingly. This “wish list” could be used for RFIs/RFPs as organisations evaluate (or used as requirements to build) systems and tools for their MDR needs. |
| Problem Statement |
|---|
Metadata repositories (MDRs) may require large investments of capital and resources but offer little to no return if they do not meet an organisation’s needs. Many companies have struggled to implement a functional and effective MDR system for their data standards metadata, making it challenging to document and organise their standards, and hindering downstream standards consumption and automation efforts. |
| Problem Impact | |
|---|---|
| Incorporating a better MDR will lead to efficiencies in standards implementation and maintenance, facilitate end-to-end standards implementation and automation, and improve standards compliance. |
| Project Leads | |
|---|---|
| Rahul Madhavan, PointCross/XBIOM | rahul@pointcross.com |
| Aparna Venkat, Merck | aparna.venkataraman@merck.com |
| Reema Baweja, Daiichi Sankyo | reema.baweja@daiichisankyo.com |
Nicola Newton, PHUSE Project Coordinator |
CURRENT STATUS (Updated Quarterly) |
|---|
|
| Deliverable | Timelines |
|---|---|
White Paper |
, multiple selections available,