Medical Conditions and the Adjustment Library
Medical Conditions is the school-controlled list of health or learning conditions that can be recorded against students in Junipa. It keeps condition names consistent, reduces duplicate labels, and gives administrators a single place to maintain the wording staff see in student records.
When the Adjustment Library is enabled, Medical Conditions also becomes part of the school’s adjustment setup. Each condition can carry two extra lists:
- Student presentation: how a student with this condition may present at school.
- Suggested adjustments: practical supports staff may consider for a student with this condition.
What Medical Conditions Does
Use Medical Conditions when the school needs a consistent condition list for student profiles, enrolments, journals, reports, and related workflows.
Administrators can:
- Add a condition.
- Rename a condition.
- Remove a condition after checking where it is used.
- Show or hide the condition code column when code-level checking is needed.
- Review how many students currently have a condition recorded.
The visible condition name is school wording. Codes exist for system stability and import consistency, but administrators do not usually need to see them.
What Changes When Adjustment Library Is Enabled
With the Adjustment Library enabled, the Medical Conditions page shows each condition as part of a larger support library.
The page still lives under Tools, Medical Conditions. The page message explains that the condition list is now operating with Adjustment Library behaviour.
For each condition, administrators can maintain:
- Student presentation rows, one presentation per row.
- Suggested adjustment rows, one adjustment per row.
- School wording for each suggested adjustment.
- Official NCCD category and type mapping for each suggested adjustment.
This lets a school keep plain, local wording while still mapping that wording back to official NCCD language.
School Wording And Official NCCD Wording
Suggested adjustments can be written in the school’s own language. For example, staff may use a phrase such as “break tasks into smaller steps” because that is the wording used in daily planning.
That school wording can then be mapped to the official NCCD category and adjustment type. This means the phrase remains readable for staff, while Junipa can still understand how it relates to NCCD evidence and reporting structures.
The same pattern applies when a school uses evidence setup terms. A school can maintain its own evidence setup labels and connect them to official NCCD categories and types.
Practical Admin Workflow
- Go to Tools, Medical Conditions.
- Confirm the condition list uses the names your staff expect.
- Open the student presentation or suggested adjustments area for a condition.
- Add or edit one row at a time.
- For suggested adjustments, choose the official NCCD category, then choose the official NCCD wording.
- Save the row.
- Use the condition’s Manage Library page when you need a focused view of one condition’s presentation and adjustment lists.
What Staff See Later
When staff view a student with a medical condition, Junipa can use the condition’s presentation and suggested adjustment rows as prompts. Descriptions and administrative fields should stay out of the way unless they add useful context for that student.
Global NCCD Category Updates
Official NCCD categories and types are managed centrally in Distillery. When Junipa publishes changes from Distillery, each tenant stores its own copy in Firestore. That keeps every school self-contained while allowing one global update to be published across connected tenants.
If a new official NCCD category or type is added later, update it once in Distillery and publish it to schools. The Medical Conditions Adjustment Library then uses the tenant’s published copy when administrators map school wording to official NCCD wording.