- 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
DCF Children in Placement: Annual Point-in-Time Trend By Gender
data.ct.gov | Last Updated 2023-09-12T18:03:43.000ZThis dataset contains aggregate data concerning the number of unique children placed in open DCF placements on the observation date (July 1st each year). These figures are broken out by the DCF Region and Office responsible for the child's care, the child's Gender, whether the placement setting is in or out-of-state, and by the categorical Placement Type in which the child is residing on the observation date.
- API
Environmental Monitoring Results for Radioactivity: Milk Samples
data.ct.gov | Last Updated 2024-04-26T18:12:27.000Z- Reporting units of sample results [where 1 picoCurie (pCi) = 1 trillionth (1E-12) Curie (Ci)]: • Milk Samples are reported in pCi/L. - Data Quality Disclaimer: This database is for informational use and is not a controlled quality database. Efforts have been made to ensure accuracy of data in the database; however, errors and omissions may occur. Examples of potential errors include: • Data entry errors. • Lab results not reported for entry into the database. • Missing results due to equipment failure or unable to retrieve samples due to lost or environmental hazards. • Translation errors – the data has been migrated to newer data platforms numerous times, and each time there have been errors and data losses. - Error Results are the calculated uncertainty for the sample measurement results and are reported as (+/-). - Environmental Sample Records are from the year 1998 until present. Prior to 1998 results were stored in hardcopy, in a non-database format. Requests for results from samples taken prior to 1998 or results subject to quality assurance are available from archived records and can be made through the DEEP Freedom of Information Act (FOIA) administrator at deep.foia@ct.gov. Information on FOIA requests can be found on the DEEP website. FOIA Administrator Office of the Commissioner Department of Energy and Environmental Protection 79 Elm Street, 3rd Floor Hartford, CT 06106
- 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
Nursing Homes with Residents Positive for COVID-19, April - June 2020 - Archive
data.ct.gov | Last Updated 2023-08-02T15:47:30.000ZNursing homes with residents positive for COVID-19 from 4/22/2020 to 6/19/2020. Starting in July 2020, this dataset will no longer be updated and will be replaced by the CMS COVID-19 Nursing Home Dataset, available at the following link: https://data.ct.gov/Health-and-Human-Services/CMS-COVID-19-Nursing-Home-Dataset/w8wc-65i5. Methods: 1) Laboratory-confirmed case counts are based upon data reported via the FLIS web portal. Nursing homes were asked to provide cumulative totals of residents with laboratory confirmed covid. This includes residents currently in-house, in the hospital, or who are deceased. Residents were excluded if they tested positive prior to initial admission to the nursing home. 2) The cumulative number of deaths among nursing home residents is based upon data reported by the Office of the Chief Medical Examiner. For public health surveillance, COVID-19-associated deaths include persons who tested positive for COVID-19 around the time of death (laboratory-confirmed) and persons whose death certificate lists COVID-19 disease as a cause of death or a significant condition contributing to death (probable). Limitations: 1) As of the week of 5/10/20, Point Prevalence Survey testing is being offered to all asymptomatic nursing home residents to inform infection prevention efforts. Point prevalence surveys will be conducted over a period of several weeks. Some nursing homes had adequate testing resources available to conduct surveys prior to this date. Differences in survey timing will impact the number of positive results that a nursing home reports. 2) Cumulative totals of residents testing positive are being collected rather than individual resident data. Thus we cannot verify the counts, de-duplicate, and/or verify whether there is a record of a positive lab test. This may result in either under- or over-counting. 3) The number of COVID-19 positive residents and the number of confirmed deaths among residents are tabulated from different data sources. Due to the timing of availability of test results for deceased residents, it is not appropriate to calculate the percent of cases who died due to COVID-19 at any particular facility based upon this data. 4) The count of deaths reported for 4/14 are not included in this dataset, as they were not broken out by laboratory-confirmed or probable. They can be viewed in the DPH Report here: https://portal.ct.gov/-/media/Coronavirus/CTDPHCOVID19summary4162020.pdf?la=en
- API
Assisted Living Facilities with Residents Positive for COVID-19 - ARCHIVE
data.ct.gov | Last Updated 2023-08-02T15:04:13.000ZNote: This dataset is no longer being maintained and will not be updated going forward. The weekly and cumulative number of residents with confirmed COVID-19 and with COVID-19 associated deaths is obtained from data self-reported by individual assisted living facilities to the Long Term Care Mutual Aid Plan web-based reporting system (www.mutualaidplan.org/ct). Both confirmed and suspect deaths are included. Confirmed deaths include those among persons who tested positive for COVID-19. Suspected deaths include those among persons with signs and symptoms suggestive of COVID-19 but who did not have a laboratory positive COVID-19 test. Due to differing data collection and processing methods between LTC-MAP and the death data sources used previously, cumulative death data for residents was re-baselined on July 14, 2020. The resident death data before and after July 14, 2020 should not be added due to the differing definitions of COVID-19 associated deaths used and the possibility of duplication of deaths among prior and current data. The cumulative number of deaths among assisted living residents is based upon data reported by the Office of the Chief Medical Examiner. For public health surveillance, COVID-19-associated deaths include persons who tested positive for COVID-19 around the time of death (laboratory-confirmed) and persons whose death certificate lists COVID-19 disease as a cause of death or a significant condition contributing to death (probable). As of 7/15/20 deaths reported by the Office of the Chief Medical Examiner are no longer being updated on a weekly basis.
- API
DCF Children in Placement: Annual Point-in-Time Trend By Race/Ethnicity
data.ct.gov | Last Updated 2023-09-12T18:01:54.000ZThis dataset contains aggregate data concerning the number of unique children placed in open DCF placements on the observation date (July 1st each year). These figures are broken out by the DCF Region and Office responsible for the child's care, the child's Race/Ethnicity, whether the placement setting is in or out-of-state, and by the categorical Placement Type in which the child is residing on the observation date.
- 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
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 Qualified Census Tracts
data.ct.gov | Last Updated 2023-08-02T19:28:36.000ZThis dataset provides access to Qualified Census Tracts (QCTs) in Connecticut to assist in administration of American Rescue Plan (ARP) funds. The Secretary of HUD must designate QCTs, which are areas where either 50 percent or more of the households have an income less than 60 percent of the AMGI for such year or have a poverty rate of at least 25 percent. HUD designates QCTs based on new income and poverty data released in the American Community Survey (ACS). Specifically, HUD relies on the most recent three sets of ACS data to ensure that anomalous estimates, due to sampling, do not affect the QCT status of tracts. QCTs are identified for the purpose of Low-Income Housing Credits under IRC Section 42, with the purpose of increasing the availability of low-income rental housing by providing an income tax credit to certain owners of newly constructed or substantially rehabilitated low-income rental housing projects. Also included are the number of households from the 2010 census (the “p0150001” variable), the average poverty rate using the 2014-2018 ACS data (the “pov_rate_18” variable), and the ratio of Tract Average Household Size Adjusted Income Limit to Tract Median Household Income using the 2014-2018 ACS data (the “inc_factor_18” variable). For the last variable mentioned in the previous paragraph, the income limit is the limit for being considered a very low income household (size-adjusted and based on Area Mean Gross Income). This value is divided by the median household income for the given tract, to get a sense of how the limit and median incomes compare. For example, if ratio>1, it implies that the tract is very low income because the limit income is greater than the median income. This ratio is a compact way to include the separate variables for the household income limit and median household income for each tract.