Back to all updates

over 10 years ago

Submission Checklist

Please view this document in entirety in PDF format a http://www.ehealth.va.gov/docs/mass/TCMS-Submission_Checklist.pdf

A successful submission to the Scheduling Contest will need to contain the following items:

  • Scheduler Application
  • Integration code tying the scheduler to the installed VistA instance
  • Additional OSEHRA compliant testing code to satisfy the test scenarios

These items should be installed appropriately with the scheduler placed as appropriate for the submission, with the integration code placed into the running VistA instance and (optionally) in the VistA FOIA repository clone, and with the OSEHRA compliant testing code placed into the appropriate directory.

In a Linux Virtual Machine:

/home/contestant/OSEHRA/Dashboards/OSEHRA-Automated-Testing

In a Windows Virtual Machine:

C:\Users\contestant\OSEHRA\Dashboards\OSEHRA-Automated-Testing

These additional tests must be placed in each one of the three VMs that are assigned to the contestant.

Additional required documentation should all be placed into the appropriate directory.

In a Linux Virtual Machine:

/home/contestant/ContestantDocuments

In a Windows Virtual Machine:

C:\Users\contestant\ContestantDocuments

and should consist of:

  • User Guide Describing how to run the contestant scheduler in that platform.
  • Detailed description of how to run the testing scenarios, focusing on differences between the instructions provided to the contestant and the requirements of the contestant submission. NOTE that evaluators will only execute the tests specified in this document’s instructions. It is the contestant’s responsibility to ensure that this document clearly specifies how to run each one of the tests on which the contestant will be evaluated.
  • A traceability matrix relating Veterans Affairs (VA) requirements to scheduler demonstrations.
  • Software as a Service (SaaS) code while the evaluation is underway (if Software as a Service is used).
  • Specific licensing for any open-source components.
  • Licenses for any other components, authorizing VA and its evaluators to use and inspect the software in the VM during the evaluation period.
  • Checksum of the entire VM, summarizing the state of the VM at the time of submission.

These items must be stored in each one of the VMs, with the content corresponding to that specific VM.