Community
NHID-Clinical is an open proposal, not a finished standard. The most useful thing you can do is tell us where it is wrong.
Where the conversation happens
Everything is public. There is no mailing list to join and nothing gated behind a form.
Discussions
Open questions, disagreements about the controls, and "has anyone seen this in the wild" reports.
Open Discussions ↗Issues
Specification defects, reference-implementation bugs, and concrete change proposals.
Open Issues ↗Run a shadow evaluation
The single most valuable contribution is measurement against real traffic. A Tier‑0 shadow evaluation is observe‑only: nothing is enforced, no vendor changes are required, and you keep your own data. It is a 90‑day engagement whose technical core is a 2‑4 week measurement sprint using the Shadow Pilot Kit.
We are actively looking for the first partners. If that might be your organization, book a conversation — it is the fastest way to find out whether this is a fit.
Contribute to the specification
- Challenge a control. If IDG‑01, PDX‑01, DBC‑01, EIT‑01 or ATR‑01 does not survive contact with your workflow, that is worth an Issue.
- Bring counter-examples. Call patterns the heuristics misclassify are more useful than agreement.
- Port an adapter. Six vendor adapters exist; a seventh for your platform is a self-contained contribution.
- Review the claim boundaries. If anything on this site overclaims, say so — see claim-boundaries.md.
Honest status. NHID-Clinical is a practitioner-led open proposal under CC BY 4.0. It is not an accredited standard, a certification program, or a regulatory requirement, and there is no external certification authority. Conformance testing is self-administered.