NIH Web Services Discovery System and B2B eXchange Technology Briefing Vienna, VA October 2005 David RR Webber

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

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 Grants applications posted electronically  eSNAP - FY 2003 = 329 FY 2004 = 2,854 Since 10/1/2004 =  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 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 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

Technology Approach Overview of Architecture and Components

10 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

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

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

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

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

15 Example: eRA and Grants.gov Grants.gov Intake & Processing eRA eXchange Services Business Validation DB Load Image generation Validation Results Notification eRA COMMONS Interface Status Validation results Image Verification Sign-Off ERAERA ApplicantGrants.gov eRA COMMONS eRA Exchange eRA eXchange Services & eRA Pure Edge Forms eRA eXchange Intake eRA eXchange XML validation download Web forms interface ebXML

Technology Detail Components, Specifications and Implementation

17 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

18 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

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

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

21 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

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

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

24 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

25 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

26 eXchange Business Services Integration with the eRA eXchange client Message payload processors Interface with eRA database and business systems

27 Message Flow Sequence Diagram

28 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

29 Role of the Registry for eRA 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

Timelines Schedule of Deliverables

31 eXchange Project Planning AUGSEPOCTNOVDECJANFEBMAR Grants.gov interfacing WSDL + Hermes client Self- Installer + Certification Rules Engine Business Semantics + Versioning Registry Integration Metadata + Partner Profiles Self-test Automated provisioning

32 Grants.gov Interfacing Schedule

Opportunity Summary Lessons learned; Technology Metrics

34 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

35 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

36 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

Q & A Discussion AC-Technologies For more information Visit our Website:

38 Project Resources NIH eRA Project site – NIH Grants site Commons online site – Grants.gov online site –

39 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)  -  -  -

40 Technology Resources