About four times a year, we release a major update for iProva. In these updates, we introduce new features and ensure that existing functionalities work even easier and better. These updates also ensure that iProva stays technically 'up to date'.

Curious about what's new in iProva 5.13? You can read about it on this page.

iProva 5.13 will be rolled out from 8 January 2020.

Documents & processes

  • If you have marked a document as a favourite, we will now keep you informed automatically via notification if there are any changes to that document.
  • If you create a new document by uploading a file, we will now immediately check for you whether that document already exists in the system. This way, we help you avoid having the same document stored and managed in multiple places! Unchanged is that you can always use the properties screen of a document can detect whether very similar documents exist.
  • Through the community we have heard that writers submitting a draft version of a document often fail to fill in the 'Changes from previous version' field. We have chosen to keep filling this field optional (more writers may follow after the one submitting now) but we have modified the screen so that the fill-in field is more quickly recognised as such.
  • When you start editing an interactive document, we now automatically save your changes on a continuous basis. The "Save and Close" button at the top of the editor has therefore been replaced by a "Close" button. Next to this button you can see the current status: "Saved" or "Saving".

Reporting, analysing and improving

Input validation

For certain fields on the form, as an application manager, you always had the option of setting entry requirements.
For example, for a text field you can specify the maximum number of characters that can be entered, and for a numeric field you can specify that only integers between 0 and 10 can be entered.

However, it was a long-held wish of our Community  to have more freedom in this, and as an application manager also be able to define your own input masks. Think phone numbers, patient identification numbers, contracts, batches and so on.
By checking the input more carefully already while filling in the form, you build up more pure data, and that in turn can help you later, for example if you want to link iProva to a business intelligence system is going to lay.

Creating such input masks is done via Application manager > System settings > Regular expressions.
You will already find some examples of input masks here, such as postcode and phone number.
Besides the input mask itself, you can also set here which error message text should be displayed if the user tries to enter something that does not meet the input criteria.

To define input masks, we use regular expressions (or regex for short). This is a very powerful technique, but not very easy for beginners to learn. However, many examples of regular expressions for all kinds of applications can be found online (look at here under "Community patterns") and, in addition, many tutorials can be found for writing regular expressions.

After a regular expression is created by an application manager, you can activate it at a form field.
For fields of type 'Text', 'Number' or 'Web page', you will now find the new option 'Additional validation'. Here, you can choose from the expressions defined in your iProva. If you choose to apply a regular expression to a field, this automatically disables the other settings for input validation (e.g. maximum number of characters).

Integration with ECD (client file)

This development is specific to healthcare facilities.

The iProva "Reporting & Analysis" module delivers even more value when linked to your healthcare institution's electronic patient or client file. Think, for example, of the registration of incidents. How convenient would it be if the staff member could insert information about the patient or client into the incident form at the push of a button? It would be even better if we could also eliminate double recording of the same information in both the incident report and the client file.

As of iProva 5.13, this far-reaching integration is also available for Pinkroccade Healthcare's mijnCaress.
This link needs to be purchased separately (in two parts; from Infoland and from Pinkroccade). Please contact your account manager for more information.

Is your organisation using a different ECD or EPD? Read on the Community about the options for your situation.

Keywords Extraction

In iProva 5.12, we have interactive reporting added that are fed by keyword extraction from reports. To further optimise the results in these reports, we are introducing new functionalities for administrators in iProva 5.13.

As an application manager, you can now easily search all keywords and quickly see how often a keyword occurs.
You can then create rules that are automatically applied. For example, to consistently replace an old name of an organisation or department with the new name, so that in the interactive reports you only see the new name, but based on all reports where the keyword (old or new name) occurred.

You can find these functions under Application management > System settings > Keywords.

And further...

  • For the field type "Numerical value calculated by formula" options were so far limited to multiplying values and adding values. We have added "subtract" and "divide" options in this release.
  • In the workflow, you can have actions performed on a status transition. One such action is setting a field value. Here we reinforce the existing option to set a date field. You can now also set the field to a value related to another date field (e.g. 30 days after the date in field A).
  • Until now, it was not possible to add a follow-up task or split-off notification to a notification that had reached an end status. This restriction has been removed in iProva 5.13.
  • For multilingual organisations, we make it possible to enter the description of the action in multiple languages when setting out action items, so that each action taker is offered instructions in their own language.
  • We have added an action on status transition; from this release, it is possible to transfer values of a selected card from a card bin to a field of the notification.

Risk management

We are expanding the capabilities of our solution for integral risk management further out:

Working with different types of risks

If your organisation uses multiple risk templates (for different types of risks), you can now use each template:

  • set up a separate dashboard.
  • set a different risk matrix (if desired)

Risk assessment with a group of colleagues

Furthermore, in iProva 5.13 we introduce entirely new functionality for evaluating a set of risks in a session with a group of content expert colleagues.

The chair of the session decides which risks will be discussed and opens iProva on a beamer or TV screen. The other session participants use their own laptop, tablet or smartphone.

  1. Once the chairman starts the evaluation session in iProva, the screen below appears with a QR code.
  2. Participants can scan the QR code, then log into iProva.
  3. The chairman then guides the group through the set of risks.
    For each risk, each participant is asked to estimate the severity and probability for this risk, and enter it on their device.
  4. Once everyone's results are in, the chairman can reveal everyone's chosen scores on the big screen. You can then have discussions with your colleagues, and together arrive at the correct severity and probability.
  5. When filled in by the chairman, these values are automatically adopted at risk in iProva.
  6. You then move on to the next risk until all risks have been covered.

Questionnaires

  • For organisations working with questionnaire surveys, we are going to provide more overview. From now on, when you start working on a questionnaire survey, you will get an overview of all tasks that have already been done, and all tasks that still need to be done. It will also be possible to work with more people on one questionnaire in the context of a questionnaire survey.
  • When conducting a questionnaire through a questionnaire survey, there is the option of having the questionnaire completed anonymously.
    Until now, the filler was then given the opportunity to enter personal data anyway - but it was not mandatory.
    Feedback via the Community tells us that this was insufficiently clear. It was insufficiently clear to fillers that they did not have that data needed provide - and so in practice an anonymous survey was not so anonymous after all.
    We have therefore added a setting; when you go to create a questionnaire survey and you choose 'anonymous', you can now choose whether or not to be given the opportunity to fill in personal data.

And further in iProva 5.13 ...

  • For user accounts managed in iProva itself (not Active Directory accounts), we are changing the methodology for determining how 'strong' a password should be. Instead of just setting the minimum password length, we now look at more factors, and give the user immediate visual feedback on them.
  • The default security settings (for new iProva tenants) will be tightened.
  • The entire iProva user interface is also available in the German language as of iProva 5.13.
    Until now, iProva was already fully available in Dutch, English and French, but only partially available in German.

For application managers & ICT

Additional information for application managers & ICT can be found at my.infoland.co.uk.
After logging in, select My products > iProva > Download updates.

You can find additional release notes containing:

  • indication of the impact of this update (per iProva module)
  • changes in system requirements
  • overview of bug fixes

And further:

  • checklist for application managers
  • download the update (for iProva on-premise)
Copyright ©2021 Zenya. All Rights Reserved.