KB Type: Research Theme
Domain Area: Technical
Confidence: Researched (Andrew via NbLM, RS-03)
Depth Hint: Standard
Version: 1.0 — 2026-04-23
Status: Active

The NDIA's current CRM system continues to rely on Primary and Secondary Disability fields that feed legacy algorithms for eligibility and funding allocation. Simultaneously, the new PACE Framework emphasises functional Recognised Impairment Types — shifting from medical diagnosis to how the disability functionally impacts the participant across Intellectual, Cognitive, Neurological, Sensory, Physical, and Psychosocial domains. A practitioner-ready template bridges both systems by capturing Primary and Secondary Disability diagnoses with ICD-10 or ICD-11 codes alongside PACE impairment type checkboxes. This dual approach satisfies legacy CRM requirements, removes clinical ambiguity for NDIA planners, and fully aligns with the PACE architecture — including the eight NDIS Outcome Domains, five-position item codes, and Digital Lock mechanisms.

The NDIA's current CRM system continues to rely heavily on Primary and Secondary Disability fields. These legacy fields remain essential because they directly drive the existing algorithms used for determining scheme eligibility and calculating funding allocations. Even as new frameworks are introduced, these fields cannot be omitted.

Primary and Secondary Disabilities refer to the specific clinical or medical diagnoses for which the participant is receiving NDIS support — for example, Schizophrenia (Primary) or Type 2 Diabetes (Secondary). Integrating International Classification of Disease codes (ICD-10 or ICD-11; e.g., F20.9 or E11) alongside these text descriptions is highly beneficial. Supplying the exact ICD code elevates the clinical authority of the document and leaves no ambiguity for the NDIA planner regarding the precise medical diagnosis driving the participant's needs.

While the legacy system relies on medical diagnoses, the new PACE framework emphasises functional Recognised Impairment Types. Instead of naming a disease, this classification system uses checkboxes to identify how the disability functionally impacts the participant:

The PACE architecture aligns these functional impairments with the eight NDIS Outcome Domains, sophisticated five-position item codes, and new funding mechanisms including Digital Locks.

A highly effective master participant statement template bridges this gap by capturing both sets of requirements in its opening section. It explicitly maps the legacy Primary/Secondary Disability fields and their corresponding ICD codes right next to the new PACE Recognised Impairment Types checkboxes. This creates a complete bridge: the ICD codes provide the medical diagnosis required by the legacy CRM, while the checkboxes outline the functional impairment required by the PACE framework. The template also bridges qualitative goals to quantitative budgeting by incorporating PACE item codes and specific Digital Lock recommendations.

For Support Coordinators and Psychosocial Recovery Coaches, bridging these systems elevates a template from theoretically good to practically usable in the real world:

Ensures Funding and Eligibility: It satisfies both old and new NDIA data requirements, ensuring the participant's needs translate accurately into the agency's funding algorithms without administrative friction.

Reduces Administrative Burden: By effectively bridging the systems, the template simplifies the transition. Rather than forcing a practitioner to tabulate every flexible support item, the bridged template utilises exception-based Risk-Based Budget Controls. Coordinators only do the heavy lifting of documenting budget architecture when there is a high-risk scenario requiring a support to be Stated or Digitally Locked.