Page History

...

• Simplify and streamline community creation, curation, maintenance, discovery, and discoveryreuse;
• Support content harmonization leveraging automated means for identification of overlapping content;
• Support interoperability and integration of data elements, modules of elements, and semantics into existing and novel workflows; and
• Support knowledge extraction.

The requirements outlined below are described in more detail in the DRAFT Extended MDR RequirementsV10.9.docx.

...

  (the Extended MDR Requirements is a more descriptive document, adn therefore lengthy.  We are still working to make a more stakeholder readable version of it).

SI Data Semantics Outline

...

2.5       Alternatives and Analysis

- compare the NCI requirements with open source and commercial metadata repository softwareWe have been analyzing the capabilities of several existing metadata repositories and those providing repository capabilities, comparing this information with the NCI requirements. These solutions are partial solutions. A prioritization task will help us determine which solutions are the best match for NCI.

2.5.1    NLM CDE Repository  

...

2.5.7    cTAKES, YTEX, MetaMap, UNIM        UNIM   (deferred further investigation, these are capabilities not full-blow repositories)  

2.5.8    TransMart      TransMart  (deferred further investigation)

2.5.9    DataType Registry – CNRI     

...

2.5.13  USHIK

2.5.14  Mayo

2.5.15  IMOS Consulting

2.5.16  Elsevier

2.5.17  CEDAR

2.5.18  BRICS18  NIH BRICS

3          Requirements and High Level Use Cases

...