Build / Assess / Run

Department blueprint

Select the services this department provides or plans. The blueprint responds: requirements that do not apply are marked not applicable rather than padding a checklist. Every item states the authority behind it, and jurisdiction-specific facts that have not been verified stay at research required.

Document suite Operations engine

Service scope

Architected so further neurodiagnostic modalities can be added later without pretending they share identical requirements.

Applicable requirements

45 in the model library

Applicability follows the selected services.

Evidenced

Document on file, current and approved

Gap or partial

Has an owner and an action

Research required

Never guessed, never fabricated

Jurisdiction-specific positions must be verified against a primary source before anything is recorded.

Domain status and evidence

Deliberately not one universal score. Open a domain to trace source, applicability, organization evidence, gap, action, owner, approval and review.

Technical leadership

A defined technical lead role with real decision rights, not informal authority.

Technical lead role with defined decision rights

A technical lead is designated with written decision rights over technical procedure, competency verification and equipment standards.

Gap

Authority: NeuroOps model best practice
Source: NeuroOps model synthesis (no external authority)
Version / effective: Model v1.2 · 2026-06-01
Verified: Yes · reviewed 2026-07-01
Applicability: applicable
Artifact type: Job description
Organization evidence: None on file
Owner: Senior technologist (acting technical lead)
Action: Draft from the NeuroOps model template, route for technical and administrative review.
Approval path: Technical review → Administration → Publish → Staff acknowledgment
Review / due: 2026-12-15

History: 2026-08-02 Dana Reyes — Applicability determined from selected services.. Entries are appended, never edited in place.

Authority types, kept distinct

The distinction is the product. Collapsing these categories is how organizations end up believing a recommendation is a law.

Type	What it means	How NeuroOps handles it
Law / regulation	Law	Only ever populated from a verified jurisdiction-specific source. Unverified means research required, never assumed.
Accreditation / credentialing framework	Accreditation	A framework an organization or individual may elect. Holding it is not a legal permission and lacking it is not illegality.
Professional standard / guideline	Professional	A professional recommendation. It is not law and must never be presented as law.
Organization / local requirement	Local	Applies inside this organization only. It is not a national requirement.
NeuroOps model best practice	Model	Original NeuroOps synthesis informed by cited sources. It is not an external standard and carries no external authority.

Not legal advice

Regulatory records are research notes, not legal advice or a legal opinion. Confirm any statute, regulation or requirement with the issuing authority and your own counsel before acting.

No PHI, no patient-level data

This platform holds aggregate operational counts, workforce records and competency attestations. It has no patient fields, no patient-level logs and no case records, and makes no compliance-certification claim.

NeuroOps provides compliance and readiness infrastructure and evidence mapping. It does not certify legal, regulatory or accreditation compliance, and completing a blueprint is not a finding of compliance. Local review is required where indicated.