Transcript Registry Managed Exchange

NIH
Web Services
Discovery
System and
B2B eXchange
SICoP Technology Briefing
NSF, Vienna, VA
January 2006
David RR Webber
[email protected]
SICoP Workshop Focus

How are We Building Collaboration Readiness and Discernment?
1.
How can multiple communities from diverse sectors work together
using relevant scenarios to build stewardship practices that support
readiness and realization of shared missions? (30JP)
2.
How is the emerging maturity of notation systems generally,
including the DRM v2.0, enabling multiple notation (modeling)
systems to reinforce and map to one another, while contributing to
current demands for real-time readiness and visibility of the "whole
picture"? (30JQ)
3.
How can the capacities of trust, agility, and accountability be
achieved through federated stewardship among communities still
building common ground and understanding? (30JR)
4.
How can Communities of Interest define their identities, roles, and
governance relationships in a manner that reinforces their
individual and collective capacities? (30JS)
2
Agenda

Business Objectives, History, Deliverables

Technology Approach

Technology Detail

Timelines

Opportunity Summary
3
Business
Objectives,
History,
Deliverables
Overview of Work
in Progress
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 subprojects 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:

SBIR/STTR totals:

Grand totals to date:
Submissions processed within the last 24 hours: 102
Grant images created within the last 24 hours: 25
Total SBIR/STTR submissions processed: 7932
Total SBIR/STTR grant images created: 1849
Total unique SBIR/STTR applications with outstanding validation errors: 517
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
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
Content
Security
Transport
Payload
Handling
Business
Systems
Workflow
14
Registry
Manage
Exchange Operational Details
Virus
Check
Staged
Network
Fire
Content
Wall
Transport
Synch
Asynch
Errors
Business
Certificates
Identity
MoUs
Profiles
Scripts
Dispatch
Industry
Handling
Semantics
Send
Workflow
Rules
Partners
Payload
Receive
Business
Systems
Security
Registry
Validation
Business
Rules
Errors
Events Actions
Role +
Context
Content
Versions
15
Scripts
Manage
Grants Implementation Overview
Government
Partners
1
Messages
5
Messages
Transport
ebMS
server
Applicant
Authority
Partner
transaction
authentication
CPA
check
data
validation
XML
Structure
Rules
Partner
Management
Web forms
CPA
instances
2
Proxy
Submission
Service
Provider
Oracle
database
Central
ebXML
Registry
CPA
instances
3
4
System
Administrators
Manage Partner
Interactions
Local Applicant
Company
16
(Persistent
Storage)
Service Provider view - single process
Institution Service Provider
REGISTRY
ebXML
HL7
Protocol
Authoring
Grant
Administration
Clinical Trial
System
AE reporting
Internal
Approvals &
Workflows
Personal
Profile and
Pub
management
ebXML
ebXML
Single User Interface or Site
Grant
application
Authoring
ebXML
ebXML
HL7
ebXML
17
Example: eRA and Grants.gov (Competitive Grants)
Applicant
Pure Edge
Forms
1
Grants.gov
Grants.gov
Intake &
Processing
2
eRA Exchange
eRA
ebXML
eRA eXchange
Intake
download
OPEN /
PLUGGABLE
eRA eXchange
XML validation
MONO
3
CLOSED
SYSTEM
6
eRA eXchange
Services &
eRA COMMONS
eRA COMMONS
Interface
Status
Validation results
Image Verification
Sign-Off
18
5
email
eRA eXchange
Services
Business Validation
DB Load
Image generation
4
Validation Results
Notification
E
R
A
Technology
Detail
Components,
Specifications and
Implementation
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
Network Infrastructure
ebXML delivery
Certification
Staged delivery
HL7 support
Service
Security
Authentication,
Message Transfer
Service
Validation, Routing
Roles
MoU
Persistence Queue
Registry of Rules
SQL
Certs
and Agreements
Queue Monitor
XML
DB
Dispatch Handler
Internal Applications
HL7/XML Data
Integration
Partner
Services
Management
Management
22
Nouns
Exchange Concurrent Processing Architecture
Load Balancing
External
1
Staged
Delivery
Agent
Notify
Sender A
Partner
Security
Services
4
Application
Process
Queuing
4
Request /
Response
Download
Queue
Publish
Payload
Staging
Area
2
Sender B
1
Requests
Payload
Responses
Dispatch
Services
Send
External
Dispatch
Agent
5
Receipt
Agent(s)
7
3
From: / To: filtering
Received
Queue
Subscribe
Partner
Security
Services
Delivery
Services
6
(Pluggable exchanges controlled
using Hermes messaging server –
using: WSDL, ebMS, AS/2, HL7)
23
Example Messaging Hub and B2B components
NIH
Single Sign On
Institution Service Provider
AE reporting
Internal
Approvals &
Workflows
Personal
Profile and
Pub
management
ebXML
services
eXchange
AUDITS
• Tracking
• Security
• Mgmt statistics
• Activity reports
ebXML
services
Processors
Research
Administrators
Applicants
Clinical Trial
System
eRA 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
OpDiv
Population
Tracking
NLM Pub
system
IRB Approvals,
Pop Tracking
AE reporting
NIH
24
eRA
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
Example: Grants.gov interfacing
Grants.Gov
Staged Delivery
OC4J
2. Send
pre-notification
ebXML
OC4J
4. Send notification
5. Request payload
Era Exchange
Exchange Client
6. Payload delivery
7. Delivery Status
8. Processing status
26
Exchange services
eRA eXchange Overview Today
Other
NIH Internal Systems
eRA eXchange
Grants.gov
Package Handlers
API
NLM
eRA Systems
Exchange
Services
Routing
Validation Service
Partner
System
Interface
WSDL
Reporting
eCGAP
Format
Management Audits
API
Virus Checking
HERMES
ebMS
Authorization registry
eRAHERMES
NCRR
Common Services
Staged Delivery
Grants.gov
WSDL
Transaction Handlers
Trading
Partner
System
HERMES
ebMS
Audits
Registration
ebMS
Client
eRA SAN
27
ENotification
API
Message
Processors
ebMS
Server
NCI ?
HERMES
ebMS
Business
Applications
eRA
Bus Data
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
Delivery
Persist
Rules
Business
for SQL
Rules
1
Structure
validation
Oracle
API
Triggers
SQL
tables
5
2
SQL
commands
4
3
Application
XML content
XML-based error outputting
XSD schema
Result logging
Dynamic
Structure rules
Structure sub-components
with includes allows re-use
Rule Driven
Error Reporting
Email notifications
8
Error
Logging
31
Rule Components
Transaction
Delivery
Config
1
Match Transaction
Type to Rule-base
through enveloping
Single
Controlling
Integrated
XML Script
CPA
pairs
Structure
CAM
2
Rules
DROOLS
3
Persist
Rules
Business
for SQL
Rules
Structure
validation
2
Transparency
SQL
commands
4
3
Table
Updates
X-DB
4
Error
Output
XSLT
5
XML-based error outputting
Result logging
Dynamic
Structure rules
Rule Driven
Error Reporting
Email notifications
5
Error
Logging
32
Open
Public
Specification +
Open Source
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

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
eXchange Project Planning
Grants.gov
interfacing
WSDL +
Hermes
OCT
2005
NOV
DEC
Rules
Engine
2000
Grant
Apps
Hermes
client
SelfInstaller +
Certification
Business
Semantics
+
Versioning
JAN
FEB
2006
36
MAR
Registry
Integration
Metadata +
Partner
Profiles
APR
Self-test
Automated
provisioning
MAY
Opportunity
Summary
Lessons learned;
Technology
Metrics
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
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.org
www.ebxml.org
www.oasis-open.org
www.ebxmlbook.com/interop
www.ebxmlbook.com/benefits
www.ebxmlforum.org
44