eHealth Clinical Portal Programme Board: Terms of Reference
eHealth Clinical Portal Programme Board: Terms of Reference
eHealth Clinical Portal Programme Board: Terms of Reference
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>eHealth</strong> <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong>: <strong>Terms</strong> <strong>of</strong> <strong>Reference</strong><br />
1. Purpose<br />
The <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong> provides direction and leadership to the<br />
<strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong><br />
2. Remit<br />
3. Chair<br />
Strategy<br />
• Owns the vision for the programme, providing clear direction and<br />
leadership throughout its life, including any phases agreed.<br />
• Ensures the alignment <strong>of</strong> <strong>Clinical</strong> <strong>Portal</strong> activity with <strong>eHealth</strong> strategic<br />
direction and related matters across the Scottish Government.<br />
• Agrees the clinical portal sourcing strategy.<br />
• Agrees and owns the <strong>Clinical</strong> <strong>Portal</strong> roadmap<br />
Governance<br />
• Provides strong links into senior decision-making bodies and structures<br />
within NHS <strong>Board</strong>s, including Chief Executives and Chairs.<br />
• Approves the programme Business Case<br />
• Oversees the <strong>Clinical</strong> <strong>Portal</strong> programme plan, project portfolio and<br />
interdependencies.<br />
• Approves the funding model to support realisation <strong>of</strong> the desired<br />
programme outcomes.<br />
Management<br />
• Acts as a focus for all <strong>Clinical</strong> <strong>Portal</strong> related activity<br />
• Approves programme budget decisions, in line with delegated authority<br />
• Manages programme level risks and issues.<br />
• Provides the mandate to set up, close and suspend individual projects<br />
<strong>of</strong> the programme<br />
• Approves the communications strategy and plan<br />
• Delegates authority as appropriate, for example to the VPR Discovery<br />
Project <strong>Board</strong> or the IAM <strong>Programme</strong> <strong>Board</strong><br />
The <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong> is chaired by Paul Rhodes, <strong>eHealth</strong><br />
<strong>Programme</strong> Director, Scottish Government Health Department, (SGHD).<br />
4. Membership<br />
The <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong> is drawn from a range <strong>of</strong> senior<br />
stakeholders from across the organisation, including Chief Executive, Director<br />
<strong>of</strong> Finance, <strong>eHealth</strong> and <strong>Clinical</strong> Leads and SGHD. This to ensure that the<br />
<strong>Board</strong> has the appropriate support and authority to take decisions on behalf <strong>of</strong><br />
the service and the mechanism for such decisions to be disseminated and<br />
implemented. Members have a role <strong>of</strong> communicating and championing the
programme with the stakeholder groups they represent. Membership will be<br />
by invitation <strong>of</strong> the <strong>Board</strong>. In the normal course <strong>of</strong> events, substitutes are not<br />
permitted.<br />
Members<br />
Paul Rhodes<br />
<strong>eHealth</strong> <strong>Programme</strong> Director, SGHD (Chair)<br />
John Turner Chief Executive, NHS 24<br />
Stella Clark<br />
Medical Director (primary care), NHS Fife<br />
Jason Leitch<br />
National <strong>Clinical</strong> Lead for Patient Safety and Improvement, SGHD<br />
Robin Wright<br />
Chair <strong>eHealth</strong> Leads, NHS Lanarkshire<br />
Cliff Barthram<br />
CCLG representative, NHS Tayside<br />
Caroline Hutchinson EESS Project Manager representing Directors <strong>of</strong> HR<br />
Ian Welsh<br />
Chief Executive: Long Term Conditions Alliance<br />
Susan Douglas-Scott Patient representative<br />
Alan McDevitt<br />
GP representative<br />
Annie Buchanan Nurse Directors’ representative, NHS Fife<br />
Lorna Ramsay <strong>Clinical</strong> Lead, NSS<br />
Julie Falconer<br />
<strong>Programme</strong> Manager, SGHD<br />
5. <strong>Clinical</strong> <strong>Portal</strong> Governance Context<br />
Note that the national Identity Access and Management (IAM) programme will<br />
report to the <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong>. This is due to the strategic role<br />
that IAM takes in the longer-term view <strong>of</strong> portal delivery. The budget<br />
responsibility delegated to the <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong> from the<br />
Strategy <strong>Board</strong> will include funding for the IAM <strong>Programme</strong><br />
6. Accountability<br />
The <strong>Clinical</strong> <strong>Portal</strong> <strong>Programme</strong> <strong>Board</strong> will report direct to the <strong>eHealth</strong> Strategy<br />
<strong>Board</strong>. The <strong>Board</strong> should consider in light <strong>of</strong> the frequency <strong>of</strong> its meetings and<br />
the significance <strong>of</strong> programme decisions required, whether it wishes another<br />
group to carry out some work on its behalf. Options would include:<br />
• the full <strong>Programme</strong> <strong>Board</strong> agrees to meet regularly to minimise the<br />
requirement for delegation;<br />
• the Chair (senior Responsible Owner) is empowered to make decisions
7. Meetings<br />
on behalf <strong>of</strong> the <strong>Board</strong> between meetings;<br />
• a sub-group <strong>of</strong> the <strong>Board</strong> is formed with a more frequent meeting<br />
schedule;<br />
• the <strong>eHealth</strong> <strong>Programme</strong> <strong>Board</strong> is requested to take a role<br />
It is suggested that the <strong>Board</strong> meets on a six-weekly basis, and or when the<br />
need arises. If the <strong>Board</strong> wishes to meet less frequently, then the options<br />
outlined in item 6 above should be considered.