Retrieve Form for Data Capture (RFD)

George Cole, Steve Speicher, Dave Iberson-HurstGeorge Cole, Steve Speicher, Dave Iberson-HurstAllscripts, IBM, Assero

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

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.

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

Actors and Transactions

Clinical Trial: Visit WorkflowSponsored by

Clinical Trial: Lab & Image DataSponsored by

Disease Registry

Sponsored by

Drug Safety

Sponsored by

Bio-Surveillance

Sponsored by

’07 HIMSS New Directions

’07 HIMSS New Directions

SiemensAllscriptsAccenture

Cerner Allscripts Allscripts

NovartisSentrxRelsys

IBM DIFZ IBM

NovartisSentrxRelsys

PhaseForward

Outcome IBM

SASSAS IBM Assero SAS

Pfizer Lilly Novartis Genzyme

SAIC

Form Filler

Form Manager

Form Receiver

Form Archiver

RFD World

14355M8354673993L-716

A87631

A87631L-716

Clinical Trials Sponsor

Federal or State Agency

Disease Registry

Drug Safety Data Collection Agency

Paired Form

Manager / Form

Receiver

Physician Office

CN-1

A robust Form Filler

Paired Form

Manager / Form

Receiver

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

RFD Format of a Form

• RFD forms are XForms

• RFD XForms must conform to profile constraints

• …XForms overview is coming…

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.

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

SOAP Option

• All transactions have SOAP Option

• RFD.xsd – shared schema

• RFDFormManager.wsdl

• RFDFormReceiver.wsdl

• RFDFormArchiver.wsdl

Retrieve Form

• formID - required

• archiveURL - optional

• prepopData – optional, and if supplied this must be with HTTP POST

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

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

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

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

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

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

Call to Action

• Read the Profile; Provide Comments

• Participate in Testing– EHR’s– Cardiology & Radiology Domains– Life Sciences