HealthTech vertical 6-pack

HealthTech / Clinical AI
6 sibling specs · 1 canonical shape per artifact

Six sibling specs for AI tools that touch PHI, FHIR resources, clinical decisioning, and AI/ML medical devices. The Suite vertical 6-pack that lets a hospital, payer, or digital health vendor publish Decision Cards, Incident Cards, and Evidence Bundles regulators can validate.

Regulatory floor

FDA SaMD (510(k) / De Novo / PMA + PCCP per Dec 2024 final) · HIPAA Privacy + Security Rules · Section 1557 of the ACA · IMDRF AE Terminology · CTCAE severity scale

Canonical example anchored throughout the 6-pack

Key design innovation vs sibling-vertical equivalents

FHIR-bridged audit events; FDA SaMD lifecycle Operator; HIPAA 18 Safe Harbor identifier categories in vault contract; OMB SPD 15 + Section 1557 + Fitzpatrick skin-type-classifier in bias coverage.

The six sibling specs

Every Kinetic Gain Protocol Suite vertical 6-pack contains exactly these six artifact shapes. The same six shapes appear in every vertical — only the per-vertical content (data categories, regulatory basis, invariants) differs.

Operator audit-stream

fhir-resource-access-audit

Per-AI-tool FHIR resource access events hash-chained for HIPAA + Section 1557 evidence

Operator regulatory-lifecycle

fda-samd-classification-board

FDA SaMD classification lifecycle (510(k) / De Novo / PMA + PCCP per Dec 2024 final)

Decision Card vault contract

phi-vault-contract-profile

AI Procurement Decision Card v0.3 vault contract profile naming HIPAA's 18 Safe Harbor identifier categories

Reference implementation

The HealthTech audit-stream now has a full end-to-end reference implementation in Node.js: fhir-resource-access-audit-reference (AGPL-3.0).

It reads from a FHIR R4 server (HAPI public test in live mode, fixtures in test mode), applies a HIPAA Safe-Harbor vault contract, emits Suite-compliant hash-chained events, and re-verifies its own output against the spec's published JSON Schema in CI. Green CI is evidence the spec is implementable end-to-end — not just well-typed example data.

Why parallel structure matters

A buyer's procurement team operating across mixed regulated verticals — HealthTech AI vendors plus FinTech AI vendors plus HR Tech AI vendors — can apply the same six-shape Suite vocabulary to every vendor in every vertical. The kg-suite-vertical-router tool routes any artifact to the right vertical's verification logic with one CLI command. The kg-suite-vertical-comparator tool surfaces the SAME-vs-DIFFERENT design contributions across all six verticals as a single reference table.