In the world of data sharing, whether it be financial data like ACORD, DTCC, NTSC and or any number of other standards, there is always one common goal: conform the data into a reliable, consistent format that everyone can use regardless of their position in the process. When it comes to forms automation, many different data standards have been used in part or whole by different constituents, which has resulted in countless data models making it seemingly impossible to directly share data related to forms processing. With the advent of Quik!, we designed a data standard that manages form data explicitly, and it is called the Quik! Field Definition.
At the heart of every Quik! product and solution is a common core architecture that defines how Quik! works: the Quik! Field Definition. The purpose of the Quik! Field Definition is to make all forms and documents work in the same manner through a defined set of field types with common field names. Whether a form's job is to open a new account or change an address or inform a customer about changes, any time the form requires the customer's first and last name, that name should appear on the form in the correct place regardless of how the form is visually designed. The Quik! Field Definition makes this possible by having the same field on different forms built the exact same way.
Today, the Quik! Field Definition has grown to over 90,000 unique fields (and growing), organized into a highly structured field design that enables any process to generate and accept for form data. The Quik! Field Definition is a published, non-public standard, available to any company who maintains a Quik! customer account and distributes their forms to Quik! users.
The first version of the Quik! Field Definition (released in 2001) was designed to enable data to flow from a database onto a form. Since most databases were designed to hold contact data, the only data that is available from most databases is basic contact information (name, SSN, DOB, address, etc). Therefore, version 1.0 of the definition supported basic fields and filled out the most common and repetitive data on forms. Version 2.0 (released in 2005) continues to support this need and adds the ability to reliably pull data from forms once the user has completed filling out the form and submits it electronically. All forms built using the Version 2.0 definition are able to deliver information from any form in the same manner every time.