Skip to content
National Clinical Informatics Service for Scotland National Clinical Informatics Service for Scotland

Menu

  • Clinical Safety
    • Clinical Safety Cases
    • Our Approach to Clinical Safety
  • Medical Device Regulations
    • Software as a Medical Device
    • Quality Management System
  • Clinical Terminologies
  • Primary Care Informatics
  • About us
    • The Team
    • Contact Us
  1. Home
  2. Stage 2 Project Initiation

Back to   Home

Introduction

  • Introduction
  • What is a CSC?
  • Previous CSCs
  • CSO and CSE Skillset

Benefits

  • Benefits of a CSC

Approach

  • PRINCE2
  • Process Flowchart
  • Quality Management System (QMS)
  • Roles & Responsibilities
  • MDR & SaMD
  • Risk Controls
  • Approach to creating a Clinical Safety Case
  • ISO Standards

CSC Stages

  • Pre Project Tasks
  • Stage 1 Project Start Up
  • Stage 2 Project Initiation
  • Stage 3 Managing Product Delivery
  • Stage 4 Managing Product Delivery
  • Stage 5 Managing Product Delivery
  • Stage 6 Managing Product Delivery

Governance

  • Overall Project Governance

Case Studies

  • Feedback and Testimonies
  • Case Studies

Documentation

  • Templates
  • Standard Operating Procedures (SOPs)
View Categories
  • Home
  • Playbook
  • CSC Stages
  • Stage 2 Project Initiation

Stage 2 Project Initiation

2 min read

Define scope
This is done through a combination of discussion with the commissioning programme, SMEs, NCSAS team and agreed by the NCSAS Head of Service and Chief Clinical Informatics Officer (CCIO).

Create CSC documentation
Several key documents are created from templates at this stage:
• Project Brief
• Clinical Risk Management Plan (CRMP)
• Project Initiation Document (PID)
• Project Risk and Issues Log
• Planner
• Action Log
• Daily Log
• Controls evidence list

Create Clinical Risk Management File (CRMF)
The Clinical Risk Management File is the folder where all of the relevant CSC documentation is stored for transfer back to the commissioning board on completion of the CSC. The file should be created at this stage and populated over the course of the CSC.

Book CSC meetings
To ensure effective collaborative working and communication, regular meetings are scheduled with the CSC project team. These may include project management, Head of Service and CCIO representation as required.

Identify contacts from programme
A CSC requires regular communication with key members of the commissioning programme team to ensure free-flow of information. Relevant individuals are identified who the CSC project team can approach for documents and to have questions answered in a timely fashion.

Identify Subject Matter Experts (SMEs)
We identify key individuals from all areas relevant to the programme e.g. Information Governance, Cybersecurity, Programme leads, Technical, Architecture, Clinical. We consider individuals at both board and national level and also identify any CSOs/CSEs within the programme team.
Initial SME session(s) are conducted as appropriate to gather information needed at this stage.

Collate and review programme documentation
The CSC project team collate and review any available programme or solution documentation to develop an awareness of the digital solution e.g. architecture documents, security protocols, data flows, DPIA, supplier CSC.

Review related CSCs
The CSC project team review any previous completed CSCs that may have factors in common with the digital solution, or indeed integrate with it. This furthers understanding and allows identification of relevant hazards, causes or controls which may be transferrable.

Orientation Workshop
The Orientation Workshop is a precursor to the Hazard Workshops and is an opportunity for all invited to learn about the digital solution; the approach, scope and timelines for producing the CSC; and to engage with the programme team, SMEs, and the NCSAS team.

Updated on 23 May 2024
Stage 1 Project Start UpStage 3 Managing Product Delivery

© Copyright, National Clinical Informatics Service for Scotland 2026