Difference between revisions of "Retrieve Form for Data Capture"
m |
|||
Line 44: | Line 44: | ||
This utilizes a feature in XForms 1.1 to be able to change the submission target using the <xforms:resource> element for <xforms:submission>. | This utilizes a feature in XForms 1.1 to be able to change the submission target using the <xforms:resource> element for <xforms:submission>. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==WSDL== | ==WSDL== |
Revision as of 10:27, 24 February 2011
Retrieve Form for Data Capture (RFD) enables EHR applications to directly request forms from clinical trial sponsors and public health reporting.
Summary
Retrieve Form for Data Capture provides a method for gathering data within a user’s current application to meet the requirements of an external system. RFD supports the retrieval of forms from a form source, display and completion of a form, and return of instance data from the display application to the source application.
The profile relies upon XForms technology to support negotiation between the form display and form provider systems, so that iterative exchanges can deal with issues like form selection, completion of a series of forms, partial completion of forms, returning to forms partially filled out in earlier sessions. RFD also supports archiving a copy of the completed form.
<Include a simple graphic that, at a glance, gives an impression of what the profile does. See Help - Tips and Tricks for details on including an image/graphic.>
Benefits
Details
<Detailed discussion of what the profile does and how it works>
Use Cases
XForms in General
XForms is an XML application that represents the next generation of forms for the Web. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG. An XForms-based web form gathers and processes XML data using an architecture that separates presentation, purpose and content. The underlying data of a form is organized into instances of data schema (though formal schema definitions are not required). An XForm allows processing of data to occur using three mechanisms:
- a declarative model composed of formulae for data calculations and constraints, data type and other property declarations, and data submission parameters
- a view layer composed of intent-based user interface controls
- an imperative controller for orchestrating data manipulations, interactions between the model and view layers, and data submissions.
Thus, XForms accommodates form component reuse, fosters strong data type validation, eliminates unnecessary round-trips to the server, offers device independence and reduces the need for scripting.
XForms is a standard developed by the World Wide Web Consortium (W3C).
Simple XForm Example
Pre-population of XForm fields with EHR data
Simple working sample that prefills a data field
This utilizes the capability within XForms to have more than one data instance represented within an XForm's model. One instance contains the instance data to be used to prepopulate a form (with an id of iPropopulate). Once the instances are loaded within an XForm's processor, the values are copied from the propopulate instance into the working instance (to be submitted). This copying is accomplished by setting an event listener for the 'xforms-ready' event, which is dispatched after a XForms is loaded, to set values from one instance to another.
Multiple Submits
Working sample of multiple submits
This utilizes a feature in XForms 1.1 to be able to change the submission target using the <xforms:resource> element for <xforms:submission>.
WSDL
Systems Affected
<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >
References
IBM developerWorks XForms articles
List of XForms Implementations
Mozilla Firefox addon for XForms
FormsPlayer (Internet Explorer addon for XForms)
Note: to install this on Windows Vista, you must either run Internet Explorer as Administrator, or temporarily turn off User Access Control (UAC)
See Also
Profile Status: Trial Implementation
The IT Infrastructure Technical Framework is the official master document for this Profile.
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
<Replace the Template links below with links to the actual pages for the Profile>
The Profile FAQ Template answers typical questions about what the Profile does.
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile.
The Profile Implementation Template provides additional information about implementing this Profile in software.
This page is based on the Profile Template