Path to Production

To ensure the success of your newly digitized form and process, testing and user training need to occur before the form goes live into the eForms Solution production environment.

STEP 3: Path to Production

This page contains technical information that is best reviewed with your technical support. Please visit our Glossary for an explanation of terms you are not familiar with.

Testing
 Prior to testing, it is highly recommended that you perform both UI (user interface) and UX (user experience) validation. This involves engaging some of your form users for feedback as you design and build your form(s), systems and workflows.
Once you and your users are satisfied with what has been built, it's time to finalise your requirements and begin testing. To begin this step, please reach out to your eForms contact to schedule time with the eForms QA (quality assurance) team.

There are 2 distinct testing phases:

1. eForms testing

The following activities are performed by the eForms QA team with some support from your team where changes and additional information are required:

 

The eForms QA team will do the following to prepare for your testing:


Test environment (UAT) set-up

  • Set up and provide you with test accounts for your QA team
  • Migrate your form(s) into the eForms Solution UAT environment for testing
  • Set up the eForms Solution UAT environment to submit to your receiving system based on the method you selected to receive form data (this includes firewall set-up where required)
  • Validate that forms submitted from the eForms Solution test environment reach your test receiving system.
The above test environment set-up only applies to testing with the eForms Solution Launcher. If you wish to test your form(s) and receiving system with EMR vendors you will need to contact them directly.

Submission Acknowledgement message set-up‎

Based on any custom wording you provide, the eForms QA team will set up and validate the Submission Acknowledgement messages to meet your requirements. 


See System Set-up for more information on Receiving System connectivity and Submission Acknowledgement messages.

 

The eForms QA team will perform a brief validation of your form(s):


Best Practices alignment

The eForms QA team will validate your form(s) and PDF output against our Best Practices and provide you with recommended or required changes where applicable.
Refer to the Best Practices tab on the Form Building page to ensure your form aligns prior to testing. 


FHIR tagging review

The eForms QA team will validate your form(s) to ensure FHIR tags of standard fields are correct and the resulting FHIR message is complete.


PDF validation

The eForms QA team will:

  • Validate your PDF structure
  • Ensure that all fields that are required to display on the PDF are included
 

2. Form owner testing

Your team is responsible for running your own integration and user acceptance testing of your form(s), system, and end-to-end workflow. Some of the required testing activities are outlined in this section. The 'Preparing for testing' activities can be completed prior to the completion of the eForms testing activities listed above.

 
Your team is responsible for the following preparation activities:

Scope of Testing

Please provide the scope of your testing to the eForms QA team. The eForms QA team will share EMPI (patient) and PLR (provider) test data for your testing. The scope of your testing is at the discretion of your team. 

We recommend the scope of your testing include:

  • The UI/UX validation of your form(s) design, look & feel
  • Field by field test cases of your form(s) - including conditional form fields
  • User (form filler & receiver) workflow test cases

Best Practices alignment

Make any changes to your form based on feedback from the eForms QA team.

Receiving system design & FHIR compliance

Validate your receiving system design and ensure it is FHIR compliant.

Receiving system connectivity

As referred to on the System Set-up page, set up connectivity for your chosen method of receipt with the eForms QA environment.‎
 

 

Your team is responsible for conducting various tests to ensure the design and set-up of your form(s) and system meet your requirements. These tests should include:


Draft form functionality

  • Save drafts of forms prior to submitting
    Note: If nested form functionality is used, ensure that information is saved on the child form
  • Retrieve drafts of forms

Data pre-population functionality

Ensure patient and provider information pre-populate on the form as expected.

PDF output functionality and design

  • Test that the PDF output downloads as expected
  • Customized PDF
    • Ensure that the overall PDF layout meets your requirements
    • Ensure that all fields that are required to display on the PDF are included

Submission Acknowledgement messages

Verify that the wording of the messages is correct.‎
 

 

Your team is responsible for developing and carrying out testing with your form users to ensure fulsome testing and validation of your newly digitized solution.‎

 
Your team is responsible for performing End-to-End validation between the eForms Solution system and your receiving system.

Tester(s) should fill and submit information in the eForms Solution and validate receipt of those messages in your receiving system.‎
 

 

‎Once your testing is complete, it's time to decide if you're ready to go-live with your newly digitized form(s)! If your team decides it's a 'Go' please reach out to your primary eForms team contact to start that process.

 
 



User onboarding

To ensure your form-fillers can use your form(s) upon go-live, you will need to train your users and provide them with access to your form(s) in the eForms Solution. 

 

Controlled access to eForms

Most forms in the eForms Solution feature integrated patient and provider look-up functionality. As certain patient and provider information is considered sensitive and/or private, the eForms Solution is not available to the general public, and access is strictly controlled.

Two methods of access 

1. EMR (Electronic Medical Record)

Users accessing eForms from an integrated EMR will be authenticated and have their access granted by the EMR.

2. eForms Launcher

Users accessing the eForms Solution through the eForms Launcher (via Chrome) must contact the eForms team to request access. The eForms team will verify the request and grant access upon approval.

You are responsible for designating an approver who will handle all user access requests to your form(s). 
This approver can be an individual, small team, or shared email address. An approver is responsible for verifying the appropriateness of your form users, as well as identifying any potential misuse that may occur on the part of those users.

 

‎Develop Formal Training and Documentation

You are responsible for conducting training and developing documentation for your form(s), and defining and communicating these processes to your users.

Proper training and documentation will help:

  • Users understand how to use the form(s)
  • Identify who to contact if a user has issues
  • Ensure data consistency
  • Drive adoption of the form
  • Increase user satisfaction
As the details of a form can vary considerably, you should be prepared to instruct your users on the nuances of your form(s). Some documentation examples include:

  • What to do if a patient or provider is not found on look-up?
  • Should PDFs be saved? If so, where?
  • How will we work with saved drafts?

Familiarity with eForms Fundamentals

As part of your agreement with the eForms Solution, you are expected to understand the eForms Solution fundamental functionality, such as:

  • Looking up patients and providers
  • Saving and recovering drafts
  • Generating and saving PDFs
 

Go-live!

Publishing your form

It is time to work with the eForms team to release your form(s) into the eForms Solution Production environment!

Prior to the release date...

  1. You will have exchanged production environment connectivity information with the eForms QA team. The eForms QA team will work with you to set up connectivity between the eForms Solution Production environment and your receiving system.
  2. You will have scheduled a release date with the eForms QA team.
  3. You will have successfully completed your End-to-End Testing.
  4. Your team will have made a 'Go' decision to proceed with releasing your form into the eForms Solution Production environment.

On the release date...

  1. eForms QA team will release your form(s) into the eForms Solution Production environment.
  2. eForms QA team will work with you to perform a Smoke Test as the final validation of your form(s). This involves submitting a completed form (using a “DONOTUSE” patient) to your receiving system to ensure that the end-to-end process functions as expected. This will validate that:
    • The data is received by your receiving system and the information contained in the message are correct.
    • Save draft functionality works as expected (if applicable).
    • PDF functionality works as expected (if applicable).
If the Smoke Test is successful, your form(s) are now considered live and ready for use!

Post go-live change requests

Any changes required to a form after it has gone live into the eForms Solution production environment will require a change request. 

If we built your form(s) for you, please submit your requested changes to the eForms Solution inbox. Your requested changes will then be entered into our development queue.

If you built your own form(s), please notify us via the eForms Solution inbox and request that your form be moved to the UAT environment for testing.

Tab Heading