MESA/Form Filler
| The test definitions on this page are RETIRED, but are kept here, for now, as an archive. |
MESA/Form Filler
CRD Profile Tests
Form Filler Test 40001-100 CRD Content Profile - CDA R2 Valid Schema
Form Fillers test that their pre-population document is a valid CDA R2 document. Follow the instructions for Content Creators in: http://ihewiki.wustl.edu/wiki/index.php/MESA/Content_Creator#40001-01.2C_-02.2C_-03.2C_....:_CDA_R2_Valid_Schema
DSC Profile Tests
Form Filler Test 40001-101 DSC Content Profile - CDA R2 Valid Schema
Form Fillers test that their pre-population document is a valid CDA R2 document. Follow the instructions for Content Creators in: http://ihewiki.wustl.edu/wiki/index.php/MESA/Content_Creator#40001-01.2C_-02.2C_-03.2C_....:_CDA_R2_Valid_Schema
RFD Integration Profile Tests
Form Filler Test 14350: RFD Vendor Interoperability - Retrieve Form
This test is retired for NA2012.
Form Managers in the RFD profile are required to serve up forms by Form ID.
This test enables (encourages) internet testing prior to the Connectathon. Form Managers publish a URL which Form Fillers can use for internet testing of RFD. This test is marked as REQUIRED in gazelle. For some participants, internal problems with firewalls, or other issues, makes internet testing impossible. So, in essence, pre-connectathon testing for RFD is optional, but if we marked it as such in gazelle, we fear you would not have read this test to know that you have an opportunity to test with your partners prior to the connectathon.
- Form Managers will make an entry in a shared Google spreadsheet indicating the URL which Form Fillers can use for internet testing of the 'Retrieve Form' transaction. The spreadsheet is stored here: http://spreadsheets.google.com/ccc?key=pbVa2DxUyoRmYekJgRFAXJQ&hl=en
If you cannot access the spreadsheet, please contact Lynn Felhofer.
- In this spreadsheet, Form Manager systems enter a URL for accessing their Form Manager over the internet. They should also include values for formID(s) available on their system, and whether they support XHTML and/or XForms.
- As a Form Filler, you should access the Form Managers prior to the pre-connectathon (Mesa) test deadline.
- When you complete internet testing, create a .txt file that lists the Form Managers you have successfully with. If you had problems, add a note to that effect. Upload that .txt file as the results for test 14350. This will be a signal to the project manager that your system has done internet testing.
- The goal is no surprises at the connectathon.
Form Filler Test 14354: RFD Vendor Interoperability - Submit Form
This test is retired for NA2012.
Form Fillers which support the Submit Form transaction should run this tests.
This test enables (encourages) internet testing prior to the Connectathon. Form Managers publish a URL which Form Fillers can use for internet testing of RFD. This test is marked as REQUIRED in gazelle. For some participants, internal problems with firewalls, or other issues, makes internet testing impossible. So, in essence, pre-connectathon testing for RFD is optional, but if we marked it as such in gazelle, we fear you would not have read this test to know that you have an opportunity to test with your partners prior to the connectathon.
- Form Receivers will make an entry in a shared Google spreadsheet indicating the URL which Form Fillers can use for internet testing of the 'Submit Form' transaction. All RFD testing participants have access to this spreadsheet. The spreadsheet is stored here: http://spreadsheets.google.com/ccc?key=pbVa2DxUyoRmYekJgRFAXJQ&hl=en
- In this spreadsheet, Form Receiver systems enter a URL for accessing their system over the internet. They should also include if they support SOAP transport.
- As a Form Filler, you should access the Form Receivers prior to the pre-connectathon (Mesa) test deadline. You can use forms from test 13540.
- When you complete internet testing, create a .txt file that lists the Form Managers you have successfully with. If you had problems, add a note to that effect. Upload that .txt file into kudu as the results for test 14354. This will be a signal to the project manager that your system has done internet testing.
- The goal is no surprises at the connectathon.
Form Filler Test 14356: RFD Vendor Interoperability - Archive Form
This test is retired for NA2012.
Form Fillers which support the Archive Form transaction should run this tests.
This test enables (encourages) internet testing prior to the Connectathon. Form Managers publish a URL which Form Fillers can use for internet testing of RFD. This test is marked as REQUIRED in gazelle. For some participants, internal problems with firewalls, or other issues, makes internet testing impossible. So, in essence, pre-connectathon testing for RFD is optional, but if we marked it as such in gazelle, we fear you would not have read this test to know that you have an opportunity to test with your partners prior to the connectathon.
- Form Archivers will make an entry in a shared Google spreadsheet indicating the URL which Form Fillers can use for internet testing of the 'Archive Form' transaction. All RFD testing participants have access to this spreadsheet. The spreadsheet is stored here: http://spreadsheets.google.com/ccc?key=pbVa2DxUyoRmYekJgRFAXJQ&hl=en
- In this spreadsheet, Form Archiver systems enter a URL for accessing their system over the internet. They should also include if they support SOAP transport.
- As a Form Filler, you should access the Form Archivers prior to the pre-connectathon (Mesa) test deadline. You can use forms from test 13540.
- When you complete internet testing, create a .txt file that lists the Form Managers you have successfully with. If you had problems, add a note to that effect. Upload that .txt file into kudu as the results for test 14356. This will be a signal to the project manager that your system has done internet testing.
- The goal is no surprises at the connectathon.