View Source

{scrollbar:icons=false}

h1. {page-info:title}

h2. Pre Interview:

|| Item || Information/Response ||
| {color:#000000}{*}Date{*}{color}{color:#000000}:&nbsp;{color} | 12/10/2009 |
| {color:#000000}{*}Requirement # unique id{*}{color}: | Init1dbw4 |
| *Originator/Customer's Name*: | [Michael Riben|mailto:mriben@mdanderson.org] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
| *Originator/Customer's Company*: | MD Anderson \\ |
| *Stakeholder Community*: \\
Enter appropriate category of stakeholder from Primary Stakeholders:&nbsp;&nbsp;
* Software and Application designers and architects
* Software and Application engineers and developers
* Scientific and medical researchers
* Medical research protocol designers
* Clinical and scientific research data and metadata managers
* Clinicians
* Patients
* Medical research study participants
* Broader Stakeholders: caBIG® Community WS NIH projects and related commercial COTS vendors (caEHR, SDO's (HL7, CDISC); International Collaborators (e.g NCRI, cancerGrid, China), Government and regulatory bodies (FDA, CDC, ONC) \\
_[_(link to view SemConOps Stakeholders description_|Semantic Infrastructure Concept of Operations Stakeholders])._ | caBIG® Community WS Projects \\ |
| *Summary of requirement pre-interview, by Reviewer:* | MD Anderson is one of potentially many cancer research organizations that will be adopting non-caBIG technologies in order to meet their research and enterprise goals.&nbsp; However, it is highly desirable to adopt caBIG/NCI metadata standards in order to be able to share data and build interoperable systems.&nbsp; The challenge is that there is a need to develop localized data elements and terminologies that are not centrally managed at NCI.&nbsp; Different departments, labs, clinics, etc. within the research organization desire to maintain ownership of their metadata while still reusing common standards whenever possible.&nbsp; Therefore, the proposal is to federate the metadata infrastructure such that different organizations, departments, labs, software applications, etc. can maintain their own metadata while standards flow both top-down and bottom-up.&nbsp; The current semantic infrastructure at NCI is not amenable to this type of federated model.&nbsp; The caDSR has not been designed in a fashion that would allow other organizations to deploy their own caDSR and have data flow between the instances.&nbsp; MD Anderson is proposing to leverage and extend the cgMDR project in order to pilot federation of metadata management at their organization.
!camdr_approach.png|alt="flow of metadata management using cgMDR",width=488,height=377!
This would facilitate a federated architecture such as this:
!camdr_architecture.png|align=center,width=488,height=377,alt="diagram showing federated architecture"!\\
See the [VCDE:attached presentation|^MDACCMDR.ppt] for more information. All users of the semantic infrastructure would be effected by these requirements. \\ |
| *Recommended Next Step* Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room | Follow-up Interview |
\\
{scrollbar:icons=false}