Homelessness Management Information System (HMIS) Sample Clauses

The Homelessness Management Information System (HMIS) clause establishes requirements for the collection, management, and reporting of data related to individuals and families experiencing homelessness. It typically mandates that participating organizations use a standardized database to record client information, service usage, and outcomes, ensuring data consistency and confidentiality. By setting these standards, the clause facilitates coordinated care, improves service delivery, and enables accurate reporting for funding and policy decisions, ultimately addressing the need for reliable data in managing homelessness programs.
Homelessness Management Information System (HMIS). A Homeless Management Information System (HMIS) is a local information technology system used to collect participant-level data and data on the provision of housing and services to homeless individuals and families and persons at risk of homelessness. Each Continuum of Care is responsible for selecting an HMIS software solution that complies with HUD's data collection, management, and reporting standards. The San Diego regional HMIS software is called Clarity. Contractor must enter and maintain data in the RTFH-approved HMIS. Contractor must comply with the HMIS Policies and Procedures in effect during the Agreement term, including those for data collection, data entry, data quality, standards for missing data, incomplete data, and timeliness of data entry. The Contractor will provide written authorization for the City to be listed as a Program Administrator once the Program has been enrolled in HMIS and registered with the RTFH. If necessary, the Contractor shall provide written authorization to RTFH for the City to be listed as Program Administrator. Any health information provided to, or maintained within HMIS shall not be subject to public inspection or disclosure under the California Public Records Act (Chapter 3.5 (commencing with Section 6250) of Division 7 of Title 1 of the Government Code). For purposes of this paragraph, “health information” means “protected health information,” as defined in Part 160.103 of Title 45 of the Code of Federal Regulations, and “medical information,” as defined in subdivision (j) of Section 56.05 of the Civil Code. City may, as required by grant funders or otherwise, amend or modify required data elements, disclosure formats, or disclosure frequency.
View SourceView Similar (4)
Homelessness Management Information System (HMIS). A Homeless Management Information System (HMIS) is a local information technology system used to collect client-level data and data on the provision of housing and services to homeless individuals and families and persons at risk of homelessness. Each Continuum of Care is responsible for selecting an HMIS software solution that complies with HUD's data collection, management, and reporting standards. The San Diego regional HMIS software is called Clarity. Contractor must enter and maintain data in the RTFH-approved HMIS. Contractor must comply with the HMIS Policies and Procedures in effect during the Agreement term, including those for data collection, data entry, data quality, standards for missing data, incomplete data, and timeliness of data entry. The City shall be listed as a Program Administrator once the Program has been enrolled in HMIS and registered with the RTFH. If necessary, the Contractor shall provide written authorization to RTFH for the City to be listed as Program Administrator. Any health information provided to, or maintained within HMIS shall not be subject to public inspection or disclosure under the California Public Records Act (Chapter
View Source

Related to Homelessness Management Information System (HMIS)

  • Information Systems The Customer is aware that vehicles manufactured, supplied or marketed by a company within the Volvo Group are equipped with one or more systems which may gather and store information about the vehicle (the “Information Systems”), including but not limited to information relating to vehicle condition and performance and information relating to the operation of the vehicle (together, the “Vehicle Data”). The Customer agrees not to interfere with the operation of the Information System in any way.

  • Enterprise Information Management Standards Performing Agency shall conform to HHS standards for data management as described by the policies of the HHS Chief Data and Analytics Officer. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • DEFECTIVE MANAGEMENT INFORMATION 5.1 The Supplier acknowledges that it is essential that the Authority receives timely and accurate Management Information pursuant to this Framework Agreement because Management Information is used by the Authority to inform strategic decision making and allows it to calculate the Management Charge.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment. 5.2 If a Reconex Customer is served by resold Verizon Telecommunications Service or a Verizon Local Switching UNE, subject to any call blocking feature used by Reconex, to the extent reasonably feasible, Verizon will route Voice Information Services Traffic originating from such Service or UNE to the Voice Information Service platform. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.3 Reconex shall have the option to route Voice Information Services Traffic that originates on its own network to the appropriate Voice Information Services platform(s) connected to Verizon’s network. In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow Reconex to route Voice Information Services Traffic originated on its network to Verizon. For such Voice Information Services Traffic, unless Reconex has entered into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers, Reconex shall pay to Verizon without discount the Voice Information Services provider charges. Reconex shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.4 Reconex shall pay Verizon such charges in full regardless of whether or not it collects charges for such calls from its own Customers. 5.5 For variable rated Voice Information Services Traffic (e.g., NXX 550, 540, 976, 970, 940, as applicable) from Reconex Customers served by resold Verizon Telecommunications Services or a Verizon Local Switching Network Element, Reconex shall either (a) pay to Verizon without discount the Voice Information Services provider charges, or (b) enter into an arrangement with Verizon to ▇▇▇▇ and collect Voice Information Services provider charges from Reconex’s Customers. 5.6 Either Party may request the other Party provide the requesting Party with non discriminatory access to the other party’s information services platform, where such platform exists. If either Party makes such a request, the Parties shall enter into a mutually acceptable written agreement for such access. 5.7 In the event Reconex exercises such option, Reconex will establish, at its own expense, a dedicated trunk group to the Verizon Information Service serving switch. This trunk group will be utilized to allow Reconex to route information services traffic originated on its network to Verizon.

  • Management Information To be Supplied to CCS no later than the 7th of each month without fail. Report are to be submitted via MISO CCS Review 100% Failure to submit will fall in line with FA KPI FROM THE FOLLOWING, PLEASE SELECT AND OUTLINE YOUR CHARGING MECHANISM FOR THIS SOW. WHERE A CHARGING MECHANISM IS NOT REQUIRED, PLEASE REMOVE TEXT AND REPLACE WITH “UNUSED”. 5.1 CAPPED TIME AND MATERIAL CHARGES 5.2 PRICE PER STORY POINT CHARGES 5.3 TIME AND MATERIALS CHARGES