CONNECT 4.0
July 26, 2012
Webinar Technical Details
I’ve written a hook to a major EMR. Can I
contribute the code?
During discussion
time, “raise hand”
to speak
I’ve written a hook to a major EMR. Can I
contribute the code?
Type questions in advance; click send
2
Questions + answers appear in chat window
Introduction
Brian Humphrey
CONNECT Architect
Greg Turner
CONNECT Product Manager
3
What is CONNECT?
4
What is CONNECT?
CONNECT is an open-source solution to
support health information exchange (HIE).
CONNECT uses Nationwide Health
Information Network standards to ensure
HIEs interoperate with other current and
future exchanges.
CONNECT can be used to:
• Set up a HIE within an organization.
• Tie a health information exchange into
other HIEs including the Exchange.
5
CONNECT Building Blocks
CONNECT sits between the HIE
implementation system and can interface
with the NwHIN Exchange.
CONNECT sends messages to the Exchange or
any user of the NwHIN specs, and receives
messages from the network on behalf of the
adopter.
A CONNECT adopter is required to create
or implement services called adapter
services that allow for processing the
messages to and from CONNECT. This
includes error handling where necessary.
CONNECT provides reference adapters that
include sample code on how to connect back-end
systems to CONNECT using adapter services.
6
CONNECT Building Blocks
CONNECT BUILDING BLOCKS
EHR/HIE
Implementation System
System that wishes to
CONNECT to Nationwide
Health Information
Network
Nationwide Health
Information Network
CONNECT
Government
sponsored facilities
Master Patient Index
System (MPI)
Document Registry
Document Repository
Policy Engine
7
Regional Health
Information
Organizations
EHR/HIE
Implementation
Adapter Service
Creates/sends messages to
CONNECT and
receives/processes and
responds to messages from
CONNECT.
Disease-oriented
care networks
Federation of
enterprises (hospitals
and care providers)
Other Communities
of Care
CONNECT is Open Source Software
• Open source license
• Open release planning, sprint review
and planning sessions
• Community contributions welcomed
- Bug reports + fixes
- Features requests + implementations
• FHA-sponsored Product Management,
Curation, + Development
• Transitioning to community-managed
open-source project model
8
CONNECT 4.0
9
CONNECT 4.0 Approved Features
1) CONNECT adopters shall have the
ability to increase throughput targeting
increased numbers of PD, QD, RD, AD
and DS transactions (GW-451)
2) CONNECT adopters shall have the
ability to exchange and process large
payload sizes of up to 1 GB (GW-473)
3) CONNECT adopters shall have the
ability to run on additional application
servers such as WebSphere and
WebLogic to meet their environment
needs (GW-2402)
4) CONNECT adopters shall have the
ability to get more comprehensive event
logging and metric data (counts and
duration) using improved logging in
CONNECT (GW-2260 and GW-1252)
10
5) CONNECT adopters shall be able to
determine the state of a transaction
across messages in order to better
troubleshoot and analyze the operation of
CONNECT and their trading partners
(GW-2259)
6) CONNECT adopters shall have the
ability to minimize deployment load by
supporting a lightweight gateway which
allows smaller server footprint and use of
system resources and allows the federal
partners to maximize the use of their
custom-built adapters (GW-1593)
7) CONNECT adopters shall have the
ability to support Direct messages to
allow for greater adoption and exchange.
(GW-860)
#1 – Increase Throughput for CONNECT
BENEFITS
FEATURE
CONNECT adopters shall
have the ability to increase
throughput targeting
increased numbers of PD,
QD, RD, AD and DS
transactions
More efficiency of gateway at
higher volumes
Support more widespread or
national rollout plans for health
data exchange
Better utilization of adopter
infrastructure
11
#2 – Large Payload Support
BENEFITS
FEATURE
CONNECT adopters shall
have the ability to
exchange and process
large payload sizes of up
to 1 GB
Increased ability to support the
data exchange needs of more
adopters
Enable additional use cases that
require the exchange of larger
file sizes
Positive impact on performance
of gateway when handling larger
payloads
12
#3 – Support for Multiple App Servers
BENEFITS
FEATURE
CONNECT adopters shall
have the ability to run on
additional application
servers such as
WebSphere and
WebLogic to meet their
environment needs
13
More deployment options
Model for the community to add
support for other app servers
Adopters can use their preferred
app servers and take advantage
of internal sysadmin expertise for
things like security, scalability, etc.
CONNECT Messaging
Component Diagram
14
DS Deployment Diagram
15
CONNECT Client Class Diagram
= other JAX-WS options
(community or future
development
16
#4 – Event Logging
BENEFITS
FEATURE
CONNECT adopters shall
have the ability to get
more comprehensive
event logging and metric
data (counts and
duration) using improved
logging in CONNECT
Allows adopters to better understand
usage and performance
Supports better planning and
management of deployment
Provides opportunity for automated
monitoring
Provides opportunity for dynamic
scaling based on load
17
Inbound Life Cycle Event State Diagram
18
Event Logging Sequence Diagram
19
#5 – Transaction Logging
BENEFITS
FEATURE
CONNECT adopters shall
be able to determine the
state of a transaction
across messages in order
to better troubleshoot
and analyze the operation
of CONNECT and their
trading partners
20
Provides a more holistic view of a
complete transaction with any given
exchange partner
Increased insight for troubleshooting
and issue resolution
More input for transaction
management and planning
#6 – Lightweight Gateway
BENEFITS
FEATURE
CONNECT adopters shall
have the ability to minimize
deployment load by
supporting a lightweight
gateway which allows
smaller server footprint
and use of system
resources and allows the
federal partners to
maximize the use of their
custom-built adapters
21
Adopters with capable back-end
systems can have a more lightweight
deployment footprint
Allows for more economical allocation
and use of infrastructure resources
Paves ground for communitycontributed adapter layers – to
EMRs & etc.
Path to a Lightweight Gateway
Adapter
Current
Functionality
Gateway
Current
Functionality
Adapter
Current
Functionality
Adapter
Current & Migrated
Functionality
Adapter
Migrated Gateway
Functionality
Gateway
Lighter Gateway
Gateway
Lighter Gateway
22
#7 – Direct Integration with CONNECT
BENEFITS
FEATURE
CONNECT adopters
shall have the ability to
support Direct
messages to allow for
greater adoption and
exchange
Fulfills Meaningful Use (Stage 2)
Provides a means to support both
NwHIN Exchange and Direct
transactions through one deployment
Offers a built-in growth or migration
path for additional use cases
Supports expanding federal,
commercial, and state and regional
HIE needs
23
More Details on CONNECT 4.0
Release info:
https://developer.connectopensource.org/display/CON
NECTWIKI/Release+4.0+-+In+Progress
Requirements
artifacts:
https://developer.connectopensource.org/display/CON
NECTWIKI/Requirements+Artifacts
Design approach
documents:
https://developer.connectopensource.org/display/CON
NECTWIKI/CONNECT+4.0+Design+Approaches
JIRA:
http://issues.connectopensource.org
Forums:
http://www.connectopensource.org/developerresources/forums/developer-forum
24
Product Roadmap –
Getting There
25
CONNECT 4.0 Development Timeline
July 16
June 18
Aug 13
Sep 10
Oct 9
WebSphere (2)
WebLogic (2)
Open Source App Server (1)
Remove Metro
Dependency (3)
Large Payload (3)
Lightweight
Gateway (2)
Direct (2)
3.3.1 Release (3)
Transaction & Event Logging 4)
Dec 10
Jan 14
Lightweight
Gateway (2)
4.0 Release Testing P1 & P2
(3)
Direct (2)
Alpha 2
26
Alpha 1
4.0 IV&V (2)
Feb 11
Program Release
Support (1)
Nov 5
Nov 5
Mar 11
Mar 31
4.0 Support & Transition (3 ½)
CONNECT 4.0
= 1 sprint (2 weeks)
Beta
Useful Links
www.connectopensource.org
https://developer.connectopensource.org
https://github.com/CONNECT-Solution/CONNECT
mailto:connect@hhs.gov
Contributing code:
https://developer.connectopensource.org/display/CONNECTWIKI/Contr
ibuting+Code
Sprint info:
https://developer.connectopensource.org/display/NHINProgress/Progre
ss+Summary+Page
27
Join Us for Sprint Review/Planning
Join us for sprint review and planning sessions, every other Monday, 10am-noon
ET beginning July 16.
The Connect product team will share the work of the last sprint for community review
and feedback. We’ll then transition into a high-level planning session to set the themes
for the coming sprint, in the context of the product roadmap. Community input and
insights are welcome, so please join us!
The approximate timeframe is a review between 10am and 11:30, followed by a half
hour planning discussion, but we will not hold fast to that time frame; instead we’ll flow
from one to the other based on content and conversation.
Sprint Review + Planning: Every other Monday (July 30, 2012) 10am-12pm ET
Tel: 646-216-4772 866-946-0485 Participant Code 922 914 63
Web: https://arkadin.webex.com/arkadin/j.php?J=703876882 (meeting id 703 876 882)
28
Upcoming Community Events
July 26, 2012 (11am ET)
Webinar on CONNECT 4.0
July 30, 2012 (10am ET)
Next sprint review/planning meeting
3.3.1
August 1, 2012
CONNECT Release 3.3.1
August 16-17, 2012
CONNECT Code-a-Thon
29
Questions and Discussion
30
Webinar Technical Details
During discussion
time, “raise hand”
to speak
Can I upgrade to CONNECT 3.3 without
changing any current CONNECT hooks?
Type questions in advance; click send
31
Questions + answers appear in chat window