Use the API interfaces on Clinical One microservices to build and deliver unified business processes

The great news is the Clinical One platform is built on the concept of an "RESTful API first" technology strategy. Every User Interface page built to support the current Clinical One RTSM and Data Collection capabilities serves as an orchestration layer that is loosely coupled via RESTful APIs to the Clinical One microservices. Every RESTful API call requires the same context across four key parameters: Tenant, User, Study, and Mode. This enables so many aspects of working with the valuable data captured in Clinical One for RTSM & Data Collection activities for your studies and sets the stage to integrate, perform complex analytics and extend the platform to enable a robust ecosystem around the core Clinical one Platform.

In this discussion, please post ideas, questions, etc. around your Clinical One Platform data strategy considerations and we'll get you pointed in the right direction!