- API
Monthly Slot Revenue from Casinos for Current Year (displayed in $)
data.ct.gov | Last Updated 2024-06-17T17:48:04.000ZMohegan Sun Footnotes: (1) Monthly contributions are due to the State by the 15th of the following month. (2) Mohegan Sun did not include the value of eBonus credits redeemed by patrons at slot machines in its video facsimile devices Win amounts; however, the value of eBonus credits wagered was included in the reported Handle. In addition, please be advised that the Casino Hold % column amounts may be understated and the Payout % column amounts may be overstated as a result of this. (3) From July 1, 2009 to June 30, 2012, if the aggregate amount of eBonus coupons or credits actually played on the Mohegan Tribe's Video Facsimiles during a particular month exceeded 5.5% of “gross operating revenues” for that month, the Mohegan Tribe paid to the State an amount equal to twenty-five percent (25%) of such excess face amount of eBonus coupons or credits used in such calendar month (the "eBonus Contribution"). Beginning on July 1, 2012, and for all months thereafter, the aggregate amount threshold for determining the eBonus Contribution increased from 5.5% to 11% of "gross operating revenues." (4) The value of eBonus free slot play credits redeemed during February 2009 totaled $1,910,268; however, it was determined that eBonus credits redeemed were overstated by $1,460,390 for January 2008 though January 2009. February 2009 is adjusted by this amount. March 2009 was was adjusted by an additional $8,139. (5) During fiscal year 2010 the Mohegan Tribe and the State of Connecticut settled a dispute regarding the proper treatment of eBonus for the period November 2007 through June 2009. As a result of this settlement, the State of Connecticut received $5,727,731, including interest. (6) For fiscal years 2007/2008 and 2008/2009, Poker Pro Electronic Table Rake Amounts of $401,309 and $42,188, respectively, were included in the calculation to determine the amount of Slot Machine Contributions to the State of Connecticut. (7) The Mohegan Sun Casino officially opened on Saturday, October 12, 1996. On October 8-10, video facsimile/slot machines were available for actual play during pre-opening charitable gaming nights. (8) Beginning with the month of May 2001, Mohegan Sun Casino reports video facsimile/slot machine win on an accrual basis, reflecting data captured and reported by an on-line slot accounting system. Reports were previously prepared on a cash basis, based on the coin and currency removed from the machines on each gaming day. (9) Cumulative Win amount total should be reduced by $1,452,341.21 to correct for an over reporting of slot revenues for prior periods related to errors in the accrual carry forward of estimated cash on floor. Foxwoods Footnotes: (1) Monthly contributions are due to the State by the 15th of the following month. (2) The operation of the video facsimile/slot machines began at Foxwoods on January 16, 1993. (3) Foxwoods did not include the value of Free Play coupons redeemed by patrons at slot machines in its video facsimile devices Win amounts; however, the value of Free Play coupons wagered was included in the reported Handle. In addition, please be advised that the Casino Hold % column amounts may be understated and the Payout % column amounts may be overstated as a result of this. (4) From July 1, 2009 to June 30, 2012, if the aggregate amount of Free Play coupons or credits actually played on the Mashantucket Pequot Tribe's Video Facsimiles during a particular month exceeded 5.5% of “gross operating revenues” for that month, the Mashantucket Pequot Tribe paid to the State an amount equal to twenty-five percent (25%) of such excess face amount of Free Play coupons or credits used in such calendar month (the "Free Play Contribution"). Beginning on July 1, 2012, and for all months thereafter, the aggregate amount threshold for determining the Free Play Contribution increased from 5.5% to 11% of "gross operating revenues." (5) During fiscal year 2010 the Mashantucket Pequot T
- API
COVID-19 Reported Patient Impact and Hospital Capacity by Facility
data.ct.gov | Last Updated 2024-07-04T10:30:44.000ZThe "COVID-19 Reported Patient Impact and Hospital Capacity by Facility" dataset from the U.S. Department of Health & Human Services, filtered for Connecticut. View the full dataset and detailed metadata here: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/anag-cw7u The following dataset provides facility-level data for hospital utilization aggregated on a weekly basis (Friday to Thursday). These are derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities. The hospital population includes all hospitals registered with Centers for Medicare & Medicaid Services (CMS) as of June 1, 2020. It includes non-CMS hospitals that have reported since July 15, 2020. It does not include psychiatric, rehabilitation, Indian Health Service (IHS) facilities, U.S. Department of Veterans Affairs (VA) facilities, Defense Health Agency (DHA) facilities, and religious non-medical facilities. For a given entry, the term “collection_week” signifies the start of the period that is aggregated. For example, a “collection_week” of 2020-11-20 means the average/sum/coverage of the elements captured from that given facility starting and including Friday, November 20, 2020, and ending and including reports for Thursday, November 26, 2020. Reported elements include an append of either “_coverage”, “_sum”, or “_avg”. A “_coverage” append denotes how many times the facility reported that element during that collection week. A “_sum” append denotes the sum of the reports provided for that facility for that element during that collection week. A “_avg” append is the average of the reports provided for that facility for that element during that collection week. The file will be updated weekly. No statistical analysis is applied to impute non-response. For averages, calculations are based on the number of values collected for a given hospital in that collection week. Suppression is applied to the file for sums and averages less than four (4). In these cases, the field will be replaced with “-999,999”. This data is preliminary and subject to change as more data become available. Data is available starting on July 31, 2020. Sometimes, reports for a given facility will be provided to both HHS TeleTracking and HHS Protect. When this occurs, to ensure that there are not duplicate reports, deduplication is applied according to prioritization rules within HHS Protect. For influenza fields listed in the file, the current HHS guidance marks these fields as optional. As a result, coverage of these elements are varied. On May 3, 2021, the following fields have been added to this data set. hhs_ids previous_day_admission_adult_covid_confirmed_7_day_coverage previous_day_admission_pediatric_covid_confirmed_7_day_coverage previous_day_admission_adult_covid_suspected_7_day_coverage previous_day_admission_pediatric_covid_suspected_7_day_coverage previous_week_personnel_covid_vaccinated_doses_administered_7_day_sum total_personnel_covid_vaccinated_doses_none_7_day_sum total_personnel_covid_vaccinated_doses_one_7_day_sum total_personnel_covid_vaccinated_doses_all_7_day_sum previous_week_patients_covid_vaccinated_doses_one_7_day_sum previous_week_patients_covid_vaccinated_doses_all_7_day_sum On May 8, 2021, this data set has been converted to a corrected data set. The corrections applied to this data set are to smooth out data anomalies caused by keyed in data errors. To help determine which records have had corrections made to it. An additional Boolean field called is_corrected has been added. To see the numbers as reported by the facilities, go to: https://healthdata.gov/Hospital/COVID-19-Reported-Patient-Impact-and-Hospital-Capa/uqq2-txqb On May 13, 2021 Changed vaccination fields from sum to max or min fields. This reflects the maximum or minimum number report
- API
CT DCF Abuse/Neglect Reports and Allegations by Town and State Fiscal Year
data.ct.gov | Last Updated 2023-09-12T17:46:42.000ZThis dataset contains aggregate data concerning abuse/neglect reports accepted for a response from DCF. Traditionally, DCF has had only one manner of responding to such reports, which was a mandated Child Protective Services (CPS) Investigation. As of April 2012, DCF began responding to low-risk reports through a voluntary Family Assessment Response (FAR) process. Reports handled through a FAR response still contain allegations that meet the statutory definitions of neglect, but they do not receive a decision concerning whether they are substantiated or not. This policy has resulted in fewer substantiated allegations since its implementation, but the agency continues to serve as many or more families reported for abuse/neglect.
- API
Substance Abuse Care Facilities
data.ct.gov | Last Updated 2024-07-04T10:01:37.000ZLicensed Substance Abuse Care facilities derived from Licenses and Credentials recorded in Connecticut's eLicensing system. Includes active and inactive licenses. This dataset is pulled from the full State Licenses and Credentials dataset: https://data.ct.gov/Business/State-Licenses-and-Credentials/ngch-56tr/data Updated daily.
- API
Next Generation Accountability System
data.ct.gov | Last Updated 2024-06-18T12:41:03.000ZConnecticut’s Next Generation Accountability System is a broad set of 12 indicators that help tell the story of how well a school is preparing its students for success in college, careers and life. The system moves beyond test scores and graduation rates to provide a more holistic, multi-factor perspective of district and school performance. The 12 Indicators are: 1. Academic achievement status measured by state assessments 2. Academic growth 3. Assessment participation rate 4. Chronic absenteeism 5. Postsecondary preparation - coursework 6. Postsecondary readiness – exams and college credit 7. Graduation – on track in ninth grade 8. Graduation – four-year adjusted cohort graduation rate – all students 9. Graduation – six-year adjusted cohort graduation rate – high needs 10. Postsecondary entrance rate – all students (college enrollment) 11. Physical fitness 12. Arts access
- API
Fires in Connecticut
data.ct.gov | Last Updated 2023-05-08T18:56:47.000ZOnly fires are included here. All other incidences, including EMS calls and False Alarms have been excluded. This dataset contains Connecticut Fire Department Incidents as reported to the National Fire Department Incident Reporting System (NFIRS). Note that the 2014 and 2016 data has far more entries than the other years. In particular, they detail "False Alarm and False Calls" and "Rescue and Emergency Medical Service (EMS) Incidents" NFIRS collects details on Fire, HazMat and EMS incidences nationwide, detailing the type of incident, where it occurred, the resources used to mitigate it and more, with a goal of understanding the nature and causes of the incidents. Information is also collected on the number of civilian or firefighter casualties and an estimate of property loss. Participation in NFIRS is voluntary. Data is released yearly, with a considerable delay. Each Incidence is assigned a 3 digit Incidence Type Code. The code describes the situation emergency personnel found when they arrived. Incidence Types are grouped into larger categories, called Series. For example, Series 400, 'Hazardous Condition' category includes incidence types: 411, 'Gasoline or other flammable liquid spill; 412, 'Gas leak and 413, 'Oil or other combustible liquid spill '. Not every Incidence Type is included in the data. In 2012, 2013, 2014 and 2015, the NFIRS data releases contained these Series/Incidence Types: Series 100: Fire Incidences, Series 400: Hazardous Condition (No Fire), Incidence Type 561: Unauthorized burning, under the 'Service Call' Series, Incidence Type 631: Authorized Controlled Burning, under the 'Good Intent Call' series and Incidence Type 632: Prescribed fires also under the 'Good Intent Call' series. The 2014 and 2016 release included these additional series: 200: Overpressure Rupture, Explosion, Overheat (No Fire), 300: Rescue and Emergency Medical Service (EMS) Incidents, 500: Service Calls, 600: Good Intent Call Series, 700: False Alarm and False Call, 800 Severe Weather and Natural Disaster 900: Special Incident Type. The official NFIRS documentation has been attached to this dataset. This dataset does not contain all the detail available in the NFIRS database. If after reviewing the documentation, you find additional information you would like added to the dataset, please let us know.
- API
Connecticut Fire Department Incidents (2012-2021)
data.ct.gov | Last Updated 2023-09-18T14:19:59.000ZThis dataset contains Connecticut Fire Department Incidents as reported to the National Fire Department Incident Reporting System (NFIRS). Note that some years have far more entries than other years. In particular, they detail "False Alarm and False Calls" and "Rescue and Emergency Medical Service (EMS) Incidents" NFIRS collects details on Fire, HazMat and EMS incidences nationwide, detailing the type of incident, where it occurred, the resources used to mitigate it and more, with a goal of understanding the nature and causes of the incidents. Information is also collected on the number of civilian or firefighter casualties and an estimate of property loss. Participation in NFIRS is voluntary. Data is released yearly, with a considerable delay. Each Incidence is assigned a 3 digit Incidence Type Code. The code describes the situation emergency personnel found when they arrived. Incidence Types are grouped into larger categories, called Series. For example, Series 400, 'Hazardous Condition' category includes incidence types: 411, 'Gasoline or other flammable liquid spill; 412, 'Gas leak and 413, 'Oil or other combustible liquid spill '. Not every Incidence Type is included in the data. In 2012, 2013, 2014 and 2015, the NFIRS data releases contained these Series/Incidence Types: Series 100: Fire Incidences, Series 400: Hazardous Condition (No Fire), Incidence Type 561: Unauthorized burning, under the 'Service Call' Series, Incidence Type 631: Authorized Controlled Burning, under the 'Good Intent Call' series and Incidence Type 632: Prescribed fires also under the 'Good Intent Call' series. The 2014 and 2016 releases included these additional series: 200: Overpressure Rupture, Explosion, Overheat (No Fire), 300: Rescue and Emergency Medical Service (EMS) Incidents, 500: Service Calls, 600: Good Intent Call Series, 700: False Alarm and False Call, 800 Severe Weather and Natural Disaster 900: Special Incident Type. The official NFIRS documentation has been attached to this dataset. This dataset does not contain all the detail available in the NFIRS database. If after reviewing the documentation, you find additional information you would like added to the dataset, please let us know.
- API
Department of Economic and Community Development (DECD) - Dry Cleaning Establishment Remediation Portfolio
data.ct.gov | Last Updated 2024-02-02T15:00:51.000ZThis is a list of financial assistance agreements for Dry Cleaning Establishment Remediation Fund projects from Fiscal Year 2005 through 2023. This dataset will be updated annually.
- API
Prescription Drug Drop Boxes
data.ct.gov | Last Updated 2024-07-04T09:00:38.000ZThe medication collection and disposal program provides a safe disposal location for citizens to properly dispose of unused household medications
- API
CT School Learning Model Indicators by County (14-day metrics) - ARCHIVE
data.ct.gov | Last Updated 2023-08-07T19:50:49.000ZNOTE: This dataset pertains only to the 2020-2021 school year and is no longer being updated. For additional data on COVID-19, visit data.ct.gov/coronavirus. This dataset includes the leading and secondary metrics identified by the Connecticut Department of Health (DPH) and the Department of Education (CSDE) to support local district decision-making on the level of in-person, hybrid (blended), and remote learning model for Pre K-12 education. Data represent daily averages for two-week periods by date of specimen collection (cases and positivity), date of hospital admission, or date of ED visit. Hospitalization data come from the Connecticut Hospital Association and are based on hospital location, not county of patient residence. COVID-19-like illness includes fever and cough or shortness of breath or difficulty breathing or the presence of coronavirus diagnosis code and excludes patients with influenza-like illness. All data are preliminary. These data are updated weekly and reflect the previous two full Sunday-Saturday (MMWR) weeks (https://wwwn.cdc.gov/nndss/document/MMWR_week_overview.pdf). These metrics were adapted from recommendations by the Harvard Global Institute and supplemented by existing DPH measures. For national data on COVID-19, see COVID View, the national weekly surveillance summary of U.S. COVID-19 activity, at https://www.cdc.gov/coronavirus/2019-ncov/covid-data/covidview/index.html DPH note about change from 7-day to 14-day metrics: Prior to 10/15/2020, these metrics were calculated using a 7-day average rather than a 14-day average. The 7-day metrics are no longer being updated as of 10/15/2020 but the archived dataset can be accessed here: https://data.ct.gov/Health-and-Human-Services/CT-School-Learning-Model-Indicators-by-County/rpph-4ysy As you know, we are learning more about COVID-19 all the time, including the best ways to measure COVID-19 activity in our communities. CT DPH has decided to shift to 14-day rates because these are more stable, particularly at the town level, as compared to 7-day rates. In addition, since the school indicators were initially published by DPH last summer, CDC has recommended 14-day rates and other states (e.g., Massachusetts) have started to implement 14-day metrics for monitoring COVID transmission as well. With respect to geography, we also have learned that many people are looking at the town-level data to inform decision making, despite emphasis on the county-level metrics in the published addenda. This is understandable as there has been variation within counties in COVID-19 activity (for example, rates that are higher in one town than in most other towns in the county).