CONNECT 4.0 July 26, 2012. Webinar Technical Details 2 Type questions in advance; click...
-
Upload
scarlett-murphy -
Category
Documents
-
view
215 -
download
0
Transcript of CONNECT 4.0 July 26, 2012. Webinar Technical Details 2 Type questions in advance; click...
CONNECT 4.0July 26, 2012
Webinar Technical Details
2
Type questions in advance; click send Questions + answers appear in chat window
During discussion time, “raise hand” to speak
I’ve written a hook to a major EMR. Can Icontribute the code?
I’ve written a hook to a major EMR. Can Icontribute the code?
Introduction
Brian HumphreyCONNECT Architect
Greg TurnerCONNECT 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
7
CONNECT BUILDING BLOCKS
Master Patient Index System (MPI)
Master Patient Index System (MPI)
Document RegistryDocument Registry
Document RepositoryDocument Repository
Policy EnginePolicy Engine
EHR/HIE Implementation System
System that wishes to CONNECT to Nationwide
Health Information Network
CONNECT
EHR/HIEImplementation Adapter Service
Creates/sends messages to CONNECT and
receives/processes and responds to messages from
CONNECT.
Nationwide Health Information Network
Regional Health Information
Organizations
Regional Health Information
Organizations
Government sponsored facilities
Government sponsored facilities
Disease-orientedcare networks
Disease-orientedcare networks
Federation of enterprises (hospitals and care providers)
Federation of enterprises (hospitals and care providers)
Other Communitiesof Care
Other Communitiesof 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)
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)
10
#1 – Increase Throughput for CONNECT
FEATURE
CONNECT adopters shall have the ability to increase throughput targeting increased numbers of PD, QD, RD, AD and DS transactions
BENEFITS
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
CONNECT adopters shall have the ability to exchange and process large payload sizes of up to 1 GB
BENEFITS
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
FEATURE
#3 – Support for Multiple App Servers
CONNECT adopters shall have the ability to run on additional application servers such as WebSphere and WebLogic to meet their environment needs
BENEFITS
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.
13
FEATURE
CONNECT Messaging Component Diagram
14
DS Deployment Diagram
15
CONNECT Client Class Diagram
16
= other JAX-WS options(community or future development
#4 – Event Logging
CONNECT adopters shall have the ability to get more comprehensive event logging and metric data (counts and duration) using improved logging in CONNECT
BENEFITS
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
FEATURE
Inbound Life Cycle Event State Diagram
18
Event Logging Sequence Diagram
19
#5 – Transaction Logging
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
BENEFITS
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
20
FEATURE
#6 – Lightweight Gateway
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
BENEFITS
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 community-contributed adapter layers – to EMRs & etc.
21
FEATURE
Path to a Lightweight Gateway
22
AdapterCurrent
Functionality
GatewayCurrent
Functionality
GatewayLighter Gateway
AdapterCurrent
Functionality
AdapterMigrated Gateway
Functionality
GatewayLighter Gateway
AdapterCurrent & Migrated
Functionality
#7 – Direct Integration with CONNECT
CONNECT adopters shall have the ability to support Direct messages to allow for greater adoption and exchange
BENEFITS
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
FEATURE
More Details on CONNECT 4.0
https://developer.connectopensource.org/display/CONNECTWIKI/Release+4.0+-+In+Progress
https://developer.connectopensource.org/display/CONNECTWIKI/Requirements+Artifacts
https://developer.connectopensource.org/display/CONNECTWIKI/CONNECT+4.0+Design+Approaches
http://issues.connectopensource.org
http://www.connectopensource.org/developer-resources/forums/developer-forum
24
Release info:
Requirements artifacts:
Design approach documents:
JIRA:
Forums:
Product Roadmap – Getting There
25
CONNECT 4.0 Development Timeline
26
Transaction & Event Logging 4)
Direct (2)
Lightweight Gateway (2)
3.3.1 Release (3)
Remove Metro Dependency (3)Large Payload (3)
WebSphere (2)WebLogic (2)Open Source App Server (1)
Alpha 1
July 16 Aug 13 Sep 10 Oct 9 Nov 5June 18
Direct (2)
4.0 IV&V (2)
Lightweight Gateway (2)
4.0 Support & Transition (3 ½)
CONNECT 4.0Alpha 2
Nov 5 Dec 10 Jan 14 Feb 11 Mar 11 Mar 31
Beta
4.0 Release Testing P1 & P2 (3)
= 1 sprint (2 weeks)
Useful Links
www.connectopensource.org
https://developer.connectopensource.org
https://github.com/CONNECT-Solution/CONNECT
mailto:[email protected]
Contributing code:https://developer.connectopensource.org/display/CONNECTWIKI/Contributing+Code
Sprint info:https://developer.connectopensource.org/display/NHINProgress/Progress+Summary+Page
27
Join Us for Sprint Review/Planning
28
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 ETTel: 646-216-4772 866-946-0485 Participant Code 922 914 63Web: https://arkadin.webex.com/arkadin/j.php?J=703876882 (meeting id 703 876 882)
Upcoming Community Events
July 26, 2012 (11am ET)Webinar on CONNECT 4.0
July 30, 2012 (10am ET)Next sprint review/planning meeting
August 1, 2012CONNECT Release 3.3.1
August 16-17, 2012CONNECT Code-a-Thon
29
Questions and Discussion
30
Webinar Technical Details
31
Type questions in advance; click send Questions + answers appear in chat window
During discussion time, “raise hand” to speak
Can I upgrade to CONNECT 3.3 without changing any current CONNECT hooks?