Data governance for emerging technologies: applying ICH E6(R3) Section 4 to new paradigms

Free Lesson Preview

This is just the beginning

The full CRC track covers 8 courses from study start-up to close-out — the skills sponsors actually look for.

Already enrolled? Sign in

The technologies change. The principles do not.

Over the past three lessons, you have encountered data collection paradigms that would have been unrecognizable to a coordinator working ten years ago. Participants completing symptom diaries on smartphones at 7:00 PM from their living rooms. Cardiac patches generating 22 million data points per day without any human intervention. Laboratory values appearing in the EDC before the coordinator opens the system, transferred by an integration engine that runs every 60 minutes.

Each technology is different. The data volumes differ by orders of magnitude. The failure modes are distinct -- assessment fatigue is not the same problem as adhesive failure, and neither resembles a mapping error in an integration engine. The coordinator's operational responsibilities shift from technology to technology in ways that the preceding lessons have detailed.

And yet. Open ICH E6(R3) Annex 1, Section 4 -- the data governance framework you studied in Module 1 -- and you will find that it does not mention ePRO. It does not mention wearable devices. It does not mention EHR-to-EDC integration by name. It does not need to. The Section 4 framework was written to govern data regardless of the technology that produces it. The data lifecycle applies whether the data originate from a coordinator's keyboard, a participant's smartphone, a cardiac patch sensor, or an automated transfer engine. The computerized systems requirements apply to any system that creates, processes, or stores clinical trial data. The audit trail requirements apply to every modification, whether made by a human or an algorithm. The proportionality principle applies to every governance decision, from how rigorously to verify a transferred value to how frequently to review a compliance dashboard.

This is the capstone lesson of this course, and its purpose is synthesis. We are not learning new technologies here. We are applying the governance framework you already know to the technologies you have already studied -- and asking a question that will define the next decade of your career: what does the coordinator become when the data no longer need to be transcribed?