This page is part of the Clinical Study Schedule of Activities (v1.0.0: STU1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Home

Official URL: http://hl7.org/fhir/uv/vulcan-schedule/ImplementationGuide/hl7.fhir.uv.vulcan-schedule				Version: 1.0.0
Active as of 2023-04-18				Computable Name: StudyScheduleOfActivities

Background

Vulcan Schedule of Activities (SoA) Project

The core of this project is to define a usable pattern for a Clinical Trial Schedule of Activities structure using FHIR Resources and Processes, such that:

• it can be shared
• it can be interpreted, and
• it can be implemented in healthcare systems (such as EHR or PHR systems) and/or clinical research systems

The conduct of Clinical Trials are guided by the International Conference on Harmonization (ICH) guidelines for Good Clinical Practice (GCP) E6 (R2).¹ Core to this is the writing of a Clinical Trial Protocol, a document intended to describe the objectives, design, methodology, statistical considerations and aspects related to the organization of the clinical trial.

Trial protocols provide the background and rationale for conducting a study, highlighting specific research questions that are addressed, and taking into consideration ethical issues. Trial protocols must meet a standard that adheres to the principles of Good Clinical Practice (as mentioned above), and are used to obtain ethics approval by local Ethics Committees or Institutional Review Boards.

The Clinical Trial Protocol incorporates all the aspects of what is needed to define how the study is to be conducted and reviewed; for the purposes of this first iteration of the Implementation Guide we are constraining the scope to focus just on the elements incorporated in the Schedule of Activities.

What is the Schedule of Activities?

The NCI Controlled Vocabulary definition of the Schedule of Activities is: ²

A standardized representation of planned clinical trial activities including interventions (e.g., administering drug, surgery) and study administrative activities (e.g., obtaining informed consent, distributing clinical trial material and diaries, randomization) as well as assessments. See also schedule of assessments. Compare to study design schematic.

It is a focused section of the Protocol Document that lays out what activities are expected, and structurally when they are expected to occur. It is a design that is interpreted by the stakeholders to drive how the study is defined, planned and performed.

Vulcan SoA Implementation Guide (IG)

This IG is intended to provide a roadmap for adopters looking to use FHIR resources in order to support the planning and implementing Clinical Research designs. The Schedule of Activities is defined ​in a clinical trial as a standardised representation of planned activities, including interventions (e.g., administering drug, surgery), studying administrative activities (e.g., obtaining informed consent, distributing clinical trial material and diaries, randomization) and assessments.​

​The purpose of the Schedule of Activities is to communicate the scheduling of the planned activities required to support the research objectives of the study to enable operational implementation.​

Within the Vulcan SoA project we have considered two principal study types:

• Prospective – e.g., randomized clinical trials (RCT), concurrent cohort studies, observational studies, epidemiology, real world evidence (RWE)
• Retrospective – e.g., cohort studies, case-control studies, real world evidence

Examples of positive outcomes for this project include:

• Participant identification – feasibility , inclusion/exclusion criteria (prospective/retrospective)​
• Participant management – appointment scheduling (prospective)​
• Real world evidence – research data selection (retrospective)​
• Audit/Inspection – regulatory oversight period identification ​
• Resource planning (prospective)​
• Logistics planning (prospective)​
• Protocol adherence – streamlined deployment of protocol updates
• Portfolio management – reporting consistency across sites
• Site operational efficiency – task automation (e.g. order entry, reminders, etc) based on SoA
• Digital SOA can “serve as single source of truth” and be re-purposed downstream
  • Automate creation of EDC specification
  • Automate creation of SDTM datasets (especially trial design domains)
• Help/automate sites set up a study leading a reduced site burden
• Help sites run a study (scheduling, procedures to be performed)
• Help ensure compliance with a protocol
• Ensure SOA/protocol is implemented uniformly across sites

This iteration of the IG is designed to provide directional guidance and not be a prescriptive instruction of how to exactly implement SOA across all systems. As we learn more about how the different systems work and can be interfaced, we will continue to improve the IG to accommodate more use cases; iteratively working towards a solution that will be both functional and scalable.

Future elements for the Implementation Guide

There are different levels of complexity of SoA, which may not be fully represented in the current iteration of this IG. For example, how the design of an SoA may be implemented concerning different protocol types (e.g., adaptive, master, umbrella, basket, etc.). Furthermore, the type of research can vary across SoA designs, such as randomized vs. observational clinical trials, including the different data modalities to collect data (e.g., electronic data capture vs. direct data capture). The scope for the IG has been constrained to deliver a minimal viable solution for representation of a SoA. The following topics will be or have been evaluated for incorporation in the IG:

• Unscheduled or Conditional Activities
• Management of protocol compliance (deviations, violations, etc.)
• Complex protocols (e.g., adaptive, umbrella, basket)
• Non-trial integrations (e.g., use of RWD such as a vital statistic registry that determines a patients death via f/up period)
• How adjudications are managed
• Patient site transfers (i.e., relocations)
• Patients re-enrolling multiples times
• Inclusion/Exclusion criteria
  • Computable and Evaluable criteria that can be defined and processed by electronic systems
  • Complex inclusion/exclusion criterions
• Enhanced SoA headers (e.g., that include visit type such as home health, satellite site, virtual)
• How to better describe more complex activities (multi-omics, digital therapeutics, etc.)
• Tracking of primary, secondary, tertiary, and exploratory endpoints
• Instructional guidance in other protocol sections/footers that provide additional detail
• Managing multiple sub-study consents that can occur throughout the trial (some voluntary and others conditional-based)

Note that many of these expand the existing scope of the SoA project and will work best in a collaboration with other research-aware IGs such as the Vulcan Retrieval of Real World Data for Clinical Research IG. We have a rigorous process for evaluating and incorporating use cases into the development process.

References