We are happy to release v6.3 and the highlights of this release are:
Print token to include any field (including custom fields)
REDCap integration enhancements
See last section
Version | Download |
---|---|
Enterprise | Email support@openspecimen.org |
Community | Post any installation related questions on forums.openspecimen.org |
Software/Hardware requirements
Review this page before attempting to upgrade for any changes: Software/Hardware Requirements.
Dashlets used in dashboards can now be managed by super admins through UI. Go to Extras → Dashlets to see the list of dashlets.
New features:
For more details refer: Dashboard
The CP list page can now be configured to include any field of CP including custom fields. Criteria to sort the CP list and filters (on the left side) can also be configured.
E.g: End data and CP type (custom field) are displayed in the list view.
For more details: CP list view
The CPs that are to be visited frequently can be made to appear at the top of the list by 'star'ring them. This will make it easier for the super-admins to access the protocols that are frequently visited, saving the efforts to search the same protocols every time.
More information: Starring of a Collection Protocol
With the new Eval token, you can
Refer for more details: 'Print Rules'
Freezer maintenance tasks like cleanup, defrost, consolidate, servicing, etc has to be performed as regular intervals. You can now
For more details: 'Container Maintenance Tasks'
In previous versions, there was no way to assign specific Jobs to users (it was all or none). However, some jobs might be relevant only to some users. Al
Now you can
For more details: Jobs
While creating catalogs, admins can:
Reorder subform fields via XML
If you want to change the order of fields within a subform after a form is created, download the form XML and change the order fields within subform to reorder.
Include dropdowns created using Dropdown Manager
For more details: 'Fancy Control'
Every protocol event(time point) defined in the protocol might not be relevant for every participant. For example, consider a study where mother and partner are registered and some samples are collected during delivery which is only relevant only for mother.
This is done via JSON configurations. For more details: Visits configuration
Now you can add more than one events for the same set of specimens. Earlier you had to go a back to the specimens lists, select the same set of specimens, add the events.
This enhancement will reduce the steps and reduce changes of errors.
When collecting primary specimens, the received event details might not be known. However during specimen collection, the Received Event is created by default with received time as current date/time. This can be confusing since it is not clear which specimens are actually received by the lab.
To fix this:
Users can query for all specimens which are yet to be received in the lab and update the status once received.
In previous versions, query module was available to all users. It was not possible to restrict certain users from creating new queries, downloading data OR hiding query module. In v6.3, roles can be configured to control access to create, run, export data and delete queries.
For more details: 'Query Privilege (v6.3)'
Below are some REDCap integration enhancements: