MESA/Form Filler

From IHEWiki

Jump to: navigation, search

MESA/Form Filler

Contents


[edit]

Retrieve Form for Data Capture (RFD) Integration Profile Tests

This section describes tests that are specific to the IHE Retrieve Form for Data Capture Integration (RFD) profile.

There is no test software required for these tests.

[edit]

Form Filler Test 14350: RFD Vendor Interoperability - Retrieve Form

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.

  • 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. All RFD testing participants have access to this spreadsheet. The spreadsheet for the NA 2010 connectathon is stored here: http://spreadsheets.google.com/ccc?key=pbVa2DxUyoRmYekJgRFAXJQ&hl=en
  • 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 SOAP transport.
  • 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 into kudu 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.
[edit]

Form Filler Test 14352: RFD Exchange Sample Pre-Population XML

This test is due 2 weeks before the normal deadlines. Submit a document (even if your work is not complete) so the other participants can review your sample.

Form Fillers may include the "prepopData" in the Retrieve Form transaction sent to the Form Manager. (This test may not apply to your system if you do not support pre-population.) This is a well-formed xml document which provides context information to the Form Manager for use in pre-populating XForm fields in the form returned to the Form Filler. The format of "prepopData" is defined by content profiles such as CRD (Clinical Research Data Capture), MCH (Mother & Child Health) and DSC (Durg Safety Content).

This test enables (encourages) internet testing prior to the Connectathon. Form Fillers publish sample "prepopData" content which Form Managers can use for internet testing of RFD.

In test 14352, Form Fillers submit one or more sample prepopData XML document(s) that your system will produce. The purpose of this test is to allow the Project Manager to post this sample to Form Managers so they can read/test/render the documents in advance of face to face testing.

Instructions

To run this test, follow these steps:

1. Create a prepopData XMLdocument.

2. Name this file: <your_system_name>_14352.xml

3. Upload the XML file and screen capture snapshot into kudu under MESA Tests -> Pre-Connectathon...Objects for test 14352.

4. Create a short txt file indicating you have completed the upload step. Upload that txt file into the Kudu system under the MESA test log results for this test.

5. As Form Manager actors test with your data, you may receive a request for interpretation or directives from the Project Manager to repair attributes. This may prove to be an iterative process.

Evaluation

The evaluation for this test is performed by the other participants. As they review your document, there will be conversation about items in the document.

The goal is no surprises at the connectathon.

[edit]

Form Filler Test 14354: RFD Vendor Interoperability - Submit Form

Form Fillers which support the Submit Form transaction should run this tests.

This test enables (encourages) internet testing prior to the Connectathon. Form Receivers publish a URL which Form Fillers can use for internet testing of RFD.

  • 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 for the NA 2010 connectathon 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.
[edit]

Form Filler Test 14356: RFD Vendor Interoperability - Archive Form

Form Fillers which support the Archive Form transaction should run this tests.

This test enables (encourages) internet testing prior to the Connectathon. Form Archivers publish a URL which Form Fillers can use for internet testing of RFD.

  • 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 for the NA 2010 connectathon 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.
Retrieved from "http://ihewiki.wustl.edu/wiki/index.php/MESA/Form_Filler"