OCNG OpenClinica Next Generation 1

© What Is OCNG? OpenClinica Next Generation A Test Bed For New Technology Developed Independently of OC 3.x Keeping Same Features, Adding a Few More Same Database Schema 100% REST Interface Complete Client and Server Decoupling Alpha Release 26-Aug

© How much of this will end up in the real OpenClinica? It depends on how much you like it. When it is released as an Alpha it will have many documented aspects to it that may become part of a future OpenClinica release. 3

© Project Timeline July 8: Initial pre-pre-pre-alpha that will include a narrow cross section (about 10%) of the basic operations of OC, now mimicked in this new architecture July 15, July 22, July 29, August 5, August 12, August 19: Weekly milestone releases tracking a path to the August 26 Alpha release. August 26: Alpha release of OCNG that will include a wide cross section (about 80%) of the current operations of OC, along with many new features. 4

© 100% REST, 100% Data Portable ODM Fragments Sent Back and Forth Every OpenClinica action will be represented Complete Decoupling of Service and Clients 5

© One OpenClinica Service, Many Clients The Web Service Is The Web Application All clients will access this service the same way: OpenClinica Browser Client External REST Web Service Clients iOS Applications Android Applications All of these clients access the same REST URLs and send and receive the same ODM fragments in either JSON or XML. 6

© Architecture Breakdown The following components will be described in terms of their composition and differences from the current architecture: Same Database Schema, Many Databases Supported Full Hibernate ORM Implementation Fully Published Service Layer REST URL Interface Fully Decoupled HTML Client 7

© Same Database Schema, Many Databases Full Backwards Compatibility With 3.x Schema Database For Storage and Not Application Logic Removal of Vendor-Specific Artifacts While Postgres Default, Support for Many Vendors 8

© Full Hibernate ORM Implementation Vendor-neutral database support by using Object Relational Mapping and no vendor-specific procedures. Hibernate will be used for the Object Relational Mapping (ORM) functionality. Straightforward Data Entities and Data Access Objects that map the OpenClinica services to the data that is acted on. There will be a single location for all native SQL calls. 9

© Fully Published Service Layer All of the application services will be mapped to a published service layer specification This eliminates the secret sauce factor where it is difficult to trace application functionality. Each of the services will be grouped and mapped to a similarly grouped set of REST URLs so that it is easy to work with the application logic. 10

© REST URL Interface All interaction with OpenClinica is accomplished via a data exchange referenced by an easy to understand REST convention. These REST URL patterns map smoothly to the published OpenClinica service layer. XML and JSON, usually in the format of ODM or ODM fragments, are exchanged as data. 11

© Fully Decoupled HTML Client The HTML, JavaScript, and CSS based client is independent of the OpenClinica and its services. Once loaded into browser, only service calls and data are exchanged. Same REST URL based service API that would be used by another type of client. Same REST URL based service API this is used by external web service interfaces. 12

© CRF Authoring Improvements A unified interface will generate the eCRF, the printable CRF, and the authoring interface to the CRF. Layout will be more controllable since every item can be custom sized and positioned. Rules and Validation can be authored in the form interface. Excel-based CRFs will still be supported but not required. 13

© 14 Enough of your Vulcan logic, where is the code? Application and source code distribution: The latest deployment: OCNG Wiki: +OpenClinica+Next+Generationhttp:// :8090/display/OCNG/OCNG+- +OpenClinica+Next+Generation