Kno2®

Integrated EHR partners utilizing the QHIN network FIND integration via the Kno2 API will need to configure the Responder role in each of the end user's Kno2 organizations as part of the overall integration configuration.

Within the Kno2 tenant, access Settings &gt; API

Select the '+' option under "Integrations"

- Within the Kno2 tenant, access Settings &gt; API
- Select the '+' option under "Integrations"

The Add Integration modal will open:

Integration URL = This is the base URL where each of your Responder services are hosted

- The unique path for each of the query types is added to this value, e.g. <a href="https://myehr.example.com/" rel="nofollow noopener noreferrer" target="_blank">https://myehr.example.com/</a>

Authentication Type = Obtain this value from the vendor (likely, your EHR) who is integrated with Kno2 for query and response functionality

Api Key = Similar to username, this represents the account to be used when making requests to your responding system (e.g. your EHR)

- This value is obtained from the system being connected to respond to queries
- Care must be taken to protect this value as it is used to retrieve patient information
- Please note: this is not your Kno2 client id

Api Secret = The corresponding client secret or password to the Api Key to be used when making requests to your responding system.

- This value is obtained from the system being connected to respond to queries
- Care must be taken to protect this value as it is used to retrieve patient information
- Please note: this is not your Kno2 client secret

Patient Query = The unique portion appended to the Integration URL to indicate where patient queries shall be sent, e.g. query/patient

Document Query = The unique portion appended to the Integration URL to indicate where document queries shall be sent, e.g. query/documents

Document Retrieve = The unique portion appended to the Integration URL to indicate where document queries shall be sent, e.g. query/documents/retrieve

- Integration Type = QHIN
- Integration URL = This is the base URL where each of your Responder services are hosted
 - The unique path for each of the query types is added to this value, e.g. <a href="https://myehr.example.com/" rel="nofollow noopener noreferrer" target="_blank">https://myehr.example.com/</a>
- Authentication Type = Obtain this value from the vendor (likely, your EHR) who is integrated with Kno2 for query and response functionality
- Api Key = Similar to username, this represents the account to be used when making requests to your responding system (e.g. your EHR)
 - This value is obtained from the system being connected to respond to queries
 - Care must be taken to protect this value as it is used to retrieve patient information
 - Please note: this is not your Kno2 client id
- Api Secret = The corresponding client secret or password to the Api Key to be used when making requests to your responding system.
 - This value is obtained from the system being connected to respond to queries
 - Care must be taken to protect this value as it is used to retrieve patient information
 - Please note: this is not your Kno2 client secret
- Patient Query = The unique portion appended to the Integration URL to indicate where patient queries shall be sent, e.g. query/patient
- Document Query = The unique portion appended to the Integration URL to indicate where document queries shall be sent, e.g. query/documents
- Document Retrieve = The unique portion appended to the Integration URL to indicate where document queries shall be sent, e.g. query/documents/retrieve

Once the fields are completed, click Add.

___________________________________________________________

Under Integrations click Edit (Pencil) in the Row for the QHIN Integration

- Within the Kno2 tenant, access Settings &gt; API
- Under Integrations click Edit (Pencil) in the Row for the QHIN Integration
- Make the necessary changes
- Click Save

Configure a QHIN Responder

Edit a QHIN Responder Configuration