protocol-integrity

Generate and verify clinical protocol integrity with SHA-256 audit trails.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JoaoBiomed/NEXUSEcosystem --skill protocol-integrity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protocol-integrity
Source: https://github.com/JoaoBiomed/NEXUSEcosystem/tree/main/nexus-app/.claude/skills/protocol-integrity
Command: npx skills add https://github.com/JoaoBiomed/NEXUSEcosystem --skill protocol-integrity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified approach to generate and verify clinical protocols, ensuring safety, traceability, and consistency throughout the protocol lifecycle. It supports end-to-end workflows including OIEG-based generation, Gemini integration, JSON parsing, SHA-256 audit trails, safety gates, prescription validation, and patient-communication fields.

Core Features & Use Cases

  • End-to-end protocol generation (OIEG) and integrity verification for both pre-change and post-change scenarios.
  • Safety gates, audit trails, and dual-field normalization to ensure regulatory compliance and data integrity.
  • Dispatcher integrity checks across EndoInject, iMeddis, LabPro, BodyScan, and Lifestyle modus, with clear records and status tracking.

Quick Start

Activate the protocol-integrity workflow to generate, validate, and audit a clinical protocol end-to-end.

Frequently Asked Questions about protocol-integrity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify clinical protocol integrity and generate SHA-256 audit trails?

Verify clinical protocol integrity by applying end-to-end generation workflows and SHA-256 audit trails. This process validates safety gates, dual-field normalization, and dispatcher records to ensure regulatory compliance and data traceability across clinical workflows.

What is the best way to automate clinical protocol generation and safety gate validation?

Automate clinical protocol generation by activating the protocol-integrity workflow, which applies OIEG-based generation and safety gates. It validates prescription data, JSON parsing, and M1-M7 patient communication fields to ensure consistent clinical safety.

Does protocol integrity verification support multiple clinical modus like EndoInject and LabPro?

Yes, protocol integrity verification supports multiple clinical modus including EndoInject, iMeddis, LabPro, BodyScan, and Lifestyle. It performs dispatcher integrity checks across these platforms with clear records and status tracking for comprehensive coverage.

How does SHA-256 audit trail verification work for clinical protocol changes?

SHA-256 audit trail verification for clinical protocol changes works by hashing protocol states and logging them immutably. This creates a traceable record of modifications, satisfying shape contracts and ensuring end-to-end data integrity across pre-change and post-change scenarios.

Can I use Gemini integration for JSON parsing and clinical protocol validation?

Yes, you can use Gemini integration for JSON parsing and clinical protocol validation. The workflow coordinates Gemini integration to parse protocol data, validate dual-field safety normalization, and apply verification suite tests to satisfy shape contracts.

What are the limitations of automating clinical protocol integrity checks across different modus?

Automating clinical protocol integrity checks requires satisfying strict shape contracts, dual-field safety normalization, and M1-M7 patient communication fields. Limitations arise if dispatcher records or safety gates are misconfigured across the EndoInject, iMeddis, LabPro, BodyScan, and Lifestyle modus.