OAuth 2.0 Token Verification

Item	Name	Description
A	Access Token Location	Determines where the access token is located in client requests. Request Header: The field to the right specifies the HTTP header to pull the access token from. This same header will be sent in the request to the verification URL. Query Parameter: The field to the right specifies the query parameter to pull the access token from. This same parameter will be sent in the request to the verification URL.
B	Verification URL	The HTTP URL to perform a GET request to for access token verification. If the response code is >= 400, the authentication attempt is rejected by the server, and the request will not be processed through the channel.

Mirth® Connect by NextGen Healthcare User Guide

JavaScript HTTP Authentication

Allows you to authenticate users with a custom JavaScript script. With this script you have access to source map variables, and can choose whether to send a challenged or failure response back to the client. The default script simply allows all requests to pass. The Script field will show <Default Script Set> if the default script is currently being used. If you have made any modification to the script, the Script field will show <Custom Script Set>. Select the Script field to edit the JavaScript: This script expects either a boolean ( true to accept the request, false to send back a failure response) or an AuthenticationResult object to be returned (for additional information, see User API) . There are three types of results you can return: AuthenticationResult.Success(): The request will be accepted and processed through the channel. AuthenticationResult.Challenged(authenticateHeader): The request will not be processed through the channel. A 401 response will be sent back to the clie

Mirth® Connect by NextGen Healthcare User Guide

Digest HTTP Authentication

Provides Digest Authentication support for HTTP-based source connectors. Item Name Description A Realm The protection space for this server. B Algorithms Specifies the digest algorithms supported by this server. MD5: The security data A1 contains the username, realm, and password. MD5-sess: The security data A1 will also contain the server and client nonces. Both: Both MD5 and MD5-sess. C QOP Modes The quality of protection modes to support. auth: Regular authentication with client nonce and count in the digest. auth-int: Same as auth (regular authentication), but also with message integrity protection enabled. D Opaque A string of data that should be returned by the client unchanged. Velocity Variable Replacement is supported in this field. The default value, ${UUID}, means that a randomly generated universally unique identifier will be sent back on each digest challenge. E Credentials Use Table: When selected, use the Credentials table (E) to populate credentials. To Use the Table Se

Mirth® Connect by NextGen Healthcare User Guide

Choose an Authentication Type

Select an option from the drop-down window. Once an HTTP Authentication type is selected, fields associated with the type appear. For additional information on each HTTP Authentication type, select a links below. Basic HTTP Authentication Digest HTTP Authentication JavaScript HTTP Authentication Custom Java Class HTTP Authentication OAuth 2.0 Token Verification Parent topic: HTTP Authentication Settings

Help Guide for NextGen® Enterprise PM 8

Authorization Inquiry

Select Authorization Inquiry from one of the defined access paths. The Authorization Inquiry appears. Enter field information according to the following table: Field Description Patient Insurances (Required) Select the patient's insurance(s). Note: In order for the payer to display in the Patient Insurances field, it must be listed on the Insurance Listing window for the specified patient and it must be added to the Eligibility/Referral system. Requesting Physician (Required) Select the physician requesting for NextGen® Eligibility Verification. Requesting Location Select the location for the requesting physician. If there are no additional locations in the practice, this field does not display. Note: If the list in the Requesting Location field is empty, you do not have a valid provider number for that location and payer. Check the Group Information section of the Provider master file to see if the payer name and a provider number exist for the Requesting Physician Select Authorizatio

Mirth® Connect by NextGen Healthcare User Guide

HTTP Listener

This source connector acts as an HTTP server, listening for requests from one or more remote clients. The messages sent to the channel can be the raw payload, or an XML document allowing multipart payloads to be parsed in a consistent and easy-to-use way. The HTTP payload can be either Base64 encoded or converted using a charset, depending on the Content-Type. Responses that go back to each client can be fully configured, including custom response headers. Finally, static resources or directories can be automatically hosted, to allow the connector to act as a simple web server that serves specific content. Additional options are available with the SSL Manager extension. Supported property groups: Listener Settings Source Settings HTTP Authentication Settings Item Name Default Value Description A Base Context Path The context path for the HTTP Listener URL. Note: If this is specified, any requests made at this base context path must have a trailing slash in the request URI. B Receive Ti

Interoperability Connector Suite User Guide

Destination Connector Options

Option Name Description Use Default WSDL If enabled, will use standard WSDL and operations. To use custom operations, disable this option, provide a WSDL URL, and select Get Operations. WSDL URL The full URL to the WSDL describing the web service method to be called. Select the Get Operations after entering a URL. Use UDDI Select Yes to use a UDDI provider to determine the Location URI. Select No to use the default Location URI or provide your own. See UDDI for more information. Location URI The dispatch location for the port / endpoint defined in the Connector. This field is filled in automatically when you select Get Operations and does not usually need to be changed. If left blank, the default URI defined in the WSDL will be used. Convert Response to JSON If enabled, responses will be converted from XML to JSON. Expanded JSON Response If enabled, the JSON version of the response envelope will always use an expanded format where all children are expanded into arrays and objects. The

OAuth 2.0 Token Verification

Recommendations

JavaScript HTTP Authentication

Digest HTTP Authentication

Choose an Authentication Type

Authorization Inquiry

HTTP Listener

Destination Connector Options

OAuth 2.0 Token Verification

JavaScript HTTP Authentication

Digest HTTP Authentication

Choose an Authentication Type

Authorization Inquiry

HTTP Listener

Destination Connector Options