Rce Directory Service Sample Clauses

Rce Directory Service a. See requirements in Section 4.5 of this SOP as applied to the XP Code T-HCO-HED.
AutoNDA by SimpleDocs
Rce Directory Service. 1. All QHINs, Participants, and Subparticipants MUST list any directly contracted Delegates in their Directory Entry(ies). 2. A Principal is responsible for providing the Delegation Notice to its QHIN when the Principal wants to authorize a First Tier Delegate to initiate Delegated Requests in connection with the services provided by the First Tier Delegate to the Principal. 3. A First Tier Delegate is responsible for providing the Delegation Notice to its QHIN when the First Tier Delegate wants to authorize a Downstream Delegate to initiate Delegated Requests in connection with the services provided by the Downstream Delegate to the First Tier Delegate. 4. A Downstream Delegate is responsible for providing the Delegation Notice to its QHIN when the Downstream Delegate wants to authorize another Downstream Delegate to initiate Delegated Requests in connection with the services provided by the Downstream Delegate to the Downstream Delegate making the notification to its QHIN. 5. By submitting a Delegation Notice, the QHIN, Participant, or Subparticipant submitting the Delegation Notice is attesting that it has a direct written agreement with such Delegate authorizing the Delegate to conduct TEFCA Exchange for or on behalf of a Principal that is also listed in the RCE Directory Service. 6. Upon receipt of a Delegation Notice from an individual(s) authorized to provide the Delegation Notice for a Participant or Subparticipant entity, the QHIN MUST inspect the Delegation Notice for completeness and validity and notify the Participant or Subparticipant of its determination within five (5) business days. a. The QHIN MUST update the RCE Directory Service within one (1) business day of determining the Delegation Notice to be complete and valid. The Directory must be updated by the QHIN by listing the First Tier Delegate or Downstream Delegate within the Directory Entry of the Participant or Subparticipant submitting the Delegation Notice. The Directory Entry of the Participant or Subparticipant submitting the Delegation Notice must use the “Delegation of Authority (DOA)” extension with reference to the Organization resource(s) for the Delegate named in the Delegation Notice. b. If the QHIN determined that the Delegation Notice is incomplete and additional information is required to validate the legitimacy of the Delegation Notice, the QHIN MUST request such information from the Participant or Subparticipant that submitted the Delegation Notice by the end of third ...
Rce Directory Service a. A Health Plan Parent listed in the RCE Directory Service MUST publish all its participating Health Plans to the RCE Directory to identify the source of a Query as required in Section 4.4.1 and Section 4.5.1 of this SOP. 5.1 EXCHANGE PURPOSE CODE (XP CODE) a. All TEFCA Exchange under HCO Care Coordination/Case Management MUST use the XP Code T-HCO-CC.
Rce Directory Service a. See requirements in Section 4.5 of this SOP.
Rce Directory Service 

Related to Rce Directory Service

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Pregnancy and Maternity Services This plan covers physician services and the services of a licensed midwife for prenatal, delivery, and postpartum care. The first office visit to diagnose a pregnancy is not included in prenatal services. This plan covers hospital services for mother and newborn child for at least forty-eight

  • Surgery Services This plan covers surgery services to treat a disease or injury when: • the operation is not experimental or investigational, or cosmetic in nature; • the operation is being performed at the appropriate place of service; and • the physician is licensed to perform the surgery. This plan covers reconstructive surgery and procedures when the services are performed to relieve pain, or to correct or improve bodily function that is impaired as a result of: • a birth defect; • an accidental injury; • a disease; or • a previous covered surgical procedure. Functional indications for surgical correction do not include psychological, psychiatric or emotional reasons. This plan covers the procedures listed below to treat functional impairments. • abdominal wall surgery including panniculectomy (other than an abdominoplasty); • blepharoplasty and ptosis repair; • gastric bypass or gastric banding; • nasal reconstruction and septorhinoplasty; • orthognathic surgery including mandibular and maxillary osteotomy; • reduction mammoplasty; • removal of breast implants; • removal or treatment of proliferative vascular lesions and hemangiomas; • treatment of varicose veins; or • gynecomastia.

  • Compensation for Basic Services A. Owner shall make payment for Part I and Part II services monthly. The payments shall be in proportion to the progress of Engineer's work. Final payment for each phase shall become due and payable upon completion and approval by Owner of that phase of Engineer's work. B. Owner shall make payment for Construction Phase services not more frequently than monthly in proportion to the amount of the gross progress payments to Contractor(s). C. Owner shall make no deduction from Engineer's compensation on account of penalties, liquidated damages or other sums withheld from Contractor(s) through no fault of Engineer. D. Owner shall make payment for Construction Completion Phase services upon completion of the requirements set forth in subsections II. F. 1, 2 and 3. E. Engineer shall submit requests for payment monthly on forms provided and in a manner prescribed by Owner.

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