Global System Architecture and Design Requirements Sample Clauses

Global System Architecture and Design Requirements. 4.17.3.1 The Contractor shall comply with federal and State policies, standards and regulations in the design, development and/or modification of the Systems it will employ to meet the aforementioned requirements and in the management of Information contained in those Systems. Additionally, the Contractor shall adhere to DCH and State-specific system and data architecture preferences as indicated in this Contract. 4.17.3.2 The Contractor’s Systems shall: · Employ a relational data model in the architecture of its databases and relational database management system (RDBMS) to operate and maintain them; · Be SQL and ODBC compliant; · Adhere to Internet Engineering Task Force/Internet Engineering Standards Group standards for data communications, including TCP and IP for data transport; · Conform to standard code sets detailed in Attachment L; · Contain industry standard controls to maintain information integrity applicable to privacy and security, especially PHI. These controls shall be in place at all appropriate points of processing. The controls shall be tested in periodic and spot audits following a methodology to be developed jointly and mutually agreed upon by the Contractor and DCH; and · Partner with the State in the development of future standard code sets, not specific to HIPAA or other federal effort and will conform to such standards as stipulated by DCH. 4.17.3.3 Where Web services are used in the engineering of applications, the Contractor’s Systems shall conform to World Wide Web Consortium (W3C) standards such as XML, UDDI, WSDL and SOAP so as to facilitate integration of these Systems with DCH and other State systems that adhere to a service-oriented architecture. 4.17.3.4 Audit trails shall be incorporated into all Systems to allow information on source data files and documents to be traced through the processing stages to the point where the Information is finally recorded. The audit trails shall: · Contain a unique log-on or terminal ID, the date, and time of any create/modify/delete action and, if applicable, the ID of the system job that effected the action; · Have the date and identification “stamp” displayed on any on-line inquiry; · Have the ability to trace data from the final place of recording back to its source data file and/or document shall also exist; · Be supported by listings, transaction Reports, update Reports, transaction logs, or error logs; · Facilitate auditing of individual Claim records as well as batch audits; and ·...
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Global System Architecture and Design Requirements. 4.17.2.1 The Contractor shall comply with federal and State policies, standards and regulations in the design, development and/or modification of the Systems it will employ to meet the aforementioned requirements and in the management of Information contained in those Systems. Additionally, the Contractor shall adhere to DCH and State-specific system and data architecture preferences as indicated in this Contract. 4.17.2.2 The Contractor’s Systems shall: 4.17.2.2.1 Employ a relational data model in the architecture of its databases and relational database management system (RDBMS) to operate and maintain them; 4.17.2.2.2 Be SQL and ODBC compliant; 4.17.2.2.3 Adhere to Internet Engineering Task Force/Internet Engineering Standards Group standards for data communications, including TCP and IP for data transport; 4.17.2.2.4 Conform to standard code sets detailed in Attachment L; 4.17.2.2.5 Contain controls to maintain information integrity. These controls shall be in place at all appropriate points of processing. The controls shall be tested in periodic and spot audits following a methodology to be developed jointly and mutually agreed upon by the Contractor and DCH; and
Sample 1Sample 2
Global System Architecture and Design Requirements. 4.17.2.1 The Contractor shall comply with federal and State policies, standards and regulations in the design, development and/or modification of the Systems it will employ to meet the aforementioned requirements and in the management of Information contained in those Systems. Additionally, the Contractor shall adhere to DCH and State-specific system and data architecture preferences as indicated in this Contract. 4.17.2.2 The Contractor’s Systems shall: 4.17.2.2.1 Employ a relational data model in the architecture of its databases and relational database management system (RDBMS) to operate and maintain them; 4.17.2.2.2 Be SQL and ODBC compliant; 4.17.2.2.3 Adhere to Internet Engineering Task Force/Internet Engineering Standards Group standards for data communications, including TCP and IP for data transport; 4.17.2.2.4 Conform to standard code sets detailed in Attachment L; 4.17.2.2.5 Conform to HIPAA standards for data and document management that are currently under development within one hundred twenty (120) Calendar Days of the standard’s effective date or, if earlier, the date stipulated by CMS; 4.17.2.2.6 Contain controls to maintain information integrity. These controls shall be in place at all appropriate points of processing. The controls shall be tested in periodic and spot audits following a methodology to be developed jointly by and mutually agreed upon by the Contractor and DCH; and 4.17.2.2.7 Partner with the State in the development of future standard code sets not specific to HIPAA or other federal effort and will conform to such standards as stipulated in the plan to implement the standards. 4.17.2.3 Where Web services are used in the engineering of applications, the Contractor’s Systems shall conform to World Wide Web Consortium (W3C) standards such as XML, UDDI, WSDL and SOAP so as to facilitate integration of these Systems with DCH and other State systems that adhere to a service-oriented architecture. 4.17.2.4 Audit trails shall be incorporated into all Systems to allow information on source data files and documents to be traced through the processing stages to the point where the Information is finally recorded. The audit trails shall: 4.17.2.4.1 Contain a unique log-on or terminal ID, the date, and time of any create/modify/delete action and, if applicable, the ID of the system job that effected the action; 4.17.2.4.2 Have the date and identification “stamp” displayed on any on-line inquiry; 4.17.2.4.3 Have the ability to trace dat...
Sample 1
Global System Architecture and Design Requirements. The Contractor shall comply with Federal and Puerto Rico policies, standards and regulations in the design, development and/or modification of the Systems it will employ to meet the aforementioned requirements and in the management of information contained in those Systems. Additionally, the Contractor shall adhere to ASES and Puerto Rico-specific system and Data architecture standards and/or guidelines.
Sample 1
Global System Architecture and Design Requirements. 8.2.1 The Contractor shall comply with Federal and Puerto Rico policies, standards and regulations in the design, development and/or modification of the Systems it will employ to meet the aforementioned requirements and in the management of information contained in those Systems. Additionally, the Contractor shall adhere to ASES and Puerto Rico-specific system and Data architecture standards and/or guidelines. 8.2.2 The Contractor’s Systems shall meet Federal and industry standards of architecture, including but not limited to the following requirements: 8.2.2.1 Conform to HIPAA standards for Data and document management; 8.2.2.2 Contain controls to maintain information integrity. These controls shall be in place at all appropriate points of processing. The controls shall be tested in periodic and spot audits following a methodology to be developed jointly by and mutually agreed upon by the Contractor and ASES; and 8.2.2.3 Partner with ASES in the development of transaction/event code set, Data exchange and reporting standards not specific to HIPAA or other Federal efforts and will conform to such standards as stipulated in the plan to implement the standards. 8.2.2.4 Be supported by listings, transaction reports, update reports, transaction logs, or error logs; 8.2.3 The Contractor shall house indexed images of documents used by Enrollees to transact with the Contractor in the appropriate database(s) and document management systems so as to maintain the logical relationships between certain documents and certain Data. The Contractor shall follow all applicable requirements for the management of Data in the management of documents. 8.2.4 The Contractor shall institute processes to insure the validity and completeness of the Data it submits to ASES. At its discretion, ASES will conduct general Data validity and completeness audits using industry-accepted statistical sampling methods. 8.2.5 Where a System is herein required to, or otherwise supports, the applicable batch or on-line transaction type, the system shall comply with HIPAA standard transaction code sets. 8.2.6 The Contractor shall assure that all Contractor staff is trained in all HIPAA requirements, as applicable. 8.2.7 The layout and other applicable characteristics of the pages of Contractor websites shall be compliant with Federal “Section 508 standards” and Web Content Accessibility Guidelines developed and published by the Web Accessibility Initiative and, Puerto Rico Act 229 of 2003, as ame...
Sample 1

Related to Global System Architecture and Design Requirements

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS 1. The Contractor certifies that it will provide a drug-free workplace by: a. Publishing a statement notifying employees that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Contractor’s workplace and specifying the actions that will be taken against employees for violation of such prohibition;

  • Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:

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