1 / 6

Emerging Technologies

Emerging Technologies. Working Group Update. Metadata Definitio n. Leader: Isabelle deZegher No formal meeting Finalize document through TC – Available Apr2014. ST: Representing PRM/ SDM.xml in RDF. Leader: Geoff Low Review the current draft model

marika
Download Presentation

Emerging Technologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Emerging Technologies Working Group Update

  2. Metadata Definition • Leader: Isabelle deZegher • No formal meeting • Finalize document through TC – Available Apr2014

  3. ST: Representing PRM/SDM.xml in RDF Leader: Geoff Low • Review the current draft model • Discuss modeling of study parameters/parameter groups, study activities and planned activities • Discuss next steps for the RDF model • Do not want it to become another “under-used” representation of structured protocol content

  4. ST: Analysis Results Metadata Co-Leads: Ian Fleming, Marc Andersen • Introduce team and concept to the broader community • Developed draft metadata for count and summary statistic analysis procedures • Identified central tendency, t-test, ANOVA as next analyses to develop • Identified strategy for researching publically available existing models • Identified alignment needs with the define.xml team and standard scripts repository white paper team

  5. ST: keyCRF Leader: Landen Bain, Gokce B. LaleciErturkmen Areas to be Developed: • Overall process update (including programming, SDV, query management, audit …) • Mapping CDASH / CCD (CDISC / HL7…probably not PhUSE) • Functionalities/ UI for managing change of CCD Xpath mapping based on context • Benefit case - value of CCD integration in EDC • Archives definition Next Steps: • CDASH/CCD mapping • Confirm with CDISC possibility to work on mapping • Draft mapping for a few limited domains • Define project and what can be done in PhUSEwithout funding • Pilot

  6. Lowering the Barrier to Cloud Adoption Leader: Tony Hewer • Enthusiasm about what we’ve come up with in our first draft • Analytics done in the cloud • Ways of working • Additional (technical and procedural) controls around data access •  Cloud is facilitating “freer” access  roles and rules • App architecture – leverage cloud elasticity  increased validation  think about deployment • Cloud is enabling wider aspects of “consent”  use of data  privacy rules by nation/state • Overwhelming scope??? • Audits/due-diligence - Ubiquity!!! • Physical location(s) of IaaS • We had deliberately avoided getting into s/w dev and DevOps ?? • FAQs section  future edtions • Cloud is a great leveller – apps, data availability, ease of use • IP – pre-clinical

More Related