HIMSS IT Data Healthcare Information and Management Systems Society - onetomapanalytics/Meta_Data GitHub Wiki

HIMSS IT Data - Healthcare Information and Management Systems Society

General description

  1. Database primary purpose - Provide detailed historical data about information technology use in hospitals and integrated healthcare delivery networks
  2. Overall data type - Health facilities
  3. Dataset type - Longitudinal
  4. Data source - Survey
  5. Data level - Hospital level
  6. Geographic location of the data collection sites - United States
  7. Sponsor, manager, or home institution - Dorenfest Institute for Health Information
  8. Date range - 2005 - 2015
  9. Geolocation data - Zip code, street address, city, state, latitude, and longitude
  10. Dates - Last month of the fiscal year; year the entity was formed or acquired; year a determined software was contracted; month and year a determined software was contracted and implemented; complete date the change was made to the HIMSS Analytics Database; date the data collection was completed; year the disaster cover plan was written
  11. Hospital identifiers - Entity ID (unique within survey year) and unique id (fixed ID), Medicare ID, and name; facility ID, Independent Health System ID, phone number
  12. Longitudinal tracking - Track entities using the above-mentioned identifiers
  13. Financial variables - Expenses (i.e., equipment, building, project, or software expenses); depreciation (i.e., recognized portion of the capital investment expenses from past years); budget (for the current fiscal year for Acute-Care Hospital, medical devices, operating expenses); payroll expenses (includes all salaries and wage expenses); percent of Managed Care, Medicaid, Medicare, and commercial insurances that make up the patient revenue at the hospital; funding for construction or expansion projects; annual operating cost (staffing and property expenses); annual revenue
  14. Clinical areas of interest - all
  15. Number of records - 1,467 integrated healthcare delivery systems (IHDSs) and data on over 32,000 facilities
  16. Variables that are uniquely present in this dataset - Data on the U.S. hospital IT market, including an annual report with summary statistics

Applicable methods

  1. Association methods, such as multivariate regression analysis (1), generalized linear regression models (2), logistic regression models (3, 4), negative binomial regression (5)
  2. Machine learning (6)
  3. Propensity scores (7, 8)

High-impact designs

  • Examine the scope of corporate strategies for multi-business health care firms (9)

  • Analyze the extent of health IT adoption for medication safety in hospitals (10)

  • Enrichment of the dataset by linking the HIMSS with another dataset, such as Leapfrog Group (11), the American Hospital Association (AHA) (2, 11, 12), the Centers for Medicare & Medicaid Services (CMS) Chronic Conditions Data Warehouse Geographic Variation Database (12), and the Annual Financial Disclosure Reports and Patient Discharge Databases of the California Office of Statewide Health Planning and Development (OSHPD) (13)

Data dictionary

To access the HIMSS data dictionary, click here

Variable categories

  1. Demographics [e.g., facility location, number of FTEs total and per function, entity type, number of licensed beds, number of physicians, size of population served by the entity; type of region it services (i.e., county, state, regional, national)]
  2. Hospital information [e.g., AHA number of admissions; financial (see under "General description"); information related to the system used; number of discharges, inpatient days, births, ED visits, nurses, ORs, outpatient visits, and surgical operations]
  3. Software (e.g., applications ID, product/software ID and name, vendor ID and name, category)
  4. Barcoding and biometric technology (e.g., if used, department, type)
  5. Entity history (e.g., type of current or planned activity, timeframe to construction or expansion projects)
  6. Medical device (e.g., type, number, ID)

Linkage to other datasets

  • Linkages can be established for any dataset that might have geolocation (i.e., zip codes) or identification data (i.e., entity name or Medicare ID)