v1.1.1

Full Changelog: v1.1...v1.1.1

This was released on 2025-01-08.

New features

MAVIS-1723: Add flags to child records #2709 #2773 #2776

This adds a number of flags to the component when viewing a ‘child record’ allowing the nurses to see clearly if there are any flags on the patient.

After:

Invalid record

Sensitive record

Deceased patient

Bug fixes

MAVIS-1754: Fix typo on school movers confirmation screen #2711

Without the fix, the screen reads ‘Cohort record record’. Before:

MAVIS-1746: Don't link to patients out of the organisation #2724

If an cohort upload into Mavis resulted in the patient being moved to another SAIS team, the SAIS staff used to be able to see a link to the patient's record but would see an error page (due to no longer having access to that patient's record), which is not a good user experience.

Instead, Mavis no longer displays the link and provides an explanation why the patient is not available:

MAVIS-1768: Ensure notices are always visible #2726

We fixed a bug where notices were only visible if there was at least one deceased patient, and wouldn’t show if there were only restricted or invalidated patients.

MAVIS-1770: Fix notes error message on consents #2768

We fixed a bug where if you invalidate a consent, and don’t fill in the ‘Notes’ section, the error reads ‘can't be blank’ instead of ‘Enter notes.’ After:

MAVIS-1769: Show details from consent form if available #2772 #2786

The parental consent form page used to show the child info from the cohort record, not from the actual consent form itself. In the rare cases where this didn't match (i.e. if the SAIS staff matched the consent form to the wrong patient deliberately or by mistake), the true child info on the consent form wasn't being shown.

MAVIS-1771: Prevent double-recording of HPV vaccinations by navigating back #2737

When using the vaccinate flow it’s possible to inadvertently record two vaccinations for the same patient by navigating back to the confirmation after submitting it and then submitting it again.

MAVIS-1762: Improve performance on register attendance page #2769 #2770 #2781

We found during a training session that the Register attendance page sometimes loads in ~20 seconds depending on the exact data. We found low-hanging DB fixes which reduce this to under 1 second.

MAVIS-1780: Sort attendances alphabetically by default #2788

This gives the page a default sorting order.

MAVIS-1772: Hide health answers from invalidated or outdated consent responses on the consolidated view of health answers #2775

This avoids showing health answers for consents that have been invalidated or overridden by a newer consent response from the same person. The invalidated or overridden data is still available to review by clicking through to those particular consent forms, and the fact that they are invalidated is highlighted.

MAVIS-1778: Error submitting consent response when parent adds a phone number from "check and confirm" screen #2787

If a parent adds a phone number after the consent confirmation page, Mavis now prompts them to provide a contact method otherwise they're unable to submit the consent form.

MAVIS-1800: Offline spreadsheet opens with errors when many vaccinators present in the organisation #2804

Avoid Excel displaying an alert about corrupted data when an offline spreadsheet is opened by an organisation with lots of vaccinators.

MAVIS-1786: Incorrect date shown for manually matched consent response

Fixes a bug where manually matched consent response date shown on the patient page didn't match when the response was submitted by the parent.

MAVIS-1787: Filter children in a programme by status times out

Fixes Mavis performance and avoids a time out when filtering children within the HPV programme view by status.

Under the hood

• Data consistency: Validate presence of privacy_policy_url #2715
• Deployment: Enable docker layer caching, speeding up deployments #2741
• Performance: Don't use not_invalidated scope #2716
• Refactor: Pass parent relationship to AppParentSummaryComponent #2744
• Refactor: Don't create parents by default in tests #2743
• Refactor: Re-enable accessibility tests on release 1B pages #2746
• Refactor: Remove remaining explicit type from specs #2750
• Refactor: Mark JavaScript tests with :js #2751
• Refactor: Disable :js tests if Chrome is unavailable #2752
• Refactor: Choose an organisation on login without CIS2 #2745
• Refactor: Add hertfordshire onboarding ymls #2755
• Refactor: Fix home_educated value in model office script #2767
• Refactor: Fix flaky manage attendance feature test #2774
• Refactor: Fix time-sensitive feature test that breaks in 2025 #2805
• Refactor: Don't bulk queue PDS lookup jobs on staging envs #2785

Dependency bumps

• Bump aws-sdk-s3 from 1.176.0 to 1.176.1 #2759
• Bump caxlsx from 4.1.0 to 4.2.0 #2760
• Bump rails from 8.0.0.1 to 8.0.1 #2761
• Bump csv from 3.3.0 to 3.3.1 #2762
• Bump good_job from 4.5.1 to 4.6.0 #2763
• Bump idb from 8.0.0 to 8.0.1 #2764
• Bump @playwright/test from 1.49.0 to 1.49.1 #2765
• Bump sass from 1.82.0 to 1.83.0 #2766
• Bump aws-sdk-rds from 1.262.0 to 1.264.0 #2802
• Bump rubocop-govuk from 5.0.5 to 5.0.7 #2803
• Bump faraday from 2.12.1 to 2.12.2 #2792
• Bump esbuild from 0.24.0 to 0.24.2 #2795
• Bump capybara_accessible_selectors from aed2860 to c380ba7 #2790

New known issues

MAVIS-1812: Activity log entries for "a parent submitting consent" and "the consent being manually matched to a cohort record" are being shown as one

In cases where consent responses are manually matched to cohort records after initial submission, the Activity Log displays the matching timestamp rather than the original consent submission time. This creates misleading entries showing "consent given" instead of "records manually linked." While consent information remains accurate on the Child Record tab, users should reference that location rather than the Activity Log for correct consent timestamps. This issue is scheduled for urgent fix in the next release.

Impact: No clinical safety risk, as all consent details are correctly stored and displayed on the child's record.

Workaround: Check the Child Record tab for accurate consent submission dates and times.