NIH Web Services Discovery System and B 2 B e. Xchange Technology Briefing Vienna, VA October 2005 David RR Webber webberd@od. nih. gov
Agenda n Business Objectives, History, Deliverables n Technology Approach n Technology Detail n Timelines n Opportunity Summary 2
Business Objectives, History, Deliverables Overview
NIH e. RA – Competitive Grants Applications n Currently handling about 2, 000 pieces of paper annually – scanning to digital images n Web front door - “Commons” system: w Number of Commons Logons: FY 2004: 565, 344 FY 2005 to present: 946, 330+ w Registered Organization (All) = 2884, and Registered Persons - 45334 n Grants applications posted electronically w e. SNAP - FY 2003 = 329 FY 2004 = 2, 854 Since 10/1/2004 = 5783+ w The total number of FSRs processed (internal and external) = 54657 4
e-CGAP: Electronic Competitive Grant Application Process n Paperless grant applications and all post submission downstream processing n Extending a seamless grant workflow into the external community n Promote the concept of service provider n Leads to need for system to system interfaces and data streams n Which leads to the use of business to business electronic commerce concepts and standards n HHS Award Winning effort 5
Need to provide a common view The typical grant applicants’ challenge Juggling all the various different formats and procedures 6
Transactions in place n Submission of modular grants n Submission of full budget grants (no subprojects or consortia) n Validation result returned to Submitter system n Validation service before submission n Grant image generation by NIH n View and approve generated image for sign-off of submission (web GUI) n Investigator Personal profile query and update n Status inquiries in grant workflow processing n Notification of peer review assignment 7
Beyond Grants Applications n The ability to interface quickly and easily to external parties with limited resources is not just a grants applications need n Secure reliable verifiable common communications infrastructure based on open public specifications n Other potential applicable areas: w HHS - Cancer Research Centers w CDC – Emergency Alerting systems w NSF – National Science Foundation grants w Navy – Medical Services coordination w FEMA – Emergency supply chain delivery w DHS – Intra-agency information sharing w EPA – External regulatory reporting 8
Technology Approach Overview of Architecture and Components
Leveraging Open Standards n Combining best-of-breed solution with both eb. XML and Web services working together n Open source solution components to allow unrestricted integration by partners n Foundation of eb. XML formal interchange model n Leveraging loose coupling of web services 10
Exchange Functional Components Network Content Security Transport Payload Handling Business Systems Workflow 11 Registry Manage
Exchange Operational Details Virus Check Staged Network Fire Content Wall Certificates Transport Synch Asynch Identity Mo. Us Profiles Partners Payload Semantics Receive Business Systems Industry Handling Errors Business Security Scripts Dispatch Send Workflow Rules Registry Validation Business Rules Errors Events Actions Role + Context Content Versions 12 Scripts Manage
Grants Implementation Overview Government Partners 1 Messages Transport eb. MS server Applicant Authority 5 Partner transaction authentication CPA check data validation XML Structure Rules Partner Management Web forms CPA instances 2 Proxy Submission Service Provider Oracle database Central eb. XML Registry CPA instances 3 4 System Administrators Manage Partner Interactions Local Applicant Company 13 (Persistent Storage)
Service Provider view - single process Institution Service Provider REGISTRY eb. XML HL 7 Protocol Authoring Grant Administration Clinical Trial System AE reporting Internal Approvals & Workflows Personal Profile and Pub management eb. XML Single User Interface or Site Grant application Authoring eb. XML HL 7 eb. XML 14
Example: e. RA and Grants. gov Applicant Grants. gov Intake & Processing Pure Edge Forms 1 2 e. RA Exchange e. RA e. Xchange Services & e. RA eb. XML e. RA e. Xchange Intake download e. RA e. Xchange XML validation 3 Web 6 form s int erfac e e. RA COMMONS Interface Status Validation results Image Verification Sign-Off 15 5 email e. RA e. Xchange Services Business Validation DB Load Image generation 4 Validation Results Notification E R A
Technology Detail Components, Specifications and Implementation
Information Exchange Integration requirements n Outward facing messaging systems n Formal agreement profiles for business participants n Business process workflow definitions n Information exchange rules n Registry to hold agreements, definitions, scripts… n Internal integration routing and dispatch methods n User interfacing for entry and control 17
B 2 B Exchange Design Goals n Automated registration of participants n Ability to self-certify exchange transactions n Version control and ability to approve partners n Centralized registry for participant management n Declared and shared business rule scripting n Integration through messaging services n Backend application integration services n Uses open public specifications and open source 18
Architecture Needs Overview Web service delivery Network Infrastructure eb. XML delivery Certification Staged delivery Service Security Authentication, Message Transfer Service Validation, Routing Roles Mo. U Persistence Queue Registry of Rules SQL Certs and Agreements Queue Monitor XML DB Dispatch Handler HL 7/XML Data Internal Applications Integration Partner Services Management 19 Nouns
Conceptual Messaging Hub and B 2 B components NIH Single Sign On Institution Service Provider AE reporting Internal Approvals & Workflows Personal Profile and Pub management eb. XML services e. Xchange AUDITS • Tracking • Security • Mgmt statistics • Activity reports eb. XML services Processors Research Administrators Applicants Clinical Trial System e. RA Personal Profile Message Clinicians Grant Administration Processors Trainees Grant application Authoring Protocol Authoring Application Receipt and Review • Partner Information • Exchg Agreements • Transactions Def • Bus process info • Authorizations Message Fellows Single User Interface or Site Researchers REGISTRY Grant Management Internal Workflow IC Op. Div Population Tracking NLM Pub system IRB Approvals, Pop Tracking AE reporting NIH 20 e. RA
Technical discussion of the e. Xchange n Exchange context n Exchange components w 4 major components ü e. RA e. Xchange Client ü e. RA e. Xchange Services ü e. RA Registry n eb. XML n Web services 21
Example: Grants. gov interfacing i eb W v er s e G 1. es c n tio lis ica pl p ta OC 4 J n tio a lic pp ta e. G 3 Grants. Gov t m fir on n io at Staged Delivery c 9. 2. Send pre-notification eb. XML 4. Send notification 5. Request payload Era Exchange OC 4 J Exchange Client 6. Payload delivery 7. Delivery Status 8. Processing status 22 Exchange services
e. RA e. Xchange Overview Today Other NIH Internal Systems e. RA e. Xchange Grants. gov Package Handlers API NLM e. RA Systems Exchange Services Routing Validation Service Partner System Interface WSDL Reporting e. CGAP Format Management Audits API Virus Checking HERMES eb. MS Authorization registry e. RAHERMES NCRR Common Services Staged Delivery Grants. gov WSDL Transaction Handlers Trading Partner System HERMES eb. MS Audits Registration eb. MS Client e. RA SAN 23 ENotification API Message Processors eb. MS Server NCI ? HERMES eb. MS Business Applications e. RA Bus Data
e. RA Exchange – Components n Multiple message handlers w. Hermes is used to provide messaging services w. Grants. gov toolkit – web services for intake w. Current CGAP intake, WSDL web services n e. Xchange Common Services w. Validation, virus checking, routing w. Authorization w. Audits n Leveraging open source solutions 24
e. RA e. Xchange “client” (local server) n Based on HERMES w. Full service eb. MS message handler w. Open source, fully distributable n e. RA enhancements w. Simplified API to send and receive messages w. Configured to connect to e. RA Exchange n Registry interface n e. Xchange interface w 2 Step message intake for large payloads w. Queues to buffer messages and protect business systems 25
e. Xchange Business Services n Integration with the e. RA e. Xchange client n Message payload processors n Interface with e. RA database and business systems 26
Message Flow Sequence Diagram 27
Linkage Between Messaging and CPA n Messaging envelope contains: n CPA validation contains: w Sender name w Service / Action names w Sender CPA id value w Receiver CPA id value w Optional certificate w CPA id lookup to registry w Verifies sender w Verifies valid Service / Action pairs for this partner w Coupling from Service / Action to transaction validation w Coupling from Service / Action to backend delivery w Verify certificate 28
Role of the Registry for e. RA n Trading partner management w. Registration of trading partners with NIH n Authorization to do e-business with NIH n Authentication integrated with COMMONS w. Simplified management of CPAs w. Self service management of SP capabilities & certifications n Metadata management w. All XML schemas for transactions w. All trading partner capabilities (including all of NIH services) w. Definition of data elements in each transaction w. Instructions, documentation, and other n Version management of objects in registry 29
Timelines Schedule of Deliverables
e. Xchange Project Planning Grants. gov interfacing WSDL + Hermes Rules Engine Hermes client Self. Installer + Certification Business Semantics + Versioning AUG SEP OCT NOV DEC JAN 2005 2006 31 Registry Integration Metadata + Partner Profiles FEB MAR Self-test Automated provisioning
Grants. gov Interfacing Schedule 32
Opportunity Summary Lessons learned; Technology Metrics
Lessons Learned n Providing self-service facilities is key to rapid adoption n Infrastructure exists today off-the-shelf to create pre-built templates for industry domains n Using open specifications allows integration into wide range of environments n Open source solutions allows partners to readily obtain technology n Use of CPA id to manage partners and versioning 34
Technology Metrics n Create infrastructure that can support large communities via registry-managed control mechanisms w Provide simple integration for external partners by providing open source solutions as base-line w Supports commercial tools that implement eb. MS V 2. 0+ and web services w Built-in methods that allow centralized control over rules, versions, and delivery routing w Reasonable security without being overly inhibiting to adoption w Complete integrated audit trail logging n Using existing specifications and toolsets w Proven technology with wide adoption and reference deployments 35
Opportunities n Provide infrastructure for application across a broad cross section of related agency and departmental areas: w HHS - Cancer Research Centers w CDC – Emergency Alerting systems w Navy – Medical Services coordination w FEMA – Emergency supply chain delivery w DHS – Intra-agency information sharing w EPA – External regulatory reporting w NSF – National Science Foundation Grants 36
Q&A Discussion AC-Technologies For more information Visit our Website: http: //www. ac-tech. com
Project Resources n NIH e. RA Project site – http: //era. nih. gov n NIH Grants site - http: //era. nih. gov/Electronic. Receipt/ n Commons online site – https: //commons. era. nih. gov/commons/ n Grants. gov online site – http: //www. grants. gov/Get. Started 38
Software Components n Open Source components w‘Hermes’ freeb. XML messaging server w‘OMAR’ freeb. XML Registry system wj. CAM content assembly mechanism and validation component with versioning capability n Oracle database server n Tomcat Server n Technology Specifications (ISO 15000) w- http: //ebxml. org w- http: //oasis-open. org w- http: //ebxmlbook. com/interop/ 39
Technology Resources n www. freeb. XML. org www. ebxml. org www. oasis-open. org www. ebxmlbook. com/interop www. ebxmlbook. com/benefits www. ebxmlforum. org 40
Скачать презентацию NIH Web Services Discovery System and B 2
669492440f96fb1a1c46cf832f7bc066.ppt