Verne supports the full lifecycle of data within the register, from creation and maintenance to archiving and disposal. All created and edited data within Verne is subject to the business rules of the register.
Verne stores details about all new, altered or deleted data. Verne also stores “before images” of all data before it is updated or deleted. This allows authorised users to view a complete change history of all data within the system.
The following describes the lifecycle of data items within the Verne product from capture/input (e.g., user entry and third party integrations), data validation (completeness, quality), persistence, modification and changes.
Data passes through three distinct steps as it is processed and managed within Verne.
- Input/Capture: All externally available Verne business services provide an online form that allows capture of required data. For every business service provided a corresponding web service can be provided. These web services provide the same functionality and the same business rules and data validation as the online forms. A Verne business service can be configured to allow an internal user to invoke the business service on behalf of a third party. This allows the system to cater for the receipt of paper applications.
- Data Validation: A form cannot be submitted until all required fields have been completed and documents uploaded. Validation rules will be enforced to ensure data is valid. Rules can be applied to an attribute or to the business service, rules can be conditional based on a previously entered value. Verne applies different levels of severity to error conditions that it encounters when validating a business service.
- Persistence: Verne stores data and tracks versioning information in a database. The Verne data persistence layer is responsible for storing all data into a database. All modifications and changes to data on the register will be made via a series of business services. When an external user is completing a service online they can, depending on the configuration of the business service, save the business service as a draft. Information submitted to a Verne register, whether it be an application for registration or a change of address, will be saved in a pending state until it is determined the information is acceptable. Changes can be applied to the register as follows:
- Immediately on submission of an online form. This approach relies on system validation to ensure the information provided is acceptable.
- Following internal review. Where the online form requires review by an internal user the information will not be applied to the register until an internal user has reviewed the information provided and accepted/approved the application.
Every time changes are applied to the register by a business service, a new version of the entity is created by Verne’s versioning process. This process avoids the two major pitfalls associated with historical data, namely the proliferation of duplicated data, and the process intensive nature of deriving data from timestamps. Versioning retains a history of all new, altered or deleted data. Versioning also enables Verne to present a snapshot of data at any particular time in a registered entity’s life cycle, based on the version of the entity in place at that time.
