For NHLBI research investigators who need to find, access, share, store, cross-link, and compute on large scale data sets, the NHLBI Data Resource will be a cloud-based platform that has as its foundation the NIH Data Commons that provides tools, applications, and workflows to enable these capabilities in secure workspaces. The NHLBI Data Resource will be a rationally organized digital environment, integrated within the broader NIH Data Commons ecosystem, that will accelerate efficient biomedical research and maximize community engagement and productivity. Ultimately, the NHLBI Data Resource will drive discovery leading to novel diagnostic tools, therapeutic options, and prevention strategies to treat heart, lung, blood, and sleep disorders.

The relationship between DataSTAGE (Storage, Toolspace, Access and analytics for biG data Empowerment) and the Data Commons Pilot Phase Consortium (DCPPC) is quite straightforward: DataSTAGE is meant to be one (early) instance of the Data Commons, particularized for the purposes of NHLBI.  These are two separate, but related projects, meant to be mutually beneficial. There are expectations that the DCPPC and DataSTAGE will each cross-inform the other project of significant processes, emerging standards, and decisions using an RFC process that has been described here (access to link requires membership in the DCPPC organization on GitHub).  This should permit loose coupling, and yet parallel progress, in order to reap the benefits of both of these two efforts. We believe that collaboration and transparency should enable a cohesive product.

Critical to managing the relationship between the two projects is to garner an understanding of the high-level timelines and cross-dependencies. The Data Commons has undertaken a method of prototyping and rapid evolution. The DataSTAGE is focused on providing an initial implementation for the NHLBI community.  These differences requires a bridged approach to determine what Commons infrastructure should be deployed for STAGE, and what additional work needs to be performed to ensure that the STAGE functionality is robust and meets NHLBI security requirements. There will be a process developed for deciding how the software platform and components becomes part of the STAGE, and on how these bridging activities are coordinated.

STAGE infographic portrait1