Senior Clinical Informatics Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose."
Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
Preserve ALL substantive information; do NOT invent or summarize away detail.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
Prefer a few substantive sections over many thin ones.
Output ONLY the HTML fragment — no /, no markdown code fences.
Now, let's parse the content.
The posting starts with a paragraph about the merger on 1 April 2026, forming PSD Scotland. That's background.
Then "Flexible Location: PSD Scotland is a remote-friendly employer..." That's about location/working arrangements.
"Work Pattern: Fixed Term, Part Time, 3 days per week; 6 sessions (24)> hours per week Fixed-term or Secondment** for 2 years from date of appointment..." That's schedule.
"Salary: The successful candidate will be remunerated according to their professional background, e.g. Consultant, GP, SAS or other appropriate pay scale. You must have eligibility and entitlement to work in the UK..." That's pay.
"Who We Are" section describes the organization.
"The Opportunity" describes the role.
"Key Skills We Are Seeking" lists skills.
"Benefits Which Matter" lists benefits.
"Diversity and Inclusion" section.
"Next Steps" includes application process, interview dates, etc. This is application instructions, so should be removed per instruction.
Also there's a paragraph about right to work, visa, etc. That's legal/boilerplate, should be removed.
Contact information for adjustments: "If you are considering applying and would like to discuss the opportunity, any adjustments or alternative work patterns, please contact Dr Sam Patel sam.patel@nhs.scot." That could be kept as a note.
But the instruction says remove application instructions. The contact for adjustments might be considered part of application process. However, it's also about flexible working. I'll include it in the Work Pattern or Flexible Location section.
Now, I need to structure into sections with h3 headings.
Possible sections:
- About the Role (or The Opportunity)
- Responsibilities (maybe from Key Skills and Opportunity)
- Requirements (from Key Skills and other requirements)
- Benefits
- Work Pattern (Schedule)
- Pay (Salary)
- Location / Flexible Working
- Diversity and Inclusion
- About the Organization (Who We Are)
But the instruction says prefer a few substantive sections over many thin ones. So I can combine some.
Let's see the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I'll create:
- About the Role (combining "The Opportunity" and "Who We Are"? But "Who We Are" is about the organization. Could be separate "About the Organization".)
- Responsibilities (from Key Skills and Opportunity)
- Requirements (from Key Skills, and also the requirement for registered medical practitioner, license to practice, etc.)
- Benefits
- Work Pattern (Schedule)
- Pay
- Flexible Working (Location)
- Diversity and Inclusion
But note: "Key Skills We Are Seeking" is a list of skills/experience. That could be Requirements or Qualifications.
Also, the role requires: "registered medical practitioner with a license to practice and substantial clinical experience, with a strong background in health informatics, and a demonstrable track record in supporting the effective use of data, information, and digital technology to improve health and social care delivery." That's a requirement.
The Key Skills list includes:
- Substantial experience of delivering care within the UK health system, combined with experience of leading or supporting digital health or clinical informatics programmes.
- Experience of applying clinical informatics expertise to digital products and services, including influencing their design, development or implementation.
- Experience of clinical safety, risk management and governance, with practical knowledge of relevant digital clinical safety standards or frameworks.
- Experience of leadership and collaborative working, including influencing change and engaging effectively across clinical, technical, professional and organisational boundaries.
- Demonstrate honesty, integrity, care and compassion when dealing with others, utilising tact and persuasion skills when necessary
- Ability to work on own initiative, to organise and prioritise own workloads, to meet strict deadlines
These are requirements/skills.
Also, there's a note: "It is not essential to be in a Senior Clinical Informatics role right now—you may be returning from a career break..." That's part of Diversity and Inclusion or Requirements.
Now, Benefits list:
- Life-work balance - with opportunities for flexible working and hybrid working
- Generous NHS pension scheme
- Annual incremental salary progression (up to the maximum of the salary band) plus annual NHS salary scale review
- Annual Leave - 27 Days increasing in line with service plus 8 days public holiday
- NHS discounts and more
Work Pattern: Fixed Term, Part Time, 3 days per week; 6 sessions (24) hours per week. Fixed-term or Secondment for 2 years. NHS applicants get secondment first; non-NHS fixed-term or secondment considered.
Salary: remunerated according to professional background (Consultant, GP, SAS or other appropriate pay scale). Must have eligibility to work in UK.
Flexible Location: remote-friendly, staff based throughout Scotland, support office-based and hybrid working, welcome conversations about alternative working patterns.
Diversity and Inclusion: paragraph about hiring best talent, encourage applications from all backgrounds, under-represented groups, etc.
Now, I need to output HTML fragment with h3 headings and ul/li for lists, p for prose.
I'll structure as:
About the Role
... from The Opportunity and Who We Are ...
Responsibilities
- ... from Key Skills and Opportunity ...
But the posting doesn't explicitly list responsibilities; it lists skills sought. However, the Opportunity says: "The role will have an emphasis on the clinical risk management (CRM) for the development of national level health and care technologies built by PTS; however, will have the opportunity to expand the service and build wider clinical informatics services." That's a responsibility.
I can infer responsibilities from the skills. But the instruction says preserve ALL substantive information; do NOT invent. So I should not create responsibilities that aren't stated. The posting has "Key Skills We Are Seeking" which are essentially requirements. There's no explicit "Responsibilities" section. So maybe I should not create a Responsibilities heading if there's no explicit list. Instead, I can have a "Requirements" or "Skills and Experience" section.
The instruction says: "include a section ONLY when the posting has real, specific content for it". So if there's no responsibilities list, don't create a heading.
Thus, I'll create sections based on actual content:
- About the Organization (Who We Are)
- About the Role (The Opportunity)
- Requirements (Key Skills We Are Seeking, plus the medical practitioner requirement)
- Benefits
- Work Pattern
- Pay
- Flexible Working
- Diversity and Inclusion
But "About the Organization" and "About the Role" could be combined? The instruction says prefer a few substantive sections. I'll keep them separate as they are distinct.
Now, let's write the HTML.
First, the background paragraph about merger: "On 1 April 2026, NSS and NES became one national organisation... Public Services Delivery Scotland (PSD Scotland)." That's part of Who We Are.
I'll include that in About the Organization.
Now, the "Flexible Location" and "Work Pattern" and "Salary" are metadata. The instruction says: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." But these are not minor; they are important details. However, they are not section headings like "Pay" and "Schedule" are example headings. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Pay and Schedule are example headings. So I should create Pay and Schedule sections if the posting states them. It does state Salary and Work Pattern. So I'll create Pay and Schedule sections.
Similarly, Flexible Location could be part of Schedule or a separate "Location" section. But the example doesn't include Location. I'll include it in Schedule or as a separate "Flexible Working" section. Since the posting has a distinct "Flexible Location" paragraph, I'll make a "Flexible Working" section.
Now, the "Next Steps" and legal boilerplate about right to work, visa, etc. should be removed.
Contact for adjustments: "If you are considering applying and would like to discuss the opportunity, any adjustments or alternative work patterns, please contact Dr Sam Patel sam.patel@nhs.scot." I'll include that in Flexible Working or as a note.
Now, let's draft.
I'll start with About the Organization.
About the Organization
On 1 April 2026, NHS National Services Scotland (NSS) and NHS Education for Scotland (NES) merged to form Public Services Delivery Scotland (PSD Scotland). This new organisation plays a pivotal role in supporting the renewal and ensuring the long-term sustainability of health and care services across Scotland. PSD Scotland unites expertise from NES and NSS to accelerate national programmes that support the NHS to deliver better care, now and in the future. The organisation supports staff with education and training, provides tools and data that improve services, and runs vital national functions such as procurement, logistics, and blood, tissue and cell services. PSD Scotland acts as the public sector’s enabler of transformation, driving digital innovation, workforce development, and Once for Scotland services to deliver efficient, equitable, and future-ready health and social care. Its work supports the ten-year direction set by the Scottish Government's Health and Social Care Service Renewal and Population Health frameworks, bringing care closer to home, strengthening prevention, and helping build a sustainable, joined-up system that is innovative and responsive to local communities.
Then About the Role:
About the Role
The role is line managed by the Digital Clinical Lead for PTS under the Medical Directorate and aligns to the
for prose." Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's parse the content. The posting starts with a paragraph about the merger on 1 April 2026, forming PSD Scotland. That's background. Then "Flexible Location: PSD Scotland is a remote-friendly employer..." That's about location/working arrangements. "Work Pattern: Fixed Term, Part Time, 3 days per week; 6 sessions (24)> hours per week Fixed-term or Secondment** for 2 years from date of appointment..." That's schedule. "Salary: The successful candidate will be remunerated according to their professional background, e.g. Consultant, GP, SAS or other appropriate pay scale. You must have eligibility and entitlement to work in the UK..." That's pay. "Who We Are" section describes the organization. "The Opportunity" describes the role. "Key Skills We Are Seeking" lists skills. "Benefits Which Matter" lists benefits. "Diversity and Inclusion" section. "Next Steps" includes application process, interview dates, etc. This is application instructions, so should be removed per instruction. Also there's a paragraph about right to work, visa, etc. That's legal/boilerplate, should be removed. Contact information for adjustments: "If you are considering applying and would like to discuss the opportunity, any adjustments or alternative work patterns, please contact Dr Sam Patel sam.patel@nhs.scot." That could be kept as a note. But the instruction says remove application instructions. The contact for adjustments might be considered part of application process. However, it's also about flexible working. I'll include it in the Work Pattern or Flexible Location section. Now, I need to structure into sections with h3 headings. Possible sections: - About the Role (or The Opportunity) - Responsibilities (maybe from Key Skills and Opportunity) - Requirements (from Key Skills and other requirements) - Benefits - Work Pattern (Schedule) - Pay (Salary) - Location / Flexible Working - Diversity and Inclusion - About the Organization (Who We Are) But the instruction says prefer a few substantive sections over many thin ones. So I can combine some. Let's see the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll create: - About the Role (combining "The Opportunity" and "Who We Are"? But "Who We Are" is about the organization. Could be separate "About the Organization".) - Responsibilities (from Key Skills and Opportunity) - Requirements (from Key Skills, and also the requirement for registered medical practitioner, license to practice, etc.) - Benefits - Work Pattern (Schedule) - Pay - Flexible Working (Location) - Diversity and Inclusion But note: "Key Skills We Are Seeking" is a list of skills/experience. That could be Requirements or Qualifications. Also, the role requires: "registered medical practitioner with a license to practice and substantial clinical experience, with a strong background in health informatics, and a demonstrable track record in supporting the effective use of data, information, and digital technology to improve health and social care delivery." That's a requirement. The Key Skills list includes: - Substantial experience of delivering care within the UK health system, combined with experience of leading or supporting digital health or clinical informatics programmes. - Experience of applying clinical informatics expertise to digital products and services, including influencing their design, development or implementation. - Experience of clinical safety, risk management and governance, with practical knowledge of relevant digital clinical safety standards or frameworks. - Experience of leadership and collaborative working, including influencing change and engaging effectively across clinical, technical, professional and organisational boundaries. - Demonstrate honesty, integrity, care and compassion when dealing with others, utilising tact and persuasion skills when necessary - Ability to work on own initiative, to organise and prioritise own workloads, to meet strict deadlines These are requirements/skills. Also, there's a note: "It is not essential to be in a Senior Clinical Informatics role right now—you may be returning from a career break..." That's part of Diversity and Inclusion or Requirements. Now, Benefits list: - Life-work balance - with opportunities for flexible working and hybrid working - Generous NHS pension scheme - Annual incremental salary progression (up to the maximum of the salary band) plus annual NHS salary scale review - Annual Leave - 27 Days increasing in line with service plus 8 days public holiday - NHS discounts and more Work Pattern: Fixed Term, Part Time, 3 days per week; 6 sessions (24) hours per week. Fixed-term or Secondment for 2 years. NHS applicants get secondment first; non-NHS fixed-term or secondment considered. Salary: remunerated according to professional background (Consultant, GP, SAS or other appropriate pay scale). Must have eligibility to work in UK. Flexible Location: remote-friendly, staff based throughout Scotland, support office-based and hybrid working, welcome conversations about alternative working patterns. Diversity and Inclusion: paragraph about hiring best talent, encourage applications from all backgrounds, under-represented groups, etc. Now, I need to output HTML fragment with h3 headings and ul/li for lists, p for prose. I'll structure as:
About the Role
... from The Opportunity and Who We Are ...
Responsibilities
- ... from Key Skills and Opportunity ...
or drop it." But these are not minor; they are important details. However, they are not section headings like "Pay" and "Schedule" are example headings. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Pay and Schedule are example headings. So I should create Pay and Schedule sections if the posting states them. It does state Salary and Work Pattern. So I'll create Pay and Schedule sections.
Similarly, Flexible Location could be part of Schedule or a separate "Location" section. But the example doesn't include Location. I'll include it in Schedule or as a separate "Flexible Working" section. Since the posting has a distinct "Flexible Location" paragraph, I'll make a "Flexible Working" section.
Now, the "Next Steps" and legal boilerplate about right to work, visa, etc. should be removed.
Contact for adjustments: "If you are considering applying and would like to discuss the opportunity, any adjustments or alternative work patterns, please contact Dr Sam Patel sam.patel@nhs.scot." I'll include that in Flexible Working or as a note.
Now, let's draft.
I'll start with About the Organization.
About the Organization
On 1 April 2026, NHS National Services Scotland (NSS) and NHS Education for Scotland (NES) merged to form Public Services Delivery Scotland (PSD Scotland). This new organisation plays a pivotal role in supporting the renewal and ensuring the long-term sustainability of health and care services across Scotland. PSD Scotland unites expertise from NES and NSS to accelerate national programmes that support the NHS to deliver better care, now and in the future. The organisation supports staff with education and training, provides tools and data that improve services, and runs vital national functions such as procurement, logistics, and blood, tissue and cell services. PSD Scotland acts as the public sector’s enabler of transformation, driving digital innovation, workforce development, and Once for Scotland services to deliver efficient, equitable, and future-ready health and social care. Its work supports the ten-year direction set by the Scottish Government's Health and Social Care Service Renewal and Population Health frameworks, bringing care closer to home, strengthening prevention, and helping build a sustainable, joined-up system that is innovative and responsive to local communities.
Then About the Role:About the Role
The role is line managed by the Digital Clinical Lead for PTS under the Medical Directorate and aligns to the