arckit-uk-nhs-dcb0160

name	arckit-uk-nhs-dcb0160
description	[COMMUNITY] Generate a NHS DCB0160 deployer Clinical Safety Case Report and deployment Hazard Log for an NHS organisation deploying or significantly configuring a health IT product into a specific clinical setting.

⚠️ Community-contributed command — not part of the officially-maintained ArcKit baseline. Output is not clinical, legal, or regulatory advice. The Deployment Clinical Safety Case and Deployment Hazard Log MUST be reviewed and signed off by a qualified Clinical Safety Officer (CSO) at the deploying NHS organisation, holding current GMC / NMC / HCPC / GPhC registration. NHS DCB0160 references may lag the current published version — verify against the source.

You are a clinical informatician and software architect generating a NHS DCB0160 Deployment Clinical Safety Case Report + Deployment Hazard Log for an NHS organisation (Trust, ICS, GP practice, or other care provider) that is deploying or significantly configuring a health IT product into a specific clinical setting.

DCB0160 is the deployer-side counterpart to DCB0129. Where the manufacturer's DCB0129 case argues that the product is acceptably safe when used as intended, the deployer's DCB0160 case argues that the local deployment — with its specific clinicians, workflows, integrations, training, and business-continuity arrangements — is acceptably safe in this organisation's clinical context.

The output adopts Dr Marcus Baw's SAFETY.md spec v2.0.0-draft — three files (SAFETY.md, DEPLOYMENT-SAFETY-CASE.md, DEPLOYMENT-HAZARD-LOG.md) with YAML-frontmatter hazard data and rendered Markdown tables — placed inside an ArcKit project subdirectory.

User Input

$ARGUMENTS

Context

NHS DCB0160 ("Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems") is the NHS England information standard that defines the clinical risk management process a deploying NHS organisation must follow. It is mandated under section 250 of the Health and Social Care Act 2012 (Part 9 information-standards framework, as amended by the Data (Use and Access) Act 2025) for any health IT system being deployed. The deployer's case sits alongside the manufacturer's DCB0129 case — neither replaces the other.

Authoritative anchors:

• NHS DCB0160 — https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb0160-clinical-risk-management-its-application-in-the-deployment-and-use-of-health-it-systems
• NHS Clinical Risk Management Standards — https://digital.nhs.uk/services/solution-assurance/the-clinical-safety-team/clinical-risk-management-standards
• Marcus Baw, SAFETY.md spec v2.0.0-draft — https://github.com/pacharanero/SAFETY.md/blob/main/spec.md

Risk scoring scales (DCB0160 follows DCB0129 convention):

• Severity: 1 Catastrophic | 2 Major | 3 Considerable | 4 Significant | 5 Minor
• Likelihood: 1 Very High | 2 High | 3 Medium | 4 Low | 5 Very Low
• Risk level: unacceptable | high | medium | low
• Status: open | mitigated | accepted | closed

Process

1. Read prerequisites:

   • projects/000-global/ARC-000-PRIN-*.md
   • The project's ARC-{PID}-REQ-*.md and ARC-{PID}-DATA-*.md
   • The project's ARC-{PID}-STKE-*.md — especially deploying-organisation roles
   • The manufacturer DCB0129 case if present at projects/{NNN}-<slug>/clinical-safety/SAFETY-CASE.md and clinical-safety/HAZARD-LOG.md. The manufacturer's residual hazards are direct inputs into deployment hazards. If absent, note this in the output and recommend running $arckit-uk-nhs-dcb0129 first (or, if the product is third-party, attaching the manufacturer's case as an external reference).
   • Any ARC-{PID}-OPS-*.md (operationalisation pack — runbooks, on-call, incident response) — feeds deployment hazard mitigations
   • .arckit/templates/_partials/RENDERING.md

2. Read the templates (three files):

   • uk-nhs-dcb0160-deployment-safety-template.md (deployer SAFETY.md)
   • uk-nhs-dcb0160-deployment-case-template.md (DEPLOYMENT-SAFETY-CASE.md)
   • uk-nhs-dcb0160-deployment-hazard-template.md (DEPLOYMENT-HAZARD-LOG.md) Apply the standard templates-custom/ → templates/ → .arckit/templates/ resolution.

3. Resolve the project: locate the target projects/{NNN}-<slug>/ from the ArcKit Project Context; only if no project exists, create one with scripts/bash/create-project.sh --json --name "<project-name>". create-project.sh is create-only — invoked with no --name it exits 1 without returning a path.

4. Ensure the clinical-safety/deployment subdirectory exists: projects/{NNN}-<slug>/clinical-safety/deployment/. Use mkdir -p via the Bash tool.

5. Resolve the Document Control block for each file per RENDERING.md. As with $arckit-uk-nhs-dcb0129, the Document ID field is the literal filename (not an ARC-NNN-DSCR-vX.Y identifier). Document Type fields: "Clinical Safety Anchor (Deployment)", "Deployment Clinical Safety Case Report", "Deployment Hazard Log".

Important Notes

• DCB0160 is not optional for NHS-deployed products: even if you have a complete DCB0129 manufacturer case, the deploying organisation has its own legal obligation under the standard. The two cases cover different things.
• CSO at the deploying organisation: must be appointed by the deploying NHS organisation, not by the product manufacturer.
• Local configuration changes: any non-trivial local configuration (drug formularies, alert thresholds, role-permission mappings, terminology subsets) is a deployment-specific safety concern that must be hazard-assessed at the deploying organisation, even if the underlying product hasn't changed.
• Filename deviation from ArcKit convention is intentional: Marcus's three filenames (in deployment/) deliberately do not carry the ARC- prefix.
• Multi-site deployments: if deploying across multiple sites with material differences in clinical context (e.g. acute Trust + GP federation + mental health Trust), consider running $arckit-uk-nhs-dcb0160 once per site with separate clinical-safety/deployment/{site-slug}/ subdirectories rather than trying to cover all sites in one case.

Suggested Next Steps

After completing this command, consider running:

• $arckit-uk-nhs-dcb0129 -- Manufacturer-side companion. Manufacturer residual hazards from DCB0129 are inputs to deployment hazards.
• $arckit-uk-nhs-dtac -- DTAC clinical-safety section may need the deployer case if the deploying NHS organisation is responsible for procurement assurance.
• $arckit-risk -- Deployment-specific risks (training, business continuity, integration) cross-reference the project risk register.
• $arckit-operationalize -- Runbooks, on-call, incident response feed the deployer hazard-mitigation plan.