Forms are used to collect data and to collect approvals for a range of industries to ensure that a consistent process is being used. Once the data has been collected and approvals obtained, the forms are usually filed in a physical repository (ranging from a single folder to a filing cabinet or cardex depending on the volume). Examples include patient forms, new user forms, change control forms, booking forms and so forth.
Post archival, any information required from the forms has to be searched for manually encompassing a process of physically retrieving a folder and then manually sifting through forms. The subject of the search might not be identified, data may have been recorded incorrectly and approvals applied in error.
The purpose of the project is to develop a system that will use an electronic system for the design and handling of forms. The user will be able to select form fields, name the fields and layout the fields in a suitably aesthetic way, effectively mirroring a paper form that is already in use.
Forms will be completed electronically and the data saved in the database. This will allow reporting on the form data and control selections (e.g. checkboxes, options, etc.).
Approvals will also be electronic and comprise of a workflow.
The initial focus will be to develop a prototype that enable a feasibility study to be carried out to determine whether the project is suitable to move forward with.
The scope of the system is:
• Ability to make custom forms.
• To link associated records (other forms).
• Workflow based approvals
• Audit-trialled changes showing who made a change.
• Multi-level user access (e.g. Creator/Approver/User)
The system will be designed such that there will be a design mode and operate mode. Those with design privileges will be able to create forms and release them to operations.
Operations is the execution of the form. The user will enter and/or select data to fill-out the form in the same way that a paper form is filled out.
The idea is that each field is modelled from a custom-field object having it’s own identity (e.g. name, data type, etc).
The architecture can be prototyped in a traditional RDMS such as Access or MySQL using a web page front end. A web front end would be preferred.
We are open to options and suggestions about the architecture to utilize simple, effective new technology.
25 freelancers are bidding on average $1539 for this job
Hello, I'm a professional developer for more than 12 years. I've gone through your requirements document and I'm ready to start. Please send me a message to discuss further. Thanks, Mario