Semantic Infrastructure Concept of Operations Links |
|---|
Initiative |
Forum Topic |
Confluence Migration |
Analyst/Participant Interview |
Business Analyst Use Case |
User Story |
|---|---|---|---|---|---|
ICR IRWG Requirements - model loading |
|
Domain User Story 3 |
|||
|
|
|
|||
|
|
||||
|
|||||
|
|
||||
|
|
|
|||
ICR IRWG requirements - models and algorithms |
|
|
|
||
|
|
||||
|
|
|
|||
|
|
|
|||
|
|||||
|
|
||||
|
|
|
|||
|
|
|
|||
|
|||||
|
|||||
1] |
|
|
|
||
|
|
||||
|
|||||
|
|||||
|
|
|
|||
|
|
|
|||
|
Use Cases - Init1pm9.pm16 - Automate |
||||
|
|
||||
|
|
|
|||
|
|
||||
|
|
|
|||
|
|
||||
|
|
||||
|
|
||||
ICR IRWG requirements - cde-cde and metadata mapping |
|
|
|
||
|
|
|
|||
|
|
||||
MD Anderson Federated Registries |
|
|
|
||
cancerGrid Federated Registries |
|
|
Formal Requirements Statement; Summary of Services Use Cases (see Michael Riben) |
|
|
Medidata |
|
||||
|
|||||
Metadata repositories should contain corresponding metadata |
— |
— |
— |
— |
|
Policies/protocols that will ensure concurrent registration of model/metadata |
|
|
|
|
|
|
|||||
Mapping/transformation support for ISO21090 data types |
|
||||
|
|
|
|||
|
|||||
|
|||||
|
|
|
|||
|
Genzyme - Will be handled by CBIIT Team |
|
|||
HL7 MDR Requirements |
|
|
|
||
|
|
|
|||
|
|
||||
|
|||||
|
|||||
|
|
|
|
||
|
|
|
|
||
TCGA Integration Use Cases |
— |
||||
Harmonize and reuse metadata across different terminologies |
— |
— |
— |
||
US Department of Defense (USDOD) |
— |
— |
— |
— |
|
HHS OS - Data sharing |
— |
— |
— |
||
Usage Tracking/Statistics for Semantic Infrastructure Services |
— |
— |
— |
— |
|
Curator Harmonization Activities |
— |
— |
— |
||
HHS OS - Data.gov |
— |
— |
— |
— |
|
Support for Curation Workflow Activities |
— |
— |
— |
— |
|
Federated Metadata Registries |
— |
— |
— |
— |
|
— |
— |
||||
— |
— |
— |
|||
Conformance Profiles |
— |
— |
|||
Conformance Profile Browser |
— |
— |
— |
||
Conformance Profile Registry (or Repository) and Format |
— |
— |
— |
||
Conformance Profile Editor |
— |
— |
— |
||
Testing conformance with conformance profiles |
— |
— |
— |
||
Support for Knowledge Management to Discoveries: Scientific Workflows and Artificial Intelligence |
— |
||||
— |
— |
— |
— |
||
|
|
|
|
||
— |
— |
— |
|||
— |
— |
— |
|||
ICR IRWG requirements - caGrid querying |
— |
— |
— |
||
— |
|||||
— |
— |
— |
|||
Rules/OWL2 Based Inferencing |
— |
— |
— |
— |
|
— |
— |
— |
— |
||
LEXEvs: capture the need for new content development in NCI Thesaurus |
|
|
|
||
|
|
|
|
||
|
|
||||
|
|
|
|||
— |
— |
— |
|||
— |
— |
— |
|||
5] |
|
|
|
||
NCI level vocabulary services for Diseases and Interventions |
|
— |
|||
— |
— |
||||
FDA |
— |
— |
— |
— |
|
— |
|
||||
— |
— |
— |
|||
— |
— |
— |
|||
ICR IRWG requirements - metamodel for LIMS |
— |
— |
— |
||
6] |
Brain Tumor in silico study: Pathology/Radiology data models |
|
|||
— |
— |
— |
|||
— |
— |
— |
— |
||
CDISC SHARE |
— |
— |
— |
||
— |
— |
||||
— |
— |
||||
Support for Structured Eligibility |
— |
— |
|||
caEHR |
— |
— |
— |
— |
|
ICRi WG Use Case Scenarios |
— |
— |
|||
— |
— |
— |
— |
||
Seamless integration of Data and Services through workflows |
— |
— |
— |
||
Contractor and Software Vendor Application Development Support |
|
|
|||
Federated Data w/single source of 'truth' |
— |
— |
— |
||
CTMS Interoperability Scenarios: Maximize reuse, Minimize development |
|
|
|||
Programmatic access to 'Materials and Methods' section of a paper |
— |
|
|||
Registration of Models in GME |
— |
— |
— |
||
LexEVS "Portal" for use by other apps |
— |
— |
— |
— |
|
Support for Reusable Modules/Sections of Forms |
— |
— |
