 |
Page History
...
An important part of the requirements gathering process is to engage end users and stakeholders. In an infrastructure project of this nature, a good way to relay the types of functionality that will be supported is through user stories. This list is not meant to be exhaustive. These stories demonstrate are representative of the types of functionality that will be directly supported by the infrastructure, as well as the types of tooling that will be enabled by the infrastructure.
Stories
# | Story | Priority | Status |
|---|---|---|---|
1 | Search for all "pre-cancerous" biospecimens that are available for sharing at Washington University, Thomas Jefferson University, and Fox Chase Cancer Center. | Must | Draft |
2 | Identify samples obtained for glioblastoma multiforme (GBM) and the corresponding CT image information | Must | Draft |
3 | Automatically discover analytical steps for Illumina bead array analysis using inference based on the semantic metadata of the parameters. |
| Draft |
4 | Discover and orchestrate services to achieve LS research goals; e.g. start with a hypothesis, identify relevant services that provides the necessary analysis and data, create the workflow/pipeline, report findings. |
| Draft |
5 | Support the addition of data elements to an existing information model and automatically capture and publish the information about the extensions. | Must | Draft |
6 | When defining new datasets for caIntegrator's data-warehouse for biomedical data collection and analysis, automatically record these new datatypes in a well-defined and federated manner so that data can be shared. | Must | Draft |
7 | Support patient to trial matching through the use of computable eligibility criteria |
| Draft |
8 | Create, import and reuse forms and form components (modules) | Must | Draft |
9 | Support of form annotations to enable form behavior | Must | Draft |
10 | Managing semantic relationships in order to link and share data | Must | Draft |
...
