NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (reillysm), last modified by Unknown User (wileyal) on Dec 20, 2011

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Semantic Infrastructure Concept of Operations Initiatives Links

Initiatives:
Unable to render {include} The included page could not be found.

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. 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

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.
  • 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
  • No labels