1 / 43

NIH Web Services Discovery System and B2B eXchange

NIH Web Services Discovery System and B2B eXchange. NSF Technology Briefing Vienna, VA January 2006 David RR Webber webberd@od.nih.gov. Agenda. Business Objectives, History, Deliverables Technology Approach Technology Detail Timelines Opportunity Summary.

cytheria-zenon
Download Presentation

NIH Web Services Discovery System and B2B eXchange

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. NIH Web Services Discovery System andB2B eXchange NSF Technology Briefing Vienna, VA January 2006 David RR Webber webberd@od.nih.gov

  2. Agenda • Business Objectives, History, Deliverables • Technology Approach • Technology Detail • Timelines • Opportunity Summary

  3. Business Objectives, History, Deliverables Overview

  4. NIH eRA – Competitive Grants Applications • Currently handling about 2,000,000 pieces of paper annually – scanning to digital images • Web front door - “Commons” system: • Number of Commons Logons: FY 2004: 565,344 FY 2005 to present: 946,330+ • Registered Organization (All) = 2884, and Registered Persons - 45334 • Grants applications posted electronically • eSNAP - FY 2003 =  329 FY 2004 =  2,854 Since 10/1/2004 =   5783+ • The total number of FSRs processed (internal and external) = 54657

  5. e-CGAP: Electronic Competitive Grant Application Process • Paperless grant applications and all post submission downstream processing • Extending a seamless grant workflow into the external community • Promote the concept of service provider • Leads to need for system to system interfaces and data streams • Which leads to the use of business to business electronic commerce concepts and standards • HHS Award Winning effort

  6. Need to provide a common view The typical grant applicants’ challenge Juggling all the various different formats and procedures

  7. Existing CGAP Transactions in place • Submission of modular grants • Submission of full budget grants (no sub-projects or consortia) • Validation result returned to Submitter system • Validation service before submission • Grant image generation by NIH • View and approve generated image for sign-off of submission (web GUI) • Investigator Personal profile query and update • Status inquiries in grant workflow processing • Notification of peer review assignment

  8. Grants.gov Interfacing Schedule

  9. Sample - Hourly Diagnostics Reporting • Time Related Reporting: • Submissions processed within the last 24 hours: 102 • Grant images created within the last 24 hours: 25 • SBIR/STTR totals: • Total SBIR/STTR submissions processed: 7932 • Total SBIR/STTR grant images created: 1849 • Total unique SBIR/STTR applications with outstanding validation errors: 517 • Grand totals to date: • Total submissions processed: 8560 • Total grant images created: 2011 • Total applications awaiting verification: 61 • Total applications verified: 1924 • Total applications rejected: 26 • Total applications processed through Receipt and Referral: 1810 • Total unique applications with outstanding validation errors: 576

  10. Beyond Grants Applications • The ability to interface quickly and easily to external parties with limited resources is not just a grants applications need • Secure reliable verifiable common communications infrastructure based on open public specifications • Other potential applicable areas: • HHS - Cancer Research Centers • CDC – Emergency Alerting systems • NSF – National Science Foundation grants • Navy – Medical Services coordination • FEMA – Emergency supply chain delivery • DHS – Intra-agency information sharing • EPA – External regulatory reporting

  11. Technology Approach Overview of Architecture and Components

  12. Leveraging Open Standards • Combining best-of-breed solution with both ebXML and Web services working together • Open source solution components to allow unrestricted integration by partners • Foundation of ebXML formal interchange model • Leveraging loose coupling of web services

  13. Exchange Functional Components Network Security Content Transport Payload Handling Registry Business Systems Manage Workflow

  14. Staged Virus Check Certificates Identity Fire Wall MoUs Profiles Synch Partners Asynch Industry Semantics Errors Receive Validation Scripts Send Role + Context Scripts Business Rules Dispatch Business Rules Errors Content Events Actions Versions Exchange Operational Details Network Security Content Transport Payload Handling Registry Business Systems Manage Workflow

  15. Partner transaction authentication Messages Messages 5 data validation CPA check Transport ebMS server XML Structure Rules Oracle database (Persistent Storage) Central ebXML Registry 4 CPA instances System Administrators Manage Partner Interactions Grants Implementation Overview Government Partners 1 Applicant Authority Partner Management Web forms CPA instances 2 Proxy Submission Service Provider 3 Local Applicant Company

  16. Grant Administration Clinical Trial System AE reporting Grant application Authoring Internal Approvals & Workflows Protocol Authoring Personal Profile and Pub management Service Provider view - single process REGISTRY Institution - Service Provider ebXML ebXML HL7 ebXML Single User Interface or Site ebXML ebXML HL7 ebXML

  17. Example: eRA and Grants.gov (Competitive Grants) eRA eXchange Services & eRA Applicant Grants.gov eRA Exchange 2 ebXML Grants.gov Intake & Processing eRA eXchange Intake OPEN / PLUGGABLE Pure Edge Forms download eRA eXchange XML validation MONO CLOSED SYSTEM 1 3 eRA eXchange Services Business Validation DB Load Image generation 4 eRA COMMONS 5 E R A 6 Validation Results Notification eRA COMMONS Interface Status Validation results Image Verification Sign-Off email Web forms interface

  18. Technology Detail Components, Specifications and Implementation

  19. Information Exchange Integration requirements • Outward facing messaging systems • Formal agreement profiles for business participants • Business process workflow definitions • Information exchange rules • Registry to hold agreements, definitions, scripts… • Internal integration routing and dispatch methods • User interfacing for entry and control

  20. B2B Exchange Design Goals • Automated registration of participants • Ability to self-certify exchange transactions • Version control and ability to approve partners • Centralized registry for participant management • Declared and shared business rule scripting • Integration through messaging services • Backend application integration services • Uses open public specifications and open source

  21. Architecture Needs Overview Web service delivery ebXML delivery Staged delivery HL7 support Network Infrastructure Certification Service Authentication, Validation, Routing Security Service Message Transfer Roles MoU Persistence Queue Registry of Rules and Agreements Certs SQL DB Queue Monitor Nouns XML Dispatch Handler HL7/XML Data Services Integration Management Partner Management Internal Applications

  22. Exchange Concurrent Processing Architecture Load Balancing Staged Delivery Agent Partner Security Services 4 Application 1 Notify External Sender A Process Queuing 4 7 Subscribe Request / Response Download Queue Publish 3 From: / To: filtering Received Queue Dispatch Agent Receipt Agent(s) 5 Requests Payload Staging Area Payload Responses Delivery Services 2 6 Dispatch Services Send External Sender B Partner Security Services (Pluggable exchanges controlled using Hermes messaging server –using: WSDL, ebMS, AS/2, HL7) 1

  23. REGISTRY • Partner Information • Exchg Agreements • Transactions Def • Bus process info • Authorizations Message Processors Message Processors Grant Administration Clinical Trial System AE reporting Internal Workflow Internal Approvals & Workflows Protocol Authoring Grant application Authoring Grant Management Population Tracking eRA Personal Profile NLM Pub system IRB Approvals, Pop Tracking AE reporting NIH Personal Profile and Pub management ebXML services ebXML services AUDITS • Tracking • Security • Mgmt statistics • Activity reports Example Messaging Hub and B2B components NIH Single Sign On Institution - Service Provider Application Receipt and Review Researchers eRA IC OpDiv Fellows eXchange Single User Interface or Site Trainees Clinicians Research Administrators Applicants

  24. Technical discussion of the eXchange • Exchange context • Exchange components • 4 major components • eRA eXchange • eRA eXchange Client • eRA eXchange Services • eRA Registry • ebXML • Web services

  25. 1.Get application list 3. Get application 9. confirmation 2. Send pre-notification 4. Send notification 5. Request payload 6. Payload delivery 7. Delivery Status 8. Processing status Example: Grants.gov interfacing Grants.Gov Web services Staged Delivery ebXML OC4J OC4J Exchange Client Era Exchange Exchange services

  26. eRA eXchange Overview Today Other NIH Internal Systems Grants.gov NCI ? eRA eXchange HERMES ebMS NCRR Package Handlers Common Services API NLM Trading Partner System Transaction Handlers Staged Delivery Authorization registry Virus Checking Management Audits Reporting Validation Service Routing Grants.gov WSDL eRA Systems Exchange Services eRA- HERMES HERMES ebMS E- Notification HERMES ebMS API eCGAP Format API WSDL Business Applications Partner System Interface Message Processors eRA SAN ebMS Server Audits Registration ebMS Client eRA Bus Data

  27. eRA Exchange –Components • Multiple message handlers • Hermes is used to provide messaging services • Grants.gov toolkit – web services for intake • Current CGAP intake, WSDL web services • eXchange Common Services • Validation, virus checking, routing • Authorization • Audits • Leveraging open source solutions

  28. eRA eXchange “client” (local server) • Based on HERMES • Full service ebMS message handler • Open source, fully distributable • eRA enhancements • Simplified API to send and receive messages • Configured to connect to eRA Exchange • Registry interface • eXchange interface • 2 Step message intake for large payloads • Queues to buffer messages and protect business systems

  29. eXchange Business Services • Integration with the eRA eXchange client • Message payload processors • Interface with eRA database and business systems • Pluggable XML-driven data persistence • PDF document handling and generation • next – XML-driven versioning and validation • next – Rules engine integration (DROOLS)

  30. Rule Driven Transaction Handling Transaction Delivery Handling 7 Match Transaction Type to Rule-base through enveloping 6 Persist Rules for SQL Delivery 1 Oracle API Structure validation Business Rules Triggers SQL tables 5 SQL commands 4 2 3 Application XML content XML-based error outputting XSD schema Result logging Dynamic Structure rules Email notifications Rule Driven Error Reporting Structure sub-components with includes allows re-use 8 Error Logging

  31. Rule Components Transparency Single Controlling Integrated XML Script CAM Structure 2 Transaction Delivery Match Transaction Type to Rule-base through enveloping 1 DROOLS CPA pairs Rules 3 Persist Rules for SQL Table Updates X-DB Config Structure validation Business Rules 4 Error Output XSLT SQL commands 4 2 3 5 XML-based error outputting Result logging Open Public Specification + Open Source Dynamic Structure rules Email notifications Rule Driven Error Reporting 5 Error Logging

  32. Linkage Between Messaging and CPA • Messaging envelope contains: • Sender name • Service / Action names • Sender CPA id value • Receiver CPA id value • Optional certificate • CPA validation contains: • CPA id lookup to registry • Verifies sender • Verifies valid Service / Action pairs for this partner • Coupling from Service / Action to transaction validation • Coupling from Service / Action to backend delivery • Verify certificate

  33. Role of the Registry for eRA Information Dissemination to all Trading Partners • Trading partner management • Registration of trading partners with NIH • Authorization to do e-business with NIH • Authentication integrated with COMMONS • Simplified management of CPAs • Self service management of SP capabilities & certifications • Metadata management • All XML schemas for transactions • All trading partner capabilities (including all of NIH services) • Definition of data elements in each transaction • Instructions, documentation, and other • Version management of objects in registry

  34. Timelines Schedule of Deliverables

  35. eXchange Project Planning Grants.gov interfacing WSDL + Hermes Rules Engine 2000 Grant Apps Hermes client Business Semantics + Versioning Registry Integration Self-test Self- Installer + Certification Automated provisioning Metadata + Partner Profiles OCT NOV DEC JAN FEB MAR APR MAY 2006 2005

  36. Opportunity Summary Lessons learned; Technology Metrics

  37. Lessons Learned • Providing self-service facilities is key to rapid adoption • Infrastructure exists today off-the-shelf to create pre-built templates for industry domains • Using open specifications allows integration into wide range of environments • Open source solutions allows partners to readily obtain technology • Use of CPA id to manage partners and versioning

  38. Technology Metrics • Create infrastructure that can support large communities via registry-managed control mechanisms • Provide simple integration for external partners by providing open source solutions as base-line • Supports commercial tools that implement ebMS V2.0+ and web services • Built-in methods that allow centralized control over rules, versions, and delivery routing • Reasonable security without being overly inhibiting to adoption • Complete integrated audit trail logging • Using existing specifications and toolsets • Proven technology with wide adoption and reference deployments

  39. Opportunities • Provide infrastructure for application across a broad cross section of related agency and departmental areas: • HHS - Cancer Research Centers • CDC – Emergency Alerting systems • Navy – Medical Services coordination • FEMA – Emergency supply chain delivery • DHS – Intra-agency information sharing • EPA – External regulatory reporting • NSF – National Science Foundation Grants

  40. Q & A Discussion • AC-Technologies • For more information • Visit our Website: • http://www.ac-tech.com

  41. Project Resources • NIH eRA Project site – http://era.nih.gov • NIH Grants site - http://era.nih.gov/ElectronicReceipt/ • Commons online site – https://commons.era.nih.gov/commons/ • Grants.gov online site – http://www.grants.gov/GetStarted

  42. Software Components • Open Source components • ‘Hermes’ freebXML ebXML messaging server • ‘OMAR’ freebXML Registry system • jCAM content assembly mechanism and validation component with versioning capability • Oracle database server • Tomcat Server • Technology Specifications (ISO15000) • - http://ebxml.org • - http://oasis-open.org • - http://ebxmlbook.com/interop/

  43. Technology Resources • www.freebXML.orgwww.ebxml.orgwww.oasis-open.orgwww.ebxmlbook.com/interop www.ebxmlbook.com/benefitswww.ebxmlforum.org

More Related