A software update was released to SHIP/CIMS and SRS environments.
The release includes the following new features
Please note: Many of the features outlined in these notes depend on configuration options. If you identify a feature from these notes that interests you, but is not currently available in your configuration, please contact Infoxchange.
SRS Client Details
Ancestry
- Ancestry has now been added as a core component of the client details data model. If used it will be displayed on the client details form.
- Ancestry utilises the ABS 1249.0 – Australian Standard Classification of Cultural and Ethnic Groups (ASCCGEG) 2016.
- The purpose of this field is to provide a self-assessed measure of ethnic origin or cultural group affiliation.
- Initially, it will only be switched on at the request of customers, or where the service is required to report Ancestry as part of national or state data collection (eg the DSS Data Exchange).
- Whilst sometimes referred to as ‘Cultural Background’ the recommended label for this field to align with current national standards is ‘Ancestry’. This is a single select field (aligning with current reporting requirements). It would be expected that for clients who identify with more than one cultural or ethnic affiliation their ‘primary’ affiliation is recorded.
Customer Reference Number
- The Centerlink Customer Reference Number has now been added as a core component of the client details data model. This is a ten character field, consisting of 9 alphabet characters followed by digit. Initially this field will only be switched on at the request of customers
PDF Export
- If a photo has been added to the client details form, this photo will now be included in the PDF Export.
- It is now possible to optionally remove the worker’s name from PDF exports.
Referrals
- Some configurations include configured demographic fields. Referrals sent between workgroups with the same configured fields will be able to transfer these fields as structured data (hence pre-populating client details if the referral is used to create new clients in the destination workgroup).
- A fix has been applied so that a consistent referral ID is always displayed to the user in the referrals tab on the home page and the referrals tab on the person page.
- When creating a referral, if the worker users the ‘Client File’ feature to add profile objects that include documents, these documents will now be included as separate attachments to the referral. The user will have the option to delete these attachments, as necessary, before sending the referral.
- The referral template has been updated to allow recording of consent, but still permit a referral to be sent when the consent has been set to ‘no’. This functionality is only configured where an administrative or legislative framework is in place to permit referrals without the subject’s consent.
Enquiries
- It is now possible to configure additional gender items in the enquiry form.
Restrictions
- In the dialog form used to restrict access to client records, the list of persons effected by the restriction now includes their relationship with the current person.
Profiles and Associations*
- If a profile or association* object (eg. a case summary) has linked notes validation has been added to prevent deletion of the profile / association object.
- If a profile or association* object (eg. a case summary) has linked notes validation has been added to prevent the user changing the start date and end dates on the object such that existing notes would fall outside the date range of the profile / association object.
- For those organisations using the association* object (a form which can be associated with multiple persons), the association can now be configured so that the start date for a person’s association can either default to the current date, or alternatively, default to the start date of the association object.
* An association is a record in SRS, similar to a profile, which can be linked to multiple clients. Associations are used for objects like Case Summaries, Family Profiles, Placement Records, etc. The linked persons may or may not be related. The existence of association records will be dependent on the workgroup configuration.
Reports
- Some standard reports have been updated to include new DSS fields where applicable
Custom Help
- For organisation who have a custom SRS Help site, help content can now be customised for individual profile objects (eg. Support period profiles, assessments, family profiles, carer profiles etc.)
NDIS
- It is now possible to relabel NDIS event types. For some users “Service Event” has been relabelled “Direct Support” and “Service Note” has been relabelled “Indirect Support”.
- When an NDIS note record is recorded and the user selects “Service Event” or “Direct Support”, all support items, and not just Service Events / Discrete Services are displayed. Billing rules remain unchanged.
- When an NDIS note record is recorded and the user selects “Service Note” or ‘Indirect Support’ the Support Item field is hidden. Service Notes / Indirect Support activities are not counted towards billing so it is not necessary to identify the Support Item.
- NDIS support agreements that are identified as ‘Self-Managed’ are now excluded from the NDIS Bulk Upload. Self-managed items can now be reported via a separate list so that services provided can be directly invoiced to the participant.
Other Minor Enhancements and Bug Fixes
- This release also includes a number of other minor enhancements and bug fixes.