Building and Testing a Trusted Agent Data-Sharing Infrastructure Bob Galbraith and Rita Mohsin NBME and FSMB April 17, 2007

Embed Size (px)

Text of Building and Testing a Trusted Agent Data-Sharing Infrastructure Bob Galbraith and Rita Mohsin NBME...

  • Slide 1
  • Building and Testing a Trusted Agent Data-Sharing Infrastructure Bob Galbraith and Rita Mohsin NBME and FSMB April 17, 2007
  • Slide 2
  • Trusted Agent Team FSMB Dale Austin, Tim Knettler, Rita Mohsin, Graham Calvert, Elizabeth Miles, Cyndi Streun, Dennison Herger, Bobby Dowling, Kevin Caldwell, Roxanne Huff NBME Bob Galbraith, Joe Crick, Kenny Yu, Madhav Iyer, Sue Gebeline, Martin Lambert, Kathie Rose Ohio State Medical Board Dianne Thompson, Penny Grubb, Kay Rieve New Hampshire & Kentucky Board Penny Taylor and Brenda Knopp Input from Medbiquitous
  • Slide 3
  • Data-Sharing infrastructure Real time access to data in many repositories Gathers data specific to function Report out to authorized viewers Scaleable, secure and confidential ONLY functions when authorized by the physician identified by the data What is a Trusted Agent?
  • Slide 4
  • Trusted Agent General Concept Delivering the right data to the right people at the right time for the right purpose with the authorization of the individual identified
  • Slide 5
  • Paper-and-Pencil (20 th Century) 70 licensure jurisdictions had different forms for initial application (even though data elements comparable) paper-and-pencil self-reported data, validated later
  • Slide 6
  • Common License Application Form (CLAF) One primary form, common data Option for state-specific addendum 3 States agreed to Pilot viz. OH, KY, NH Streamlining of the Application Process Data called from repositories through hub Data already source-verified (by Federations Credentials Verification Service FCVS) CLAF pre-populated with verified data Real time formatting and submission 24/7 The CLAF Pilot (21 st Century)
  • Slide 7
  • Web services architecture Real-time access to repositories Independent of system & data base structure Actual gathering, compilation and report out of data occur only upon authorization of the physician identified. The CLAF Pilot - 2
  • Slide 8
  • The CLAF Pilot - 3 The Medical Professional accesses CLAF, which requests necessary data from the Trusted Agent Hub Hub gathers data from FSMB & NBME, and returns to CLAF CLAF compiles application form and after inspection by the physician, transmits to SMB
  • Slide 9
  • Electronic medium/Online Near real time 24/7 Reduces burden of paperwork Data pre-population Increases accuracy and completeness Reduces burden of data entry Enables license applications to multiple jurisdictions simultaneously CLAF - Benefits
  • Slide 10
  • Trusted Agent Hub and CLAF Design Document/Literal Web Services All applications and services registered in Trusted Agent no UDDI Generic XML schemas for applications and providers interface Custom XML schemas for data returned from provider Unique security KEY for each member of Trusted Agent Data encrypted (using KEY) for service specific request/response Successful user login to return a time-expired certificate Service request (except login) requires a valid certificate Secure VPN communication with applications and providers SSL based Trusted Agent registration application on internet
  • Slide 11
  • Technology used: Trusted Agent CLAF Oracle Application Server on Linux J2EE 1.3 Oracle Database with VPD Java JDeveloper XML SOAP 1.1 WSDL 2.0 Oracle Application Server 10g on Solaris J2EE 1.3 Oracle Database 9i Microsoft.Net Framework 2.0 C# Microsoft Server 2003 IIS 6.0 XML/XSLT SOAP 1.1 WSDL 2.0
  • Slide 12
  • CLAF/Trusted Agent Hub Interaction
  • Slide 13
  • Performance of Pilot Around 1000 medical professionals have interacted with CLAF and TA Hub 100+ completed applications submitted