CONNECT 3.3 Overview webinar

triangledriprockInternet and Web Development

Aug 7, 2012 (5 years and 5 months ago)

363 views

CONNECT

Program

Discussion


July
7
, 2012

Agenda


Part 1


CONNECT 4.0 Implementation


Approved list of features


Requirements artifact status


Key technical changes and what these mean for the partners and
community


Development timeline, including changes since CCB and major
milestones


Assumptions and expectations of the partners and community


Key questions to partners


Custodial agent & development transition


Community outreach

2

Agenda


Part 2


Direct integration with CONNECT 4.0


Requirements


Use cases


Scope of the Direct feature


Supported transport scenarios


Transaction flow for Direct messages


Assumptions and constraints

3

CONNECT 4.0

Approved List of Features

4


Priority


(#1)


CONNECT adopters shall have the ability to increase throughput targeting increased



numbers of PD, QD, RD 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 performance 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)



Approved
by
CONNECT CCB
+ FHA Managing Board, May
2012 & FHA June 14th

CONNECT 4.0

Requirements Artifacts Status


CONNECT 4.0 RSD v 1.1


Features included
-

#1 to #6


Updates forthcoming to satisfy Section 508 compliance


CONNECT 4.0 RSD Addendum v TBD


Features included
-

#7


In draft, pending review and subsequent updates


Approval status



5

Stakeholder

CONNECT 4.0 RSD v1.x

CONNECT 4.0 RSD Addendum

CMS

Approved v1.0

Writing in progress

SSA

Approved v1.0

Writing in progress

DOD

Pending

Writing in progress

VA

Pending

Writing in progress

ONC

Approved v1.1

Writing in progress

CONNECT 4.0

Key Technical Changes


Removal of Metro web services tool


New work to support backwards compatibility/NwHIN Exchange
specification ambiguity


Creating cleaner lines between functionality


Support of WebSphere and WebLogic


Assessment of alternate open source application server


Support of Direct

6

CONNECT 4.0 Timeline

Changes Since May 16th CCB


Refined the CONNECT 4.0 requirements and
implementation LOEs


Added the CONNECT
-
Direct integration feature to
CONNECT 4.0 scope


Developed and released CONNECT 3.2.2 (6/11)


Developed and plan to release CONNECT 3.3.1 (7/27)


Budgeted hours to support an August 2012 Code
-
A
-
Thon


Accounted for the end of year holiday period


7

CONNECT 4.0

Development Timeline

Transaction & Logging Performance (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 5

June 18

Program Release
Support (1)

Direct (2)

4.0 IV&V (2)

Lightweight
Gateway (2)

4.0 Support & Transition (3 ½)

GA

Alpha 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)

CONNECT 4.0

Major Milestone
s


Alpha 1
-

10/5/12
-

Code release (IV&V can conduct testing)
-

contains releasable
source and binaries for Multi
-
Application Server Support, Large Payloads, and
Transaction & Performance Logging. Wiki design approach documentation for each of
the features will also be complete.


Alpha 2
-

12/7/12
-

Code release (IV&V can conduct testing)
-

contains releasable
source and binaries for Direct Integration and Lightweight Gateway. Wiki design
approach documentation for each of the features will also be complete.


Beta
-

1/2/13

-

CONNECT 4.0 having completed one cycle of Release Testing.
Release includes source, binaries, requirements specification, wiki design approaches,
design documents, installation instructions, test plans


GA


2/8/13

-

CONNECT 4.0 having completed three cycles of release testing and
IV&V. Release includes source, binaries, requirements specification, wiki design
approaches, design documents, installation instructions, test plans, test summary
report (Product team), test summary report (IV&V), release notes, and release support
activities (wiki, blogs, webinar materials)



Note
-

Within each block where a feature is named with (x) after it, the (x) refers to the number of
sprints the feature will take to complete in that block of time


9

CONNECT 4.0

Key Assumptions


Assumptions:


The Government fully funds the revised Option Year 1 budget


Product Team will remain the CONNECT custodial agent through the
release of CONNECT 4.0


Product Team will update the existing CONNECT C&A artifacts based
on the features in CONNECT 4.0, with no formal C&A testing cycle is
required


Product Team assumes no additional CONNECT patches are needed
for prior releases, beyond CONNECT 3.2.2 and 3.3.1


If the federal partners or community identify the need for additional patch
releases, the Product Team will produce a cost and time impact analysis for
CCB review before proceeding


Partners and community provide input via the CONNECT Community
Portal (Wiki) on design approaches and other key artifacts

10

CONNECT 4.0

Key Expectations


Expectations:


Each partner will identify one or more technical resources to attend
the bi
-
weekly Sprint Review and Planning Sessions and to review
design approaches and other development artifacts posted to the
CONNECT Community Portal at www.connectopensource.org


Each partner will review the plans and approaches for decoupling
CONNECT from Metro and replacing with Apache CXF


Each partner will identify development resources to download the
Alpha 1 release to assess what tweaks are needed by each agency to
deploy CONNECT 4.0 in their respective environments

11

Questions for Partners


Are the federal funding partners (FFP) planning to deploy
CONNECT 4.0 on WebSphere (WS) or WebLogic (WL)
when first deploying the CONNECT 4.0 release? Or are
any federal partners planning to remain initially with
GlassFish (GF) and transition to WS/WL at a later date?

12

Questions for Partners


Given the likelihood of the partners deploying CONNECT
4.0 on WS or WL, should the Product Team invest the
cycles to produce FIPS instructions for GF?

13

Questions for Partners


Is there a FFP who is willing to identify in
-
house
development resources to collaborate with the Product
Team to build out the process and document the
implementation of FIPS for a WebSphere
implementation?

14

Questions for Partners


CONNECT 4.0 will be packaged with Apache CXF in a
single EAR file that can be configured and deployed by
each adopter's development resources. In addition,
CONNECT will be deployable on the latest version of
WS/WL, and a TBD open source application server. Is
this implementation approach acceptable to each FFP?

15

Custodial Agent & Development
Transition (7 weeks, post CONNECT
4.0)



Product Team will collaborate on
-
site (as needed) with
each federal partner's development staff to transition
outstanding development activities


Product Team will support each partner (as needed) with
installing CONNECT 4.0 in their respective development
environments


What other activities would the partners like the Product
Team to assist with during the transition period following
the release of CONNECT 4.0?


16

CONNECT 4.0

Community outreach


CONNECT 4.0 awareness


Code
-
A
-
Thon


August 2012


“Next Release” webinar


July 2012 (tentative)


Open sprint review and planning meetings

17

18

Questions

+

Discussion

CONNECT

Program

Discussion
-

Direct

July
7
, 2012

Agenda


Direct integration with CONNECT 4.0


Requirements


Use cases


Scope of the Direct feature


Supported transport scenarios


Transaction flow for Direct messages


Assumptions and constraints

20

CONNECT 4.0 Support of Direct


June 14
th

FHA and ONC leadership approved the Direct
feature user story for inclusion in
CONNECT
4.0


“As
a CONNECT user I need CONNECT to integrate with and



support
the
Direct Project specifications.”


Work began on collecting requirements and creating the Direct
Addendum to the RSD for
CONNECT
4.0


The Addendum is a separate document however the Addendum is
reliant on the RSD and its content


Business purpose


Provide both Exchange and Direct capabilities in one solution


Increase potential use cases and data exchange partners for existing
CONNECT adopters


Provide an additional method of meeting Meaningful Use Stage 2
requirement of supporting Direct




21

CONNECT 4.0 Support of Direct

Use Cases


Problem: Direct sender is unable to communicate with an
Exchange partner


Dr. John is only able to send using Direct transport


Exchange partner only understands Exchange specifications









Use Case 1 to be supported: CONNECT adopter/recipient receives a
Direct message from a Direct sender

22

Dr. John

(Direct
Sender)

NHIO

(Exchange partner)

Govt. sponsored
facilities

(Exchange partner)

CONNECT 4.0 Support of Direct

Use Cases


Problem: Exchange partner is unable to communicate
with a Direct recipient


Dr. John is only able to accept messages using Direct transport


Exchange partner only understands Exchange specifications









Use Case 2 to be supported: CONNECT adopter/sender sends a
Direct message to a Direct recipient








23

Dr. John

(Direct
recipient)

NHIO

(Exchange partner)

Govt. sponsored
facilities

(Exchange partner)

CONNECT 4.0 Support of Direct

Scope of the Direct Feature


Support of approved Direct specifications and transports


Applicability Statement for Secure Health Transport specification


XDR and XDM for Direct Messaging specification


Transports


SMTP/RFC 5322+MIME


SMTP/RFC 5322+XDM


SOAP+XDR


Integrate Direct RI (JAVA) functionality with CONNECT


Direct HISP functionality


Selectable installation (i.e., install CONNECT with Direct and without
Direct)


New or updated interfaces to support the scoped scenarios


Perform audit logging on Direct traffic


Collect performance metrics data for Direct messages






24

CONNECT 4.0 Support of Direct

Supported Transport Scenarios

25

CONNECT 4.0 Support of Direct

Supported Transport Scenarios

26

The scope of this enhancement will be limited to the scenarios
below:

1.
Push from Sender (SMTP/RFC 5322+MIME) to Recipient (SMTP/RFC 5322+MIME) via
(SMTP/RFC 5322+ MIME)

2.
Push from Sender (SMTP/RFC 5322+MIME) to Recipient (SMTP/RFC 5322+XDM) via
(SMTP/RFC 5322+MIME). Recipient is expected to handle non
-
XDM package.

3.
Push from Sender (SMTP/RFC 5322+XDM) to Recipient (SMTP/RFC 5322+XDM) via
(SMTP/RFC 5322+XDM)

4.
Push from Sender (SMTP/RFC 5322+XDM) to Recipient (SMTP/RFC 5322+MIME) via
(SMTP/RFC 5322 +XDM). Recipient is expected to handle XDM package.

5.
Push from Sender (SOAP+XDR) to Recipient (SMTP/RFC 5322+MIME) via (SMTP/RFC
5322 +XDM). Recipient is expected to handle XDM package.

6.
Push from Sender (SOAP+XDR) to Recipient (SMTP/RFC 5322 +XDM) via (SMTP/RFC
5322 +XDM).

Note
1
: Additionally
in
scenarios #
3
, #4, #5
and
#6
, there will exist the capability/option in CONNECT
to process the XDM content as XDR.

Note
2
: Current
Exchange scenario in CONNECT for Document Submission will continue to be
supported i.e. Push from Sender (via DS interface) to Exchange Recipient (SOAP+DS) using (SOAP
+DS).

CONNECT 4.0 Support of Direct

Transaction Flow for Direct Messages

27

CONNECT
(
INITIATING GATEWAY
)

SMTP
/
RFC
5322
+
MIME
SMTP
/
RFC
5322
+
MIME
DIRECT REFERENCE
IMPLEMENTATION
CONNECT
(
RESPONDING GATEWAY
)
DIRECT REFERENCE
IMPLEMENTATION
CONNECT
ADOPTER
/
SENDER
CONNECT
ADOPTER
/
RECIPIENT
SOAP
+
XDR
CONNECT
ADOPTER
/
SENDER
CONNECT
ADOPTER
/
RECIPIENT
SMTP
/
RFC
5322
+
XDM
ADAPTER
SOAP
+
DS
(
Exchange
)
ADAPTER
SMTP
/
RFC
5322
+
XDM
PROCESS XDM AS
XDR
S
/
MIME encrypted
(
SMTP
/
RFC
5322
+
MIME
)
S
/
MIME encrypted
(
SMTP
/
RFC
5322
+
XDM
)
SOAP
+
DS
(
Exchange
)
S
/
MIME encrypted
(
SMTP
/
RFC
5322
+
XDM
)
PROCESS XDM AS
XDR
SMTP
/
RFC
5322
+
XDM
CONNECT
(
INITIATING GATEWAY
)
DIRECT REFERENCE
IMPLEMENTATION
CONNECT
(
RESPONDING GATEWAY
)
DIRECT REFERENCE
IMPLEMENTATION
SOAP
+
DS
(
Exchange
)
CONNECT 4.0 Support of Direct

Assumptions & Constraints


Key assumptions


Selected Direct RI will handle the STA, Mail Server and XDM / XDR conversion


CONNECT 4.0 will only support currently approved Direct specifications


Selected Direct RI contains support for the storing and retrieving of certificates
which will be independent from the Exchange certificate model


Current Direct production model will be followed for locating Direct provider
addresses


Correlating two independent Direct messages will not be supported in CONNECT
4.0 since functionality is not addressed in the current Direct specifications


Direct payload size will be determined by the Direct RI
-

Mail Server


Key constraints


For CONNECT 4.0, SOAP use cases will be restricted to the scenarios (SOAP to
SMTP) but will not include (SMTP to SOAP)


All Direct assumptions and constraints detailed for the pilot implementation will also
apply to CONNECT 4.0



28

29

Questions

+

Discussion

Appendix


Reference slides + background materials follow

30

CONNECT 4.0

Priorities from May 16 CCB

31


Priority


(#1)


CONNECT adopters shall have the ability to increase throughput targeting increased numbers of PD,



QD, RD 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 performance 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)


As a CONNECT user I need CONNECT to integrate with and support the DIRECT Project specifications


(GW
-
860)





(#8)


CONNECT adopters shall have the ability to provide a generic feed to their monitoring systems to assist


with the notification of gateway performance
(GW
-
452)


(#9)


CONNECT adopters shall be able to call a simpler interface (well defined API Adapter to Gateway) to



integrate with CONNECT as quickly and as simply as

possible
(GW
-
1194)



Scope line for
inclusion in 4.0. Approved
by
CONNECT CCB
+ FHA Managing Board, May
2012 & FHA June 14th

Features below line are not scheduled for inclusion in a release.