Purpose of the Application:
This is a quality improvement data entry and collection system. Vermont Oxford Network (VON) maintains a quality improvement registry providing Neonatal Intensive Care Units with quality improvement reporting services.
Purpose of the Migration from eNICQ 5 to eNICQ 6:
This release is a major security and architecture re-design of the eNICQ application. In addition to enhanced security features, the database design for eNICQ 6 uses a key-value pair pattern to allow future product upgrades to be conducted with greatly reduced IT support. Web communications also now use RESTful API technology, which we hope will reduce security conflicts.
Timeline of the Migration
Your eNICQ users will need to have the eNICQ 6 migration complete in order to begin data entry for the 2018 birth year. However, they will be able to complete their entry and closeout of all their 2017 records while still in the old eNICQ 5 product. This gives a little wiggle room, but VON advises that your team begin preparations for migration as soon as you are able.
Basic Architecture of eNICQ 6
The architecture between eNICQ 5 and eNICQ 6 is fundamentally the same. Both applications are thick windows clients with a SQL Server database as the back end, no executables server-side other than stored procedures within its own database. The application also communicates with our web servers via RESTful API but can function offline for limited periods of time.
There are a few choices that your IT team will get to make on setup.
First, the hosting of the database has to be established. We advise hosting the database on an existing instance of SQL Server 2012 or higher that will be managed/secured by a database administrator or similar IT professional. It is also possible to host the database on a free instance of SQL Server 2012 Express that is bundled with the installer. We don't recommend this, however.
If you find that your current instance of eNICQ 5 is being hosted on a local Express database, now would be a great time to move to a more secure hosting location. If you aren't sure where the existing instance of eNICQ 5 stores its data, you can find out easily.
The second choice your team will make is how you will secure the application and its data. This can be managed easily via AD group membership. VON recommends using AD groups to manage access as it is an easy method for IT teams to handle, and most security is often managed by IT teams. Additionally, you can tie in your database authentication to the same AD groups, locking at two levels (application and database) with a single method.
The other option to manage application security is to use the VON services login to manage application access. With this option, the same login and passwords that your staff use to sign on to the VON website can be used to sign on to the eNICQ application. Under this model, a staff person at your organization (designated as the "VON Services Administrator") will take responsibility for managing account access to the eNICQ application.
Please see the remainder of the eNICQ 6 FAQ for additional questions. You can also email us direct at firstname.lastname@example.org.