ISO 11179-3:2012 Figures Denise Warzel Convenor SC32/WG2 April 11, 2014.
CaDSR Software Users Meeting 3.1 Requirements Review 9/19/2005 caDSR Software Team Host: Denise...
-
Upload
clinton-mitchell -
Category
Documents
-
view
213 -
download
0
Transcript of CaDSR Software Users Meeting 3.1 Requirements Review 9/19/2005 caDSR Software Team Host: Denise...
caDSR Software Users Meeting
3.1 Requirements Review9/19/2005
caDSR Software TeamHost: Denise Warzel
NCICB, Assistant Director, caDSR
D. Warzel
caDSR 3.1 RequirementsReview
Form Builder Enhancements Curation Tool EnhancementsCDE Browser EnhancementsUML Model BrowserAdmin Tool EnhancementsSentinel Tool Enhancements Subset Value DomainsExpanded EVS linkagescaDSR UML Model EnhancementsParallel Enhancements/Fixes: – UML Model Loader– Semantic Integration Workbench (SIW) (expanded Beta program)– Excel Loader
D. Warzel
caDSR 3.1 RequirementsReview
Form Builder Enhancements – Question matching functionality similar to that found in the NCICB CRT desktop
application – Skip patterns – Form, Module, Question, Valid Value– Define UI Widget– Module search/copy– Subset Value Domains – Oct 3 design review– Classify and/or Designate all CDEs on Form– Display VD Attributes for Questions when DE has a Non-enumerated Value Domains.
Datatype, Format, Max Length, Min Length, Precision, Unit of Measure
Discussion: – Consider Module ‘status’, naming conventions to facilitate search/copy– Subset Value Domain: Handling of the CDE explicitly to identify that there is a subset
– could be handled using versions of the same CDE 1.0.1? “Mil Spec numbering”– Report for showing all “Usage” – CS/CSI link to create new CS if not already established
D. Warzel
caDSR 3.1 RequirementsReview
Curation Tool– Enhance attributes displayed for EVS concepts
Semantic Type, Concept status (e.g. retired)
– Attach documents– Search SnoMed– Search using Concepts: DEC, DE, Object Class, Value Domain – Search DE for “Derived Data Elements”– Search VD using Datatype
Discussion: - Concept Search: Name, Concept code
D. Warzel
caDSR 3.1 RequirementsReview
CDE Browser– Customized field selection for downloads from the CDE Browser– Improved Search
Search within results
Google like, “AND” and “OR” logic – More LOVs: EVS Root Concept ‘Widget”, Object Class, Classification Scheme
UML Model Browser – Search for, Browse, Export UML Model: Classes and Attributes
Discussion: – Would like to order the fields selected for download– Display Value Domain Representation information and concepts in Browser View– Help facilitate the VCDE model review to support the workflow– Extra line added in Excel download – TT item– Would like to be able to view the ‘UML Diagram’ more of a visual graphical view for
navigationConsider the “documentation” that is exported from the UML ModelUML Model friendly ‘language’Be nice to see the attributes (data elements) of the “class” including the inheritance
D. Warzel
caDSR 3.1 RequirementsReview
Admin Tool– Allow Concept Class maintenance– Allow DEs to be searched for and Classified using Public IDs– Versioning of Protocols– User set “Latest Version Indicator”– Conceptual domain, Classification Scheme, Classification Scheme Item
Maintenance– Contact/Submission/Steward UI support– View/Review all Related Versions
Discussion: – Maybe Amendments by Protocol ID – sounds like a standard for protocol
metadata is not yet agreed upon for this community– Versioning: Cooperative groups us same Protocol ID and put a new
Amendment number – Versioning: option to copy relationships to all forms from original
Version of Protocol– Conduct Forms Management KA
D. Warzel
caDSR 3.1 RequirementsReview
Sentinel Tool– History Table and Report format enhancements– Improve Alert create/edit UIs– Allow Alert creation via API– Set by “Protocol”
Subset Value Domains- Oct 3rd Proposal
- Includes establishing existing subsets from Forms
Discussion: Include Dianne Reeves in revised design reviews
D. Warzel
caDSR 3.1 RequirementsReview
Expanded EVS linkage – Association/EVS linkage for Conceptual Domain, Classification Scheme
and CSI caDSR Database Model
– Forms Metadata– Protocol, Service Metadata– Version Protocols– Change “Preferred Name” to “Short Name”
On screen annotation that “Long Name” is ISO 11179 Preferred Name
"Read Only" caDSR Requirements analysis
Discussion: – In caDSR metamodel and UIs, handling of ordering using Boolean
operators between Multiple Qualifiers in the concept map: Concept Relationships (e.g. circulatory invasion)
D. Warzel
caDSR 3.1 Requirements“In Parallel”
UML Loading– Value Domain support– Point to existing caDSR Content– Support for UML Model Versioning– Export to XMI “Round Trip”– Automated Conceptual Domain selection
Semantic Integration Workbench (SIW)– Expanded Beta – NOW (email: [email protected] to participate)– Coming in Version 2:
Annotation using existing caDSR Content– Value Domains
Validation of EVS and caDSR linkagesSet Conceptual Domains – EVS Root Concept
Excel Loader– Support for loading Concept Class– Support for linking Concepts to OC, Prop, Value Meaning, VD, etc.
Discussion: – Validation for exact semantic mapping at all levels of the metadata – Priority would reuse of
CDEs, Value Domains, with Validation of Class (Object Class) and Attributes (Property)
D. Warzel
Q& A
See SAIC 3.1 Requirements Document
Surfacing potential discrepencies/mappings between CDEs created absent an Object Model or in different vocabulary spaces
– Concept drift, alternative mappings
– Consider feature in curation tool to search Meta for concept based on source vocab concept identifier, use NCI Thesaurus concept code instead