CONNECT Codebase (2.x, 3.x, 4.x)
Switch branches/tags
sprint90 CONNECT_sprint_192 CONNECT_sprint_188 CONNECT_sprint_187 CONNECT_sprint_186 CONNECT_sprint_185 CONNECT_sprint_184 CONNECT_sprint_183 CONNECT_sprint_182 CONNECT_sprint_180 CONNECT_sprint_178 CONNECT_sprint_177 CONNECT_sprint_176 CONNECT_sprint_175 CONNECT_sprint_174 CONNECT_sprint_173 CONNECT_sprint_172 CONNECT_sprint_171 CONNECT_sprint_170 CONNECT_sprint_169 CONNECT_sprint_168 CONNECT_sprint_167 CONNECT_sprint_166 CONNECT_sprint_165 CONNECT_sprint_164 CONNECT_sprint_163 CONNECT_sprint_162 CONNECT_sprint_160 CONNECT_sprint_158 CONNECT_sprint_157 CONNECT_sprint_156 CONNECT_sprint_155 CONNECT_sprint_154 CONNECT_sprint_153 CONNECT_sprint_152 CONNECT_sprint_151 CONNECT_sprint_150 CONNECT_sprint_148 CONNECT_sprint_146 CONNECT_sprint_143 CONNECT_sprint_142 CONNECT_sprint_141 CONNECT_sprint_140 CONNECT_sprint_139 CONNECT_sprint_138 CONNECT_sprint_137 CONNECT_sprint_136 CONNECT_sprint_135 CONNECT_sprint_134 CONNECT_sprint_133 CONNECT_sprint_132 CONNECT_sprint_131 CONNECT_sprint_130 CONNECT_sprint_129 CONNECT_sprint_126 CONNECT_sprint_125 CONNECT_sprint_124 CONNECT_sprint_123 CONNECT_sprint_122 CONNECT_sprint_121 CONNECT_sprint_120 CONNECT_sprint_119 CONNECT_sprint_118 CONNECT_sprint_117 CONNECT_sprint_116 CONNECT_sprint_115 CONNECT_sprint_114 CONNECT_sprint_112 CONNECT_sprint_111 CONNECT_sprint_110 CONNECT_sprint_107 CONNECT_sprint_105 CONNECT_sprint_102 CONNECT_sprint_101 CONNECT_sprint_99 CONNECT_sprint_98 CONNECT_sprint_97 CONNECT_sprint_96 CONNECT_sprint_95 CONNECT_sprint_94 CONNECT_sprint_93 CONNECT_sprint_92 CONNECT_sprint_90 CONNECT_sprint_89 CONNECT_sprint_87 CONNECT_sprint_86 CONNECT_sprint_85 CONNECT_sprint_18_20170626 CONNECT_sprint_17_20170612 CONNECT_sprint_16_20170530 CONNECT_sprint_15_20170515 CONNECT_sprint_14_20170501 CONNECT_sprint_13_20170417 CONNECT_sprint_12_20170404 CONNECT_sprint_11_20170320 CONNECT_sprint_10_20170306 CONNECT_sprint_9_20170221 CONNECT_sprint_8_20170206 CONNECT_sprint_7_20170123 CONNECT_sprint_6_20170109
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.


CONNECT is an open source software solution that supports health information exchange - both locally and at the national level. CONNECT uses Nationwide Health Information Network standards and governance to make sure that health information exchanges are compatible with other exchanges being set up throughout the country.

This software solution was initially developed by federal agencies to support their health-related missions, but it is now available to all organizations and can be used to help set up health information exchanges and share data using nationally-recognized interoperability standards.


CONNECT is released under the Revised BSD License.


CONNECT can be used to:

  • Set up a health information exchange within an organization
  • Tie a health information exchange into a regional network of health information exchanges using Nationwide Health Information Network standards
  • Send and receive Direct messages; see: Setting up CONNECT as a Direct HISP

By advancing the adoption of interoperable health IT systems and health information exchanges, the country will better be able to achieve the goal of making sure all providers have access to patient health data. Health data will be able to follow a patient across the street or across the country.


Three primary elements make up the CONNECT solution:

  • The Core Services Gateway provides the ability to locate patients at other organizations, request and receive documents associated with the patient, and record these transactions for subsequent auditing by patients and others. Other features include mechanisms for authenticating network participants, formulating and evaluating authorizations for the release of medical information, and honoring consumer preferences for sharing their information. The Nationwide Health Information Network Interface specifications are implemented within this component.

  • The Enterprise Service Components provide default implementations of many critical enterprise components required to support electronic health information exchange, including a Master Patient Index (MPI), XDS.b Document Registry and Repository, Authorization Policy Engine, Consumer Preferences Manager, HIPAA-compliant Audit Log and others. Implementers of CONNECT are free to adopt the components or use their own existing software for these purposes.

  • The System Administration Module provides a graphical user interface (GUI) to simplify the configuration, support, and administration of the CONNECT solution. Key features include: graphical system overview, connection management, property and adapter configuration management, audit log viewer, Direct configuration, and the Cross-Gateway Query Client for testing basic message exchanges against other systems.


  • 5.0 released June 2017
  • 4.7 released September 2016
  • 4.6 released March 2016
  • 4.5 released July 2015
  • 4.4 released December 2014
  • 4.3 released March 2014
  • 4.2 released August 2013
  • 4.1 released April 2013
  • 4.0 released February 2013
  • 3.3 released March 2012

For more information about CONNECT's history, see

Building from Source

To build CONNECT from source run:

    $ mvn clean install

####Building an ear All services profiles are active by default, if you want to exclude a service, in this case Patient Discovery, you can turn off the profile by adding a "!" to the name of the service profile you'd like to exclude (needs to be escaped with "" char on *NIX) platforms:

    $ mvn clean install -P \!PD

You can also specify explicitly what services are included in the ear by passing in the individual profiles. For example, if you only want to include PD:

    $ cd Product/Production/Deploy/
    $ mvn clean install -P PD

For more information on CONNECT supported application servers build and deployment visit: Installation Instructions page.


After the CONNECT Gateway has been installed, the Validation Suite can be run to verify that the installation is working correctly.

To run Validation Suite via Maven script against a standalone installation of the application server:

    $ cd <CONNECT_CLONE_DIR>/Product/SoapUI_Test/ValidationSuite
    $ mvn verify -Dstandalone -Dproperties.dir=<application server configuration dir>

To execute Validation Suite via SoapUI, run the Validation Suite project file ConnectValidation-soapui-project.xml via SoapUI's command line runner (or testrunner.bat in Windows).

You can find more details at: CONNECT Validation Suite


###Generate & View You can generate the project's site information by performing the following:

    $ mvn -P\!embedded-testing site:site site:stage -DstagingSiteURL=/tmp/fullsite

Then open your browser and view [file:///tmp/fullsite/index.html]


Please checkout code contribution for guidelines about how to contribute.