1 / 22

Retrieve Form for Data Capture (RFD)

The Retrieve Form for Data Capture (RFD) method gathers data within a user's application to meet external system requirements. It offers standardized external form display in EHR, flexible profiles, and seamless integration. Use cases include drug trials, bio-surveillance, pharmacovigilance, and more. Actors and Transactions involved in RFD streamline form retrieval, submission, and archival processes. XForms, part of RFD, ensure W3C compliance, platform independence, and user-friendly interfaces.

phyllisdobbs
Download Presentation

Retrieve Form for Data Capture (RFD)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Retrieve Form for Data Capture (RFD) George Cole, Steve Speicher, Dave Iberson-Hurst Allscripts, IBM, Assero

  2. Retrieve Form for Data Capture (RFD) provides a method for gathering data within a user’s current application to meet the requirements of an external system

  3. RFD Profile • A standard way of displaying external data capture forms inside an EHR. • Many-to-many integration – any EHR can retrieve forms from many external systems. • Low barrier of entry for EHR and external systems. • Flexible profile to accommodate both low-tech and sophisticated implementations.

  4. Five Use Cases • Investigational New Drug Trials • EHR linked to pharma sponsor via EDC. • Bio-surveillance • EHR linked to local and national bio-surveillance systems. • Pharmaco-vigilance • EHR linked to FDA and sponsors. • Cardiology research data registry • EHR linked to NCDR, US national registry. • Radiology • EHR linked to National Oncologic PET Registry

  5. Actors and Transactions

  6. ’07 HIMSS New Directions Bio-Surveillance Sponsored by Drug Safety Sponsored by Clinical Trial: Lab & Image Data Sponsored by Clinical Trial: Visit Workflow Sponsored by Disease Registry Sponsored by

  7. ’07 HIMSS New Directions Pfizer Lilly Novartis Genzyme SAIC Allscripts Accenture Form Filler Cerner Siemens Allscripts Allscripts SentrxRelsys Form Manager IBM Novartis DIFZ IBM SentrxRelsys Form Receiver PhaseForward Novartis Outcome IBM SAS Form Archiver IBM SAS Assero SAS

  8. RFD World A87631 A87631 14355 M8354673993 Physician Office L-716 L-716 Clinical Trials Sponsor Federal or State Agency Drug Safety Data Collection Agency Paired Form Manager / Form Receiver Paired Form Manager / Form Receiver Disease Registry CN-1 A robust Form Filler

  9. RFD Profile Phases • Integration Profile Phase • Define standard format for forms • Define standard method for retrieving and submitting forms • Content Profile Phase • Provide domain-specific form requirements • Enable form population from EHR mapped data

  10. RFD Format of a Form • RFD forms are XForms • RFD XForms must conform to profile constraints • …XForms overview is coming…

  11. RFD Actors • Form Filler: An actor for retrieving XForms • Form Manager: An actor for supplying XForms • Form Receiver: An actor for receiving submitted instance data • Form Archiver: An actor for receiving submitted instance data for archival.

  12. RFD Transactions • Retrieve Form • Supply a FormID to Form Manager to retrieve an XForm • Submit Form • XForm Submit action, Posting Instance Data to a Form Receiver • Archive Form • Think of this as a Carbon Copy feature • Optional XForm Submit action for Form Fillers to use • Retrieve Clarifications • Retrieve a list of Organizational Data Clarifications

  13. SOAP Option • All transactions have SOAP Option • RFD.xsd – shared schema • RFDFormManager.wsdl • RFDFormReceiver.wsdl • RFDFormArchiver.wsdl

  14. Retrieve Form • formID - required • archiveURL - optional • prepopData – optional, and if supplied this must be with HTTP POST

  15. Retrieve Form – Expected Actions • formID – used to determine the XForm • archiveURL – when supplied, XForm shall perform Archive Transaction using the supplied value • prepopData – may be used to determine the XForm, and/or may be used to pre-populate the XForm

  16. XForms • XML Powered Forms • Standards-based • World Wide Web Consortium (W3C) specification • http://www.w3.org/MarkUp/Forms/ • Platform independent • Capable of embracing many devices • Produces a user interface appropriate for the connecting device • Gaining support in browsers • Firefox (Windows, Linux, and Mac), and Internet Explorer

  17. Why XForms ? • Open W3C standard – no proprietary lock-in • Single instrument for all platforms – leaving rendering as a client decision • Off-line and on-line data collection • Can implement business rules • Required fields • “Skip patterns” based on user response, such as branch, reveal/hide fields • Binding of questions to schema and vocabulary • Integrated instrument submittal • No scripting – faster creation of instruments

  18. Goals of XForms • Rich, XML-based, forms to meet the needs of business and consumer web applications • Support for desktop browsers and other mobile devices • Decoupled data, logic, and presentation • Reduce/eliminate the need for script • Support for structured form data in all XML • Advanced forms logic

  19. How XForms Works • Model-View-Controller • Model: XML data model • View: XForms controls • Input, Select, Select1, Date Pickers,Range, … • Final rendering is decided “on the glass” • Controller: XForms processor • Submit • Binds

  20. References • XForms • XForms 1.1, W3C Working Draft. http://www.w3.org/TR/2004/WD-xforms11-20041115/ • Comparison of XForms and HTML forms http://en.wikipedia.org/wiki/XForms • W3C XForms Turtorial http://www.w3schools.com/xforms/default.asp • XForms Renderer/Browsers • Mozilla XForms project page http://www.mozilla.org/projects/xforms/ • X-Smiles (an open XForms renderer/browser) http://www.xsmiles.org/ • formsPlayer (IE plugin) http://www.formsplayer.com/content/index.html

  21. Call to Action • Read the Profile; Provide Comments • Participate in Testing • EHR’s • Cardiology & Radiology Domains • Life Sciences

More Related