• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

Enhancements And Changes

• In “Configuration parameters” under “User configuration” and “Profiles”, in the “Allow user to copy records for this module?” dropdown list for all modules, we added a new option called “Allow single copy” that allows administrators to enable users to create a single copy of one or more records. When this option is enabled, creating more than one copy of a record or set of records is automatically unavailable. If creating multiple copies is enabled, DCIQ displays the first 20 copied records due to pagination limits, but users can search for additional copies as required.
• We removed the COVID-19 resource button from all navigation in DCIQ. We also removed all related environment variables.
• DCIQ now allows the new "Max Harm" fields to be included as variables in "Capture" email notifications for LFPSE. This enhancement ensures notifications can display the maximum harm recorded on an incident when multiple people are affected.
• We introduced the ability to fully configure the "Contributory Factors Framework" used in both "Investigation" and "Enterprise Risk Manager" modules. Organisations can now tailor "Contributory Factors Framework" values to meet their specific needs, including defining parent-child relationships between factors for more structured categorisation. Once configured, these values are available for selection within "Investigation" to align with local requirements. The "Contributory Factors Framework" is shared between the "Investigations" and "Enterprise Risk Manager" modules. This enhancement replaces the legacy Datix-based framework, which is no longer supported.
• DCIQ allows users to customise workflow statuses in "Investigation" to match their organisation’s needs. Administrators can relabel existing statuses, add up to eight new ones, disable or reinstate statuses, and reorder them for better workflow control. Disabled statuses will make related records inaccessible, but reinstating them restores access. The “Rejected” status remains available and can be reordered. Users are able to customise the statuses in field maintenance.
• Previously, due dates in "Investigation" were hard-coded to a fixed time period. To accommodate varying organisational needs across different regions, DCIQ now allows configuration of "Investigation" timescales. Administrators can set a custom value, which will be added to the investigation's created date. Please note that changes apply only to new "Investigation" records. Existing records will retain their original timescales. This feature takes working days and public holidays into account.
• Administrators can now change the default labels in the "Investigation" module to match their organisation’s terminology. Once updated, the new labels replace the original text throughout the module, including menus, banners, and record details. This helps ensure the system aligns with local processes and language preferences.
• Previously, only the originating record’s reference was visible on an event in the "Investigations" module, which made it harder for customers who use IDs as their primary key. Users had to copy the reference and search manually in "Capture" to find the source record. As of this release, the event card now displays the originating record ID alongside the reference. DCIQ also displays a clickable link to the source record at the bottom of the card. The link opens the record in a new tab. If users do not have permission to view the record, DCIQ displays the standard permission error message.
• The NHS Patient Safety Incident Response Framework (PSIRF) encourages organisations to broaden the scope of investigations by reviewing groups of similar incidents together, rather than performing detailed investigations into individual incidents. To support this approach, DCIQ now allows users to link multiple incidents or events to a single investigation record via the linked events panel by using either ID or query. It also allows them to link new events to an existing investigation, reassign events from one investigation to another, or unlink events from investigations when needed. When searching for investigations to link, users can use either the investigation ID or title. DCIQ controls access by the user's security group permissions. If they do not have permission to view a record, DCIQ displays the standard permission error message.
• DCIQ now synchronises "Investigations" record data directly to "Incidents" records through new read‑only fields that show the "Investigation status", "Investigation ID", and "Investigation reference". DCIQ populates these fields automatically and does not allow users to edit them from the "Incidents" form. It allows users to link them to more than one investigation, and displays them in a table where selecting an investigation opens it in a new tab. If multiple incidents are linked to the same investigation, when users make updates on the investigation record, DCIQ syncs them back to all related incidents. Access to linked investigations follows existing permission rules, and DCIQ displays an error message to users without permissions.
• We have refreshed the colour palette for the main navigation bar and header across the DCIQ space. This is the first step towards creating a more unified look and feel across RLDatix solutions, following our brand guidelines.
• The following screens now reflect the updated branding, including logo, colour scheme, and font: main login screen, local user login screen, inactivity/logged out screen, and the delegations screen.
• DCIQ now allows admins to configure how many days after the review date the system sends an overdue risk review notification. By default, the system sends this notification 1 day after the review date, and admins can change this in "Notification Centre > Configure Overdue Notifications">"Overdue Days". We’ve also added the ability to customise how many days in advance the risk reminder emails are sent. By default, the system sends this notification 2 days before the review date, and admins can change this in "Notification Centre > Configure Overdue Notifications">"Overdue Days" using the new "Notification Centre > Configure Overdue Notifications">"Reminder Days" setting.
• DCIQ now allows users to manage email notifications from the ERM module at both user and group level. When disabled, the selected user(s) will not receive any emails from ERM. Otherwise DCIQ sends the emails by default.

Fixes

• We resolved a regression issue that prevented users from adding images to the "Field Help" in form design.
• Prior to this release, when a user was searching for a contact internally on a DIF1 form, DCIQ displayed an error message. The issue occurred for users allowed to search by "Date of Birth" by setting only the "Choose which fields to search on" to con_dob in "Capture Configuration", which is affecting the CON_PAS_CHK and CON_PAS_CHK_FIELDS=con_dob globals, or by setting both this and the global CON_MATCH_CRITERIA_1=con_dob. We resolved this issue.
• Prior to this release, when a user clicked a link in a DIF1 form, DCIQ took them out of the system instead of opening the link in a new tab, so they had to use the back arrow on the browser to return to DCIQ. We resolved this issue.
• Prior to this release, users who had the ACL rule "Access to Actions Linked to other records" could access all the actions on the "Actions" dashboard. We resolved this issue.
• Prior to this release, when an admin exported a crosstab report from the "Incidents" module using the report designer, in the Excel file, DCIQ did not include all data shown in the designed report. This discrepancy confused and prevented users from accessing complete data outside the system. We resolved this issue.
• Prior to this release, DCIQ was sending emails that a risk was overdue even though it was already reviewed. We resolved this issue.
• Prior to this release, when a user closed an active risk in the ERM module, the system continued to send overdue emails for the same risk record. We resolved this issue.
• Prior to this release, when a user completed a search for duplicate contacts using the "Contact Merging" criteria that returned a larger number of duplicates, DCIQ failed to download the CSV pre-merge report and displayed an "Unknown" error message. We resolved this issue. This item also relates to items no.168245 and 196626.
• Prior to this release, when a user changed a recommendation's status and clicked "Save", DCIQ displayed three error messages before saving the change. We resolved this issue.
• Prior to this release, DCIQ incorrectly displayed a custom section on the DIF2 form when a location was selected, even though no action triggered it. This section contained mandatory fields, which prevented users from saving the record and progressing it through the review process. In addition, the section did not appear immediately after the form action was triggered. Instead, it only appeared once the record was saved. We resolved these issues.
• We resolved an issue where DCIQ continued sending risk review reminder emails even after a risk was closed.
• Prior to this release, when running a merge template that included roles not present in the record, DCIQ displayed an error instead of leaving those merge fields blank. If the record contained only 2 out of 3 roles, the merge failed with an error. The moment all required roles were added, the merge worked as expected. We resolved this issue. The merge template now runs successfully even if some roles are missing, and any fields linked to unavailable roles remain empty. [Hotfix DCIQ.2025.R4.1 - 17 December 2025]
• Prior to this release, when users attempted to merge a template with an attached document in the "Safeguarding" module, DCIQ generated an error instead of completing the merge. This occurred even when the correct template was selected and the merge process was initiated. We resolved this issue. [Hotfix DCIQ.2025.R4.1 - 17 December 2025]
• Prior to this release, in the "Person Affected" form, when users selected a value in the "Treatment" field, DCIQ stored the value as "0" instead of the selected option. We resolved this issue. [Hotfix DCIQ.2025.R4.2 - 20 January 2026]
• Prior to this release, when users followed a record link in a notification email while logged out, instead of opening the intended record, DCIQ displayed an error after they logged in via domain. We resolved this issue. [Hotfix DCIQ.2025.R4.2 - 20 January 2026]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• Download PDF

Enhancements And Changes

• To align with CQC audit standards, any updates made in the physical and psychological harm contact fields and the maximum physical and psychological harm incident fields are captured in the "Full Audit" module. DCIQ generates audit records when users modify or clear values in these fields when editing existing records and during the unlinking of contacts from LFPSE incidents. If no changes are made to these fields or if changes do not affect the maximum harm levels, DCIQ does not create an audit record. This ensures a precise and meaningful audit trail and helps administrators monitor data integrity and maintain compliance. Please note that in the "Full Audit" module, DCIQ displays the numerical code value when users make changes. To correlate the code number with the code description, check the "Code Setups > Contacts (LFPSE)". "Contacts (LFPSE)" is a new module in "Code Setups" where DCIQ allows users to check the codes already defined for each of the physical and psychological harm contact coded fields by clicking on the field name.
• We have updated DCIQ to allow administrators to relabel all references to “Incidents” as “Events” across non-Capture areas of the system. This includes updates to the Notification Centre and To Do List. DCIQ allows admins to control this feature through a new “Relabel Incidents to Events” setting in "+ > System Admin > System Configuration", available in English (UK and US) only. When enabled, DCIQ passes this setting to external services, ensuring consistent terminology across the platform. Admins can relabel Capture areas via text strings in "Capture > Capture Admin", and the changes are not applicable for French or Arabic language settings.
• We introduced a new “System Language” setting in DCIQ to give administrators greater control over the platform’s default language. DCIQ allows admins to configure a default language in "+ > System Admin > System Configuration", which applies across Capture and non-Capture areas, and the To Do List. This setting only includes languages selected in the “Available Languages” list. If a user has not chosen a personal language preference, DCIQ automatically applies the system-wide language. However, if a user sets their own language in “My Preferences”, that choice will take priority. We retained all existing user language settings. By default, DCIQ continues to use “English (United Kingdom)” when no language is selected. When "Use Language Default" is selected in "My Preferences", it reflects the chosen "System Language". This update does not affect “Medications”, “Equipment”, “LFPSE”, or the Icon Wall. We have also removed the outdated global parameters “DEFAULT_LANGUAGE” and “AVAILABLE_LANGUAGES” to simplify configuration and ensure consistency. As part of this feature, in "Capture > Capture Admin > Software Settings", we have also updated the "Diagnose system problems" page. We have removed any outdated and irrelevant information that the system harbored over time and updated it to display more up-to-date information. The page now also displays settings from "+ > System Admin > System Configuration", as well as some values from "Capture > Capture Admin > System Settings > Capture Configuration", such as the system language. We have also relocated the build version information from "Capture Admin > System Information" to this page. This page is used for troubleshooting and is intended for use only by support and engineering teams.
• We added French and Arabic translations for the following features:
  • Lockout settings title only
  • Restrict Local Admin, assign own Locations
  • Restrict Local Admin, assign own Services
  • Inactivity Timeout Minutes (10 min., 60 max.)
  • Set maximum file upload limit (1MB min., 50MB max.)
  • Display previous login attempts?
  • Enable Footer Text
  • Footer Text box
  • Maintenance Mode
  • Local Admin Maintenance Mode
  • Allow investigation deletion
  • Allow risk deletion
  • Allow safety alert deletion
  • My Settings Enabled
  • Enable copying of the source record’s locations and services to the linked action?
  • Upload CSV
  • Failed to load footer
• We removed a previously implemented CustomCSS file from Yellowfin that was causing formatting issues across the user interface, including making the date picker difficult to read. With this change, Yellowfin is reverted back to its default color settings and displays the date picker more clearly. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]

Fixes

• Prior to this release, when a user clicked "Clear section" on a "Contact" section on level 1 form in all Capture modules, DCIQ removed the date picker from all date fields within that section, so the user had to type the date. We resolved this issue.
• Prior to this release, when a user created a new incident, performed a contact search, and selected a contact with valid Date of Birth (DOB) information, DCIQ automatically populated the DOB field in the incident. If the user then clicked "Clear section” and performed a contact search again on the same contact or a different contact with a valid DOB, DCIQ did not populate the corresponding DOB field even though the contact had a valid DOB displayed when the initial contact search was conducted. We resolved this issue.
• Prior to this release, when a user selected an incident form and set a field action trigger on any LFPSE-related field, DCIQ did not display the "Delete" and "Edit" options. We resolved this issue.
• Prior to this release, in "Capture Admin > Custom Settings > Code Setup" when an admin added codes to the "What was the type of device or appliance?" field in "Incidents" and saved the form, then navigated to "Capture Admin > Custom Settings > Select Design Forms" and opened the form, then selected the "Advanced" checkbox in the "What was the type of device or appliance?", DCIQ did not display the codes in the "Default value" field. Instead, it displayed a "No codes available" message. We resolved this issue.
• We resolved an issue that appeared when a reporter added a new incident. In the "Person Affected" section, when they added another person, DCIQ did not display the "Date Of Birth" date applet and did not allow them to select a date.
• Prior to this release, in "Capture > Capture Admin > Manage Dashboard Ownership", when an admin searched the page by filtering "Dashboard Owners" or when they tried to order the "Dashboard Owners" column, DCIQ did not display any results. We resolved this issue.
• We resolved an issue where DCIQ did not display data in dashboard charts when admin users created a new dashboard using an existing search criteria.
• Prior to this release, when users added a respondent on a claims form, the "Respondent" section did not display the selected listing design correctly. The columns did not match the configured design, and the "Name" column remained blank, even though the contact or organisation had name data populated. We resolved this issue.
• Prior to this release, on the "Person Affected" CON2 form, if the user set "Physical Harm" to "Fatal", DCIQ did not hide the "Psychological Harm" field. If the user left a value in the "Psychological Harm" field, LFPSE received a "Not Accepted" error. If the user removed the value in the "Psychological Harm" field, DCIQ allowed the user to submit the field without completing other mandatory fields. We resolved this issue so that when the user sets "Physical Harm" to "Fatal", DCIQ hides the "Psychological Harm" field.
• Prior to this release, in "+ > Contacts", when users edited the "Employee Status" field of a contact and tried to save the changes, DCIQ displayed an error. We resolved this issue.
• Prior to this release, in "Capture > Incidents > Design a report" when users selected filter options that contained special characters such as <, >, ;, or &, and ran the report, DCIQ did not return any data and displayed a "No data to display" message. We resolved this issue.
• Prior to this release, when a user updated or deleted a contact’s date of birth (DoB) or date of death (DoD) in the non-Capture areas of the system, DCIQ did not reflect the changes in the "Capture" area, and vice versa. This synchronisation issue resulted in outdated information being retained. Moreover, clearing DoB and DoD in the contact module and then searching for the same contact in an incident record continued to show the old values. This issue occurred despite no configuration changes being required and core fields being visible on both forms. We resolved this issue.
• Prior to this release, NHSE was not accepting incident records when the physical harm field was updated to "Fatal." DCIQ displayed an error message on the LFPSE management page that stated "FhirOperationException: A value for 'PsychologicalHarm' is required when the 'PhysicalHarm' value is non-fatal", which was not the case. We resolved this issue.
• Prior to this release, in "Capture > Incidents > New search", DCIQ displayed triggered sections and fields when the form was not configured for triggers. We resolved this issue.
• Prior to this release, when a user tried to submit an LFPSE record, DCIQ did not submit it and displayed errors on the LFPSE management page that stated ‘"xtension.exists() != value.exists() Instance failed constraint ext-1 "Must have either extensions or value[x], not both" [ "AdverseEvent.extension[0].extension[0]" ]" and "FhirOperationException: An error has occurred when validating Hl7.Fhir.Model.AdverseEvent.’". This also occurred when they tried to edit and save an existing record. We resolved this issue.
• Prior to this release, in "Capture > Incidents", when users added a new incident, in contact-related sections, such as "Person Affected Details", "Employee", and "Other Contacts", DCIQ displayed the "Date of Birth" field as editable and allowed them to edit it, but did not retain the changes upon saving and reverted them to the original data. We resolved this issue so that the "Date of Birth" field is now read-only and greyed out, consistent with the rest of the fields in these sections.Note: This change does not apply to PHSA when the EMPI integration is enabled, where the "Date of Birth" field is still editable.
• We resolved an issue where DCIQ did not allow users to add multiple injuries to a "Person Affected" contact on a logged-out DIF1 form, and only displayed the "Delete" button when users clicked "Add another injury".
• Prior to this release, in "Capture Admin > Form Design", in the "Contact" form, when a user added a new field action to non-LFPSE fields, DCIQ allowed users to select the LFPSE contact fields and to add LFPSE contact fields as new field actions, even though this should not be allowed. We resolved this issue. Note: If users have already added LFPSE contact fields as new field actions on non-LFPSE fields, DCIQ will not remove them, but users should delete them as this could cause issues on the forms and submissions of LFPSE records.
• Prior to this release, database synchronisation was failing, which resulted in outdated or missing data in Yellowfin reports. This problem affected some customers. We resolved this issue.
• Prior to this release, DCIQ allowed users to save dates in the "Date completed" field, which was earlier than the "Incident date". We resolved this issue so that DCIQ prevents the record from being saved and warns the user so that they can review the data in the dates fields. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, when a user created an incident record and linked the same contact under multiple roles, such as "Person Affected", "Reporter", or "Perpetrator", within the same incident, DCIQ incorrectly duplicated injury and body part details in the Body Part DE job, even if the injury was only recorded under one role. For example, when the user linked a contact as "Person Affected" and added injury details, then linked the same contact as "Other Contact", DCIQ transferred the injury information to the second role. As a result, both roles appeared with injury data in the DE output, despite the injury being entered only once. This behavior was inconsistent with other "Capture" modules like "Claims" and "Safeguarding", where injury data remains role-specific and is not duplicated. We resolved this issue. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, in certain scenarios, DCIQ incorrectly merged contact records into newer rather than older contacts. This led to discrepancies in the DES export, where DCIQ mismatched contact and record IDs. This made it difficult for customers to validate data, as the export showed incorrect contact information. We resolved this issue. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, in "Incidents", when users with DIF1 input-only access created a new incident and set the approval status to "Save to complete later", DCIQ did not retain the "Person Affected" details upon saving and displayed an error message that the contact search was not complete. We resolved this issue. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, in "Incidents", when users created a new incident, DCIQ did not retain incident time values when transitioning from Level 1 to Level 2 forms, and it did not record any changes in the audit trail. We resolved this issue so that DCIQ retains incident time values every time and on all form levels. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Since the DCIQ.2025.R2.1 update, the output of the location fields was changed in the JSON format and displayed as a single pipe-separated string of location titles instead of an array of location objects, each with an ID and location title. We resolved this issue. This item also relates to item no. 333899. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, when users typed a specific service name into the "Incident Service" field on the DIF1 form, the drop-down list included unrelated service names. For example, typing "Gynaecology" also displayed "Obstetrics" and other unrelated services, making it difficult to select the correct option. We resolved this issue. This item also relates to item no. 98466. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, in "+ > System Admin > Capture Admin > Custom Settings", DCIQ did not display some fields in "Code Setups" and "Form Designs" for the Incident, Feedback, and Mortality module, and displayed blank values in "Combo Links". We resolved this issue. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, DCIQ saved the wrong email address when users logged in through Active Directory. Instead of using the correct nhs.net email provided by the customer’s setup, DCIQ generated an email based on the domain name, which caused emails to be sent to the wrong address. We resolved this issue so that DCIQ correctly saves the user's actual email from Active Directory. [Hotfix DCIQ.2025.R3.1 - 09 October 2025]
• Prior to this release, in "Capture > Incidents", when users created a listing report using a query with @prompt shortcut in the "Location" or "Services" fields and selected a bottom-layer service or location to filter the results, the system returned an error and did not display any results. As part of the same fix, we also corrected the error message that appeared when the search was performed with an @prompt shortcut in the "Service" or "Location" fields with bottom-layer service or location selected. We resolved this issue so that the system correctly displays the expected search results. [Hotfix DCIQ.2025.R3.2 - 27 October 2025]
• We resolved an issue in "Capture > Feedback" where DCIQ did not retain the information in the "Subject" section fields after updating and submitting an existing record. [Hotfix DCIQ.2025.R3.2 - 27 October 2025]
• We resolved an issue where DCIQ did not load the "To Do List". [Hotfix DCIQ.2025.R3.2 - 27 October 2025]
• Prior to this release, when users tried to link a record in any module, DCIQ displayed an error and did not complete the linking. We resolved this issue. [Hotfix DCIQ.2025.R3.2 - 27 October 2025]
• We resolved an issue in "Capture > Incidents > Add a new incident" where DCIQ did not display the "ID Number type" and "ID Number" fields after users selected a patient from "Patient Search". [Hotfix DCIQ.2025.R3.2 - 27 October 2025]
• We fixed a payment-related system error found during internal testing. [Hotfix DCIQ.2025.R3.3 - 06 November 2025]
• Prior to this release, when users sent a message through the "Communication and Feedback" section, DCIQ recorded the time as one hour ahead of the time when the message was sent. [Hotfix DCIQ.2025.R3.4 - 25 November 2025]
• Prior to this release, in the "Mortality", "Claims", and "Safeguarding" modules, when users tried to access rejected records, DCIQ displayed an error. They were also unable to reject any records because in the "Reason for Rejection" dropdown, DCIQ displayed "No codes available". We resolved this issue. This item also relates to items no. 346646 and 346648. [Hotfix DCIQ.2025.R3.4 - 25 November 2025]
• Prior to this release, when a reporter submitted an incident with a UDF field that had a default value, was hidden on the INC1 form, and read-only on the INC2 form, DCIQ was expected to hide and pre-populate the field on INC1 and display it as read-only on INC2. Instead, the field appeared blank, resulting in data loss. We resolved this issue. [Hotfix DCIQ.2025.R3.4 - 25 November 2025]
• Prior to this release, when pushing patient information through the API in the Feedback module for all DCIQ customers, the process failed. The error occurred when a feedback payload included a contact link type C and was posted into the environment via API. We resolved this issue. [Hotfix DCIQ.2025.R3.5 - 02 December 2025]
• Prior to this release, the Feedback module took an extremely long time to load and then returned a 504 error. Users could not access the module as expected. We resolved this issue. This also refers to 346837 and 349299. [Hotfix DCIQ.2025.R3.5 - 02 December 2025]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• Download PDF

• Download PDF

• Download PDF

Enhancements And Changes

• When you navigate to "Capture > Incidents", DCIQ staggers the loading of the numbers of records. It loads the statuses from top to bottom, then loads the pinned queries from top to bottom. This allows users to see the numbers of records as they load, instead of waiting for the entire page to load, and significantly improves performance for environments with complex security permissions and queries or large data sets that cause slow loading. Users do not have to wait for all of the record counts to load before they click through to view records.
• DCIQ allows users to set up local authorities for the "Safeguarding" module. It allows users to easily report concerns to the relevant authority for any safeguarding issues. To enable the safeguarding referral functionality in DCIQ, users must contact support to activate the environment variable SFG_LOCAL_AUTHORITY. Once enabled, a new "Safeguarding Referral" section and a "Local Authority" field become available in Level 1 and Level 2 SFG forms, though these are hidden by default and can be made visible through form configuration. Users can then complete the setup by configuring local authority details in "Capture > Code Setups", including the authority name, email address, password, and associated template. Templates for each local authority and each type of safeguarding concern can be customised in "Document Template Administration", and users can also tailor the email template sent to local authorities. When a user selects a local authority and submits a safeguarding report, DCIQ merges the relevant data with the configured template and automatically sends an email to the selected authority. The email includes a secure link to a password-protected document, which the local authority can download. DCIQ records the date and time of the report, the selected authority, and whether the email was successfully sent; this information is available for search and reporting. If the original email fails or is sent to the wrong authority, users can resend the safeguarding referral from the Level 2 record. When a referral is manually retriggered, DCIQ revokes access to the original password-protected document and sends a new email with a new secure link to ensure data security.
• DCIQ allows users to authenticate using a combination of a smartcard and a PIN. Each smartcard has a PIV (Personal Identity Verification) ID. Cards can be reissued with a change of PIV ID. Users should authenticate using PIV/PIN combination to access DCIQ environment. If an existing user attempts to log in using an unrecognised PIV ID, DCIQ checks for an existing user that has the same forename, surname, or email address returned by IDP. If the user exists, DCIQ updates the user's PIV ID. If the user does not exist, the authentication fails. After authentication, the user can access the environment and, on login attempt, DCIQ will authenticate with IDP via SAML. DCIQ must recognize when an existing user's PIV ID has changed and updates the user's account to reflect the change. This functionality requires the environment variable SECONDARYUSERLOOKUP_ENABLED, to enable the look up of forename, surname and email address, surname and email address, or email address only. When disabled, no matching unique identifier is found, and DCIQ creates a new user.
• DCIQ allows you to display the details of recent login attempts to highlight any potential unauthorised access or access attempts. In "System Admin > System Configuration", use the "Display information about previous login attempts on login" field to enable this functionality. If you enable the functionality, when a user logs in, DCIQ displays the date and time of the user's last successful and unsuccessful login attempts. DCIQ records an unsuccessful login attempt if the user account has been manually locked, if the user's account outside its range of "Active To" and "Active From" dates, or if the user account is locked because the user exceeded the number of days of inactivity. If there has been no attempt to log in, DCIQ displays "No data recorded". If delegation is enabled, when a delegate logs in, DCIQ displays the last time they logged in on behalf of the delegator. When a delegator logs in, DCIQ also displays the last time a delegate logged in on behalf of the delegator's.
• DCIQ allows you to set a duration of inactivity for user accounts, and if a user account is inactive for that duration, DCIQ automatically locks the user account. In "System Admin > Users", we added a new "Admin" section. The "Admin" section contains new settings called "Days of inactivity before user lockout" and "Locked Out Users". The default "Days of inactivity before user lockout" setting is 180 days, but administrators can change it. When a user account is locked, it appears in the "Locked Out Users" table. DCIQ records the date and reason for locked accounts, and admins can filter list by origin and unlock user accounts manually. Locked users do not appear in "Staff" fields. These settings were previously located in the "Local users" menu. The "Admin" menu applies to both AD and Local users.
• As of this release, in "System admin > System configuration" and "System admin > Users", we added new options called "Restrict Local admin, assign own Locations" and "Restrict Local admin, assign own Services". These options allow admins to restrict a local administrator's ability to assign user services and locations to only include user services and locations that match the permissions of their user account. When enabled, local admin users are limited to assigning their own list of locations and services to other user accounts. When disabled, local admin users can assign any locations or services to other user accounts. This enhancement mitigates the risk of inadvertently granting a user access to data they should not have access to.
• Prior to this release, on the "Safeguarding" and "Redress" forms, the "Handler" field only appeared on the level 2 forms. As of this release, we added this field to the level 1 forms in the "Your manager" section. In the "Redress" module, the label is "Case Manager". In the database and in areas such as the email audit, the label is "Handler". This enhancement allows users to coordinate and manage safeguarding referrals more easily. By default, the "Handler" fields and the "Your Manager" sections are hidden.
• As of this release, only users with the relevant permissions have access to the "Reports Administration" area. This mitigates the risk of users accessing or distributing reports that contain personal identifiable data. A user has permissions to access the area if they are a full admin, a central admin, or a local admin, or if they have the "Capture" security group for "Admin", or if they have user permissions that grant access to one of the Capture module "Reports Administration". An administrator can also grant the user access to packaged report design from the "Reports Administration" area.
• To prevent users from inadvertently sending emails that contain sensitive information outside of the organisation, DCIQ allows you to add email domains to the "Notifier" whitelist. If you add one or more domains to the whitelist, DCIQ only sends emails to addresses at those domains. If a user tries to send an email to a contact with an email address that is not whitelisted, using the "Communication and feedback" section in any module, DCIQ flags the contact and allows the user to correct the email address before it sends the email. Navigate to "System Admin > Email Admin > Domain Whitelist" to view and edit the whitelist. An audit captures any changes to the whitelist, including domains added and deleted, the user who made the change, and the date and time of the change. DCIQ does not allow you to add invalid email domains to the whitelist. Filter the whitelist by keywords contained in the domain, user names, the date the domain was added, and other criteria to review the list and keep track of changes. The whitelist stores a maximum of 1,000 domains. In "System Admin > Email Admin > Email Audit", DCIQ captures successful emails, unsuccessful emails due to mail server issues, and blocked emails due to the whitelist.
• DCIQ displays footer text on all pages in all modules. DCIQ allows the administrators to control the footer text through the "Enable Footer Text" checkbox in "System admin > System configuration". DCIQ allows organisations to customise the text in the "Footer Text" box. DCIQ displays footers on the main "Capture" and "Non-Capture" pages, as well as the icon wall, the "To do" list, the "Medications" page, and the "Equipment" page, which are external services. Note: For the changes to take place, users may need to log out and then log back into DCIQ.
• DCIQ displays footer text on all pages printed from the system. Footers appear on printable documents when this feature is enabled and when the "Print" or "Export" buttons are used. For exports, the footer is included in both PDF and Excel files. This feature relates to feature no. 240571.
• DCIQ allows you to set a maximum file size for uploads. This helps to prevent users from uploading malicious files to "Capture" and "Non-Capture" records. In "System Admin > System Configuration", use the "Set maximum file upload limit" field to specify a maximum file size in megabytes. By default, the value is 50 MB. When you set a new limit, existing files of a larger size are unaffected. File size limits do not affect the administration areas of the system.
• DCIQ allows users to see record counts load progressively on landing pages. Instead of waiting for the entire page to load, DCIQ displays the "Statuses" counts first, followed by the "Pinned queries", from top to bottom. This staggered loading approach improves performance, especially in environments with complex permissions or large datasets, and enables users to start interacting with the page more quickly. Users do not have to wait for all of the record counts to load before they click through to view records. Note: This feature was previously released in DCIQ.2024.R4 to limited customers. Now, it is available to all customers. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• As of this release, the "Record Access Checker" tool is available for all users. In "System Admin > Users", when a user accesses another user's record, then clicks "Record Access Checker" and selects the module and record ID, DCIQ displays whether a specific user has access to a specific record in a selected module. Note: This feature was previously released in DCIQ.2022.R11 to limited customers. Now, it is available to all customers. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]

Fixes

• Prior to this release, when a user tried to search for risk records via the "Risk ID" filter in the "Filters" section, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, when a user navigated to the non-capture side and in the "To Do List" selected the "Filter By" option, in the "From" and "To" fields, DCIQ did not display the correct date in the calendar but the day before the current date. We resolved this issue.
• In "Capture > Capture Admin > Custom Settings > Reports Administration", in the "Module" dropdown, when a user selected "Contacts", and then created a new listing report template, DCIQ displayed an error message that prevented the user from creating it. We resolved this issue.
• Prior to this release, if a user merged two contacts with the same NHS number after assigning them both as a "Person Affected" with injuries, after the merge, DCIQ did not list the assigned injuries on the merged contact. We resolved this issue.
• Prior to this release, when a user opened an investigation record in "Analyse Data > Five Whys > Add new Five Whys entry", and added text that included an apostrophe and a forward slash to the "Problem" field, DCIQ displayed the characters in the entry incorrectly. We resolved this issue.
• Prior to this release, when a user opened an investigation record and in "Analyse Data > Contributory Factors", they selected a recommendation, DCIQ displayed a "Placeholder" text instead of comparator labels and selections. We resolved this issue.
• Prior to this release, when a user tried to save a query with a name that already existed, DCIQ displayed a prompt to change the name of the query, and also changed the "Query Type" from "Accessible Only To You" to "Accessible To Everyone". We resolved this issue so that the "Query Type" does not change.
• Prior to this release, in "Strategy > Safety Learnings", when users created a new learning or edited an existing one and set the "Keep Author Anonymous" field to "No", the field appeared blank after saving, while the field choice was saved correctly. We resolved this issue.
• Prior to this release, when a user reviewed a saved action, DCIQ displayed the "Start Date" as one day earlier than the originally entered date, even though it correctly displayed it in the "Actions" dashboard and calendar picker. We resolved this issue.
• Prior to this release, when users searched the ID number fields using the advanced criteria, DCIQ displayed errors or produced incorrect results. We resolved this issue.
• Prior to this release, when a user navigated to "Recommendations" and selected one from the "In Progress" status that did not have an "Owner", then changed its status to "Awaiting Approval" and saved it, DCIQ saved the recommendation record, but it also displayed three error messages. We resolved this issue.
• Prior to this release, in "Capture > Capture Admin > Design Forms > Incidents", when users created a form action in the "Services" field on INC1 or INC2 forms to display a hidden section, if they selected a child value, DCIQ only recognised the parent value as a valid trigger and did not display the section in the form. We resolved this issue so that DCIQ also displays the sections when users select a child value. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• We resolved an issue where under certain selections in the "Medication Problem" field, DCIQ initially displayed the "Medications Stage", but it disappeared upon saving. The issue occurred for the medication fields under the VANESSALAW_ENABLED environment variable. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• Prior to this release, in "Capture > Capture Admin > Incidents", when the “Medications Other” section had 3 or more triggers, they did not activate. The triggers were on the “Type of Error” field on INC1 and INC2 forms, and the trigger value was “Adverse drug reaction”. The issue occurred for the medication fields under the VANESSALAW_ENABLED environment variable. We resolved this issue. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• Prior to this release, in "Capture > Capture Admin > Incidents", when a user selected certain trigger values on the "Type of Problem" field in the “Medications Other” section on INC1 and INC2 forms, DCIQ did not activate the triggers for the "Stage at which the issue occurred" field. The issue occurred for the VANESSALAW_ENABLED environment variable. We resolved this issue. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• Prior to this release, in "Capture > Incidents", when some users added a new incident and searched for a person in the "Patient Search" section, then cleared the section and searched for a different person, DCIQ retained the previous person search data. Upon submitting the incident, DCIQ overwrote the second person's data with the previous person's data. This issue occurred in where the FORCE_CONTACT_MATCHING_BY_ID = Y global was enabled. We resolved this issue. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• Prior to this release, when some users used the "LFPSE Field" auto-population column options "Which specialty does the event (incident/risk/outcome) relate to?" and "Where did the incident happen?", DCIQ displayed an error message that the LFPSE fields were wrongly linked and that the changes were not saved. We resolved this issue by removing these options from the "LFPSE Field" column, along with the following options: "Where was risk identified?", "Which service areas were involved?", and "Which service areas are at risk?" because the auto-population can only be configured in the user's "Locations" and "Services" details. We also added links in the "LFPSE Auto population" section that correspond to the LFPSE fields. When users select a field, DCIQ redirects them to the "Code Setups" page for the corresponding field. [Hotfix DCIQ.2025.R2.2 - 9 July 2025]
• We resolved an issue in "Feedback > Add New Feedback" where DCIQ displayed an error message when users tried to submit a new record. [Hotfix DCIQ.2025.R2.3 - 21 July 2025]
• We resolved an issue in "Capture > Feedback > Design a Report" where DCIQ displayed an error message in the report builder when users tried to create a listing report. [Hotfix DCIQ.2025.R2.3 - 21 July 2025]
• Prior to this release, in "System Admin > Users > Admin > Lockout Settings", when users entered 0 in the "Days of Inactivity Before User Lockout" field, DCIQ did not disable the option. We resolved this issue. This fix relates to feature no. 240575. [Hotfix DCIQ.2025.R2.3 - 21 July 2025]
• Prior to this release, in DCIQ.2025.R2, DCIQ allowed local admins, alongside full admins and users with other permissions, to access "Reports administration". As of this release, we revoked the "Reports administration" access for local admins and reverted it to the previous state. This fix relates to feature no. 256994. [Hotfix DCIQ.2025.R2.4 - 31 July 2025]
• We resolved an issue where DCIQ did not retain the default values of user-defined fields (UDFs) on INC2 forms when users set them on INC1 or INC2 forms. [Hotfix DCIQ.2025.R2.4 - 31 July 2025]
• Prior to this release, in "Capture > Capture Admin > Custom Settings > Reports administration > Manage listing reports", when users selected the "Claims" module from the dropdown list and clicked an existing report from the list or "New listing report", DCIQ displayed an error message. The same happened when they saved a listing report with no values in the "Current group columns" field of a base listing report. We resolved this issue. [Hotfix DCIQ.2025.R2.5 - 7 August 2025]
• Prior to this release, in "+ > Organisations", when users clicked "List all organisations", DCIQ displayed an error message. We resolved this issue. [Hotfix DCIQ.2025.R2.5 - 7 August 2025]
• Prior to this release, in "Capture > Capture Admin > Reports administration > Reporting fields setup", in the "Medications" section, DCIQ did not display some fields. We resolved this issue. [Hotfix DCIQ.2025.R2.6 - ]
• Prior to this release, when a user searched for a contact with an apostrophe in their name in the "Number Type" field and tried to "Choose" the contact, DCIQ prevented them from progressing with populating the details into the incident form. We resolved this issue. [Hotfix DCIQ.2025.R2.6 - ]
• We resolved an issue that caused a system error when a user added a location and service to the contact listing design and tried to access a record with a contact attached. [Hotfix DCIQ.2025.R2.6 - ]
• We resolved an issue where DCIQ displayed an error and prevented users from viewing incident records in the "Incidents" module when the "Communication and Feedback" section was visible. [Hotfix DCIQ.2025.R2.6 - ]
• We resolved an issue where login attempts by some users failed and DCIQ displayed an error. [Hotfix DCIQ.2025.R2.6 - ]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• Download PDF

Enhancements And Changes

• DCIQ allows you to submit an incident report on behalf of a neighbouring organisation. When you complete an incident report, DCIQ displays a new field called "Did the incident occur whilst the patient was under your organisation's care?". If you select "Yes", DCIQ proceeds as usual. If you select "No", DCIQ displays a new field called "Under which organisation's care did the incident occur". When you select the name and ODS code of the neighbouring organisation from the field and submit the form, DCIQ sends the ODS code to LFPSE. To enable this functionality, an administrator must add the ODS code and description of the neighbouring organisation in Capture Admin > Code Set Ups > Incidents (LFPSE) in the field "Under which organisation's care did the event occur?". The form still display the fields "Where did the incident happen?", "Which service areas were involved?", and "Which specialty does the incident relate to?" regardless of where the incident took place.
• DCIQ allows users to set up local authorities for the "Safeguarding" module. It allows users to easily report concerns to the relevant authority for any safeguarding issues. To enable the safeguarding referral functionality in DCIQ, users must contact support to activate the environment variable SFG_LOCAL_AUTHORITY. Once enabled, a new "Safeguarding Referral" section and a "Local Authority" field become available in Level 1 and Level 2 SFG forms, though these are hidden by default and can be made visible through form configuration. Users can then complete the setup by configuring local authority details in Capture > Code Setups, including the authority name, email address, password, and associated template. Templates for each local authority and each type of safeguarding concern can be customised in "Document Template Administration", and users can also tailor the email template sent to local authorities. When a user selects a local authority and submits a safeguarding report, DCIQ merges the relevant data with the configured template and automatically sends an email to the selected authority. The email includes a secure link to a password-protected document, which the local authority can download. DCIQ records the date and time of the report, the selected authority, and whether the email was successfully sent; this information is available for search and reporting. If the original email fails or is sent to the wrong authority, users can resend the safeguarding referral from the Level 2 record. When a referral is manually retriggered, DCIQ revokes access to the original password-protected document and sends a new email with a new secure link to ensure data security.
• We made the following fields available in the LFPSE section of the Incidents Data Extraction template: "Is there a national or regulatory requirement to conduct an investigation in response to this event?"; "How will you respond?"; "Findings"; "What areas for improvement have been agreed as a result of this response?"; "Have safety actions been developed?"; "What safety actions have been made to address this area for improvement?"; "How will areas for improvement be addressed (e.g. wider review)?"; "Confirm how you responded".
• We upgraded Yellowfin to version 9.14. The new version includes changes to the "Browse" and the "Reports" menus and menu options. Visit the RLD Academy to view demonstration videos about the "Browse" menu and the "Reports" menu.

Fixes

• Prior to this release, if a user created too many records in quick succession, a conflict caused DCIQ to create incident records with no data except an Admin ID, and when the user saved automated information, such as DIF1 values and submitted times, DCIQ discarded all the data. We resolved this issue so that DCIQ no longer encounters the conflict and saves data instead of discarding it.
• Prior to this release, if a user had the settings "Give users access to customised report builder" set to "Yes" and "Give users access to packaged report design via reports administration" set to "No" or blank, DCIQ allowed the user to access "Reports Admin" in "Capture Admin". We resolved this issue so only users with the correct permissions can access "Reports Admin".
• Prior to this release, when a user created a Data Extraction job that contained a complaint chain field from the "Change History" table, the downloaded file did not contain any data. We resolved this issue.
• Prior to this release, when a user created a Data Extraction job that contained a complaint chain field from the "Change History" table, the downloaded file did not contain any data. We resolved this issue.
• We resolved an issue that caused DCIQ to hide the title of the "Controls" section on the form when a user created a new risk.
• We resolved an issue that caused DCIQ to delete a contact's address and phone number information when the logged-in user was linked as the reporter contact to a new Capture record.
• Prior to this release, DCIQ allowed users to save a "Person Affected" record on an incident without completing all the mandatory fields. We resolved this issue so that it is not possible to save a "Person Affected" record without completing all the mandatory fields.
• We resolved an issue with the trigger configurations on the fields "Do you have the contact's ID number?" when the fields were configured as radio buttons instead of dropdown fields. Now, if the user answers the field with "Yes" or "No" as a dropdown field or as radio buttons, DCIQ triggers the correct parts of the form.
• Prior to this release, if a user removed a locally added or subscribed medication from the "Medication" list, DCIQ removed the details of that medication from incident records. We resolved this issue so the medication details remain on incidents even when a user removes the medication from the list.
• We resolved an issue that prevented DCIQ from automatically disabling child locations when the user disabled the parent location.
• Prior to this release, in Capture Admin > Code Set Up > Incidents > Location, when NSWH users enabled the global HERO_ENABLED, DCIQ did not display the locations list. We resolved this issue.
• Prior to this release, when you enabled the "Classification Tree" for Incidents, DCIQ allowed users to search for and populate records with "Type", "Category", and "Subcategory" codes that were disabled or deactivated in the code setup. We resolved this issue so that users cannot populate or search for excluded codes.
• Prior to this release, DCIQ occasionally allowed a user to submit a value in the "Other Interventions: Please specify" field in the "Pressure Sores" section that exceeded the character limit of the field. When this happened, DCIQ displayed an error message, causing the user to resubmit the record, and resulting in DCIQ saving two copies of the same incident. As of this release, we removed the character limit of the field to resolve the issue.
• Prior to this release, DCIQ displayed some special characters, including the ampersand, asterisk, and percentage symbol, in Unicode in the "ID Number Type" field for contact matching and filtering in the "Contacts" module. We resolved this issue.
• Prior to this release, when you used contact matching with an existing contact on an INC1 form, DCIQ only pulled the latter part of the contact's location through to the contact and considered it an incomplete field. We resolved this issue.
• We resolved an issue that prevented users from using the Sync Field Labels option in "Data Extraction".
• We resolved an issue that prevented users from viewing the statuses and record count for the Safeguarding module in DCIQ. If you continue to experience this issue, navigate to Capture Admin > Workflow Administration > Safeguarding and click "Save". The Safeguarding homepage then loads the statuses, record count, and pinned queries as expected. [Hotfix DCIQ.2025.R1.1 - 21 February 2025]
• Prior to this release, when a user moved a field to another section but the field was set to trigger its original section, when the user saved the incident with a validation failure, DCIQ reloaded the form without triggering the section. This resulted in missing fields and data loss. We resolved this issue and the section now correctly re-triggers when the user reloads the form, ensuring all relevant fields remain populated. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• We resolved an issue that prevented DCIQ from populating Yellowfin reports with location data. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• Prior to this release, the triggers set between a coded field and the redesigned contact modal flow did not function as expected. We resolved this issue so that the triggers work correctly and the form behaves as intended. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• Prior to this release, in the redesigned contact modal when a user entered a "Contact ID" but did not click "Search" and then tried to submit the record, DCIQ took them to the top of the form without indicating the issue. We resolved this issue so that DCIQ displays a validation message informing users of the required action before submission. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• We resolved an issue that prevented DCIQ from populating Yellowfin reports with location and services data. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• Prior to this release, when a user added a new action to an incident record and assigned it to a user, DCIQ did not send an email notification to the user. We resolved this issue. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• We resolved an issue that prevented DCIQ from displaying the "History" section for fields with "Date/User stamped entries" enabled when a user completed the field and then revisited the form. As of this release, when a user completes a field with "Date/User stamped entries" enabled, and then revisits the form, DCIQ displays the previous values in the "History" section below the field. [Hotfix DCIQ.2025.R1.2 - 20 March 2025]
• Prior to this release, if a user enabled the new contact matching modal flow, when a person set "Do you have the contact ID number" to "Yes", searched for a contact, then selected the contact they wanted, DCIQ successfully populated the correct fields with the contact details, but did not make the fields read-only. We resolved this issue. Note: This functionality does not apply to PHSA customers. [Hotfix DCIQ.2025.R1.3 - 10 April 2025]
• We resolved an issue that caused time fields to display values incorrectly in listing reports. [Hotfix DCIQ.2025.R1.3 - 10 April 2025]
• We resolved an issue that caused DCIQ to update the "Incident Reported Time" to the current time whenever a user edited the incident report. [Hotfix DCIQ.2025.R1.3 - 10 April 2025]
• Prior to this release, in Capture > Feedback, when a user clicked the "Clear Section" button while populating the "Person Providing Feedback" form, DCIQ removed the entire contact form and did not allow the user to add another person or enter new details. The issue appeared in the "Safeguarding" and "Mortality Reviews" modules, but not in the "Incidents" module. We resolved this issue so that when users click the "Clear Section" button, DCIQ resets the data in the fields and allows you to add another person and edit the contact details. [Hotfix DCIQ.2025.R1.4 - 22 April 2025]
• Prior to this release, an issue caused DCIQ to update the "Incident Submitted Time" to the current time whenever a user edited the incident report. We resolved this issue, and as of this release, the "Incident Submitted Time" on any impacted reports displays the correct original time. [Hotfix DCIQ.2025.R1.5 - 15 May 2025]
• When a user searched for a patient by ID Number type such as MRN on all Level 2 forms, DCIQ failed to find a match and displayed all patient records instead. We resolved this issue.[Hotfix DCIQ.2025.R1.5 - 15 May 2025]
• We resolved an issue that occurred in a region-specific EMPI integration. When a user searched for a person on any Level 2 form, DCIQ failed to find a match even when a matching person existed in the database, and instead prompted the user to create a new record for the same person, which created duplicates. [Hotfix DCIQ.2025.R1.5 - 15 May 2025]
• Prior to this release, users could not access and delete certain "Safety Alert" records that had documents attached to them. The issue occurred because the system was performing excessive operations which led to memory exhaustion. To prevent this issue, we deployed enhanced logging for "Safety Alert" and improved the way DCIQ handles errors. As of this release, in these situations, DCIQ displays a red bubble warning error, but does not prevent the user from accessing the record. [Hotfix DCIQ.2025.R1.6 - 27 May 2025]
• Prior to this release, when a user added a contact to a new incident and that contact had an apostrophe in their name, when the user clicked "Choose", DCIQ did not add the contact to the incident. We resolved this issue. [Hotfix DCIQ.2025.R1.6 - 27 May 2025]
• Prior to this release, in the "Feedback" module, when an admin performed contact matching in the "Person Providing Feedback" section, DCIQ displayed an error message. We resolved this issue. [Hotfix DCIQ.2025.R1.6 - 27 May 2025]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

Enhancements And Changes

• Incident forms now include 19 additional fields: five fields named "Time", seven fields named "Time From", and seven fields named "Time To". The fields record time values in hh:mm format, and have the same validation and constraints as other time fields. The minimum value is 00:00 and the maximum value is 23:59. The fields are hidden by default. Users can search for and report on the fields. The new time fields are not available in statistical reports, but they are available in listing reports. Note: DCIQ currently makes no calculations between the "Time From" and "Time To" fields. We recommend you do not repurpose the "Time From" and "Time To" fields, as DCIQ may make calculations between them in the future.
• Prior to this release, users could not customise the "Medications (Search)" section in the "Incidents" and "Feedback" search forms. The form always displayed the entire section with all fields, regardless of whether they were in use, and there was no option to modify field labels or add explanatory text. As of this release, the "Medications (Search)" section of the form is no longer available, and the medication search functionality is aligned with the standard search functionality. Users can configure medications search in the form design settings for the "Medication Administered", "Medication Intended", and "Medication Other" sections. These changes apply only if you enable the environment variable CAPTURE_PHP_MEDS_FORMS. To enable this functionality, please contact Support. This enhancement is related to item 174116.
• Users can import HERO codes and map them to locations in DCIQ. This allows you to gather information about local patient safety issues and generate reports by location using the HERO code for that location. Users must use an XML import to map multiple values for each location, and to add, remove and update values. Note: This enhancement applies to specific customers in the NSWH region only.
• When you search for an incident or feedback, in the "Medications" section, we changed the fields from free text fields to dropdown fields. This removes the need to know the full, exact name of a medication in order to search for it, and removes the risk of mistyping or misspelling the search term. As of this release, you can use the dropdown field to find the medication you want to search for. The dropdown fields also allow you to use standard search symbols (e.g. @prompt, !=, etc.), in the same way as all other dropdown search fields. These changes apply only if you enable the environment variable CAPTURE_PHP_MEDS_FORMS. To enable this functionality, please contact Support. Note: Fields that contain a large number of code values may significantly impact performance. We recommend using the global setting CODED_FIELD_CODE_DISPLAY_LIMIT to limit the number of displayed dropdown values for coded fields and improve system efficiency. Please be aware that the global setting affects all coded fields in the system. This enhancement is related to item 168792.
• As of this release, "Time" fields are available for data extraction under the "Incident Template" in the corresponding "Time" subsection. Note: Ensure the section is not hidden in the form designer to view the "Time" fields. DCIQ currently makes no calculations between the "Time From" and "Time To" fields.
• HERO codes allow you to gather information about local patient safety issues and generate reports by location. In the ETL pipeline, we added a new field called "cod_hero" to the "location_capture" table to store HERO codes for records. Note: This enhancement applies to specific customers only.
• When you navigate to Capture > Incidents, DCIQ staggers the loading of the numbers of records. It loads the statuses from top to bottom, then loads the pinned queries from top to bottom. This allows users to see the numbers of records as they load, instead of waiting for the entire page to load, and significantly improves performance for environments with complex security permissions and queries or large data sets that cause slow loading. Users do not have to wait for all of the record counts to load before they click through to view records. This enhancement is controlled by the environment variable STAGGERED_STATUS_LOADING. To enable this functionality, please contact Support. This enhancement is for a specific environment.
• LFPSE "Status" and "Warnings" fields require the users to enter specific values in order to return results. We added help text to these fields to give users information on the requirements. The field also allow you to use wildcards, including = and ==. The help text appears on both level 1 and level 2 forms and is removable.
• As of this release, all LFPSE PSIRF string fields that support free text have a character limit of 12,000. DCIQ does not allow you to type more characters into the field. This does not affect existing data in fields.

Fixes

• Prior to this release, when users navigated to Incidents > My Reports, DCIQ displayed an error. We resolved this issue.
• We resolved an issue that caused DCIQ to not display the full text of the values in the "Location", "Other Location", "Services", and "Other Services" fields when printing the incident to PDF.
• Prior to this release, when a user searched for a piece of equipment on a capture form and selected the item they wanted from the search results, DCIQ replaced the user's search term with the brand name of the selected equipment, instead of the name of the equipment as displayed in the search results. Now, when the user selects the item from the search results, DCIQ replaces the search term with the name of the equipment instead of the brand name. In a future release, we intend to add a designating field to display the equipment name.
• Prior to this release, in the Dashboard module in "Capture", when users viewed a chart there appeared to be missing pieces of data. This is expected behaviour as it is not always possible to display all the data from the "Dashboard" view. There were also inconsistencies with the division of the sections viewed on the "Dashboard" which did not reflect the sections in the report. We resolved this issue and now DCIQ displays the appropriate sections on the dashboards. In addition, we added help text on these dashboard reports to remind users to click into the report to see full details.
• Prior to this release, in Capture > Incidents, if you created a search for a date range that spanned multiple financial years within the same annual year, then you designed a crosstab report that included "Fin Year", when you ran the report, DCIQ displayed all of the data in a single column for the annual year, instead of in different columns for each financial year. We resolved this issue.
• We resolved an issue that prevented DCIQ from showing more than ten results when you searched for equipment to add to an incident. As of this release, when you open the incident and select "Was any equipment involved in the incident?", if there are more than ten results from the search, DCIQ displays the "Next page" option.
• Prior to this release, if you set the text description of a coded field to "0", DCIQ displayed the code instead of the text description in the field dropdown. We resolved this issue so that DCIQ displays the correct text description in field dropdowns.
• Prior to this release, in Capture modules, when an admin user was searching on an extra listed date field using the "less than" or "greater than" (>) symbols, then ran a search, DCIQ displayed an error. This only happened with UDFs. We resolved this issue.
• Prior to this release, in Capture Admin, when a user created a listing design with the columns "To what extent was the patient physically harmed (including pain) in this incident?" and "To what extent was the patient psychologically harmed in this incident?" was available to be included, DCIQ did not display the values. We removed these from the listing design option because the "Maximum level of physical harm incurred by persons affected in event" and "Maximum level of psychological harm incurred by persons affected in event" are the correct fields to use to display the data.
• Prior to this release, when a user deleted a mortality record, DCIQ prevented them from deleting the contact record linked to the deleted mortality record. We resolved this issue. DCIQ allows users to delete a contact linked to a capture record which is deleted as long as it is not linked to any other record.
• Prior to this release, DCIQ allowed a user to configure the risk form so that they could trigger the "Risk Grading" and "Risk Register" fields by selecting a specific value in the "Condition" field. This meant that it was possible for the user not to trigger those mandatory fields, and if a user tried to submit the form without completing the fields, DCIQ displayed an error. To resolve this issue, we removed the ability to create a trigger for the "Risk Grading" and "Risk Register" fields.
• Prior to this release, in Capture Admin > LFPSE Trigger Mapping, when a user selected any mapping option and searched for a code using any filter option, DCIQ did not display any results. We resolved this issue.
• Prior to this release, when a user included LFPSE / PSIMS fields within a listing and added it to a form, when the user attempted to open a linked contact on that record, DCIQ displayed an automated error message. We updated the error message for contact and linked record cases so that it notifies users that DCIQ does not support the use of LFPSE / PSIMS fields in listing reports.
• Prior to this release, when admins opened an Incident form and wanted to add a new action, DCIQ displayed only one option in the "Values that will cause this section to be shown" drop-down. This was caused by the default value for the parent option being incorrectly treated as a filter for the dropdown options. We resolved this issue, and the dropdown now displays all appropriate values.
• Prior to this release, in a multi-coded UDF, when the user populated the field on the CON1 with a code that contained a full stop, then performed a contact merge, DCIQ did not allow the user to select the contact. We resolved this issue.
• Prior to this release, when a user reported a new incident and answered the "Were patients involved in this event?" field with "Yes", DCIQ displayed a warning pop-up message whenever the incident was saved or updated. DCIQ still processed and saved or updated the incident, but the message was confusing to users. We resolved this issue.
• We resolved an issue that displayed an error when you selected "Show DIF1 values" on incident records.
• We resolved an issue that prevented the user from sorting columns in the LFPSE trigger mapping section by clicking the sort arrows. As of this release, clicking the sort arrows sorts the columns as expected.
• Prior to this release, when users answered "Were patients involved in this event?" on an INC1 form which triggered "Is there an imminent risk of severe harm or death?" and "When do you think this risk will cause harm?", DCIQ hid the populated fields on the INC2 and they had to re-trigger them on an INC2 form by reselecting "No" for "Were patients involved in this event?". We resolved this issue.
• Prior to this release, when a notifier created a draft incident and added a "Person Affected" in "Saved to Complete Later" stage, edited the draft incident and clicked "clear section" on person affected then submitted a new person affected, DCIQ displayed the removed "Person Affected" on the submitted incident record. We resolved this issue.
• We resolved an issue that caused DCIQ not to save newly added controls using the "Recommendation" modal.
• Prior to this release, when a user edited or added users to a dashboard using the dashboard options if a user had a long name or a job title, DCIQ would hide the "x" option to remove the user. We resolved this issue.
• We resolved an issue that caused DCIQ to display errors when a user saved a contact record with values in the "Assessed as loan worker?" field or the "Employee Status" field.
• We resolved an issue that caused DCIQ to display system code for the "Type" field, in the "Progress Notes" section in the Incidents module.
• We resolved an issue that caused the Carlton Module to display a technical error message, even when the module was still functional.
• We resolved an issue in Evaluate > ERM > My Risk that caused "Last risk updated date" to display the wrong time in the wrong format.
• We resolved an issue that caused DCIQ to display the HTML symbol code for apostrophes in locations names.
• We resolved an issue in the Safety Alerts module where DCIQ displayed the label of the "Forename" field in the "Handler" search form as "Handler".
• We resolved a performance issue that caused a 504 timeout error when a user navigated to the "Dashboard" reporting, selecting a report, and clicked a number to view the raw data.
• We resolved an issue where DCIQ did not send emails to some recipients, even though it displayed them as sent in the logs. This happened due to a limit set by AWS. We resolved this issue by updating the email grouping setting to "Individual". In addition, we updated the help text in the email grouping configuration in Capture Admin to advise users to use the "Individual" setting.
• Prior to this release, in "Medications" on a DIF2 record, when a user populated the fields in "Administered" medication and saved it without populating the fields in "Intended / Suspected" medication or without enabling the "Intended / Suspected" section, DICQ did not save the data. We resolved this issue.
• Prior to this release, DICQ did not correctly display updates to the "Reviewed?" field in the "Reporting" database. We resolved this issue. Note: This fix only applies to new changes made to the "Reviewed?" field going forward. Users will need to update and save previous changes again for DCIQ to reflect them in the "Reporting" database. [Hotfix DCIQ.2024.R4.1 - 03 December 2024]
• Prior to this release, when a user with security group access to DIF1 input only to Incidents logged in, DCIQ did not load the record count on the "Incidents" landing page. It displayed the loading icon next to each status, making users think they could not click the records. This only happened when users had STAGGERED_STATUS_LOADING enabled and did not have pinned queries enabled for the user or profile. We resolved this issue. [Hotfix DCIQ.2024.R4.2 - 18 December 2024]
• Prior to this release, when you deactivated a location, DCIQ treated it as a disabled location and did not display records with the deactivated location in searches. As of this release, we fixed the behaviour so that users cannot create or update records using deactivated locations but they can still search for them. [Hotfix DCIQ.2024.R4.3 - 15 January 2025]
• We resolved an issue that prevented DCIQ from saving medications to an INC1 or INC2 record. [Hotfix DCIQ.2024.R4.3 - 15 January 2025]
• Prior to this release, the ETL synchronisation did not include data from the safety_learnings_udf_flattened table. This prevented users from reporting on data from user-defined fields from the "Safety Learnings" module. We resolved this issue. [Hotfix DCIQ.2024.R4.3 - 15 January 2025]
• Prior to this release, if a user added two medications to a report, then deleted one and saved the changes, in "Data Extraction", the report displayed both medications, but did not specify that one was deleted. We resolved this issue by including an additional field to identify uniquely the administered, intended, or deleted medications on the report. [Hotfix DCIQ.2024.R4.3 - 15 January 2025]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

DCIQ.2024.R3 [Bleeding Edge]

• Download PDF

Enhancements And Changes

• As of this release, all LFPSE fields are available to extract in a Data Extraction under the "Incidents Template" in the corresponding LFPSE sub-sections. Note: You must manually resynchronise certain LFPSE tables before you extract the LFPSE data. For more information, see https://grc-support.rldatix.com/hc/en-us/articles/15314284107548-How-to-sync-LFPSE-fields-for-Data-Extraction.
• We improved the level 2 Incident form design to provide more data and to allow users to manage records that need rectification for LFPSE. We added new fields for "Reference number", "Submission Date/Time", "Status", and "Warnings" in the "LFPSE - Submission Details" section. DCIQ synchronises these fields with the LFPSE management page when you submit them. Users can use the fields to search for and report on records. All of the fields are read-only. Note: The LFPSE record data may not update immediately when you save the record. Refresh the page to see the populated fields. See the Help files for more information on searching with these fields.
• To comply with the Patient Safety Incident Response Framework (PSIRF), we added nine new LFPSE fields to the level 2 Incident form. Administrator users can customise the fields in the same way as any other LFPSE governance questions, including making them read-only, hiding them, adding extra help text, and moving the fields to other sections of the form. For example, the administrator user can make the fields editable by governance leads, but read-only for all other reviewers. The fields are available for reporting. By default, the fields are hidden, and to add the fields to a form, you must enable a global. The new LFPSE PSIRF string field questions "Findings", "What areas for improvement have been agreed as a result of this response?", "How will areas for improvement be addressed (e.g. wider review)?", and "What safety actions have been made to address this area for improvement?" have a character limit of 254. We are currently working on increasing the limit for these fields to enable more data to be entered.
• In any module, when a user types a value into the "Location" field, DCIQ displays any value that is directly or indirectly linked to a value the user already selected in the "Service" field. Likewise, when a user types a value into the "Service" field, DCIQ displays any value that is directly or indirectly linked to a value the user already selected in the Location field.
• In certain circumstances, an Incidents user may need to update a record before a handler has taken ownership to complete the mandatory questions. In this release, we introduced a new permission setting called "Allow User To Bypass Mandatory Fields". When an admin assigns the setting to a user, a profile, or in "Capture Configuration", it allows that user to update records in the status of "In Holding Area, Awaiting Review" or "Awaiting Final Approval" without completing the mandatory fields. Note: Like the setting in "Capture Configuration", if you set the global INC_BYPASS_MANDATORY_FIELDS to Y, DCIQ also applies this permission across the DCIQ system. Set the new permission to "No" or leave it blank to disable the feature.
• We enhanced the Pyspark synchronisation process by implementing parallel processing and enabling horizontal scaling. The enhancement reduces the execution time of the batch processing jobs by fully utilising the allocated resources. It allows DCIQ to scale Pyspark and increase the allocated CPU, rather than increasing the memory. This batch processing job is the synchronisation process for transforming and creating the data in the flattened tables. DCIQ uses flattened tables to create views and reports to analyse data in the BI tool.
• We removed the "Give Feedback" button from non-Capture pages in DCIQ. [Hotfix DCIQ.2024.R3.1 - 19 September 2024]
• We made improvements to Capture form saving and contact saving for all types of contacts (including Persons Affected, Reporters, and other contacts). We also made improvements to underlying code and refactoring to enhance code reliability, and improvements to logging capabilities to improve traceability and issue tracking. [Hotfix DCIQ.2024.R3.3 - 15 October 2024]

Fixes

• Prior to this release, when an admin edited a new user account and completed all mandatory fields, then clicked "Save", DCIQ displayed both "User saved successfully" and "Server error" messages. We resolved this issue.
• We resolved an issue that prevented users from locating action records that are linked to Incidents. This issue occurred when changes were made to the action "Status" in field maintenance and changed the order of the statuses to "Active", "Inactive", "Complete". The order should remain as "Inactive", "Active", "Complete".
• Prior to this release, DCIQ generated an error message when there was payload posted to the Incident update API. We resolved this issue.
• Prior to this release, when a user tried to print an incident report, fields displayed as radio buttons appeared on the print page even though the user did not select their section for printing. We resolved this issue.
• Prior to this release, when a user tried to select a service in an ERM record using the "View children" option, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, when you opened an existing risk in ERM, in the "My Actions" or "All Actions" section, DCIQ displayed "Placeholder" for the "Action Type" field instead of the correct value. This occurred only in the Carlton modules. We resolved this issue.
• Prior to this release, in Capture Admin, when a user created a new listing report for incidents and used the "Sharps" fields, DCIQ displayed an error when they ran the report. We resolved this issue.
• We resolved an issue that affected the formatting of DES exports when users included certain special characters and inserted new lines in the text type fields. [Hotfix DCIQ.2024.R3.1 - 19 September 2024]
• We have resolved a character limit validation issue for the new LFPSE PSIRF string fields "Findings", "What areas for improvement have been agreed as a result of this response?", "How will areas for improvement be addressed (e.g. wider review)?", and "What safety actions have been made to address this area for improvement?". These fields now have a character limit of 254 and users cannot exceed this limit. [Hotfix DCIQ.2024.R3.2 - 01 October 2024]
• Prior to this release, when an admin attempted to generate a code in "LFPSE trigger mapping", DCIQ did not generate the code. Instead, it displayed a loading message. Please note: DCIQ generates new codes based on the systems combo link setup. For example, DCIQ generates combinations where there are parent and child links if the system uses combo linking for the "Type", "Category" and "Subcategory" fields. [Hotfix DCIQ.2024.R3.3 - 15 October 2024]
• Prior to this release, if a user created a new section on an Incident form that was triggered by setting the value of a "Yes/No" field in another section to "No", when a user opened that Incident form, the new section was already visible before setting the value of the triggering field to "No", and if the user added data to that section and saved the form, DCIQ did not save the data. We resolved this issue so that the section does not appear until the user sets the value of the triggering field to "No". [Hotfix DCIQ.2024.R3.3 - 15 October 2024]
• We resolved an issue that caused DCIQ to display an error when a user tried to submit a new safeguarding record or access an existing one. [Hotfix DCIQ.2024.R3.4 - 04 November 2024]

DCIQ.2024.R2.4 [Stable]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

Enhancements And Changes

• DCIQ allows administrators to make the entire "LFPSE-Adverse Event Governance" section, or individual fields from the section, hidden or read-only on DIF2 form designs. This means administrators now have the ability to create event-specific forms without including the "Governance" section.
• DCIQ displays a new set of fields to help users comply with Duty of Candour timescale requirements. DCIQ now allows users to extract the data recorded for the following Incident fields: "Date organisation become aware"; "Date 'in-person' notification made - Due Date"; "Date 'in-person' notification made - Completed Date"; "Date written notification sent - Due Date"; "Date written notification sent - Completed Date"; "Time to handle"; "Working days elapsed between 'Date organisation become aware' and the 'Completed date 'in-person' notification made'"; and "Working days elapsed between the 'Completed date 'in-person' notification made' and the 'Completed date written notification sent'". Note: You must enable the time chain feature flag INC_TIME_CHAIN_ENABLED and ensure the section is not hidden in the form designer to view the new fields. To define the number of working days between the date the organisation became aware and the due date the in-person notification was made, or to define the number of working days between the date of the in-person notification was completed and the due date the written notification was sent, navigate to Capture Admin > Capture Configuration > Incidents and complete the fields.
• DCIQ now displays the "How were actions or behaviours involved in what went wrong?" field when users answer the "How did people's actions differ from what was expected or intended?" field with "Other". DCIQ triggers the "LFPSE - Involved Persons" section if users answer the "Which things were involved in what went wrong?" field with "None of the above".
• DCIQ allows users to extract certain LFPSE fields in CSV format. If a field contains multiple values, DCIQ extracts all values. The LFPSE fields are available for extraction under the "Incidents Template" in separate sub-sections which appear when the environment variable PSIMS_ENABLED is set to 1. Note: You must manually resynchronise certain LFPSE tables before you extract the LFPSE data. For more information, seehttps://grc-support.rldatix.com/hc/en-us/articles/15314284107548-How-to-sync-LFPSE-fields-for-Data-Extraction.
• To improve data quality, DCIQ now allows users to use data extraction to extract and track deleted action records linked to incident records. For this purpose, in "Data Extraction", there is a new template, "Incidents Actions Deleted", where DCIQ allows users to extract the deleted action record, the incident record the action was linked to, and the date when the action was deleted. DCIQ allows users to extract in CSV format.
• We implemented a new workflow and redesigned the matching contacts modal. We introduced a new contact ID number field on DIF1 called "Do you have the contact's ID number?". This field is hidden by default. If a user answers with "Yes", DCIQ displays the ID number section where they can enter the ID number. If DCIQ does not find any matches, it displays the "Add a new contact" option, which allows the user to create a new contact. When a user searches for multiple criteria instead of just ID number, DCIQ displays other unhidden sections on the contact. The sections appear below the "ID number" section in the form design. Note: This field is compatible with the existing criteria global CON_MATCH_CRITERIA. The system requires users to enable the global FORCE_CONTACT_MATCHING_BY_ID and select the ID number as a search field for contact matching in the capture configuration. If DCIQ finds a match, users can click "Choose", edit the ID number and search again, or exit the modal. The retrieved contact is read-only and the linked data fields are editable. If DCIQ does not find a match, it will allow users to edit the ID number and search again, exit the modal, or click "Add new contact" to trigger other sections. DCIQ retains the ID number and number type in the fields.
• DCIQ displays the "Time Chain" section in a specific user interface grid on the DIF2 form with specific date fields presented in a specific order. This enables users with DIF2 access to easily navigate through the fields. The system requires the user to enable the time chain feature flagINC_TIME_CHAIN_ENABLED and ensure the section is not hidden in the form designer.
• We added several existing application fields that were missing to the Reporting database. In the "reportable_incident" table, we added the fields "contact_number", "contact_name", "contact_email" and "incident_time". In the "compl_main" table, we added the field"show_document". In the ETL pipeline, we added the table "link_injuries" and the fields "injury" and "bodypart".
• As of this release, to avoid displaying empty rows in the extracts, the Data Extraction functionality for UDFs extracts related to CSV file formats and Incident Template will retrieve only the data for new incident IDs and UDFs data that are already synchronised with the UDFs synchronisation process.
• When a user sets the frequency of the flattening job in JOB_RUNTIME, in addition to "Hourly" or "Nightly", DCIQ now allows them to select "Eight Hour Interval". The new option runs the flattening job every eight hours, for a total of three times per day. [Hotfix DCIQ.2024.R2.2 - 6 August 2024]

Fixes

• Prior to this release, when some users tried to save a query that contained wildcards, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, staff fields such as "Handler" could appear in reports and on listing pages, but whenusers were subsequently made inactive, DCIQ displayed the users in alphanumeric code IDs instead oftheir names.We resolved this issue.
• Prior to this release, when users tried to merge contacts from a feedback record that referred to multiple users, DCIQ did not display all the linked contacts. We resolved this issue.
• Prior to this release, in Capture > Incidents, DCIQ displayed an error when users searched with a wildcard on either side of a value in a UDF text field. For example, if they tried to search for variations on the word "fall" by searching with " *fal* ", DCIQ displayed an error. We resolved this issue so users can use wildcards without errors.
• Prior to this release,in the RIB notification email, DCIQ displayed multiple locations on one line, divided by a semicolon.We resolved this issue and now "Location" and "Other Location" appear on separate lines in the email.
• Prior to this release, DCIQ sent new investigator emails to named users when the incident record was saved with the "Saved to complete later" status. We resolved this issue.
• Prior to this release, if there were two popups in a DIF1 form, DCIQ greyed out the second popup message and prevented users from completing the form unless they refreshed the page. We resolved this issue.
• Prior to this release, when a user searched the user list in System Admin using the "User Delegation" orthe "Filter User" option by typingin the specific name,DCIQ displayed the whole list of peopleinstead of filtering the results. We resolved this issue.
• Prior to this release, when users used the"Edit Search Criteria" functionality to edit the search in Incidents, DCIQ displayed "No codes available" on most of the fields. We resolved this issue.
• Prior to this release, when users ran listing reports on the LFPSE fields, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, in the Incident search, when users tried to search for a term using the "*" or "%" wildcards, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, DCIQ did not allow users who were given permission to create, save, edit, and delete statistical reports to edit or delete any records. We resolved this issue.
• Prior to this release, when users logged in, DCIQ auto-populated the reporter details on a DIF1 form, and when they cleared the section and used different details, DCIQ did not display them on the DIF2 form. Instead, it displayed them as a linked contact. We resolved this issue.
• Prior to this release, when a user submitted an Incident record with the event type of "Good care", "Incident, Risk", or "Outcome", DCIQ incorrectly displayed the "Does this event meet the requirements for Duty of Candour?" field in the LFPSE section of the DIF2record.We resolved this issue by moving the field to the "LFPSE - Adverse Event Governance" section.
• Prior to this release, when users selected a new handler on a Feedback record, DCIQ sent the user a new handler email and also an email to notify them of a new feedback record, even if they did not have any security groups or profiles that provided permissions to view the record.This was caused bya connection between the global parameters "COM_EMAIL_MGR" and "EMAIL_HANDLER_GLOBAL".We resolved this issue so that new handlers only receive the handler email if they do not have any security groups which also provide them access to the Feedback record. We also resolved this issue in the Claims, Mortality, and Redress modules.
• Prior to this release, users with access to Incidents records could not delete medications from the medications section. We resolved this issue.
• Prior to this release, when a DCIQ user with access to review risk records completed a review and saved the changes, DCIQ displayed an error message. We resolved this issue.
• Prior to this release, DCIQ sent two notification emails to users selected as handlers on a DIF1 instead of just one email. We resolved this issue.
• Prior to this release, users had to wait for 20 seconds for DCIQ to open. We resolved this issue.
• Prior to this release, if a user populated the field type_id with a null value, it caused a synchronisation issue with the database. We resolved this issue so that DCIQ does accept null values in the type_id field.
• In Capture > Customer Feedback, when users open a new feedback record, the date format for "Date entered" is now changed fromYYYY-MM-DDto DD/MM/YYYY.
• We resolved an issue that prevented DCIQ from extracting the correct values for “Service Team Title” in the "Service Admitted" field when extracting from the Data Extraction Tool.
• We resolved an issue where DCIQ did not save the value for "Are you reporting a patient safety event?" on the INC1 form, which prevented DCIQ from displaying the LFPSE information on the INC2 form.
• We resolved an issue that caused extract files to display the values in the date field "Date Started" in the incorrect date format.
• Prior to this release, the reporting database did not accept null values for the user forename and surname fields, which caused a synchronisation issue. We resolved this issue so that the reporting database accepts null values for the user forename and surname fields.
• Prior to this release, if a user added more than 100 ID number type codes to the database, when a user created a new incident and performed a contact match, the contact's ID number types were editable. We resolved this issue, ensuring that the details in the Contact (Patient) Section are now read-only.
• Prior to this release there was an issue that caused medication data loss after submitting Incidents. We resolved this issue. [Hotfix DCIQ.2024.R2.2 - 6 August 2024]
• We resolved an issue in the Incidents extract file that caused the text in the "Fell From" column header to appear incorrectly. [Hotfix DCIQ.2024.R2.2 - 6 August 2024]
• We resolved an issue that caused additional characters to appear in certain extra fields in the DES extract file. [Hotfix DCIQ.2024.R2.2 - 6 August 2024]
• Prior to this release, when a user added a new incident and searched for a patient ID that did not exist in the database, DCIQ displayed an old version of the contact searching form. We resolved this issue so DCIQ displays the correct version of the contact searching form. [Hotfix DCIQ.2024.R2.2 - 6 August 2024]
• Prior to this release, in System Admin > Data Extraction Tool > Downloads, when you selected a job to view the report, DCIQ did not include the values in any police fields. We resolved this issue so that the report includes all of the relevant values for the "Yes / No" fields. [Hotfix DCIQ.2024.R2.3 - 14 August 2024]
• Prior to this release, when users used the new patient search function, DCIQ displayed the default contact listing instead of the contact matching listing form. We resolved this issue. [Hotfix DCIQ.2024.R2.3 - 14 August 2024]
• Prior to this release, when a notifier reopened a draft record and wanted to clear the existing matched contact and chose another one, DCIQ did not display the "Clear Section" option that removed the contact details. We resolved this issue. [Hotfix DCIQ.2024.R2.3 - 14 August 2024]
• We resolved an issue that allowed users without Reports Admin access to edit and delete reports on the My Reports page. [Hotfix DCIQ.2024.R2.3 - 14 August 2024]
• We resolved an issue in Capture > Back to full system admin > Data Extraction > Settings that prevented users from using the "Sync Field Labels" options. [Hotfix DCIQ.2024.R2.4 - 22 August 2024]
• Prior to this release, the existing application fields that we added to the "reportable_incident" table and the "compl_main" table did not appear in the BI tool. We resolved this issue.[Hotfix DCIQ.2024.R2.4 - 22 August 2024]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• UK - A4 PDF
• US - A4 PDF

• Download PDF

• Download PDF

• Download PDF

DCIQ.2024.R1.1 [Bleeding Edge]

• Download PDF

DCIQ.2024.R1 [Bleeding Edge]

• Download PDF

Enhancements And Changes

• We added three new user and group permissions. They allow you to grant permission to a user or group to unlink contacts, to reassign dashboards, and to trigger overdue email notifications.
• When an incident that affects a patient results in physical or psychological harm that is moderate or higher, DCIQ triggers new fields to capture the dates of the event taking place and various in-person and written notifications. These fields have configurable deadline dates, and completed dates that capture when a specific action was completed. The information in the fields is available for reporting. These fields help users comply with the Welsh government's new regulations concerning Duty of Candour requirements. To use this feature, you must enable the global variable INC_TIME_CHAIN_ENABLED.
• The Specialty list in DCIQ now contains 202 specialties. New codes have been added, edited codes have been replaced, and deleted codes have been made inactive but are still available for reporting.
• We made several improvements for LFPSE in the Incidents module. When you set the "Does the Incident appear to relate to any of these known safety challenges?" field to "Screening services incident", DCIQ displays the "Marvin reference number" in the "LFPSE - Adverse Event Safety Challenges" section. When you set "Does the Incident appear to relate to any of these known safety challenges?" to "Radiotherapy incident", DCIQ displays the "What is the radiotherapy incident code?" field in the"LFPSE - Adverse Event Safety Challenges" section. We added a field called "Was the availability of people a factor in this incident?", which allows you to display or hide the "How was people's availability involved in what went wrong?" field. The data from the new field is not sent to LFPSE. Finally, we removed the help text for the"What is the patient's sex?" field.
• You can now include the following LFPSE maximum harm fields in email notifications: "Maximum level of physical harm incurred by persons affected in event" and "Maximum level of psychological harm incurred by persons affected in event".
• We enhanced the behaviour of recurring data extraction jobs to simplify the process and avoid time-based calculation issues. When you run a recurring job with a daily, weekly, or monthly frequency, DCIQ extracts data up to the last full day before the date of extraction, and does not include any data from the date of extraction. For example, if a recurring extraction takes places on the 2nd, regardless of the time of day, it only includes data up to the 1st.
• When an incident that affects a patient results in physical or psychological harm that is moderate or higher, DCIQ triggers new fields to capture the dates of the event taking place and various in-person and written notifications. On the DIF2 form, DCIQ automatically calculates the "Due Date Written Notification Sent" date when you complete the "Completed Date 'In-Person' Notification Made" field. [Hotfix DCIQ.2024.R1.1 - 15 April 2024]
• It is now possible to customise the frequency of the background job to synchronise UDF data. Previously, the frequency was only once an hour. As of this release, you can change the frequency to once a day. For this purpose, weadded a new environment variable called JOB_RUNTIME which allows you to set the frequency to "Nightly". By default, the frequency is still "Hourly". [Hotfix DCIQ.2024.R1.5 - 30 May 2024]

Fixes

• Prior to this release, when you enabled dark mode on your iPhone and attempted to input text into any available input fields, the text was not visible. We resolved this issue.
• We resolved an issue that caused DCIQ to display a handler's name as a numerical value when you set "Show In Staff Drop-Downs?" to "No". Now, if you change the value of "Show In Staff Drop-Downs?", the handler's name always appears correctly.
• Prior to this release, if you added an "Action Type" to an Action, it did not appear in the Actions dashboard listing table. We resolved this issue.
• Prior to this release, in Incident records, when you populated the "Result" fields with "None" and ran and downloaded the extraction, the field was blank. We resolved this issue.
• Prior to this release, if user populated the Result field in an Incident record with "None", the Data Extraction tool did not extract the data from the field. We resolved this issue so the Data Extraction tool extracts the "None" value correctly.
• We resolved an issue that caused actions deleted in DCIQ to still be displayed in the Yellowfin database.
• Prior to this release, when you added a new contact to a chronology event under the Investigation record, the columns in the "Event Chronology" table displayed values that belonged to other columns.Weresolved this issue.
• Prior to this release, when you created an incident type of deteriorating patient andselected "None" for"Coloured trigger present at the time of incident" and "Coloured triggers present in the 24-hour period prior to the incident?",DCIQ did not display the "None" value in the CEC extracts.We resolved this issue.
• We resolved an issue that prevented admins from searching for users in the Full Audit section of Capture Admin.
• We resolved an issue that caused DCIQ to display an error when you searched for certain incident records in the Incidents module and viewed their DIF1 values.
• We corrected a spelling mistake in the help text for the LFPSE question "Are you reporting a patient safety event?" in Incidents.
• We resolved an issue that caused DCIQ to send overdue email reminders for a risk record that was already closed.
• We resolved an issue that allowed users to save morality review records without filling in all the mandatory fields in the MOR1 and MOR2 forms.
• We fixed several issues with listing reports exported to Excel. UK-formatted dates no longer change to US format; text fields no longer lose their formatting; time fields are formatted consistently.
• Prior to this release, some tables were missing from certain Yellowfin environments, preventing users from running the same reports as in other environments. We resolved this issue.
• We resolved an issue that caused a system error to occur when you completed a No Person incident form.
• Prior to this release,when you searched for incidents with incident status "New or AWAFA | FA" and included a search criteria of "Who Was Affected", DCIQ displayed an error. We resolved this issue.
• Prior to this release, when you submitted a safety alert, if the "Action Type" field was a radio button instead of a dropdown field, DCIQ did not save the value of the field. We resolved this issue.
• Prior to this release, in Capture > Incidents, when you added a new incident and selected "Blood, Medication and Tissues or Organs for Transplants"from the "Whichthings were involved in what went wrong?"field,DCIQ did not display the"NHSBT Reference Number" field. We resolved this issue.
• Prior to this release, when you filled in the"Was the care decisions for last days of life guidance document completed?" with data in the DCIQ records, it was empty in the Yellowfin system. We resolved this issue.
• Prior to this release, in the LFPSE section, if you set "Which things were involved in what went wrong?" to "Blood Products", then set "How were blood products involved in what went wrong?" to "Blood products were not used when they should have been", DCIQ does not trigger the subsequent field "Why were blood products not used when they should have been?". We resolved this issue.
• Prior to this release, when you created a job using the Data extraction tool, some jobs were failing and some were working for a couple of days before failing. We resolved this issue.
• Prior to this release, when you set up Progressive disclosure in the Incidents module and a trigger was set up for the Services field, DCIQ did not display the triggering value if a child value was selected. We resolved this issue.
• We resolved an issue that caused theFacility / Location not to display the full location hierarchy path when referring to location in RIB modules.
• Prior to this release, when admins tried to set up a delegation from a Reviewer profile to a Notifier profile, DCIQ did not allow them to select a user with no location assigned. We resolved this issue.
• Prior to this release, when you added a location trigger, it only worked for the tier selected in the location instead of all tiers of the location. We resolved this issue. Note: This bug was resolved in R1 but was documented in R1.7.
• Prior to this release,formatting for RIB reports did not match requirements from the original specification provided by CEC in 2021, which resulted in formatting issues of the RIB templatesPart A and Part B. We resolved this issue.
• Prior to this release, when you ran anextraction from the DES tool in JSON format that included the "Legal Entity" field, DCIQ displayed amessage that the JSON could not be parsed because it was not formed well. We resolved this issue.
• Prior to this release, DCIQ did not allow you to save a medication incident until you filled in the medication details even though that section was read-only. We resolved this issue.
• Prior to this release, within the claim's module, when a section is hidden via a form action that contains mandatory fields, DCIQ behaved as if those fields were still required to be populated before submission and prevented the record submission. We resolved this issue.
• We resolved an issue that caused the fields that are set as mandatory on the CON1 form design in the "Details of the person reporting the incident" section of the DIF1 not to be displayed as mandatory.
• Prior to this release, when you tried to expand the section that contained the approval status in level-1 and level-2 incident design forms, DCIQ displayed a "Section failed to load" alert. We resolved this issue.
• Prior to this release, when reporting a new incident when users answered the "Were patients involved in this event?" field with "Yes", a warning message immediately appeared. We resolved this issue and the message only appears upon saving the record.
• Prior to this release, users with Local Admin access received an error message when they tried to access the Full Audit in Capture Admin. We resolved this issue.
• Prior to this release, users were unable to progress within a Feedback record because the page froze when multiple message were set up in Design form actions. We resolved this issue.
• Prior to this release, when you created a new hourly job and selected the Start time before the current time, the Save and Schedule button was disabled. When you changed the Start time to be after the current time the button was still disabled and DCIQ displayed an error message unless you refreshed the page. We resolved this issue.
• Prior to this release, when reporting an incident, if you added more than two contacts in the "People Affected" section before checking the box "Was any other person involved in the incident?" and completing the respective triggered section with few additional contacts, DCIQ only saved the first two people's details within the "People Affected" section. We resolved this issue.
• Prior to this release, when you opened a Yellowfin report, DCIQ did not display data in the "Action Type" field. We resolved this issue.
• Prior to this release, users with MOR2 access could close records in Mortality Review without populating mandatory fields. We resolved this issue.
• Prior to this release, in System Admin > Data Extraction, when you created a new incident job and completed all the fields in the UDF section, then ran a DES extract, DCIQ did not display any data for the UDF fields in the output. We resolved this issue.
• Prior to this release, when you opened some reports within Yellowfin,DCIQ displayed theJSON array instead of the value.We resolved this issue.
• Prior to this release, when you navigated to a DCIQ site as a user with Yellowfin access and created a report with the ERM view, DCIQ did not record the data in certain system fields and did not record data in any user-defined fields.We resolved this issue.
• Prior to this release, in Yellowfin, DCIQ did not display some of the fields in the risk reports. We resolved this issue.
• Prior to this release, when you opened a Yellowfin report, DCIQ only displayed code numbers in the"risk subtype", "assuring board committee" and "assuming board sub-committee" fields in ERM. We resolved this issue.
• Prior to this release, in the BI Tool, the reports for Service and Location based on the fields in the "SERVICE_FLATTENED_LEVEL8" and "LOCATION_FLATTENED_LEVEL8" tables did not pull any data for these fields, even though the tables contained all the expected data. We resolved this issue.
• Prior to this release, DCIQ duplicated safeguarding records when the reporter refreshed the page after submitting a record.We resolved this issue. [Hotfix DCIQ.2024.R1.1 - 15 April 2024]
• Prior to this release, after the system migration, every time you opened the DES module, DCIQ displayed a red blank error ribbon on the header of the page. We resolved this issue. [Hotfix DCIQ.2024.R1.1 - 15 April 2024]
• Prior to this release, when you added inline bold formatting to text, there werespacing issues around the word in the PDF. We resolved this issue. [Hotfix DCIQ.2024.R1.2 - 8 May 2024]
• Prior to this release, when you searched for a contact record using the person's NHS number, DCIQ returned the wrong records. We resolved this issue. [Hotfix DCIQ.2024.R1.2 - 8 May 2024]
• Prior to this release, when DCIQ sent you emails for the Capture modules Incidents and Feedback, they did not contain the expected information. We resolved this issue. [Hotfix DCIQ.2024.R1.2 - 8 May 2024]
• Prior to this release, when DCIQ sent you emails for the Capture modules Incidents and Feedback, they did not contain the expected information. We resolved this issue. [Hotfix DCIQ.2024.R1.2 - 8 May 2024]
• Prior to this release, when you linked a person affected to an incident record, DCIQ often displayed the person's patient ID number multiple times, causing a 504 timeout error when you tried to save the record. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, DCIQ displayed duplicate ID numbers for a person affected on an incident, and did not allow you to delete the additional lines. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, when you navigated to Contacts, DCIQ displayed the NHS number multiple times on the same record. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, when you linked a person affected to an incident record, DCIQ often displayed the person's patient ID number multiple times, causing a 504 timeout error when you tried to save the record. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, when you added a contact to a capture record via the external contact lookup system, DCIQ displayed the NHS number multiple times. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• We resolved an issue that caused DCIQ to duplicate a contact's address, email address, and phone number when you linked it to another record. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, in Capture > Incidents, DCIQ displayed the codes instead of the item descriptions in the LFPSE questions section. We resolved this issue. [Hotfix DCIQ.2024.R1.3 - 8 May 2024]
• Prior to this release, DCIQ displayed a "Server is unable to complete this request" message tousers when they tried to mark actions as complete. We resolved this issue. [Hotfix DCIQ.2024.R1.4 - 23 May 2024]
• Prior to this release, when you added an incident to a DIF1 form and submitted it, DCIQ did not save the Reporter data and did not display it when you viewed the record on a DIF2 form. We resolved this issue. [Hotfix DCIQ.2024.R1.4 - 23 May 2024]
• Prior to this release, if you tried to complete certain LFPSE fields on a DIF1 with too many characters, DCIQ displayed an error and did not record the data on the DIF2 form. We resolved this issue. [Hotfix DCIQ.2024.R1.4 - 23 May 2024]
• Prior to this release, if you submitted a feedback record with an approved contact attached, DCIQ removed the person's NHS number from the contact record. We resolved this issue. [Hotfix DCIQ.2024.R1.4 - 23 May 2024]
• We resolved an issue that occurred when you tried to match a contact with a third-party patient system. The error occurred when you searched for an existing person in the Contacts module, but the third-party system could not link with the existing record. We resolved this issue. [Hotfix DCIQ.2024.R1.5 - 30 May 2024]
• Prior to this release, when you added a new incident and searched for an already existing patient in the Contacts module, DCIQ displayed a string format error that prevented you from selecting a contact. We resolved this issue. [Hotfix DCIQ.2024.R1.5 - 30 May 2024]
• We resolved some inconsistency issues in the "Patient Identifier" column. [Hotfix DCIQ.2024.R1.5 - 30 May 2024]
• Prior to this release, when you tried to apply LFPSE triggers to certain options, DCIQ did not save the change. We resolved this issue. [Hotfix DCIQ.2024.R1.6 - 19 June 2024]
• Prior to this release,if you did not include thecon_id_number in the EPR search global, DCIQ displayed an error when you tried to search for a patient or save a contact. We resolved this issue. [Hotfix DCIQ.2024.R1.6 - 19 June 2024]
• We resolved an issue that prevented DCIQ from retaining data on DIF2 LFPSE fields when adding more than 254 characters in the "What was the clinical outcome for the patient?" field. [Hotfix DCIQ.2024.R1.6 - 19 June 2024]
• We resolved an issue that prevented you from selecting an external patient on an incident if a value in the patient's data included an apostrophe. [Hotfix DCIQ.2024.R1.7 - 27 June 2024]
• Prior to this release, in a new incident, when you populated the "Route administered, prescribed, dispensed, or omitted" field, the "Dose administered, prescribed, dispensed or omitted" field, and the "Form administered, prescribed, dispensed or omitted" field in the "Administered" section, then clicked "Duplicate", DCIQ did not duplicate the values to the "Intended / Suspected" section, and dropdown values were blank for "Route Intended / Suspected" field. We resolved this issue. [Hotfix DCIQ.2024.R1.7 - 27 June 2024]
• We resolved an issue that prevented DCIQ from automatically populating the date field values in extracts produced by jobs that contain UDF date fields. [Hotfix DCIQ.2024.R1.7 - 27 June 2024]

• UK - A4 PDF
• US - A4 PDF

• Download PDF

• Download PDF

• Download PDF

Enhancements And Changes

• It is now possible to edit and create email templates for all Non-Capture email templates within the Notification Centre.
• In CSV exports from the Data Extraction function, all dates are in the format YYYY-MM-DD, and all times are in the format HH-MM-SS, regardless of the user's region.
• In Data Extractions, all time fields now display the time in the current system time UTC offset.
• We added the field COD_NCDS_LOCATION to the LOCATION_CAPTURE table and the mapping tables in the ETL for Yellowfin.
• We extended the OAuth2 authorisation for external contacts searching. Prior to this release, DCIQ can be configured to support external contact lookups using shared secrets. As of this release, access token requests can be made with the client's certificate assertions.

Fixes

• If you set "Are you reporting a patient safety event?" to "Yes", the form should only display the "Do you think any of the below were relevant to the incident occurring?" field if you set "What kind of event do you want to record?" to "Incident" or "Outcome". We resolved an issue that caused the field to appear if you set "What kind of event do you want to record?" to "Risk" or "Good Care".
• We resolved an issue that prevented users from removing Maintenance Mode from their environment.
• We resolved a database connection error issue experienced by some users attached to a particular profile on certain environments when submitting incidents.
• We resolved an issue that prevented some users from being able to add new locations to their environment.
• We resolved an issue that prevented you from viewing the audit trail for certain records in Capture & Feedback.
• Escalation comments are now visible when you accept or reject a risk record.
• When you submit a new Safeguarding record that includes a date of birth and a value in the "Date of event" field, DCIQ now correctly calculates the Age and Age Band.
• We resolved an issue that caused DCIQ to display an error when you try to complete and submit a Patient incident.
• We resolved an issue that caused DCIQ to display an error when you check for matching contacts of the Person Providing Consumer Feedback from the People Involved in a complaint feedback that is in review.
• Prior to this release, if there is a pending contact merge and you begin another contact merge, the error message does not explain why DCIQ cannot proceed to create the job. We resolved this issue so the error message is more informative.
• We resolved an issue that caused DCIQ to display the wrong error message when you view a dashboard widget that contains no data.
• We resolved an issue that caused a Javascript error when you viewed a dashboard, switched to another dashboard, then returned to view a previous dashboard.
• We resolved an issue that caused some values to bepopulated as backend codes instead of actual values.
• We resolved an issue where newly added locations were not included in the published list.
• We resolved an issue that prevented DatixWeb from linking payments to the correct claim ID when adding payments to a Claims record.
• We resolved a issue that prevented DCIQ from automatically populating the Reporter section on Capture records with the logged in user's details, and caused DCIQ to create duplicate contact instances for the user instead. [Hotfix DCIQ.2023.R9.1 - 22 January 2023]
• We resolved an issue that caused DCIQ to display a contact's ID number multiple times. [Hotfix DCIQ.2023.R9.1 - 22 January 2023]
• We resolved an issue that caused DCIQ to display duplicated patient details in the Who Was Affected section. [Hotfix DCIQ.2023.R9.1 - 22 January 2023]
• We resolved an issue where DCIQ displayed an error when opening some reports under MyReports. [Hotfix DCIQ.2023.R9.1 - 22 January 2023]
• We resolved an issue that caused DCIQ to return all records when you ran any packaged or normal report with the @prompt query in any module, instead of returning the correct records based on the query. This process also no longer returns an error. [Hotfix DCIQ.2023.R9.1 - 22 January 2023]
• We resolved an issue that caused DCIQ to display an error when you submitted a feedback report in which you set "Is the person providing feedback the person affected by the feedback?" to "Yes" and set the "People Affected" section to "None" or "No". [Hotfix DCIQ.2023.R9.2 - 30 January 2023]

• UK - A4 PDF
• US - Letter PDF

• Download PDF

• Download PDF

• Download PDF

• Download PDF

• Download PDF

• Download PDF

Enhancements and Changes

• When you enable the VANESSLAW environment variable, the 'Type', 'Class', 'Strength of drug administered', and 'Strength of drug intended / suspected' fields are visible in the Medication section in Capture records. This complies with regulatory reporting demands.
• The values in the Medications drop-down fields for Incidents ensure the medication data in Incidents fits the prescribed format and content for CIHI. This change went under a specific config for the affected region.
• If you search for a unique patient number, the system will contact the External Contact Service for any external contact match. If you do not want to search External Contact Service, DCIQ allows you to search through the Contacts module or manually add and save the contact data.
• When EMPI integration is enabled for BC, in Capture Admin > Capture Configuration, DCIQ displays the "Datix fields which can be used for data lookup in external resource" field. This allows you to query the EMPI database using the external BC(EMPI) contacts lookup.
• DCIQ admins can now map the published locations to the service-related LFPSE fields “Where did the incident happen?” and “Where was the risk identified?”. The services mappings can be defined in the Services code setups page. In level 1 or level 2 forms, when you select a mapped service, DCIQ auto-populates the LFPSE fields with the relevant value. The mappings in LFPSE auto-population page and the Services code setups page must be configured without conflicts. To download the list of list of fields and codes of service-related LFPSE fields, click here.
• DCIQ admins can now map the published locations to the location-related LFPSE fields “Where did the incident happen?” and “Where was the risk identified?”. The locations mappings can be defined in the Locations code setups page. In level 1 or level 2 forms, when you select a mapped location, DCIQ auto-populates the LFPSE fields with the relevant value. The mappings in LFPSE auto-population page and the Locations code setups page must be configured without conflicts. To download the list of list of fields and codes of location-related LFPSE fields, click here.
• The Data Extraction Start Time field now displays in the current system time UTC offset.
• The Incident field 'Sharp' can now be included as a submodule for Data Extraction. It can be extracted in both CSV and JSON formats.
• If you are an admin, in the DIF1 form designer DCIQ allows you to set default values for the ‘What kind of event do you want to record?’ field in your LFPSE records and displays a checkbox that allows you to hide it.
• If you are inactive in DCIQ for a specified amount of time when you were previously using Icon Wall, the system displays a blank screen and a message notifying you that if you do not respond soon it will log you out or take you back to a specified page.
• For LFPSE, if the Incident date and the date reported are the same then "Did the event happen today?"= Yes.
  If the incident date and the date reported do not match then '"Did the event happen today?"= No.
• It is now possible to search using LFPSE contact fields and also utilise shortcuts, such as @prompt, ==, and !=.
• It is now possible to delete attachments from Safety alerts. This allows you to correct mistakes or remove unnecessary attachments.
• DCIQ only displays active codes when generating the mappings between LFPSE section and Type, Category, and Sub-Category fields, so that the newly generated combinations have only codes that were valid at the time of the generation.
• Admin users can now map the values in type, category, subcategory fields to trigger the LFPSE section. Admins can define the mappings in the new page "LFPSE Trigger Mapping" in Capture Admin.
• In the 'LFPSE trigger mapping' feature, admins can now use the “Incident affecting” field to trigger the LFPSE sections to capture the LFPSE data.
• A toggle has been added to level 1 incident forms which allows the reporter to hide all non-mandatory LFPSE fields. The toggle appears on the form whether the reporter is logged in or not. By default, the toggle is set to No and all fields are visible. If you hide non-mandatory fields, the toggle overrides the triggers that would usually show those non-mandatory fields. If you complete a non-mandatory field, then hide all non-mandatory fields, DCIQ saves the data you added to the field.
• It is now possible to trigger the LFPSE sections from Type, Category and Subcategory fields based on mappings created by Admins.

Fixes

• We resolved an issue that allowed you to change the value in the Drug Administered field on a level 2 form, creating a mismatch with the saved medication data. This value is now read-only to prevent the mismatch.
• We resolved an issue in the Incidents module where contact matching was not successfully pulling through any contacts on level 1 forms.
• It is now possible to include the 'Marital status' field in reports for the BI Tool without error.
• If you add values to the globals EXTERNAL_CONTACTS_AUTH_STRATEGY, EXTERNAL_CONTACTS_REQUEST_METHOD and EXTERNAL_CONTACTS_REQUEST_FIELDS, within capture configuration, the values do not save. Prior to this release, DCIQ did not display a warning to inform you of this. As of this release, when you save a Capture configuration, DCIQ displays a warning to inform you that the globals will be unset.
• Prior to this release, when creating an Incident, if a user selected the medication search field and pressed Enter, a new record would be created without completing the mandatory fields on the form. As of this release, DCIQ searches the list of available medications, as expected.
• We resolved an issue that caused the Data Extraction Service to display in the wrong language.
• We resolved an issue that prevented users from submitting an incident record after completing all the mandatory fields in the form. [Hotfix DCIQ.2023.R8.1 - 16 October 2023]
• We resolved an issue that allowed you to change the value in the Drug Administered field on a level 2 form, creating a mismatch with the saved medication data. This value is now read-only to prevent the mismatch. [Hotfix DCIQ.2023.R8.1 - 16 October 2023]
• We resolved a permissions issue that was encountered during penetration testing by modifying user permissions in the JTW tokens and cookie parameters. [Hotfix DCIQ.2023.R8.1 - 16 October 2023]
• Prior to this release, in Incidents and Feedback, if a mandatory field in a Capture form was hidden behind another action, if you bypassed the field action trigger that controlled the mandatory fields, the mandatory field still prevented you submitting the record. We resolved this issue so that if the mandatory field is hidden, it does not prevent you submitting the form. [Hotfix DCIQ.2023.R8.1 - 16 October 2023]
• We resolved an issue that prevented you from submitting a record if any Datix CSS field contained a default value but was hidden on the form design. [Hotfix DCIQ.2023.R8.2 - 23 October 2023]
• We resolved an issue that prevented local administrators from seeing users with no location set on their profile. [Hotfix DCIQ.2023.R8.2 - 23 October 2023]
• We resolved an issue that prevented admin users with access to the Capture Admin > Full Audit from being able to filter based on just the date component of the Date/Time field by typing the date. [Hotfix DCIQ.2023.R8.2 - 23 October 2023]
• We resolved an issue to ensure the udf_values table in the YF dashboard includes the udf_value_id. [Hotfix DCIQ.2023.R8.2 - 23 October 2023]
• We fixed an issue that caused DCIQ to clear the first attached medications in the 'Drug administered' sections when users entered a drug intended, selected a medication, and pressed Enter. [Hotfix DCIQ.2023.R8.3 - 6 November 2023]
• Prior to this release, when PHP Medications is enabled, the Strength and Supplier fields in the medication section did not retain the data populated when the incident was saved. We resolved this issue. [Hotfix DCIQ.2023.R8.3 - 6 November 2023]
• Prior to this release, when PHP medication is enabled, the Strength and Supplier fields do not appear under both Administered and Intended/Suspected in the medication section. We fixed this issue. [Hotfix DCIQ.2023.R8.3 - 6 November 2023]
• Prior to this release, when you selected 'New medication' and added a second medication to the form in the incident module, then added a search term and pressed Enter to perform the search, DCIQ deleted the first medication already added to the record. We resolved this issue. Also, we made the behavior of initiating the meds search when pressing enter within the field consistent when php forms are enabled as well as disabled. [Hotfix DCIQ.2023.R8.3 - 6 November 2023]
• We resolved an issue that caused DCIQ to automatically submit a DIF1 form when you clicked "Clear" in the Medications section. [Hotfix DCIQ.2023.R8.3 - 6 November 2023]
• We resolved an issue where email notifications were not sent when actions were created in the Incident, Feedback, and ERM modules.[Hotfix DCIQ.2023.R8.4 - 15 November 2023]
• We resolved an issue that caused DCIQ to send numerous overdue risk and overdue actions reminder emails. [Hotfix DCIQ.2023.R8.4 - 15 November 2023]
• Prior to this release, when you searched for a patient in EPR, and you selected the patient for an incident, DCIQ added the patient to the Contacts table even if the patient already existed in the table. We resolved this issue so that DCIQ does not create duplicates in the Contacts table. [Hotfix DCIQ.2023.R8.4 - 15 November 2023]
• When you used LFPSE trigger mapping, if you deselected a triggering value, then reselected it, DCIQ did not load the DIF2 subsections of LFPSE properly, or loaded them containing previously entered data. We resolved this issue. [Hotfix DCIQ.2023.R8.5 - 22 November 2023]

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• In the Data Extraction module, when contact ID numbers are extracted the description will extract with it.
• Administrators can now choose to display a multi-select incident LFPSE field as checkboxes instead of a drop-down by making the necessary settings in the form designer.
• If PHP_MEDS_FORM is enabled, administrators can now relabel the 'Medications drug administered' and 'Medications drugs intended/suspected' section headings on DIF1 and DIF2 forms in the capture module via form design.
• When LFPSE is enabled for the first time, the LFPSE trigger question "Are you reporting a patient safety event?" will not appear on all forms by default. You must unhide this question in the form designer for using LFPSE.
• In the form designer, we added an action to all single-select LFPSE-coded fields to 'Display as radio buttons'. When you check the box, DCIQ displays the field values as radio buttons instead of options in a drop-down field. This allows you ensure consistency of LFPSE fields with the rest of the Incidents module.
• Administrators now have the option to change triggered mandatory LFPSE fields to non-mandatory on DIF1 and DIF2 forms via form design in the capture module.
• We updated the Risk and Incident UDF flat tables to ensure that the fields in the table are displayed in the correct datatype.
• If a user is not active in DCIQ for a specified period of time, if they have a page open relating to Medications, DCIQ displays a message to inform them that they will be logged out within one minute. The warning message spans the entire viewport hiding any confidential content on the application. If the user does not interact with the message, or if the user clicks 'Cancel', DCIQ logs out the user. The user must log in again to continue using DCIQ.
• If a user is not active in DCIQ for a specified period of time, if they have a page open relating to LFPSE, DCIQ displays a message to inform them that they will be logged out within one minute. The warning message spans the entire viewport hiding any confidential content on the application. If the user does not interact with the message, or if the user clicks 'Cancel', DCIQ logs out the user. The user must log in again to continue using DCIQ.
• If a user is not active in DCIQ for a specified period of time, if they have a page or tab open relating to the To Do List, DCIQ displays a message to inform them that they will be logged out within one minute. The warning message spans the entire viewport hiding any confidential content on the application. If the user does not interact with the message, or if the user clicks 'Cancel', DCIQ logs out the user. The user must log in again to continue using DCIQ.
• If a user is not active in DCIQ for a specified period of time, if they have a page open relating to Capture, DCIQ displays a message to inform them that they will be logged out within one minute. The warning message spans the entire viewport hiding any confidential content on the application. If the user does not interact with the message, or if the user clicks 'Cancel', DCIQ logs out the user. The user must log in again to continue using DCIQ.
• We improved the coherence of LFPSE fields and ensured that certain LFPSE fields only appear in the correct circumstances. DCIQ only displays the 'What is the patient's self-identified ethnicity?' field if you select 'Incident' or 'Outcome' for the question 'What kind of event do you want to record?' and select a person affected on the INC1 and INC2 form.
• When you extract data from DCIQ using Data Extraction, the extraction now informs you whether a record that was included in a previous extraction has been deleted. This allows you to identify records that have been deleted since your last extraction.
• DCIQ allows you to configure LFPSE contact drop-down fields so that it is automatically populated with a preselected value. This makes it quicker for users to complete the form and reduces the chances of user error. The user can edit the prepopulated value later.
• If a user is not active in DCIQ for a specified period of time, if they have a page open relating to Non-Capture, DCIQ displays a message to inform them that they will be logged out within one minute. The warning message spans the entire viewport hiding any confidential content on the application. If the user does not interact with the message, or if the user clicks 'Cancel', DCIQ logs out the user. The user must log in again to continue using DCIQ.
• We made various updates to the Incidents and Risks forms and form designers. These updates ensure that the forms do not trigger specific fields at inappropriate times, that the forms are cohesive to fill out, and that the forms adhere to LFPSE standards. [Hotfix 2023.R7.2 - 6 September 2023]
• We introduced two new fields in the Incidents module called "Maximum level of physical harm incurred by person's affected in event" and "Maximum level of psychological harm incurred by person's affected in event". If you add one or more person affected to the record, DCIQ auto-populates the fields with the most severe physical or psychological harm suffered by any one of the persons affected. The fields behave like core fields but do not appear in code setups or combo linking. On a DIF2 form, admins can change the labels of the fields, move them between sections, and hide or add new actions to the fields. DCIQ allows you to use the two fields as search criteria, for listing reports and statistical reports, and as fields in the Report administration. DCIQ allows you to create security groups from the two fields.

Fixes

• For the RIB module, when the part A document of a RIB template is generated, the file is now named 'reportable-incident-brief-part-a.pdf'. This is consistent with the name of the part AB document.
• We resolved an issue that caused an error when Admins attempted to load the LFPSE Auto-population feature. This now works as expected.
• We resolved an issue that caused DCIQ to display the dates of data extraction jobs in the US date format, even when the system language was set to UK English.
• We resolved an issue that caused an error when running a listing report that merged repeated values.
• We made it more visible to identify which mandatory fields without a value were preventing users from submitting data when reporting affected body parts or injuries.
• Prior to this release, if you created a user-defined section in a form with user-defined fields, then used the Move Field action to move it to another section, the fields disappeared from the section. We resolved this issue.
• We resolved an issue that prevented DCIQ from including the values of radio buttons in Print view.
• We resolved an issue that prevented you from processing a provided payload to the mortality API twice.
• We resolved an issue that prevented you from adding a row when you tried to batch update in Capture. [Hotfix DCIQ.2023.R7.1 - 29 August 2023]
• We resolved an issue where the Outcome and Risk LFPSE codes were reverting after each upgrade. [Hotfix DCIQ.2023.R7.1 - 29 August 2023]
• We've fixed an issue where the customer was receiving an error that said 'FhirOperationException: Request does not target a recognised FHIR profile' when submitting records to LFPSE on their live. [Hotfix 2023.R7.2 - 6 September 2023]
• We resolved an issue where the form designer did not display Person Affected LFPSE fields when LFPSE is enabled. [Hotfix 2023.R7.2 - 6 September 2023]
• We resolved an issue where the LFPSE field "How was the device not used when it should have been?" appeared without a trigger condition in the devices section, instead of only appearing when triggered by the value "device was used it should not have been" in the "How was the device used in what went wrong?" field in the "How was the device used in what went wrong?" field. [Hotfix 2023.R7.2 - 6 September 2023]
• We resolved an issue where the LFPSE field "How was the device used when it should not have been" was triggered inappropriately in the devices section, instead of only appearing when triggered by the value "device was used it should not have been". [Hotfix 2023.R7.2 - 6 September 2023]
• We resolved an issue that caused DCIQ to display an error when you clicked "Add Row" while attempting to batch update any record in Capture. [Hotfix 2023.R7.2 - 25 September 2023]
• Prior to this release, when a user updated a record and clicked 'Save', the loading popup would hang indefinitely and the user could not save their updates. We resolved this issue. [Hotfix 2023.R7.2 - 25 September 2023]
• Prior to this release, if a user created an incident and completed the "Are you reporting a patient safety event?" field, then edited the form to hide the field, then later edited the form to show the field again, sometimes the value in the field would be lost. We resolved this issue so there is no potential data loss. [Hotfix 2023.R7.2 - 25 September 2023]
• We resolved an issue to ensure LFPSE fields appear on the Contact form and form designer when you enable LFPSE. [Hotfix 2023.R7.2 - 25 September 2023]

• UK - A4 PDF
• US - Letter PDF

• Download CSV (DCIQ.2023.R6)
• Download CSV (DCIQ.2023.R5)

Enhancements and Changes

• When you report an LFPSE record, the form only displays the 'Estimate the patient's age' field in the 'Person Affected' section when you set 'What kind of event do you want to record' to 'Incident' or 'Outcome'.
• The field "Approximately what time did the incident happen?" is removed from the form and the RLDatix inc_time is sent to LFPSE as psims_precise_time.
• When you report an LFPSE record, the form only displays the 'What was the clinical outcome for the patient?'in the 'Person Affected' section when you set 'What kind of event do you want to record' to 'Incident'.
• When you report an LFPSE record, the form only displays the 'What is the patient's sex?' field in the 'Person Affected' section when you set 'What kind of event do you want to record' to 'Incident' or 'Outcome'.
• When you report an LFPSE record, the form only displays the 'To what extent was the patient physically harmed (including pain) in this incident?' in the 'Person Affected' section when you set 'What kind of event do you want to record' to 'Incident'.
• When you report an LFPSE record, the form only displays the ‘How much did the incident contribute to the outcome for the patient?' field in the 'Person Affected' section when you set 'What kind of event do you want to record' to 'Incident'.
• As of this release, the 'LFPSE Adverse Event Safety Challenge' section only appears on the incident form when the value "Radiotherapy event" is selected from the trigger question "Does the incident appear to relate to any of these known safety challenges?"
• As of this release, the 'LFPSE Adverse Event Agent' section only appears on the incident form when the value "Devices/Medication/Blood Products or IT" are selected from the trigger question "Which things were involved in what went wrong?"
• We updated the service and location tables in DCIQ and added the Language ID column, allowing the users of DCIQ reporting tool to filter the data by language.
• We created a new table 'Deleted_Data_Tracker' in the Yellowfin Reporting database that tracks Deleted Incident records. The table captures the deleted record's Id and the date and time that it was deleted.
• As of this release, ‘Is there imminent risk of severe harm of death?’ and ‘which groups of patients are at risk?’ fields do not display on the incident form when ‘Were patients involved in this event?’ has no value selected
• We updated the software framework for DCIQ to ensure the best quality support and to fix some minor timezone issues.
• Data extraction users only see the timestamped date and time options as the frequency for extractions.
• In Data Extraction, when you view a list of jobs, DCIQ displays the time and date a job was last executed. This allows you to accurately see the frequency of extracts, which is particularly helpful if you extract more than once a day.
• DCIQ now lists the date and time of data extraction jobs in the job listing name. This allows users to accurately gauge the frequency of extracts.
• Administrators can make non-mandatory LFPSE fields in contacts mandatory, allowing them to tailor the form to their oganisation's needs and improve the quality of the data collected through the form.
• DCIQ now allows you to make non-mandatory LFPSE fields mandatory in the Incidents form designer, allowing you to better tailor the form to your organisation's needs.
• When you create an action for a non-capture record, DCIQ automatically populates the services and locations from the record into the action. This helps maintain consistency between the record and the actions created for the record. DCIQ allows you to manually edit those prepopulated services and locations before you save the action.
• As of this release, the 'LFPSE Adverse Event Safety Challenge' section only appears on the incident form when the value "Radiotherapy event" is selected from the trigger question "Does the incident appear to relate to any of these known safety challenges?"
• As of this release, the 'LFPSE Adverse Event Agent' section only appears on the incident form when the value "Devices/Medication/Blood Products or IT" are selected from the trigger question "Which things were involved in what went wrong?"
• We updated the service and location tables in DCIQ and added the Language ID column, allowing the users of DCIQ reporting tool to filter the data by language.
• As of this release, ‘Is there imminent risk of severe harm of death?’ and ‘which groups of patients are at risk?’ fields do not display on the incident form when ‘Were patients involved in this event?’ has no value selected
• Data extraction users only see the timestamped date and time options as the frequency for extractions.
• DCIQ now lists the date and time of data extraction jobs in the job listing name. This allows users to accurately gauge the frequency of extracts.
• DCIQ now allows you to make non-mandatory LFPSE fields mandatory in the Incidents form designer, allowing you to better tailor the form to your organisation's needs.
• Administrators can map core INC coded fields to the following single-select LFPSE fields in order to configure how DCIQ automatically populates those LFPSE fields in the forms.
  Where did the incident happen?
  Which speciality does the incident relate to
  Which of these best describes your role
• DCIQ automatically populates single-set LFPSE drop-down fields, based on your organisation's configuration. This speeds up the process of filling in the form and reduces the risk of user error. DCIQ allows you to edit the automatically populated field.
• When you create an action for a non-capture record, DCIQ automatically populates the services and locations from the record into the action. This helps maintain consistency between the record and the actions created for the record. DCIQ allows you to manually edit those prepopulated services and locations before you save the action.
• The LFPSE auto population works as expected when the parent non-LFPSE fields are set to display as radio buttons or checkboxes instead of drop-down fields.
• Admins can now search through and sort the LFPSE auto-population table. This makes the table more user-friendly for editing and viewing combinations.
• Administrators can map core CON coded fields to the following single-select LFPSE Contact fields in order to configure how DCIQ automatically populates those LFPSE contact fields in the forms.
  What was the patient's sex
  What is the patient's self-identified ethnicity?
• DCIQ automatically populates multi-select LFPSE fields in forms based on the LFPSE auto-population configuration in Capture admin. This makes it faster and easier for end users to complete the form with fewer errors. The end user can edit the auto-populated fields if needed.
• Administrators can map core INC dropdown fields to the following multi-select LFPSE fields in order to configure how DCIQ automatically populates those LFPSE fields in forms.
  Which things were involved in what went wrong?
  Does the incident appear to relate to any of these known safety challenges?
  Which service areas were involved?
  What kind of medical device was involved in what went wrong?
  Which of the following were involved? (LFPSE - Adverse Event Problem Buildings Infrastructure)
  Which of the following were involved? (LFPSE - Adverse Event Problem Estates Services)
  Which of the following are you recording?
  What type of risk to patient safety are you recording?
  Where was the risk identified? / Which organisation was the risk identified in?
  Which service areas are at risk?
• Administrators can map core INC coded fields to the following single-select LFPSE fields in order to configure how DCIQ automatically populates those LFPSE fields in the forms.
  Where did the incident happen?
  Which speciality does the incident relate to
  ? Which of these best describes your role?
  Location and Service are not currently included in the types of fields you can map to LFPSE fields.
• DCIQ automatically populates single-set LFPSE drop-down fields, based on your organisation's configuration. This speeds up the process of filling in the form and reduces the risk of user error. DCIQ allows you to edit the automatically populated field.

Fixes

• We resolved an issue where duplicates of risk records were erroneously created and not accessible in the system. DCIQ now saves the risks correctly.
• We resolved an issue that caused an error the first time you click the email notification link generated from the RIB module.
• We resolved an issue with the display of the "Merge in Progress" percentage in Contact Merging.
• We resolved an issue that prevented DCIQ displaying the Contact ID of merged contacts in the exported excel after performing a contact merge.
• We resolved an issue that prevented DCIQ displaying the forename and surname of merged contacts in the Excel file you export before performing a contact merge.
• We resolved erratic, inconsistent performance issues in the non-capture audit tools. This fix prevents DCIQ timing out while loading results and displaying system errors when navigating between different sections of the tool.
• An issue where multiple duplicates of risk records were erroneously created and could not be accessed later is resolved. DCIQ now saves the risks correctly.
• We resolved an issue that prevented DCIQ from displaying the "Merge in Progress" percentage when you perform a contacts merge.
• We resolved an issue that prevented DCIQ displaying the Contact ID of merged contacts in the Excel file you export after performing a contact merge.
• We resolved an issue that prevented DCIQ displaying the forename and surname of merged contacts in the Excel file you export before performing a contact merge.
• We resolved erratic, inconsistent performance issues in the non-capture audit tools. This fix prevents DCIQ timing out while loading results and displaying system errors when navigating between different sections of the tool.
• We resolved an issue that caused DCIQ to save a snapshot of incidents every time you saved, resulting in poor performance.
• We resolved an issue that caused a system error when you complete and submit a 'No Person' incident.
• We resolved an issue that caused a system error when you attempted to open incident records with completed actions while "completed by" column is included in the action listing.
• We resolved an issue that occasionally caused an error message when you complete a 'Skin Integrity' incident.
• When you navigate to Capture > Feedback, DCIQ no longer hangs and fails to load.
• We resolved an issue that caused DCIQ to display a "404: Message Not Found" error when you enable ODS_CODES_ENABLED.
• Prior to this release, in the People Affected tab in Incidents or another Capture module, if you tried to save or alter a contact's ID Number Type through a linked data form, DCIQ did not save your changes. We resolved this issue.
• We resolved an issue that caused an error if you removed a value from the Source or Type fields in a safety alert. Now, if you remove one of the values, you can still reopen the safety alert.
• We resolved an issue that prevented you from accessing certain documents attached to records in the Incidents module.
• We resolved an issue that prevented you from searching for text fields that were "not null" using the function "==". This function now works as expected.
• We resolved an issue that prevented DCIQ from running a data extraction job at the selected one-time or hourly time.
• We resolved an issue that caused fields in the Contacts module to appear twice.
• Prior to this release, when you perform contact searching on lvl1 forms with CON_MATCH_CRITERIA and CON_PAS_CHK_FIELDS set, DCIQ returned an unfiltered list of contacts. We resolved this issue so that DCIQ returns the correct patient results for the criteria you use to search.
• We resolved an issue that caused DCIQ to discard your changes when you delete values from certain fields in a level 2 contact form.
• We resolved an issue that caused DCIQ to create a duplicate contact with a new contact ID when you matched to an existing contact in a new incident record and the ID field was not included on the L1 contact form.
• We resolved an issue that caused DCIQ to display the time of a job in UTC instead of your local time zone when you create or edit the job, even if you access data extraction in a different timezone.
• We resolved an issue that occasionally caused an error message when you complete a 'Skin Integrity' incident.
• We resolved an issue that caused DCIQ to display a "404: Message Not Found" error when you enable ODS_CODES_ENABLED.
• Prior to this release, in the People Affected tab in Incidents or another Capture module, if you tried to save or alter a contact's ID Number Type through a linked data form, DCIQ did not save your changes. We resolved this issue.
• We resolved an issue that prevented you from accessing certain documents attached to records in the Incidents module.
• We resolved an issue that prevented you from searching for text fields that were "not null" using the function "==". This function now works as expected.
• We resolved an issue that caused DCIQ to create a duplicate contact with a new contact ID when you matched to an existing contact in a new incident record.
• We resolved an issue that caused DCIQ to display the time of a job in UTC instead of your local time zone when you create or edit the job, even if you access data extraction in a different timezone.
• We resolved an issue that caused an error when Admins attempted to load the LFPSE Auto-population feature. This now works as expected.
• We've fixed an issue where the customer was receiving an error that said 'FhirOperationException: Request does not target a recognised FHIR profile' when submitting records to LFPSE on their live.
• We resolved an issue where the form designer did not display Person Affected LFPSE fields when LFPSE is enabled.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• The risk_snapshot table and all associated fields are now available in the ETL, allowing you to report on risk data. When you add or edit a risk review in DCIQ, the data is now available in the ETL. You can also populate the table with historical data using the data sync tool.
• All actions section within the action dashboard is now visible for all users without administrative permissions and will display all actions that the user has permission to access.
• In order to allow reporting on the different levels of the risk register hierarchy within the BI Tool, a new table has been added called "risk_register_hierarchy_flattened_level8"
• When “Enable copying of the source record’s locations and services to the linked action” is enabled in System configuration, the first added service to the source record on a non-capture module is pre-populated to the service field on the generated action record.
• When “Enable copying of the source record’s locations and services to the linked action” is enabled in System configuration, the first added location to the source record on a non-capture module is pre-populated to the location field on the generated action record.
• When you run a Data Extraction job, DCIQ displays a message while the synchronisation is in progress. When the synchronisation is complete, DCIQ displays the time of the last sync next to the action.
• The KO41 report now allows to to pull data from a calendar year, rather than just from a quarter.
• In the Investigations module, you can now generate documents from the connecting document merging service Ecteon in either PDF or .docx format. This allows you to produce documents that you can edit in Microsoft Word after you generate them.
• When “Enable copying of the source record’s locations and services to the linked action” is enabled in System configuration, the first add service to the source record on a capture module is pre-populated to the service field on the generated action record.
• When “Enable copying of the source record’s locations and services to the linked action” is enabled in System configuration, the first added location to the source record on a capture module is pre-populated to the location field on the generated action record.

Fixes

• We resolved an issue that caused an error when running a listing report that included medication fields.
• We resolved an issue that caused DCIQ to send risk submission notifications to all users instead of the relevant users for the risk.
• We resolved an issue that caused DCIQ to wipe the NRLS service mapping from a service when you activated or deactivated it.
• Prior to this release, when a reporter answers 'No' to the question "Is the reporter's assessment of whether this is a patient safety event correct?" in DIF2, it did not trigger the correct additional questions. We resolved this issue so that the question and responses work as intended.
• We resolved an issue that caused reports to split records into duplicate rows when you generate a CSV if the report contains multiple affected people.
• We resolved an issue that caused the contact listing to unexpectedly display the word 'Array' in the grid when a capture record has multiple linked contacts that include the 'ID Numbers' field as a column in the contact listing design.
• We resolved an issue that caused DCIQ to display saved queries as "-1" instead of "[Criteria saved against report]" in the report designer, which caused the filters to fail.
• Prior to this release, when you completed an Incident form and check "Report this incident anonymously?", the Notifications tab displayed an error under the Recipient Name column. We resolved this issue and now we display the correct Recipient Name.
• We resolved an issue that prevented you from using the search query<@today - value when searching in date fields
• We resolved an issue that prevented DCIQ from displaying the "total" when you export a payments listing report from the Claims module to Excel or PDF.
• We resolved an issue that prevented DCIQ from pulling services linked to actions through to listing design, which affected data being pulled through to reports.
• We resolved an issue that caused the listing design to display the user ID number in the "Completed By (Actions)" field instead of the user name.
• Prior to this release, when you included user defined sections in a contact form with mandatory fields included, DCIQ enforced mandatory fields when they were not necessary. We resolved this issue.
• Prior to this release, the character limits in Carlton and Capture for Action Plans was not consistent, and only Capture displayed an error message. We resolved this issue to make them more consistent.
• Prior to this release, when you made changes to the default level 2 form, then made a copy of the form, DCIQ did not copy the changes into the new form. We resolved this issue.
• Prior to this release, in the DCIQ BI Tool, the Status column only displayed 0 instead of the correct value for the status of the control in DCIQ. We resolved this issue so that the column displays the correct value.
• We resolved an issue that prevented users from editing the field and/or section action trigger values to location and service fields in Capture Form Designer.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• DCIQ allows you to extract all UDFs simultaneously in a Data Extraction job.
• When you report on users or groups in the DCIQ BI Tool, the reports contain the correct risk registers configuration data from DCIQ, which allows you to produce accurate results.
• Customisations made on the non-capture Contact form are now available to report in the DCIQ BI Tool.
• Capture users can upload multiple files using the 'Browse files' button in the Drag and Drop feature, making it faster to attach and upload files.
• When utilising the drag and drop feature, DCIQ displays the useful information to inform users of the status of the files being uploaded; progress, success and failure of uploads. Error messages are also displayed if a user attempts to navigate away from a record before file(s) have uploaded, or save a record before the files have finished uploading.
• DCIQ allows level 2 capture users to drag-and-drop multiple files onto a record in one go using the new Drag and Drop zone. Files from desktop outlook can also be dragged and uploaded when using Edge or Chrome browsers, but not Mozilla Firefox as they do not currently support it. The 'browse files' button in this new feature can also be used to select and upload multiple files at a time.
• DCIQ allows level 1 capture users to drag-and-drop multiple files onto a record in one go using the new Drag and Drop zone. Files from desktop outlook can also be dragged and uploaded when using Edge or Chrome browsers, but not Mozilla Firefox as they do not currently support it. The 'browse files' button in this new feature can also be used to select and upload multiple files at a time.
• The tables feedback_medications_link, feedback_link_medication_administered, feedback_link_medication_intended are now available in the DCIQ BI Tool.
• When you add, update or delete data in Capture Admin's Public holidays, those changes are then available in the DCIQ BI Tool.
• DCIQ allows you to extract medications linked to feedback records using the Data Extraction functionality.

Fixes

• We resolved a discrepancy in the behaviour of injury mapping in the INC1 and INC2 forms. In both forms, you can now add and remove injuries by clicking the affected body part on the injury map.
• When you search for RIBs by location, DCIQ now shows results from both the location you are searching in and any child locations.
• We resolved an issue that caused DCIQ to add 10 hours to the time you selected in the "Time completed PRA or Safety Check submitted to CE" field in an RIB record.
• We reworded the field "Has Clinical Disclosure been initiated?" to "Has Clinician Disclosure been initiated?” so the label of the field is clearer and more descriptive.
• As of this fix, if a person has no value in the field "Has Clinician Disclosure been initiated", the PDF report now shows a blank value instead of 'No'.
• We resolved an issue that caused DCIQ to make a finalised RIB record editable if you changed the status to Submitted but did not yet save the changes.
• Prior to this release, if you edited a RIB record and added new information to the Details panel, then navigated to another panel and back, DCIQ did not display the additional information until you refresh the page. We resolved this issue so that DCIQ displays the correct information.
• We resolved erratic, inconsistent performance issues in the non-capture audit tools. This fix prevents DCIQ timing out while loading results and displaying system errors when navigating between different sections of the tool.
• The following header is required to be added to the contact integration- Bypass-Validation: 1. This will allow form validation to be bypassed so values from fields which aren't active on the current contact form can be submitted without receiving a validation error.
• We resolved an issue that was preventing saving person affected contact details on an incident record.
• We resolved an issue that prevented you from changing or deleting a Section or Field action after creating them.
• We resolved an issue that caused DCIQ to intermittently time out.
• An issue where opened date was equating to the reported date, when viewing an incident that was submitted using logged-out form is now resolved.
• We resolved an issue that prevented you from saving data in an extra field added to the Users form via Capture admin.
• We resolved an issue that prevented batch updating an empty extra field with a new value.
• Prior to this release, when external contacts lookup was enabled and a user searched for a contact but found no match, the search dialogue did not display the "No matching contacts found" message. We have resolved this issue so the message now appears.
• We resolved an issue where the User Group drop-down went missing from the filter in Users dashboard.
• An issue where the reference number would go missing on a listing report when the record is moved from 'In Holding Area, Awaiting Review' to 'Being Reviewed' while the inc_ourref field is hidden from the L2 Incident form is now resolved.
• The error with listing reports containing both the Date Received and Acknowledgement time on Person providing feedback sub form is now resolved. Now a report can be created with no errors
• When saving a level 2 incident without completing the risk grading field when set as mandatory, DCIQ prevented you from saving the form without highlighting the missed field. We resolved this issue to make it clear which field is preventing you from saving the form.
• An issue where filtering of risks by Risk Status returned no results has been resolved. Now DCIQ displays the correct results for this filter.
• We resolved an issue that caused DCIQ to display the field labels incorrectly when setting up a new listing report on the Medications form.
• The system error thrown when attempting to batch delete records and their associated documents in Redress is now resolved. We resolved this issue so you can delete records as usual.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• We resolved an issue that was preventing saving person affected contact details on an incident record.
• We resolved an issue that prevented extra fields in BI reports not updating on newer records during synchronisation.
• We resolved an issue that caused DCIQ to wipe the NRLS service mapping from a service when you activated or deactivated it.
• Prior to this release, if you deleted a location or service from a person's account, DCIQ still displayed the location or service in the Capture Settings in the person's account. We resolved this issue so DCIQ removes the location or service when you delete it.
• We resolved an issue that caused dates on a listing report to appear in the wrong format when you exported them to Excel. We resolved an issue that caused descriptions and text fields on a listing report to lose their formatting when you exported them to Excel.
• Prior to this release, the "Type Of Error" field that usually appeared under "Stage At Which The Error Occurred" did not appear on Level 1 or Level 2 forms. We resolved the issue so the field appears in the correct place. When users are adding medications, the ‘Type of Error’ field is normally under the ‘Stage at which the error occurred’ field. The ‘Type of Error’ field is now missing from both the L1 and L2 forms.
• We resolved an issue that prevented you from saving a contact after performing a contact match.
• Data Extraction will use the user's language preference from DCIQ instead of having it's own language setting.
• DCIQ allows you to merge the details of any organisation associated with a record. This allows you to create document templates with the required information to easily notify local authorities.
• The DCIQ BI Reporting Tool now contains the sec_staff_group table which can be added to a view in order to assist in reporting on the Security Groups assigned to users in Capture
• DCIQ displays the automatically generated ID for safety alerts on the front end, which allows you to uniquely identify the safety alert.
• DCIQ allows admins to specify the registers that a user is permitted to submit a risk to with the new configuration setting on user's and the group's page. This will ensure that risks are submitted to appropriate registers.
• DCIQ allows you to merge the role, contact number, contact email of a linked organisation using merge codes <<org_role>>, <<org_tel1>>, <<org_tel2>, <<org_email>>. This allows you to create document templates with the required information to easily notify local authorities.
• A new flat table called 'risk_udf_flattened_uk' is available in ETL for the Risk Extra Fields. This is to provide users with greater performance than using the existing 'risk_udf_flattened' table with calculated fields.
• DCIQ allows you to merge all linked injury and body part pairings, rather than just the first injury and body type. This makes it easier to create document templates that include the required information to notify local authorities. The new merge codes are <<inc_injury selected:x>> and <<inc_bodypart selected:x>> where x=1+, 1 being the 1st non-primary injury and body part
• DCIQ displays the automatically generated contact ID on the contact form, which makes it easier to see the ID of the contact you are viewing.
• DCIQ allows you to create custom fields for Contacts in in field maintenance and add them to non-capture Contacts form, allowing you to capture whatever data your organisation requires.
• A new flat table called 'incident_udf_flattened_uk' is available in ETL for the Incident Extra Fields. This is to provide users with greater performance than using the existing 'incident_udf_flattened' table with calculated fields.
• Key DCIQ contacts data is now available in Yellowfin in a new table called "contacts_flat", which allows admins and other users to generate reports
• The DCIQ BI Reporting Tool now contains the sec_groups table which can be added to a view in order to report on the Security Groups assigned to users in Capture

Fixes

• We resolved an issue that caused dates on a listing report to appear in the wrong format when you exported them to Excel. We resolved an issue that caused descriptions and text fields to lose their formatting when you exported them to Excel.
• We resolved an issue that prevented you from saving a contact after performing a contact match.
• We resolved an issue that allowed users without the correct permissions to view and modify the Admin module.
• We resolved an issue that prevented admins from adding new locations or amending existing locations.
• An issue where contacts added via integration are not available to be selected during contact searching and matching is now fixed. Contacts added to the system via integration can now be selected from the list of results in contact matching
• When clicking the "Sync field labels" button under Data Extraction configuration, an error message was shown and extra field information was not being updated on the job page. This has been improved so that extra field information will now be updated correctly, though an error message may still be displayed if the process takes longer than 60 seconds. This message can be ignored and will be removed in future.
• Prior to this release, when you updated the colour scheme for a statistical report, DCIQ did not save the new colour scheme, and showed the old colour scheme when a report was run. We resolved this issue so DCIQ saves amended colour schemes when statistical reports are run.
• We resolved an issue in the Feedback module, where the Holding 1 Date field within the complainant chain was not pulling data through to Listing Reports. This field now pulls data through, as expected when Listing Reports are run.
• An issue where relabelled field names in the "Person Providing Feedback Chain" section of feedback module were only taking effect in the form and not in the Reports administration area is now fixed.

Release Notes

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• We resolved an issue that caused DCIQ to lose NRLS location mappings after each release. As of this release, DCIQ will retain location mappings.
• We resolved an issue that prevented users from accessing Capture Admin through the System Admin.
• We resolved an issue that prevented DCIQ from displaying the contact names of users when you merged templates. Now when you merge templates, DCIQ displays the contact names correctly.
• In the DCIQ BI reporting tool, it is now possible to include the Risk Reviewer Name in an ERM view in order to include it in reports.
• A custom designed contact form in non-Capture can be set as default to appear in risk view forms and the contacts form in the contacts module.
• When you create a document using the document template merge functionality, DCIQ allows you to select a specific ID number type. If a contact with multiple contact ID number types is linked to the record, the document displays the specific ID number type you selected. This allows you to create more precise documents.
• Data Extraction Job start times now displays the current system time, and will show the UTC offset time in brackets.
• DCIQ allows administrators to create new non-capture Contact forms and perform standard customisations on it such as label the form, create sections, hide fields, make them mandatory, move them to different sections, add triggers etc.
• DCIQ allows you to extract actions linked to ERM records in both JSON and CSV formats.
• DCIQ allows you to extract actions linked to safeguarding records in both JSON and CSV formats.
• It is now possible to execute a data extraction job that includes actions linked to redress records. This can be in json or csv format.
• DCIQ allows you to extract actions linked to mortality review records in both JSON and CSV formats.
• DCIQ users with access to the BI Tool can create a new table in Pyspark by copying an existing table from Capture. The data in the Pyspark table will automatically update reflecting any changes made to the table data in DCIQ Capture.
• DCIQ allows admin users to amend the panels in form designer. The customisations will be applied to both risk report and risk edit forms.
• Users now have the ability to report on 'Notes' for the ERM and Investigations module in both DCIQ and Yellowfin
• Data from the Claims module is now available in the BI Tool, allowing users to report on this.
• Location, service and actions data from the Feedback module is now available for generating reports within the BI Tool.
• In the BI Tool, we added the ability to translate the values selected in some of the coded fields to the user-friendly descriptions by adding the relevant tables in the ETL
• In the DCIQ BI Reporting Tool, it is now possible to add fields from the "Healthcare Commission" section in the Feedback module so that these fields can be included in reports.
• It is now possible for Administrators with access to report on Mortality data within the BI Tool.

Fixes

• When newly created contact records from Capture are updated in the Contacts module, the changes are incorrectly not reflected on the linked contact when viewing from the Capture record. This has now been fixed.
• We resolved an issue that caused DCIQ to display the person's first name twice, instead of the first name and surname, in the Staff And Contacts Attached To This Record field in the Communication & Feedback section. DCIQ now displays the person's first name and surname correctly in this section.
• We resolved an issue that caused DCIQ to send emails that should go to linked users in the communication and feedback section to the wrong people.
• We resolved an issue that caused DCIQ to lose data from string fields when you check for matching contacts or approve a contact from within the incident record.
• We resolved an issue that caused fields in the Contacts module to appear twice.
• Prior to this release, when you ran the resync utility from the Carlton API container, the app displayed a success message but did not complete the task. We resolved the issue so that the resync no longer fails.
• An issue where a daily incident extract was not outputting any data and an issue with the 'From Date' not allowing selections of the most recent dates are now fixed.
• We resolved an issue that prevented you from searching by a date field in the incidents module.
• We resolved an issue that prevented DCIQ from sending ERM notifications to users.
• We resolved an issue that prevented DCIQ from displaying certain patients' details when you search for the patient via level 2 external contact matching.
• We resolved an issue that prevented users from exporting the NRLS report from the Capture module.
• There was an issue where the start date for the Non-Capture audit log was defaulting to a specific date. This resulted in an unhelpful pagination, affecting the ability to view the audit log as intended. This has been resolved.
• We resolved an issue that caused the dashboard to hang indefinitely when you saved a new report or changed the report type.
• We resolved an issue where 'server unable to complete request' error prevented access to certain risks when using the filter.
• An issue where Body Part (Primary) is displayed as 'array' on Contacts listing on level2 Incidents form is resolved.
• We resolved an issue that prevented non-admin users from assigning action plans, even if they have the correct ACL rules.
• We resolved an issue that caused an error when an ETL resynchronisation was performed; this can now be conducted without issue.
• Prior to this release, when you filtered the risk register by category, then selected a risk, DCIQ removed the filter and displayed all results. We resolved this issue so DCIQ only displays the filtered results.
• Prior to this release, in the Feedback module, users were unable to type more than 255 characters in the Ombudsman Learning field, even if there was no character limit set within form design. We resolved this issue so that if there is no character limit set on the form, you can type any number of characters in the field.
• Issues with search bar displaying the HTML formatting when bold or underline is used, and when hovering over those fields, the tooltip did not appear. We resolved both of these issues.
• An issue where blank values are displayed for extra fields in contact matching listing design is now fixed.
• We resolved an issue that prevented you from deleting codes from Number Type in the Contacts section of Field Maintenance.
• There was an issue within the Reportable Incident Brief module where the pagination and navigation buttons were not displaying for lists of records, thus preventing users from moving between records. This has now been resolved and the expected navigation buttons appear, as well as page numbers for users to select.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• It is now possible to generate DES reports for standard and UDF data within the Claims module. These can be extracted in json and csv formats and will not cause performance issues.
• It is now possible to generate DES reports for standard and UDF data within the Safeguarding module. These can be extracted in json and csv formats and will not cause performance issues.
• The DCIQ BI Reporting Tool now contains the code_com_issue_type_descr table which can be added to a view to allow reporting on the friendly values for the "Issue Type" field related to Subjects in the Feedback module
• Users with the ability to save and schedule data extraction jobs can now extract actions linked to a claim. These can be extracted in both json and csv format.
• In System Admin, the Data Syncing panel displays the ETL Syncing tool. The tool allows system administrators to begin an ETL sync job, view the status of ongoing sync jobs and view previous sync jobs. This function is set behind an environment variable.
• Data extraction jobs for the Enterprise Risk Manager which include location and services will now extract the full nodes of the locations and services, as well as the ID and description of the node. Each node is extracted in order and there is a clear indication as to which tier the node belongs to within its hierarchy.
• A new table called safety_learning_udf_flattened is available in the BI reporting tools to assist with improved reporting on safety learning extra fields
• Users with the ability to save and schedule data extraction jobs can now extract actions linked to a Feedback record. These can be extracted in both json and csv formats.
• Data extraction users can now select up to 200 user defined fields (UDFs) to include in a job, instead of all possible UDFs. If a user attempts to select more than 200, a warning message is displayed.
• System administrators can now manually trigger sync ETL with specific tables in Capture and Carlton. This will help to prevent data issues and allow administrators to maintain the system's integrity.
• Yellowfin now contains flattened tables of user service data that updates hourly. The table allows administrators to update services assigned to users in DCIQ and to update the labels of service values assigned to users.
• DCIQ Administrators can now delete Risk Trackers via the Risk Tracker listing page, and within individual Risk Trackers themselves. Deletion of Risk Trackers is audited in the Non Capture audit log.
• We added the location_tag, location_tag_descr, and location_tag_links triggers to tables in DCIQ. This means that location tag data from DCIQ is available for use in Yellowfin and DES.
• The BI reporting tool now includes a table of holidays which displays the name and date of public holidays, so that these can be taken into account in the date calculation.
• DCIQ sends a notification email to users who have been assigned as risk owner for a risk record. If the user assigns oneself as a risk owner, then the user will not receive a notification. The notification email can be customised in the Notification centre.
• The Capture Dashboard now loads a maximum of three reports at a time to avoid errors while loading due to large data.

Fixes

• We resolved an issue that meant 'Action completed date' is not updated for an action which is reopened after closing it. As of this release, if an action is not in a completed status it will not have a completed date
• There was an issue wherein if DCIQ system is configured for external lookup, then searched for an external patient, an error is displayed. We resolved this issue so that the Capture form is populated automatically with the contact details.
• Prior to this release, when you completed an injury form and set 'Was the person injured in the incident?' to Yes, when you saved the form, DCIQ changed the value from Yes to 1. When you re-opened the form, the injury details are not retained. This issue is now resolved.
• An error was observed when adding a new incident with notifier and person affected contact with marital status code of more than 2 characters. We resolved this issue so that when you complete the form with marital status, DCIQ creates the incident.
• We resolved an issue that prevented permissioned users from creating statistical reports.
• We resolved an issue that prevented you from deleting values from the Number Type dropdown. Previously, if you navigated to System Admin > Field Maintenance, selected Contacts, then selected Number Type, when you tried to delete a value, DCIQ displayed an error. Now you can delete the values.
• We resolved an issue that prevented the users from creating statistical reports.
• Previously, Access Control List (ACL) logic for notifications parses users tied to default Enterprise Risk Manager (ERM) Rules. Any users who had the "Deny ERM" ACL Rule would receive email notifications for newly created risks they did not have access to. The expectation is that they should not receive these notifications. These emails did not allow them access to any records they should not. This has now been resolved.
• Prior to this release, if you tried to create a bar chart report for the Insurer field in Claims, DCIQ did not display the Insurer field. We resolved this issue so you can now select Insurer field and generate the bar chart report.
• Sometimes, when you logged a safeguarding incident and selected the Adult category, DCIQ also displayed the Children category. We resolved this issue so that DCIQ only triggers the correct category when you log a safeguarding incident.
• Prior to this release, the incident search form did not display the Route Administered field in the medications section. We resolved this issue so that the form displays the field.
• Previously, when you generated an NRLS export file, if there were multiple errors, DCIQ only displayed two or three errors at a time. This meant you had to generate the export repeatedly to view and resolve all of the errors. We resolved this issue so that DCIQ displays all of the errors together, so that you can resolve all of the issues without regenerating the export file.
• There was an issue with logged in Level 1 Feedback and Claims forms, where unapproved or rejected contacts were being returned in contact matching results. This has been resolved.

• A4 PDF
• Letter PDF

• Download CSV

Enhancements and Changes

Fixes

• A4 PDF
• Letter PDF

• Download CSV

Enhancements and Changes

Fixes

• A4 PDF
• Letter PDF

• Download CSV

Enhancements and Changes

• Data Extraction Administrators are able to report on incident extra field data within Data Extraction successfully. They will also be able to generate these reports without experiencing performance issues.
• In the BI reporting Tool, there is a new table called "action_udf_flattened" which allows extra fields to included in reports. This can be conducted without performance issues.
• Enterprise Risk Manager administrators are able to configure whether Contributory Factors can be included or excluded from Risk Forms. When Contributory Factors are included, it will be displayed in the Controls and Assurances panel of the Risk Form.
• A new table called mortality_udf_flattened is available in the BI reporting tools to assist with improved reporting on mortality extra fields
• A new table called incident_udf_flattened is available in the BI reporting tools to assist with improved reporting on incident extra fields

Fixes

• Previously, users were unable to open and view responses for Safety Alerts as they were being presented with 'Resource not Found', despite having permissions which should allow them to view these. We have now resolved this issue and users are able to open and view Safety Alert responses, as expected.
• There was an issue where when searching for Location(s), those that started with a lowercase letter were not being sorted alpha-numerically with the rest of the Locations list, instead being inserted into the list in an apparent random location. This has been resolved.
• There was an issue with NRLS Reporting, where the system was not generating the .xml file. The progress was hanging at 0%, and after a while a "200 SyntaxError: Unexpected token <in JSON at position 0" error message was being returned. This has been resolved.
• There was an issue in the Feedback module, where DCIQ was not sending notifications to users defined by their security groups who had Locations and/or Services that matched that of the reported feedback. This has been resolved.
• There was an issue in the Feedback module where, in the Complainant chain, the "Holding 2" date was not saving correctly. When selecting "Add Holding Letter" and entering a date, upon saving the record, the date would save as 01/01/1970, instead of what was entered. This was an intermittent issue, but has now been resolved.
• There was an issue where, if a contact listing page was designed so that the ID Number Type displayed after the ID Number, the ID Number Types would not populate despite having a value. This has been resolved, and now ID Number Types will populate regardless of the contact listing page design.
• There was an issue with Listing Report Templates, where any apostrophes in the name of the template were not being displayed correctly when that template was used in designing a report. This has been resolved.
• There was an issue with Listing Reports where when designing one, if a field was clicked on but not selected, it was still being added to the report regardless. This has been resolved.
• There was an issue where when merging contacts, the approval status for those contacts would temporarily become out of sync between Capture and non-Capture, leaving duplicate contacts within the application. This has been resolved and now data between Capture and Non-Capture contacts are synced, thus allowing duplicates to merge successfully.
• There was an issue where attempting to access the Dashboard module (Capture menu > Dashboard) was returning a ‘A system error has occurred’ error message, and users could not access the module. This has been resolved.
• There was an issue where the Sub-Type field was not being found under the Equipment section of a New Incident form, when it should have been. This has been resolved.
• There was an issue where the URL link in a Safety Alerts email pointed to a Safety Learning instead of a Safety Alert. Upon clicking the link, it would redirect the user to the splash page if the Safety Learnings module was not licensed. This has been resolved and the email link now takes the user to the expected Safety Alert.
• There was an issue where designing a Bar Chart or Line Graph that had a user defined field as 'field one' was not pulling data through to the report, and instead was returning an "Invalid data" message. This has been resolved.
• There was an issue where the reference field "Ref" on any Capture module level 2 form was not being populated, meaning the field could not be reported on. This has been resolved.
• There was an issue where performing a Risk Review on a Risk that had any actions linked to it, the reviewer was unable to view the actions due to the hyperlinks being non-responsive. This has been resolved.
• There was an issue where DCIQ systems using the Microsoft Azure Single-Sign On service was preventing certain users from logging into DCIQ if they had another Azure service open in another browser tab. This has been resolved.
• There was an issue where some Risks were unable to be deleted, leading to a technical error occurring. Access to other Risks was then forbidden. This has been resolved.
• There was an issue where attempting to link an Action form other than the default to the action section of any other Capture form design would not take effect, and the action section would only use the default action form. This has been resolved.
• There was an issue with the Data Extraction Service where some User Defined Fields were not being pulled through. This has been resolved.
• There was an issue where users were not able to view active Actions in their To Do List and attempting to view was returning an error message. This has been resolved.
• There was an issue where it was not possible to select the Safeguarding module as the module to view upon logging in. This has been resolved.
• There was an issue specific to the SPSC Feedback API, where the API to send updated messages was not sending said messages. This has been resolved.
• There was an issue with the Communication and Feedback emails that can be sent to recipients associated with non-Capture module records, where it was
  possible to only add one recipient when multiple recipients should have been allowed. This has been resolved, and now multiple recipients can be added to Communication and Feedback emails.
• There was an issue with Fishbone Diagrams, where if they were ticked as "Contributory Factors", the nodes were not appearing in the Contributory Factors section. This has been resolved.
• There was an issue where when accessing the To Do List, a ''There has been an error retrieving data. Records from the following module(s) may not be visible: ERM'' error message was being displayed. This was occurring for customers who did not have access to the ERM module. This has been resolved, and no error will appear for modules that are not accessible in the system.

• A4 PDF
• Letter PDF

• Download CSV

Important Information

As part of our ongoing efforts to help you protect your data, we have conducted a review of the contact matching functionality in DCIQ. Our recommendation has always been that contact matching should be made available only to logged in users. We have now added some advisory messages to the administrative areas of the application to help administrators identify whether there are any configuration settings that they might need to review. We have also added additional guidance to the help file providing more details on how to ensure your chosen configuration of DCIQ is as secure as possible. We will continue to expand this guidance in future releases.

If you are seeing a warning message and unsure what it means, or if you have any concerns about whether you need to make changes to your application configuration, our Customer Success team are happy to advise.

Enhancements and Changes

• Data Extraction Administrators are able to report on incident extra field data within Data Extraction successfully. They will also be able to generate these reports without experiencing performance issues.
• A new table called action_udf_flattened is available in the BI reporting tools to assist with improved reporting on action extra fields
• Enterprise Risk Manager administrators are able to configure whether Contributory Factors can should be included or excluded from Risk Forms. When Contributory Factors are included, it will be displayed in the Controls and Assurances panel of the Risk Form.
• A new table called mortality_udf_flattened is available in the BI reporting tools to assist with improved reporting on mortality extra fields
• A new table called incident_udf_flattened is available in the BI reporting tools to assist with improved reporting on incident extra fields
• It is now possible to access the BI Tool from DCIQ via the Single Sign-On (SSO) without any errors. It is only possible for the SSO to work where a unique email address is used within DCIQ. If multiple users are using the same email address, this will not work.

Fixes

• There was an issue where when searching for Location(s), those that started with a lowercase letter were not being sorted alpha-numerically with the rest of the Locations list, instead being inserted into the list in an apparent random location. This has been resolved.
• There was an issue with NRLS Reporting, where the system was not generating the .xml file. The progress was hanging at 0%, and after a while a "200 SyntaxError: Unexpected token <in JSON at position 0" error message was being returned. This has been resolved.
• There was an issue in the Feedback module, where DCIQ was not sending notifications to users defined by their security groups who had Locations and/or Services that matched that of the reported feedback. This has been resolved.
• There was an issue in the Feedback module where, in the Complainant chain, the "Holding 2" date was not saving correctly. When selecting "Add Holding Letter" and entering a date, upon saving the record, the date would save as 01/01/1970, instead of what was entered. This was an intermittent issue, but has now been resolved.
• There was an issue where, if a contact listing page was designed so that the ID Number Type displayed after the ID Number, the ID Number Types would not populate despite having a value. This has been resolved, and now ID Number Types will populate regardless of the contact listing page design.
• There was an issue with Listing Report Templates, where any apostrophes in the name of the template were not being displayed correctly when that template was used in designing a report. This has been resolved.
• There was an issue with Listing Reports where when designing one, if a field was clicked on but not selected, it was still being added to the report regardless. This has been resolved.
• There was an issue where when merging contacts, the approval status for those contacts would temporarily become out of sync between Capture and non-Capture, leaving duplicate contacts within the application. This has been resolved and now data between Capture and Non-Capture contacts are synced, thus allowing duplicates to merge successfully.
• There was an issue where attempting to access the Dashboard module (Capture menu > Dashboard) was returning a ‘A system error has occurred’ error message, and users could not access the module. This has been resolved.
• There was an issue where the Sub-Type field was not being found under the Equipment section of a New Incident form, when it should have been. This has been resolved.
• There was an issue where the URL link in a Safety Alerts email pointed to a Safety Learning instead of a Safety Alert. Upon clicking the link, it would redirect the user to the splash page if the Safety Learnings module was not licensed. This has been resolved and the email link now takes the user to the expected Safety Alert.
• There was an issue where designing a Bar Chart or Line Graph that had a user defined field as 'field one' was not pulling data through to the report, and instead was returning an "Invalid data" message. This has been resolved.
• There was an issue where the reference field "Ref" on any Capture module level 2 form was not being populated, meaning the field could not be reported on. This has been resolved.
• There was an issue where performing a Risk Review on a Risk that had any actions linked to it, the reviewer was unable to view the actions due to the hyperlinks being non-responsive. This has been resolved.
• There was an issue where DCIQ systems using the Microsoft Azure Single-Sign On service was preventing certain users from logging into DCIQ if they had another Azure service open in another browser tab. This has been resolved.
• There was an issue where some Risks were unable to be deleted, leading to a technical error occurring. Access to other Risks was then forbidden. This has been resolved.
• There was an issue where attempting to link an Action form other than the default to the action section of any other Capture form design would not take effect, and the action section would only use the default action form. This has been resolved.
• There was an issue with the Data Extraction Service where some User Defined Fields were not being pulled through. This has been resolved.
• There was an issue where users were not able to view active Actions in their To Do List and attempting to view was returning an error message. This has been resolved.
• There was an issue where it was not possible to select the Safeguarding module as the module to view upon logging in. This has been resolved.
• There was an issue specific to the SPSC Feedback API, where the API to send updated messages was not sending said messages. This has been resolved.
• There was an issue with the Communication and Feedback emails that can be sent to recipients associated with non-Capture module records, where it was
  possible to only add one recipient when multiple recipients should have been allowed. This has been resolved, and now multiple recipients can be added to Communication and Feedback emails.
• There was an issue with Fishbone Diagrams, where if they were ticked as "Contributory Factors", the nodes were not appearing in the Contributory Factors section. This has been resolved.
• There was an issue where when accessing the To Do List, a ''There has been an error retrieving data. Records from the following module(s) may not be visible: ERM'' error message was being displayed. This was occurring for customers who did not have access to the ERM module. This has been resolved, and no error will appear for modules that are not accessible in the system.

• A4 PDF
• Letter PDF

Important Information

The PDF downloads listed as UK and US have been renamed to better reflect the differences in page size. UK is now A4 PDF and US is Letter PDF.

As part of this release, the Release Notes will not be split by Geography. The exception is for modules that are only available in certain geographical regions.

This page has been condensed down, and the earliest displayed is now version 2022.1. If you require the release notes for versions before 2022.1, please raise a ticket in SupportHUB.

• Download CSV

Enhancements and Changes

• Users who can edit the Risk Register Listing, via the Enterprise Risk Manager Admin section "Risk Register Listing", can include a count of Active Risks, Pending Risks and Inactive Risks.
• Users who can access the Risk Registers dashboard can filter the list of available Registers by Name, ID and/or Active or Inactive status.
  Filters can be used individually or in conjunction with one another.
  When using the Name filter, the results will consist of any Register that either contains part of the search criteria or matches the search criteria. This is dependent on any other search criteria that is defined.
• Users who have access to the Enterprise Risk Manager Admin can access the "Risk Register Listing" page, where they can configure the columns displayed in the Risk Register Dashboard. The following columns are available:
  ID (read-only, always active), Title (read-only, always active), Parent Registers, Active Risks, Inactive Risks, Pending Risks, and Register Status (Active/Inactive).
• In the Form Designer for a Risk Form, the Risk Grading Matrix has been relocated to the "Fields & Sections" area of the designer. Administrators who design Risk forms can add field information and field help, and move the Matrix within the form.
  Additionally, users submitting or updating a Risk record will be prompted to provide an Initial Risk rating, if one was not provided.
• The "Title" and "Description" fields when adding or editing a Clinical Measurement are no longer mandatory. This means the fields can be left empty when adding or editing a Clinical Measurement.
• In addition to the existing Clinical Measurement types, the following can be recorded:
  Blood Glucose (m/mol)
  Left and Right Pupil size (mm) and Reactiveness (Reactive/Non-Reactive)
  Capillary Refill (seconds)
  Pain Score (1-10)
  NEWS2 Score (1-7)
  ETCO2 (mmHg)
  ACVPU (Alert, Confusion, Voice, Pain, Unresponsive).
  All of the types except for ACVPU, and Left and Right Pupil Reactiveness are plotted on the Clinical Measurements graph.
• Clinical Measurements can be recorded to the minute and second. In the Clinical Measurements table, the time column(s) will be bundled into 5 minute intervals, with the value that was the most recent recorded measurement being displayed. Hovering over the value will display a tooltip containing all of the recorded measurements with an exact date and time for each.
  The Clinical Measurements graph has an x-axis set in 5 minute intervals, with the most recent recorded entry plotted on the graph. Hovering over a plot point will display a tooltip containing all of the recorded measurements with an exact date and time for each.
• Administrators of a system with a large location hierarchy will be able to view the same hierarchy in the BI Tool.
• If Mortality Review field labels have been edited in the Capture Admin field relabelling, these Mortality Review data fields in Data Extraction will be updated to reflect the changes. This applies to new and cloned extraction jobs. Any existing jobs will retain their field names.
• For systems with a large location hierarchy, there is now an improved performance to any changes made to the hierarchy. The application will have a better performance for systems that, for example, contain 15,000 locations in their hierarchy.

Fixes

• There was an issue where it was not possible to open Actions that were created by users who are deactivated. It was also not possible to search for any actions created by a now deactivated user, though the Action would still show as associated to a record. An error would display when trying to access these actions. This has been resolved.
• There was an issue where the system would automatically assign an Incident reporter as the handler for that record. This has been resolved and the handler field will remain empty.
• There was an issue with the Batch Update functionality, where attempting to batch update feedback records was returning "An unexpected error occurred whilst communicating with the database" error and thus failing to complete the task. This has been resolved.
• There was an issue in the Incident module where it was not possible for users with the correct Security Group Access Level to change Incidents from the "Rejected" approval status to any other status, as the approval field was read-only. This has been resolved.
• There was an issue where when a user attempted to link a record to a Risk in the Enterprise Risk Manager, they were receiving a "A technical error has occurred" message, and it appeared that the record was linked when it actually was not. This has been resolved.
• There was an issue in the Safeguarding module, where the heading at the top of a status listing was displaying "Sfgnames with status:" instead of Safeguarding referrals with status:". This has been resolved.
• There was an issue where users with Edit Access for All Actions were receiving a "A technical error occurred" error message when attempting to update any actions. This has been resolved.
• There was an issue where the NCDS mappings were not being retained. After being added, the mappings would disappear at an indeterminate point. This has been resolved and mappings will remain after save.
• There was an issue in the Safety Alerts "For Information Only" Distribution panel where the "Per Page" drop down value was not being respected. Instead, the full list of records was being shown. This has been resolved.
• There was an issue where when a user added a Location to a record and then proceeded to add a Service, they could bypass the Location-Services link by clicking the Search icon (magnifying glass). This meant they could select any service in the system. This has been resolved.
• There was an issue where when the Locations and Services was set as mandatory in the Actions form, attempting to add information to an existing form would result in a technical error message being displayed. The error message was also displayed when attempting to complete an Action linked to a Redress form. This has been resolved.
• There was an issue with the Action Module ACL rule "Read-only access to actions linked to other records". Instead of users having read-only access to actions linked to non-Capture records they have access to, they were unable to see any actions except for the ones assigned to them. This has been resolved.
• There was an issue with Contact Listing Pages that included the ID Number Type. The ID Number Type would remain unpopulated in Level 2 Capture records where the listing page was in use, regardless of whether an ID Number Type existed or not.
  Additionally, if a value existed for a Contact's Subtype, that value would populate the ID Number Type column in the Listing page.
  This has been resolved.
• An issue presented when users attempted to "Check for Matching Contacts" via the PAS interface, where they could see the results, but upon choosing the relevant contact they were receiving a 500 error. This has been resolved.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• Users of Yellowfin can now include the Investigations Fishbone Diagram data in its hierarchical structure down to four levels. The data is stored in the new table "investigations_fishbone_flattened_level4" and can be reported on.
• Administrators who can customise Enterprise Risk Manager Risk forms can specify if the "Services", "Locations" and "Controls in Place" panels are mandatory or not.
  In the Form Designer "Form Panel" section, for a Risk Form, the Services and Locations can be set as mandatory fields together by checking the "Services & Locations" checkbox. Defining if the "Controls in Place" panel is mandatory or not is done by checking the "Controls & Assurances" checkbox.
  This will be applied to any new Risks that are reported. Editing any existing Risks will not have any form changes applied to them.
• Users who can edit Risk Listings, via the Enterprise Risk Manager Admin section "Risk Listing", can include a "Last Reviewed By" column. This will display the full name of the user who performed the last Risk Review.
• Users who can edit Risk Listings, via the Enterprise Risk Manager Admin section "Risk Listing", can include "Risk Owner", "Last risk review date" and "Last risk updated date" columns.
  "Risk Owner" will display all owners of a Risk. "Last risk review date" and "Last risk updated date" will display a date and time of YYYY-MM-DD HH:mm:ss.
• Users who can view Risks are able to filter the "My Risks" listing by Risk Owner.
  Users can search for Risk Owner by forename and/or surname and then select either a singular result or multiple results to filter on, based on the results returned from the Risk Owner search. Filtering will then return all the Risks for all of the Risk Owners specified.
  This filtering can be done in conjunction with other filtering criteria.
• Users who can view Risks are able to filter the "My Risks" listing by Initial, Current and Target Risk Grading. Filtering can be done on either one of the Risk Gradings, or a combination of the three.
  Filtering is done by searching between a minimum and maximum value. The maximum value that can be entered in the maximum field is 25. Filtering by any of these Risk Gradings will return all risks that fall within the ranges specified. If the minimum field is left empty, the field will default to a value of 1. If the maximum field is left empty, the field will default to a value of 25.
  This filtering can be done in conjunction with other filtering criteria.
• The historical Risk Review listing on a Risk record now shows the name of the user who performed the Risk Review.
• Users who can edit Risks can now modify historical Risk Reviews for a Risk via the Actions tab. This is applicable to open Risks. Any saved changes can be viewed in the System Admin Main Audit.
• Users who can edit Risk records and can view the listing of historical Risk Reviews are able to delete Risk Reviews from the Actions dropdown.
• There is a new configuration option in the Enterprise Risk Manager admin, "Enforce Risk Review on Risk closure", that will force a user to perform a Risk Review if a Risk is being closed.
• The Enterprise Risk Manager Risk Form fields "Closed Risk Date" and "Reason for Closure" are only displayed when viewing a closed Risk. These fields are hidden when reporting a Risk or viewing/editing an open Risk.
• Users who can close Risks, either via a Risk or Risk Review, will be asked to provide a reason for the closure and a closed date. Both of these are mandatory.
  Be aware that manually setting the fields "Closed Date" and "Reason for Closing" as mandatory in the System Admin Form Designer is not a recommended configuration as it will result in system errors.
• Clinical Measurements that are a part of an Investigation record can be deleted.
• The Enterprise Risk Manager field "Risk Owner" can be reported on in the BI Tool.
• In the Data Extraction Service, there is a column for Job ID in the Job List and Downloads tables.
• For any attachments, documents or templates that are missing, there is an indicator to inform the user that a file is missing. Administrators who can access the Capture Admin are able to view and resolve missing documents via the "Missing Documents" section. This is a new section to the Capture Admin. For missing templates, administrators can view and resolve these via the "Document template administration".
  When reuploading a document, the system requires the reuploaded document to have the same name as the original, otherwise the system will not accept the reuploaded document. If a document is missing and the name is unknown, the user can contact the RLDatix Support Desk with the document ID and they will be able to locate the original document name.
• There is a new panel that can be included in Enterprise Risk Manager Risk forms, called "Controls in Place". This is a part of the "Controls & Assurances" section.
  This panel is displayed by default in Risk forms and can be hidden by checking the "Hidden?" checkbox for "Controls & Assurances" in the Form Panels section of the Form Designer.
  This panel is used to add Controls when reporting a Risk. Users reporting a Risk are able to search for Controls by "Title" and "Summary” and can add as many Controls as required.
• The "Job Title" field in the Contacts module is now available to be included in views in the BI tool
• If Safeguarding field labels have been edited in the Capture Admin field relabelling, these Safeguarding data fields in Data Extraction will be updated to reflect the changes. This applies to new and cloned extraction jobs. Any existing jobs will retain their field names.
• If Redress field labels have been edited within Capture Admin, the new labels will reflect in new and cloned extraction jobs within Data Extraction Service. Any existing jobs will retain their original field names.
• If Feedback field labels have been edited in the Capture Admin field relabelling, these Feedback data fields in Data Extraction will be updated to reflect the changes. This applies to new and cloned extraction jobs. Any existing jobs will retain their field names.
• Users who can edit Risk records and/or perform Risk Reviews are able to edit the Initial Risk Grading in the Initial Risk Grading risk matrix.

Fixes

• There was an issue with Incident and Feedback forms where regardless of the language set in the field "What languages of this form would you like to edit?", the section labels for the chosen language would be reflected in the form output for other languages. This has been resolved, and the section labels for both logged in and logged out forms will always be displayed in the user's chosen language.
• There was an issue where the "Edit Feedback Chain History" option was displaying for all users in the Feedback dashboard when it should not have been. This was due to the system not respecting the associated global's default value of "N". This has been resolved, and unless the global is defined in the system with a value of "Y", the "Edit Feedback Chain History" option will not be displayed to users.
• There was an issue where any combo linking that had an Injury field as the parent field was not working as expected. The child field linked to an Injury parent field would not filter correctly when reporting an Incident. This has been resolved.
• There was an issue where Medication Notes that were added to either a new or existing Feedback record were not being saved. This has been resolved.
• There was an issue where when designing a Level 1 Feedback form, it was not possible to set any field in the "Subjects" section as a radio button. Attempting to do so would return a system error. This has been resolved.
• There was an issue where users who were manually locked out of the system were then unable to have this lock removed, thus they were unable to log into the system. This has been resolved.
• There was an issue where escalating or deescalating a risk was not updating in the Risk Register and the old value was being displayed. This has been resolved.
• There was an issue where the "Current Risk Grading" rating radio button was not being displayed when performing a Risk Review. Users had to perform a workaround, toggling between grading tabs, to force the radio button to appear. This has been resolved, and the "Current Risk Grading" rating radio button is displayed as expected when performing a Risk Review.
• There was an issue with CSV files created via the Data Extraction Service, where unexpected column or line breaks occurred for fields that either contained quotation marks (") that were not followed by another special character or started with a quotation mark. This has been resolved.
• There was an issue where changing either the "Pressure Sore" or "Medications" sections of the default INC1 form is applying the change to all other INC1 forms, only when viewing a form when logged in. Any changes made to a non-default INC1 form are not reflected when viewing that form when logged in. Viewing a form while logged out was displaying as expected. This has been resolved, and all forms all displaying as expected when logged in.
• There was an issue in the Enterprise Risk Manager where Overdue Risk Notifications were being sent out before the date set as the new review date. Also, Overdue emails were stating that a risk record was overdue by 1 day, even if the record was overdue by more than that. This has been resolved.
• There was an issue where changing the "Subject" section of the default Level 1 Feedback form is applying the change to all other Level 1 Feedback forms, only when viewing a form when logged in. Any changes made to a non-default Level 1 Feedback form are not reflected when viewing that form when logged in. Viewing a form while logged out was displaying as expected. This has been resolved, and all forms all displaying as expected when logged in.
• There was an issue where non-admin users were unable to generate pre-existing document templates within the Claims module. The template dropdown list would display a "No codes available" message instead of any templates. This only affected pre-existing templates. If a new template was added, that template was available for selection. This has been resolved, and all applicable document templates are available for selection in the template dropdown list.
• When performing a Risk Review, the “Objectives” section was visible, but never displayed any data despite Objectives being recorded against a Risk. Given that this section has never successfully worked during the risk review process, we have temporarily removed it to prevent user confusion. RLDatix will look to complete this functionality in a future release.
• There was an issue where users who did not have either the Admin or Reviewer Safety Learnings role were only able to vote on published Safety Learnings that shared their location. This has been resolved, and Published Safety Learnings can be voted on by all users in the system, regardless of their role or location.
• There was an issue in a Level 1 Incident form, where having a User Defined Section trigger a custom Contact form was not working as expected. Instead of the trigger displaying the custom Contact form, the system default Contact form was being displayed. This has been resolved.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Fixes

• When attempting to view the Audit Trail of a Capture record, the trail fails to display and the system returns a number of error messages. This has been resolved and capture record audit trails can now be viewed successfully.
• There was an issue where attempting to extract all Incident fields was failing in the Data Extraction Service. This has been resolved.
• There was an issue in the Capture Admin Email Audit where attempting to search was either returning no results or partial results. Currently, searching in this table is done on background data, not the exact data that is displayed in the table. To resolve this issue, the way data is presented in the table has been modified. Now there is a value in brackets after the main entry in the table, for example, Yes (1). This bracketed value is the searchable value, and the search functionality will perform as expected. This change has also been applied to the Capture Admin Full Audit table.
  In a future release, an update will be made to the search functionality so it is performed on the data displayed in the table, not the background data. The bracketed value will then be removed.
• There was an issue where Contact forms linked to a Capture form was not allowing a logged in Reporter to complete any empty coded fields such as Gender or Subtype. Logged in Reporters were also unable to respond to any coded field that was added as an extra field. The Contact form worked as expected for a logged out Reporter. This has been resolved and linked Contact forms work as intended for both logged in and logged out Reporters.
• There was an issue with DIF1 Incident forms where an NHS Number that had been added to a 'Person Affected' link was not being saved and subsequently not retrieved by the DIF2 form. The user would then either need to perform a contact match to retrieve the NHS Number, or manually enter it again. This has been resolved.
• There was an issue with DIF2 Incident forms where a section that had had its name modified in the Form Design, and had been checked to be a new section, was not displaying the new name in the form's left-hand menu. Instead, the original section name was being displayed. Viewing the panel would show the updated name. This has been resolved, and the left-hand menu now reflects any changes to a section's name.
• There was an issue with the ID Number fields on a Level 1 Contact form where any form design changes applied to the fields would not be reflected in the form that a user would see. This included relabelling the field and applying HTML formatting. This has been resolved, and any form design changes applied to the field will be reflected in the form that a user sees.
• There was an issue in the Actions module where a Manager/Reviewer profile was unable to complete any Actions as a "server unable to compete this request" error message was being displayed when attempting to complete an Action. This has been resolved.

• Download CSV

Enhancements and Changes

• In Data Extraction, if Incidents field labels have been changed, users who can edit jobs are able to update all field aliases.
• A Contact's extra field data can be included when creating document templates for any Capture module.
• Equipment statues now display correctly after a user subscribes to service.
• Medication statues now display correctly after a user subscribes to service.
• The Safeguarding "Date of Event" field is available for reporting in Yellowfin.
• The "Safeguarding ID" field is available in the Notepad table for reporting in Yellowfin.
• In Yellowfin, the Causal Factors data table is available, which reports data from the Causal Factors field that is available in a number of Capture module forms.
• Administrators can delete Investigation records, as long as this has been enabled in the System Configuration.
• Administrators can delete Safety Alerts, as long as this has been enabled in the System Configuration.
• If field labels have been edited in the Capture Admin field relabelling, data fields in the Data Extraction Service will be updated to reflect the changes. This applies to new extraction jobs. Any existing or cloned jobs will retain their field names.
• If Incident field labels have been edited in the Capture Admin field relabelling, these Incident data fields in Data Extraction will be updated to reflect the changes. This applies to new and cloned extraction jobs. Any existing jobs will retain their field names.

Fixes

• There was an issue where the scrollbar was not present in the left-hand navigation menu in the Enterprise Risk Manager, meaning panels in forms were inaccessible without zooming the browser out. This has been resolved.
• There was an issue where a "system error occurred" message would be returned when a user attempted to access a Mortality Review record. Users were unable to access any part of the Mortality Review module. This has been resolved.
• There was an issue in the Investigations module were some users were receiing a database error when entering objectives into a record. This was not affecting all users. This has been resolved.
• There was an issue where when the Medications panel was hidden in the Form Designer for a Risk form, it was not being reflected in the "Report a Risk" form and the panel was visible. This has been resolved.
• There was an issue where the Survey Module could not export responses of a Survey to a csv file that contained a large number of responses. In addition, there was also an issue with the date filters used on the report not being applied to the csv export. These have been resolved.
• There was an issue where an unidentified code was being displayed, instead of the value, when checking for matching contacts on a DIF2 form. This has been resolved.
• There was an issue where selecting panels in Capture forms would not take the user to the top of the page if the previously views panel was large enough to require scrolling. This has been resolved, and users will be taken to the top of the page for every form panel that is viewed.
• There was an issue where users were receiving sporadic 504 error messages when attempting to upload documents to a Claims record. Attempting to open a Claims record with a large number of attachments was causing the page to load slower than expected. This has been resolved.
• There was an issue where User Defined section numbering was not consistent when generating a Level 2 Contact form from a Level 1 Contact Form. This lead to usability issues. This has been resolved.
• There was an issue where a Level 2 Contact form that was linked to an FEE2 Feedback from was not being used when performing a search. This has been resolved.
• There was an issue where notification emails were not successfully being sent to all recipients, if there were multiple recipients that were supposed to receive the email. This has been resolved.
• There was an issue around the message "Any field actions set on this field will be deleted when it is moved" being misleading. This message would be displayed when the ALLOW_CROSS_SECTION_ACTIONS Global Parameter was enabled, despite this Global allowing for fields that have a field action associated with it to be maintained when that field is moved. This has been resolved and the message will only be displayed if the Global Parameter is not enabled.
• There was an issue where text that was manually added to Parent Codes within Code Setups was being removed as the user entered the text. This affected all Capture modules where a combo-link existed. This has been resolved and text will be retained until the relevant code has been added.
• There was an issue where relabelling the "ID Number Type" and "ID Number" on a Contact Form was not being reflected when that form was in use in a module. This has been resolved.
• There was an issue in the Enterprise Risk Manager module where dates were not being validated. This was allowing future dates to be entered into the "Opened Date" field, and past dates to be entered into the "Risk Closed Date" and "Risk Review Date" fields. This has been resolved.
• There was an issue where modifying the text in the Medications search field in an Incident record and then saving the changes was resulting in the text entered being reverted to the test that was previously used for searching. This has been resolved and it is no longer possible to modify text in the search field and then save the record without saving.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• Mortality Review, Redress and Safeguarding CCS2 field are reportable within Yellowfin.
• In the Safeguarding module there is a new field, "Date of Event", that can be added to Safeguarding forms. Also, when populating the "Date of Birth" field for a contact, the "Age" and "Age Bands" fields are automatically populated.
• The following core Investigation module fields are available in Yellowfin for reporting: "Feedback due to staff", "Feedback due to patient/support person", "Investigation Report Due", "Authorised to endorse the investigation report on behalf of the CE?", "Endorse investigation report", and "Reason for decommissioning".
• The "Keep Author Anonymous" field for a Safety Learnings record can be reported on in Yellowfin.
• The "Source of Record" field for a Contacts record can be reported on in Yellowfin.
• There is a new field that is available for a Contact Record called "Source of Record", This field allows for easy identification of how a contact was added to the system.
• Enterprise Risk Manager records can be linked to Safeguarding records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Redress records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Safety Learnings records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Mortality Review records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Feedback records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Claims records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Investigation Records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Incident records via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to Safety Alerts via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Enterprise Risk Manager records can be linked to one another via the "Linked Records" panel. Users are only able to see and select records that they have access to view.
• Linked records fields between Risks and Capture records are viewable in Yellowfin, and the data will be populated.

Fixes

• There was an issue where "additional information" data was not being saved after contact matching, when creating a new link. This was occurring when a contact was added to a DIF1 form and then matching was performed on the DIF2 form. This has been resolved.
• There was an issue where when running either a packaged or normal report, the names in the "Assigned to(Actions)" field would be displayed as codes, if there were two or more owners. This has been resolved.
• There was an issue where when the "Attachments" of the "Communications & Feedback" section of a Feedback record was set to hidden, it was not possible to send emails. This has been resolved.
• There was an issue where when Data Indicator Icons were set to be displayed and the Equipment section of a form was set to be displayed as a new panel, the Data Indicator Icon was displayed even when there was no linked Equipment data. This has been resolved.
• There was an issue where "A technical error occurred" message was being displayed when attempting to filter a Risk Register by "My Risks", or by ID or Title. This has been resolved.
• There was an issue where when a Contact Listing Design, that contained at least one extra field, was used as the CON1 form in a Capture module form, the extra fields would remain blank after the rest of the contact form was populated. This has been resolved.
• There was an issue where when performing a Risk Review and adding an Action would result in the user being returned to the Risk instead of the Risk Review. This has been resolved.
• There was an issue where non-admin users who have full access to Contacts for both Capture and non-Capture modules were receiving a Client Error message when attempting to access Contacts in a non-Capture module. Users would be able to view a contact, but not any records linked to the contact. This has been resolved.
• There was an issue where when a user clicked the log out button, instead of being logged out the page would be refreshed. This would result in the user remaining logged in. This has been resolved.
• There was an issue where attempting to open an exported Pareto graph in Excel was resulting in the user receiving several error messages that indicated issues with the exported Pareto graph. This has been resolved.
• There was an issue where the Approval Status field for a linked Contact in a Capture module form was not available for selection in Listing Reports. This has been resolved.
• There was an issue where an error was returned when attempting to edit a Statistical Report that contained the field "Impact on Person". This was due to the field having been removed in a previous release. Users were not able to edit a Report that contained this field. This has been resolved. If any non-existent field exists in a Report, users will be able to edit the Report. The system will inform the user that there is a non-existent field and that it will need to be removed in order to run the Report.

• UK - A4 PDF
• US - Letter PDF

• Download CSV

Enhancements and Changes

• When filtering in the Contacts Dashboard, the filtered results will be retained upon looking at a record from the results and then returning to the dashboard. There is also a button to clear the results of the filtering in the Contacts Dashboard.
• Improvements have been made around filtered contacts, where the results are retained when a user clicks Back on their browser after viewing a contact from the filtered results. The filtered results and the page being reviewed are retained when click "Back to Dashboard" when viewing a contact.
• Users can navigate through filtered contacts via First record, Previous record, next record, last record buttons.
• Improvements have been made to searching and selecting values. Users can use '|' for OR, '&' for AND and '!' or '!=' for NOT EQUAL TO to aid with searching for values in these fields.
• "Job Title" is a new field available in Contact Forms. Codes can be added/edited/removed via the Field Maintenance. This field is available in Combo Linking as a parent or child field. "Job Title" can also be searched for and reported on.
• The listing display in the Contacts Dashboard can be managed to display records in ascending or descending order for the ID, Name, Type, Sub type and Approval Status columns.
• Within the Action module, users can filter the Locations or Services fields to search for multiple entries.
• Selecting options from multi-select fields can be done with more ease, e.g. use of left mouse key and dragging down to select and the use of the shift and down arrow to select all values.

Fixes

• There was an issue where in an Incident form, the Incident Medication form was failing to display when checking the "Select if a medication was involved in the incident" checkbox. This has been resolved.
• There was an issue where the RP07-A code was missing when uploading an Incident to the NRLS. This was causing a build-up of Incidents as they were not being processed. This has been resolved.
• There was an issue where creating a crosstab report using the Contact field "Staff Type?" as an extra field was resulting in an "A system error has occurred" error message being returned. This has been resolved.
• There was an issue where the Clear button was not being displayed, meaning that filtered data could not be cleared when performing multiple searches in the Contact Dashboard. This has been resolved.