Validating Mi-Co, Mi-Forms, and e-Forms

If you have created a series of new e-Forms for the Mi‑Co Mi‑Forms system, the next step is to validate them. The FDA and other regulatory bodies require all GxP software to be compliant and validated. Ofni Systems is partnered with Mi‑Co for validation and will quickly and efficiently assist you with all of your validation needs.

Ofni Systems uses FastVal to write validation documentation and execute Testing Protocols, which allows us to complete validation projects in 70% less time than traditional validation methods.

Our validation professionals have experience in helping large corporations and small companies meet their compliance requirements. Our validation professionals use FastVal to produce high quality documentation, identical to existing company documentation, more rapidly than with a word processor alone. Let Ofni Systems make validating Mi-Co simple for you.

Benefits of Validating Your e-Forms

Validating your system or database means all data gathered by the e-Form can be used to make quality and GxP decisions or submitted to regulatory bodies like the FDA. You can query your data to better understand your business process. You gain confidence in your system and control over the data and who has access to it.

Ofni Systems Validation Methodology

Step 1: Gather Requirements. Document the system functional requirements. Functional requirements describe what actions the e‑form must be able to perform. This includes:

• Worksheets and charts to be included on the e-form
• Data to be entered into the e-form
• Formulas or calculations used on each e-form
• Identifying who can enter the data into the e-form
• Identify how the e-form meets applicable regulatory requirements

Step 2: Document Design Requirements. Design requirements describe how the e‑form accomplishes the functional requirements. Ofni Systems uses proprietary tools to analyze the e‑form to create comprehensive design specifications. Design specifications include:

• Inputs – Data entry, validation rules, etc.
• Processing – Workflow enforcement, code, macros, etc.
• Outputs – Reports, data exports, etc.
• Security – User level security, data protection, etc.

Step 3: Develop and Execute Test Plans. Once requirements have been outlined and documented, test plans are developed to demonstrate that all required system functionality is met and the system is properly secured. Our validation professionals will document a testing protocol, designed to demonstrate that your form meets all of your business requirements and regulatory requirements outlined by 21 CFR Part 11. As appropriate, this includes operational qualifications (OQ) and performance qualifications (PQ). Deviations, if they exist, will be reported and resolved.

Additional Resources

Additional information is available on specific types of validation:

• Validating Computer Systems
  • Validating MS Access Databases
  • Validating MS Excel Spreadsheets
  • Validating Web Pages and Web Applications
  • Computer Software Validation
• Cleaning Validation