Semantic Infrastructure Concept of Operations Initiatives Links |
|---|
Note
This page outlines the semantic infrastructure elicitation of requirements from 2009 and early 2010 and was last updated in August, 2010. The Semantic Infrastructure Roadmap is the next phase of evolution of CBIIT Semantic Infrastructure planning.
This page is the master list for organizing stakeholder business requirements for the existing semantic infrastructure, that may impact the new CBIIT semantic infrastructure roadmap. The Semantic Infrastructure Roadmap replaces the 2009 Semantic Infrastructure Concept of Operations. Any requests which do not fit into the seven initiatives described by the Semantic Infrastructure Concept of Operations were also documented. After collection of more details on all the requirements, a UML Model depicting the high level technical service requirements and their decomposed use cases was developed.
historical link: https://wiki.nci.nih.gov/download/attachments/20285848/10_06_17_UMLofREQUIREMENTS.pdf
To communicate requirements for the existing infrastructure not listed here, the contact was Denise Warzel. For requirements pertaining to the new CBIIT semantic infrastructure, the contact was Dave Hau. For semantic infrastructure requirements for caEHR, the contact was John Speakman.
Links to Related Pages
UML Model of Use Cases by Requirement Level (pdf version)
historical link: https://wiki.nci.nih.gov/download/attachments/20285848/10_06_17_UMLofREQUIREMENTS.pdf
- UML Model of Use Cases by Requirement Level (html version)
- A roadmap for requirement analysis for ECCF traceability
- SI Service Categories derived from initial use case analysis
- Supplemental Requirements Input page
- Requirements Elicitation Stakeholder Participants
- Requirements Elicitation Progression
Explanation of Columns in the Requirements Master List
- Infrastructure
- IS09 Validation - The Validation service verifies structural and semantic consistency across messages used in interoperability scenarios.
- IS10 Transformation - The Transformation service provides a functional end point to manage and enact mappings between syntactically disparate information types.
- IS11 Knowledge Management - Knowledge Management service represents a series of capabilities around the storage, versioning, searching, discovery, and expression of the semantics supporting key capabilities.
- IS12 Service Contract Management - Service Contract Management service represents a series of capabilities around the storage, versioning, searching, discovery and expression of the contract semantics supporting interoperability.
- IS13 Enterprise Vocabulary - Enterprise Vocabulary services support the management, storage, and mapping of terminologies and value sets.
- Topic - is the forum topic title from the request: Spring Requirements Forum, Winter Requirements Forum or a title given to a request that came directly from a customer or stakeholder.
- Submitter - is the stakeholder requesting the new feature or work. Email links are provided for historical purposes.
- Requirement Statement (author) - is the person initiating the process whether pulling information from the forums or receiving requests from stakeholders
- Interview Analyst - is the person in direct contact with the submitter in order to extract requirements.
- Use Case Analyst - is the person taking the requirements in order to create use cases.
- Phase 1 Target - the goal to be achieved in phase 1
- Requirement Link(s) - artifacts created during the requirements process
- Notes - notes related to this requirement
The following table contains the Requirements Master List. Click the text in the header to sort the column.
Requirements Master List
Topic | Infrastructure Service | Type | Submitter | Req Statement | Interview Analyst | Use Case Analyst | Phase I Target | Requirement Link(s) | Notes |
|---|---|---|---|---|---|---|---|---|---|
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | Formal Requirements Statement, Summary Use Cases | Requirements Input - Init1pm16 (ISO 21090) | Services for data integration | ||
Knowledge Management | Manage & Create Model Metadata | Baris | n/a | Patrick | Formal Requirement Statement and Use Case Summary | This feature already exists, clarify use cases to ensure that all are supported | |||
Knowledge Management | Manage & Create Model Metadata | Shantanu | n/a | --- | Summary Requirements statement | Provide ability to generate customized reports from metadata content | |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | --- | Formal Requirements Statement | Models | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Patrick | Formal Requirements Statement and 2-4 Summary Use Cases | Requirements Input - Init1pm9 | Automate creating CDEs from skip patterns of Forms, workflow to automate annotation and loading of Models | ||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement and 2-4 Use Cases | support end-to-end annotation and loading of models, traceability; the need to submit a model to be loaded by someone else may go away; this could be a short term solution, depending on LOE to implement | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement and 2-4 Use Cases | Models | |||
Constraint | Supplemental Specification Requirement on Ontology Best Practices | Shantanu | Shantanu | --- | Formal Requirements Statement | --- | |||
Brain Tumor in silico study: Pathology/Radiology data models | Knowledge Management | Manage & Create Model Metadata | Patrick | Shantanu | Shantanu |
| Integration Use Cases | ||
caBIG Rules Engine White Paper v4 historical link https://wiki.nci.nih.gov/download/attachments/20285848/caBIG_Rules_Engine_WP_v4.doc | Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | --- | |
Knowledge Management | Manage & Create Model Metadata | Patrick | Hua | --- | Formal Requirements Statement | Services | |||
caEHR Content Development | NA | No Requirement Specified | Patrick | --- | Patrick | Formal Requirement Statement and Use Cases | --- | caBIG Community | |
caEHR SI Services | NA | No Requirement Specified | Patrick | --- | Patrick | Formal Requirement Statement and prioritized use cases | --- | caBIG Community | |
Canada Infoway Clinical Concept Representation | No Clear Requirement Defined. | Discussion presentation on identifying Clinical Concepts through use of HL7 and Clinician Feedback. | Mark Shafarman, Bill Gilliam | --- | --- | --- | Formal Requirements Statement, high level use cases | --- | |
cancerGrid Federated Registries | Constraint | Supplement Specification Req. for Federated MDRs | --- | --- | --- | Formal Requirements Statement; Summary of Services Use Cases (see Michael Riben) | --- | caBIG Stakeholders - 11179 and Forms metadata exchange | |
Vocabulary Management | Manage & Create Model Metadata | Hua | Hua | Patrick | Formal Requirements Statement, Summary Use Cases | --- | |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | Patrick | Formal Requirements Statement | Display usage information in browsers, use this to organize search results | |||
Knowledge Management | Manage & Create Model Metadata | Baris | n/a | Patrick | Formal Requirements Statement | leverage semantics of existing content to find/reuse content from different sources to create Forms | |||
CDISC SHARE | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | Formal Requirements Statement | caBIG Stakeholder | ||
Constraint | Supplemental Specifications Requirement, build a Glossary of Model Terms | Shantanu | Hua | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | Patrick | Formal Requirements Statement and Use Case Summary | Ability to compare Object Classes, Models, etc. | |||
Knowledge Management | Manage & Create Model Metadata | Hua | Baris | Patrick | Formal Requirements Statement | --- | |||
Conformance Profile Browser | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | --- | caBIG Community - Support for ECCF Use Cases | ||
Conformance Profile Editor | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | --- | caBIG Community - Support for ECCF Use Cases | ||
Conformance Profile Registry (or Repository) and Format | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | --- | caBIG Community - Support for ECCF Use Cases | ||
Conformance Profiles | Knowledge Management | Manage & Create Model Metadata | Frank Hartel interview: | Baris | Baris | --- | Formal Requirements Statement and summary of high level use cases (actor, bus goal, success scenario) | caBIG Community - Support for ECCF Use CasesArch WS Presentation | |
Contractor and Software Vendor Application Development Support | Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement | Application Engineering | ||
Knowledge Management | Manage & Create Model Metadata | Shantanu | n/a | Patrick | Decomposed forum and other materials | caB2B use cases for improving metadata for services | |||
Knowledge Management | Align Models | Patrick | --- | Patrick | Formal Requirements Statement | leverage searches across EVS and caDSR | |||
CTMS Interoperability Scenarios: Maximize reuse, Minimize development | Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement | CTMS Application Engineering | ||
Curator Harmonization Activities | Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement, high level use cases | --- | ||
Knowledge Management | Manage & Create Model Metadata | Baris | n/a | --- | --- | allow users to search for and customize download, not just CDEs | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement and 2-4 Detailed use cases | Models | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement |
| |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | --- | Formal Requirements Statement | Allow federation of content, current limitation of what can be extracted/easily downloaded | |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | --- | Formal Requirement Statement and Draft list of prioritized use cases | Adjustable UI for the user to customize views of metadata | |||
Knowledge Management | Manage & Create Model Metadata | Shantanu | Shantanu | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Patrick | Formal Requirements Statement | Examples of High Level Services for retrieving MDR content, caDSR Services Wiki | |||
Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | --- | Formal Requirements Statement | --- | |||
FDA | NA | No Requirement Specified | --- | --- | --- | Formal Requirements Statement | --- | caBIG | |
Federated Data w/single source of 'truth' | Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement | Ability to have data spread over the grid/internet, but know which data is the original, source of truth | ||
Federated Metadata Registries | No Requirement Defined, Most likely a design constraint | Requirement for Federated MDRs captured in the Supplemental Specifications | Denise | --- | --- | Formal Requirements Statement, high level use cases | --- | Novartis MDR | |
Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | Hua | n/a | Patrick | Formal Requirements Statement; High level use cases for Services | Related to Christo Andonyadis requirements - See 8 Other | |||
Harmonize and reuse metadata across different terminologies | Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement and Use Cases | --- | ||
HHS OS - Data.gov | NA | Some References to Linked Data and Cloud Computing, but no clear KR Requirement. | --- | --- | --- | Formal Requirements Statement, high level use cases | --- | ||
HL7 MDR Requirements | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | Formal Requirements Statement and High level/priority Use Cases | HL7 CIC; caBIG Stakeholder | ||
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | See 21090 Datatype Support | Requirements Input - Init1pm16 (ISO 21090) | Services for data integration | ||
| Knowledge Management | Search Models | Shantanu | --- | --- | Formal Requirements Statement | caGrid querying | ||
| Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | --- | Formal Requirements Statement | provide capabilities to build cde-cde mapping and metadata mapping for use in services | ||
| Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | --- | Formal Requirements Statement C - Decomposed forum and other materials | metamodel for LIMS | ||
| Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Patrick | Formal Requirements Statement; Summary Use Cases | Integrated tools for model loading, traceability | ||
| Knowledge Management | Manage & Create Model Metadata | Hua | Hua | Patrick | Formal Requirements Statement and Use Case Summary | Make it easier to reuse/map CDEs to models, improve matching algorithms | ||
Knowledge Management | Align Models | Shantanu | n/a | Patrick | Formal Requirement Statement and Draft prioritized use cases | Requirements Statement - Init1pm24 | Related to dynamic extensions | ||
Knowledge Management | Manage & Create Model Metadata | Denise | --- | Baris | Formal Requirements Statement; Detailed Use Cases in Round 4 | LS and CS Governance [Life Sciences "grid" vsd] | |||
Knowledge Management | Manage & Create Model Metadata | Hua | --- | Patrick | Formal Requirements Statement | leverage semantic connections and NLP for searching/identifying reusable content | |||
Knowledge Management | Manage & Create Model Metadata | Baris | n/a | --- | Formal Requirements Statement | Portal that integrates tools | |||
Knowledge Management | Manage & Create Model Metadata | Baris | Baris | --- | Formal Requirements Statement | makes easier to use tools in a workflow, expose more metadata | |||
Knowledge Management | Manage & Create Model Metadata | Hua | --- | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | --- | See 21090 Datatype Support Use Cases | Requirements Input - Init1pm16 (ISO 21090) | Services for data integration | ||
LexEVS "Portal" for use by other apps | Knowledge Management | Search Models | --- | --- | --- | --- | -- | caBIO Portlet | |
Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | --- | ||
Knowledge Management | Manage & Create Model Metadata | Baris | --- | Patrick | Formal Requirements Statement | --- | CTS2 SFM DSTU Final 20090322 historical link: https://wiki.nci.nih.gov/download/attachments/20285848/CTS+2+SFM+DSTU+FINAL+20090322_v1+1_addenda001.doc | ||
LEXEvs: capture the need for new content development in NCI Thesaurus | Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | --- | |
Knowledge Management | Model Administration | Hua | Hua | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Model Administration | Patrick | --- | --- | Formal Requirements Statement and 2-3 Summary Use Cases | --- | |||
Knowledge Management | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement | --- | Life Sciences and Clinical Sciences Governance | ||
Knowledge Management / Transformation | Manage & Create Model Metadata | Patrick | --- | Patrick | Formal Requirements statement; Summary Use Cases | Services | |||
Mapping/transformation support for ISO21090 data types | Knowledge Management /Transformation | Manage & Create Model Metadata | Baris | n/a | Patrick | Formal Requirements Statement | Requirements Input - Init1bes12 | Services for data integration | |
MD Anderson Federated Registries | Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | --- | caBIG Community | ||
Medidata | Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Patrick | --- | Commercial COTS vendors - Form and CDE Services - CTMS WS | ||
Metadata repositories should contain corresponding metadata | Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | Guide to Mentors | |
NCI level vocabulary services for Diseases and Interventions | Knowledge Management | Manage & Create Model Metadata | Hua | n/a | Patrick | Formal Requirements Statement | --- | ||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement; Develop summary list of use cases (Most common queries) | Easier to use Browser - User Centered Design details attached | |||
Knowledge Management | Search Models | Shantanu | n/a |
| Formal Requirements Statement | --- | |||
Knowledge Management/Transformation | Manage & Create Model Metadata | Shantanu | n/a | Patrick | Formal Requirements Template Decomposed forum and other materials | --- | |||
Policies/protocols that will ensure concurrent registration of model/metadata | Knowledge Management /Transformation | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | Guide to Mentors | |
Programmatic access to 'Materials and Methods' section of a paper | Knowledge Management | Manage & Create Model Metadata | Denise |
| Patrick | Formal Requirements Statement | Similar to Yolanda's semantic workflows | ||
Knowledge Management | Manage & Create Model Metadata | Hua | Hua | Shantanu | Formal Requirements Statement | --- | |||
Registration of Models in GME | Knowledge Management | Manage & Create Model Metadata | Baris | n/a |
| Formal Requirements Statement and Use Cases | --- | ||
reqs sharing (Support metadata for Statistical Practice) | Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | Shantanu | Formal Requirements Statement; | Genzyme - Will be handled by CBIIT Team Statistical Practice Article historical link: https://wiki.nci.nih.gov/download/attachments/20285848/04-DIJ44%281%29+2459+qxd.pdf | ||
Knowledge Management | Align Models | Hua | Baris | Patrick | Formal Requirements Statement | leverage semantic metadata and model relationship to find/reuse content | |||
Knowledge Management | Manage & Create Model Metadata | Hua | Hua | Patrick | Formal Requirement Statement and Use Cases Summary (List) | related to metadata for caB2B and Dynamic Extensions Services | |||
Rules/OWL2 Based Inferencing | NA | No Requirement Specified | --- | --- | --- | Formal Requirements Statement | --- | --- | |
Seamless integration of Data and Services through workflows | Knowledge Management | Manage & Create Model Metadata | Denise | --- | C - CBIIT Interview | Formal Requirements Statement | Application Engineering | ||
Knowledge Management | Align Models | Patrick | --- | Patrick | Formal Requirements Statement | leverage semantic connections to help users find existing content when browsing or searching; Model repository; Point-of-View browsing | |||
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | Formal Requirements Statement | --- | |||
Not Defined | --- | --- | --- | --- | Formal Requirements Statement | --- | --- | ||
Knowledge Management | Manage & Create Model Metadata | Patrick | n/a | Shantanu | Formal Requirements Statement; Summary Use Cases | Better support for annotating and loading models | |||
Validation | part of Manage & Create Metadata | Baris | Baris | Patrick | Formal Requirements Statement and Use Case Summary | Requirements Input - Init1bes4 | This set of requirements and use cases is for the ability to validate models against standard models and best practices, such as checking models for cyclic references. It may or may not end up as an SIW enhancement. | ||
Knowledge Management | Manage & Create Model Metadata | Baris |
| Patrick | Formal Requirements Statement | Need to be able to register java classes that are comprised of CDEs that are associated with different Object Classes - remove the one domain class<->one object class limitation for model registration | |||
Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | --- | ||
Knowledge Management | Manage & Create Model Metadata | Shantanu | n/a | Shantanu | Formal Requirements Statement; Develop Use Case for how user envisions this would work. | The capability to annotate associations already exists in caDSR. Needs to be incorporated into overall semantic annotations, but more easily than current methods. | |||
Knowledge Management | Manage & Create Model Metadata | Denise | --- | Mohamed Patrick | Formal Requirements Statement | --- | |||
Constraint | Supplementary Specificagtion - use of .NET tools | Patrick | --- | --- | Formal Requirements Statement | Services | |||
Support for Curation Workflow Activities | No Requirement defined, most likely it is | Manage & Create Model Metadata | Denise | --- | --- | Formal Requirements Statement, high level use cases | --- | Novartis curator support | |
Support for Knowledge Management to Discoveries: Scientific Workflows and Artificial Intelligence | Knowledge Management /Transformation | Manage & Create Model Metadata | Denise | --- | Patrick | Formal Requirements Statement, 2-4 Use Cases | Requirements Input - Init3dbw2 | Wings Semantic Workflows Requirements for caBIG Infrastructure to Support Semantic Workflows; Recommendations for caBIG to Support Semantic Workflows; Use Cases for Semantic Workflows in caBIG historical links: https://wiki.nci.nih.gov/download/attachments/20285848/Requs_caBIG_InfrastructureSupportSWorkflow.ppt and https://wiki.nci.nih.gov/download/attachments/20285848/Recommendations_caBIG_SupportSemWorkf.ppt and https://wiki.nci.nih.gov/download/attachments/20285848/UseCasesForSemanticWorklowIncaBIG.doc | |
Support for Reusable Modules/Sections of Forms | Knowledge Management | Manage & Create Model Metadata | Denise | n/a | Patrick | Formal Requirements Statement; High level use cases for Services | Make Form Modules reusable | ||
Support for Structured Eligibility | Knowledge Management | Manage & Create Model Metadata | Denise | Patrick | Patrick | Formal Requirement Statement and Use Cases Summary | caBIG Community | ||
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | --- | ||||
Enterprise Vocabulary | Align Models | Hua | Hua | --- | Formal Requirements Statement | Make all VCDE approved terminologies available for model annotations | |||
TCGA AIM-E Integration Use Cases | Knowledge Management | Manage & Create Model Metadata | Shantanu | --- | Shantanu | Formal Requirements Statement and Use Cases | This project's aim is to enable the creation of radiology data in a standardized manner, and to allow for the integration of this data with genomic and clinical dataTCGA AIM-E Enterprise Use Cases TCGA AIM Data Service Directors Brief Oct 2009 Wiki Overview of Architectural and Ontological Issues in Quantitative Imaging presentation Imaging Use Case - Cooperative Group Support | ||
Testing conformance with conformance profiles | Knowledge Management | Manage & Create Model Metadata | Baris | --- | --- | --- | caBIG Community - Support for ECCF Use Cases | ||
Knowledge Management | Manage & Create Model Metadata | Shantanu | n/a | Shantanu | Formal Requirements Statement | Requirements Input - Init1sd5 | Services for data integration | ||
Knowledge Management /Transformation | Manage & Create Model Metadata | Patrick | Baris | Patrick | Formal Requirements Statement; Summary Use Cases | Requirements Input - Init1pm14 | Services for data integration | ||
Knowledge Management | Manage & Create Model Metadata | Shantanu | n/a | Shantanu | Formal Requirements Statement | --- | |||
US Department of Defense (USDOD) | NA | No Requirement Specified | --- | --- | --- | Formal Requirements Statement | --- | Requirements around need for secure content | |
Usage Tracking/Statistics for Semantic Infrastructure Services | Constraint | In supplementary specification Model Admin. Requirement | Ken Buetow | --- | --- | --- | --- | --- | --- |
Knowledge Management | Manage & Create Model Metadata | Patrick | --- | --- | Formal Requirements Statement | --- | |||
Knowledge Management | Manage & Create Model Metadata | --- | --- | --- | Formal Requirements Statement | --- | Assertation test | ||
Knowledge Management | Visualize Models | Baris | --- | --- | --- | Improve browsing of registered models with visualization tools |
Help Downloading Files
For help accessing PDF, audio, video, and compressed files on this wiki, go to Help Downloading Files.
