arckit-uk-nhs-dcb0129

To generate NHS DCB0129 clinical safety documentation, you provide project-specific requirements and data model artifacts. The skill outputs a manufacturer-side Clinical Safety Case Report and Hazard Log, automating compliance with NHS clinical risk management standards.

A DCB0129 clinical safety case submission requires a SAFETY.md, a SAFETY-CASE.md, and a HAZARD-LOG.md file. These files document the clinical safety case, hazard discovery, and risk scoring based on the Marcus Baw SAFETY.md specification.

Hazard discovery and risk scoring for NHS clinical safety cases are integrated into the documentation generation process. The skill structures hazard analysis tables and assesses risk based on DCB0129 severity and likelihood standards.

Yes, you can generate a clinical safety case for a patient-facing health app by invoking the skill with your project artifacts. A software architect can produce the initial safety documentation for review and sign-off by a Clinical Safety Officer.

Yes, you must provide project-specific requirements and data model artifacts to populate the DCB0129 hazard log templates. These inputs drive the structured safety documentation and hazard analysis required for compliance.

Automating DCB0129 clinical safety documentation generates the initial structured templates and hazard logs, but the outputs require formal review and clinical sign-off. A Clinical Safety Officer must validate the generated safety case before deployment.