Clinical Functionality Sample Clauses

The Clinical Functionality clause defines the required capabilities and performance standards of a product or service within a clinical or healthcare setting. It typically outlines specific features, workflows, or interoperability requirements that the product must support to be effectively used by healthcare professionals, such as electronic health record integration or compliance with clinical protocols. This clause ensures that the delivered solution meets the practical needs of clinical users, thereby reducing the risk of operational inefficiencies or non-compliance with healthcare regulations.
Clinical Functionality. (a) SJHC confirms that, as at the date of this Project Agreement, it has reviewed the Sites master plan, and blocking and stacking diagrams and interdepartmental matrix and that, subject to any qualifications or comments noted thereon, such Submittals satisfy the Output Specifications in respect of Clinical Functionality, so far as can reasonably be determined given the level of detail in the Submittals. (b) With each of the Design Development Submittals, Project Co shall submit to SJHC, for its review pursuant to Schedule 10 - Review Procedure, a draft report (each a “Clinical Functionality Report”) to specifically identify, with reference to the Output Specifications, such matters of Clinical Functionality that Project Co wishes SJHC to review and consider as part of the Design Development Submittals. Each Clinical Functionality Report shall demonstrate how the Output Specifications are satisfied in respect of Clinical Functionality. (c) With the Construction Document Submittals, Project Co shall submit to SJHC, for its review pursuant to Schedule 10 - Review Procedure, a final Clinical Functionality Report, and SJHC shall confirm that, subject to any qualifications or comments noted thereon, such Construction Document Submittals satisfy the Output Specifications in respect of Clinical Functionality, so far as can reasonably be determined given the level of detail in the Construction Document Submittals. (d) Each Clinical Functionality Report must be prepared in accordance with the technical submission requirements set out in MOHLTC’s Capital Planning Manual and must address the way in which the Design Data meets the following requirements of Clinical Functionality: (i) MOHLTC’s “OASIS” requirements of operational efficiency, accessibility, safety and security, infection prevention and control, and sustainability; (ii) expansion/ flexibility; (iii) internal adjacencies; (iv) internal zoning and material/staff flow; (v) hours of operation; and (vi) Plant.
View SourceView Similar (12)
Clinical Functionality. Configuration Issues
View SourceView Similar (2)
Clinical Functionality. Capacity Issues
View Source
Clinical Functionality. (a) Contracting Authority confirms that, as at the date of this Project Agreement, it has reviewed the Site master plan and blocking and stacking diagrams and that, subject to any qualifications or comments noted thereon, such Works Submittals satisfy the Output Specifications in respect of Clinical Functionality, so far as can reasonably be determined given the level of detail in the Works Submittals.
View Source
Clinical Functionality. Fabric and Infrastructure
View Source

Related to Clinical Functionality

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

  • Screening The Health Plan must work with contracted providers to conduct interperiodic EPSDT screens on RIte Care and all ACA Adult Expansion Population members under age 21 (i.e. 19 and 20-year old under this Agreement) to identify health and developmental problems in conformance with ATTACHMENT ED to this Agreement. Additional screens should be provided as Medically Necessary. At a minimum, these screens must include: • A comprehensive health and developmental history, including health education, nutrition assessment, immunization history, and developmental assessment • Immunizations according to the Rhode Island EPSDT Periodicity Schedule • An unclothed physical examination • Laboratory tests including lead, TB, and newborn screenings as medically indicated • Vision testing • Hearing testing • Dental screening oral examination by PCP as part of a comprehensive examination required before age one (1) • All other medically indicated screening services • And provide EOHHS with a list of established CPT/HCPC codes used to identify all billable services included in the EPSDT schedule.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.