nexus-protocol-engine

The engine uses deterministic triggers to process patient lab data, medication context, and history with evidence levels, producing auditable clinical protocols with risk scoring and governance controls across multiple medical domains.

Clinical protocol generation supports multiple output formats including JSON for app integration, PDFs for professional use, and patient-facing guides to ensure comprehensive communication across the healthcare ecosystem.

Yes, you can use deterministic triggers for hormonal therapy and diagnostics protocols by applying the EndoInject and LabPro Modus domains, which process patient context to yield specific therapy and metabolic outputs.

The clinical protocol engine provides governance and audit trails by implementing risk scoring, audit hashes, and status controls to ensure safe protocol deployment and full traceability across the generated medical workflows.

Using fpdf2 for generating professional medical PDFs means you are limited to its native rendering capabilities, requiring the engine's modular architecture to structure the layout and governance data before export.