DoCDat covers databases that have information on the actual or potential recipients of health care. It does not cover databases limited to the provision of resources or services (e.g. a register of hospital bed provision), useful though they are.
DoCDat focuses primarily on centralised individual-level databases, based either on prospectively or retrospectively collected data (i.e. they contain information about individuals, and centrally collate data collected from different health care providers). They must meet the following criteria:
- Inclusion in the database is defined by a common circumstance e.g. individual's condition, intervention required or undergone (which might be a diagnostic test, treatment or a collection of interventions e.g. intensive care), administrative arrangement (such as subscriber to health insurance, registered with GP, target for immunisation), or adverse outcome (e.g. maternal death). Note that this excludes cohorts defined by behaviour or environmental exposure (for aetiological research).
- Provides individual-level data, whether or not users of the database are permitted to know the identity of the individuals
- Includes data from more than one provider of health care (usually many providers in a region or country). Single-provider databases may be included if they cover an area of health care for which no multi-provider database exists.
In addition, DoCDat also includes limited information on two other types of databases:
- Non-centralised individual-level databases in which the same dataset is collected by more than one provider but the data are not collated centrally.
- Aggregated databases that collect data about groups of people rather than about individuals. For example, data about the number of patients undergoing a particular operation by their age and sex, or the number of people covered in a vaccination programme.
Limited information is also provided on databases which we have not yet had a chance to assess fully. This includes the contact details for the database custodian, so that you can investigate the database further yourself.