 |
Page History
...
| Name | Role | Present |
|---|---|---|
| Wright, Larry | NIH/NCI | x |
| Fragoso, Gilberto | NIH/NCI | x |
De Coronado, Sherri | NIH/NCI | x |
Safran, Tracy | NIH/NCI | x |
| Ong, Kim L | IS | x |
| Lucas, Jason R | IS | x |
| Bauer, Scott | Mayo | x |
| Stancl, Craig | Mayo | x |
| Endle, Cory | Mayo | x |
| Wynne, Robert | NIH/NCI | x |
| Brem, Larry | NIH/NCI [C] | x |
| Pan, JJ | NIH/NCI [E] | x |
| Tran, Tin | NIH/NCI [C] | x |
| Ahmed, Shamim | NIH/NC [C] | |
| Haber, Margaret | (NIH/NCI) | |
| Roth, Laura | (NIH/NLM) | |
| Ramani, Vivek | (NIH/NCI) [C] | |
| Carlsen, Brian | (NIH/NCI) [C] | |
| Wong, Joanne | x | |
Kuntipuram, Kumar | x |
...
| Priorities for the Extension (Scott, Craig) | VSMC, CTS2 Services, CTS2 Framework, discussion and other priorities as time allows. Continuing discussion from last week. What an implementer needs to look at. What are you going to expose. REST connectivity helps define client platform. VSMC concerns exist around ability to pull value sets from LexEVS CTS2 in the same manner. Profiles are a factor in providing common module sets to implement in order for different services to be interoperable with one another. Cooperative effort with NCBO and NLM would be appropriate. Need to justify expansion by showing examples. FDA Structured Product Labeling: some come from NCI others from NLM, NDFRT. Switch from one source to another seamlessly. What would it take to define the NLM versions. Value Sets are just pulling code and term. FDA want's own term to be represented. CDISC has it's own terms. Some suggestion that we move forward with the framework update, but given the transformations it is not required.
| ||
| 6.1 QA and Deployment (Tin, Jason, Scott) | Status: | ||
| Forums and user support (Gilberto and Sherry) | Status: | ||
| Code coverage reports and QA JUnit documentation (Tracy) |
...
