...

• AD - Admin Distribution
• PD - Patient Discovery
• DQ - Document Query
• DR - Document Retrieve
• DS - Document Submission
• DDS - Document Data Submission (Pilot)
• X12 - Core X12
• Direct - Direct Core
• admingui - Administrative GUI *.WAR, and the corresponding web services into the compiled *.EAR.
• was - Enterprise Application Archive (EAR ) for websphere application server
• weblogic - Enterprise Application Archive (EAR ) for weblogic application server 
• jboss7 - Enterprise Application Archive (EAR ) for Jboss EAP 7 and wildfly application server.

How can I switch from MySQL to Oracle database?

...

Also a list of the interfaces can be found at - Service Interfaces

Exchange:

Can

...

CONNECT facilitate custom overrides for an exchange partner. You can define them in exchangeInfo.xml. Refer to CONNECT 5.1.2#Organizationalendpointoverride

How do I initiate exchange directory download?

CONNECT can download from web services registry from both UDDI  and FHIR directories. You can configure the download in exchangeInfo.xml. For more information see Exchange Manager#ConfiguringExchange and Sample exchangeInfo

How can I import eHealth Exchange Chain of Trust?

Importing the eHealth Exchange Chain of Trust

Can CONNECT 5.2 be used with FHIR Resources? Is there any way to incorporate Patient resources, Medication resources, etc.?

CONNECT 5.2 can GET organization resources from a FHIR STU3 compliant Directory. Other functionality has not been implemented into CONNECT.

While configuring multiple gateways do we need to configure ExchangeInfo and InternalExchangeInfo.xml?

ExchangeInfo.xml is used to communicate with other gateway while InternalExchangeInfo.xml is used for internal adapters within its own gateway. If you participate in ehealth exchange network, you don't need to change ExchangeInfo.xml since CONNECT pulls the latest UDDI/FHIR from UDDI/FHIR servers periodically.

How can I resolve third party Dependency DTD/SCHEMA URLs?

...

CONNECT 5.2 be used with FHIR Resources? Is there any way to incorporate Patient resources, Medication resources, etc.?

CONNECT 5.2 can GET organization resources from a FHIR STU3 compliant Directory. Other functionality has not been implemented into CONNECT.

Can I override exchange's partners endpoints locally?

CONNECT facilitate custom overrides for an exchange partner. You can define them in exchangeInfo.xml. Refer to CONNECT 5.1.2#Organizationalendpointoverride

Can I still demonstrate Patient Discovery, Doc Query, Doc Retrieve services using test data only, and without implementing a custom adapter?

You should be able to do Patient Discovery (PD), Query for Documents (QD) and Retrieve Documents (RD) with test data without any configuration if you have installed and configured your system as given in the CONNECT installation instructions. In this case, you get docs from local database. You can configure the hibernate config files if you want to install CONNECT database on different machine. If you want to use your own database with different schema/tables, you need customize the adapters.

Does Connect support other registry queries?

The CONNECT gateway does support these other XDS stored queries, however our reference adapters are limited to the "find documents" query. You must implement the other queries in your own adapter.

How can I import eHealth Exchange Chain of Trust?

Importing the eHealth Exchange Chain of Trust

How can I resolve third party Dependency DTD/SCHEMA URLs?

CONNECT uses Java JEE standard for developing all the Web/Web Service modules. The JEE web application/Enterprise application uses DTD/SCHEMA to verify the XML deployment descriptors used, which are specific to each application server vendor and these DTD/SCHEMA are hosted by the application vendor and referenced from CONNECT Web/Web Service applications. We recently noticed that one of the application server vendor's site (hosting these DTD/SCHEMAs) was down causing the CONNECT system to be down. For example, the sun.com site which was hosting some DTD/SCHEMA was down and due to this CONNECT was not deploying/working for one of the CONNECT users. Implementation teams can resolve this issue by doing any of the following:

...

<?xml version="1.0" encoding="UTF-8"?> 
<Configuration>
    <expirations defaultDuration="1" defaultUnits="YEAR">
        <expiration assigningAuthority='1.1' unit='YEAR'>10</expiration>
        <expiration assigningAuthority='2.2' unit='YEAR'>1</expiration>
    </expirations>
</Configuration>

...

How do I initiate exchange directory download?

The CONNECT gateway does support these other XDS stored queries, however our reference adapters are limited to the "find documents" query. You must implement the other queries in your own adapter.

Where can I find more information about support, configuration, or use of CDA within CONNECT?

CONNECT does not create CDA documents that could be transferred in either the Doc Submission (XDR) or Doc Retrieve services. CONNECT is the mechanism to transfer these documents over the NHIN, not to create them and insert them into the message.

The Adapter code is responsible for either creating these documents dynamically or pulling them from an existing "repository" or file store and inserting them into the request message to CONNECT.

Is there any legal guidance for independent CONNECT developers accessing client EMR database, including read/writes for purposes of connecting it to HIE?

eHealth Exchange (formally known as NwHIN Exchange and now managed by a private the non-profit HealtheWay) requires their participants to sign a Data Use and Reciprocal Support Agreement (DURSA) to formalize the exchange partnership. Please see the link for more information and a PFD of a DURSA, http://healthewayinc.org/index.php/exchange/dursa.

Patient Discovery/Doc Query - Fan Out vs target a specific NHIE gateway for PD & DQ requests

Each message on either the entity interface or the message proxy allows you to target a specific entity by providing the homeCommunityId within a nhinTargetSystem. Fan out only occurs if this element is not provided.

Can I still demonstrate Patient Discovery, Doc Query, Doc Retrieve services using test data only, and without implementing a custom adapter?

You should be able to do Patient Discovery (PD), Query for Documents (QD) and Retrieve Documents (RD) with test data without any configuration if you have installed and configured your system as given in the CONNECT installation instructions. In this case, you get docs from local database. You can configure the hibernate config files if you want to install CONNECT database on different machine. If you want to use your own database with different schema/tables, you need customize the adapters.

NHIN:

How do we authorize into NHIN? How do we retrieve userName and password for services?

NHIN does not call for cross-HIE authentication. Instead, you authenticate your users locally however you choose, then "assert" the authentication info (who is the user, why they are requesting data, etc.) and pass this in the entity assertion class, which gets represented in the NHIN message as a SAML token. The receiving gateway then uses its own policies to determine if it will allow for this call.

What mechanism is NHIN using for identifying the Patients?

Each organization can identify its patients how it chooses. When you share patient data, you communicate the patient identifiers using a qualified patient id (local patient id + a globally unique assigning authority).

...

CONNECT can download from web services registry from both UDDI  and FHIR directories. You can configure the download in exchangeInfo.xml. For more information see Exchange Manager#ConfiguringExchange and Sample exchangeInfo

Is there any legal guidance for independent CONNECT developers accessing client EMR database, including read/writes for purposes of connecting it to HIE?

eHealth Exchange (formally known as NwHIN Exchange and now managed by a private the non-profit HealtheWay) requires their participants to sign a Data Use and Reciprocal Support Agreement (DURSA) to formalize the exchange partnership. Please see the link for more information and a PFD of a DURSA, http://healthewayinc.org/index.php/exchange/dursa.

Patient Discovery/Doc Query - Fan Out vs target a specific NHIE gateway for PD & DQ requests

Each message on either the entity interface or the message proxy allows you to target a specific entity by providing the homeCommunityId within a nhinTargetSystem. Fan out only occurs if this element is not provided.

When configuring multiple gateways, do we need to configure ExchangeInfo and InternalExchangeInfo.xml?

ExchangeInfo.xml is used to communicate with other gateway while InternalExchangeInfo.xml is used for internal adapters within its own gateway. If you participate in ehealth exchange network, you don't need to change ExchangeInfo.xml since CONNECT pulls the latest UDDI/FHIR from UDDI/FHIR servers periodically.

Where can I find more information about support, configuration, or use of CDA within CONNECT?

CONNECT does not create CDA documents that could be transferred in either the Doc Submission (XDR) or Doc Retrieve services. CONNECT is the mechanism to transfer these documents over the NHIN, not to create them and insert them into the message.

The Adapter code is responsible for either creating these documents dynamically or pulling them from an existing "repository" or file store and inserting them into the request message to CONNECT.

NHIN:

How do we authorize into NHIN? How do we retrieve userName and password for services?

NHIN does not call for cross-HIE authentication. Instead, you authenticate your users locally however you choose, then "assert" the authentication info (who is the user, why they are requesting data, etc.) and pass this in the entity assertion class, which gets represented in the NHIN message as a SAML token. The receiving gateway then uses its own policies to determine if it will allow for this call.

I want to enable my CONNECT to "grab" medical data from existing EMR systems like OpenMRS or OSCAR. Which service of CONNECT should I use?

To enable your CONNECT to "grab" medical data from an existing EMR you would probably use 3 services:

• Patient Discovery - A NHIN service to query nodes on the NHIN for information on patient's based on demographics.
• Document Query - A NHIN service to query nodes on the NHIN for metadata relating to documents about a specific patient
• Document Retrieve - A NHIN service to retrieve documents from nodes on the NHIN.

In order to use these services, you would write an adapter which integrates with these productions or depending on these product's capabilities, maybe create services in OpenMRS, OSCAR, or some integration tool which provision the adapter interface for each of these services. Then when CONNECT receives one of these requests over the NHIN, CONNECT will call your services and the EMR can respond in turn.

We are looking to integrate CONNECT into our solution by leveraging reports from other agencies, analyze them and compare them to our reports. Is there any suggestions on how to set up and configure the adapter for this system?

...

The way things look to be evolving on the NHIN specification factory (the group that makes the specs for NHIN) is that HIEM will contain sub-specs to detail for what you can issue subscriptions, called a profile. At the moment, the only thing that you are really "allowed" to subscribe for is a "consumer preference profile" (document containing the rules about who can see a "my" data). The next soon-to-be-released profile spec is for GIPSE, which covers subscriptions/notifications that contain aggregated data, expected to be used for groups like CDC collecting data from public health agencies (think: "how many people had the flu yesterday").

I want to enable my CONNECT to "grab" medical data from existing EMR systems like OpenMRS or OSCAR. Which service of CONNECT should I use?

To enable your CONNECT to "grab" medical data from an existing EMR you would probably use 3 services:

• Patient Discovery - A NHIN service to query nodes on the NHIN for information on patient's based on demographics.
• Document Query - A NHIN service to query nodes on the NHIN for metadata relating to documents about a specific patient
• Document Retrieve - A NHIN service to retrieve documents from nodes on the NHIN.

...

What mechanism is NHIN using for identifying the Patients?

Each organization can identify its patients how it chooses. When you share patient data, you communicate the patient identifiers using a qualified patient id (local patient id + a globally unique assigning authority).