QHIN Query Sample Clauses

QHIN Query a. See requirements in Section 4.4.2 of this SOP as applied to the XP Code T-HCO-HED.
AutoNDA by SimpleDocs
QHIN Query. Only Initiating Nodes of a PHA or its Delegate may initiate a QHIN Query using the T-PH XP Code, in accordance with Applicable Law and the Common Agreement.
QHIN Query a. This SOP supports TEFCA Exchange in the form of a QHIN Query. Only Initiating Nodes of Health Plans and Health Care Providers that are Covered Entities or their Delegates may initiate Queries under the XP Code T-HCO, in accordance with Applicable Law.
QHIN Query a. Only Health Plans are permitted to initiate QHIN Queries using the XP Code T-HCO- CC.
QHIN Query. The specifications in this Section are required, unless otherwise stated herein or in an applicable SOP. 1. All Delegated Requests MUST append the following within the XXXX for each transaction sent to the Responding QHIN: This <Attribute> element MUST have the FriendlyName set to “QueryAuthGrantor”. The value MUST be the Directory Entry assigned to the Principal for whom the Delegate is initiating the Request, using the FHIR Resource format. <xxxx:Attribute FriendlyName=”QueryAuthGrantor”> <xxxx:AttributeValue>Organization/2.16.840.1.113883.3.7204.1</xxxx:Attribute Value> </xxxx:Attribute>

Related to QHIN Query

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • Domain Name Data (1) Query format: whois EXAMPLE.TLD (2) Response format:

  • Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service. 2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!