Access and validation

Governance details

Documents or webpages that describe the overall governance of the data source and processes and procedures for data capture and management, data quality check and validation results (governing data access or utilisation for research purposes).

Biospecimen access

Are biospecimens available in the data source (e.g., tissue samples)?

No

Access to subject details

Can individual patients/practitioners/practices included in the data source be contacted?

No

Description of data collection

The administrative healthcare data collected in the ReS database are exactly those periodically forwarded to the Italian Ministry of Health for reimbursement purposes by Italian local and regional Health Authorities. The forwarding to the Italian Ministry of Health is mandatory. Each Italian local and regional Health Authority that has signed the specific agreement with Fondazione ReS, send these administrative healthcare data to ReS to be hosted by CINECA, which makes use of applicative operating system in Cloud Computing – SaaS (Software as a Service) mode through the infrastructure IT Service Operation Management required by the reference framework ITIL V.3.
Event triggering registration

Event triggering registration of a person in the data source

Other

Event triggering registration of a person in the data source, other

A person is collected in the data source if he/she has received whatever healthcare reimbursed by the Italian national health Service (SSN)

Event triggering de-registration of a person in the data source

Death
Loss to follow up
Other

Event triggering de-registration of a person in the data source, other

Change of residency to an area not covered by the ReS database, i.e., with whom ReS has not signed the specific agreement. Admission to a private residential healthcare facility

Event triggering creation of a record in the data source

Every healthcare service reimbursed by the Italian National Health Service (SSN) (i.e., public facilities/affiliated with the SSN), among hospital discharge, drug dispensation by local/hospital pharmacy, access to the emergency department, performance of a prescribed specialist service within a local outpatient specialist ambulatory
Data source linkage

Linkage

Is the data source described created by the linkage of other data sources (prelinked data source) and/or can the data source be linked to other data source on an ad-hoc basis?

Yes

Linkage description, possible linkage

The choice of HbA1c as illustrative example is based on four main reasons: (i) T2DM is a clinical context which is currently debated for the recent approval of SGLT-1/2 inhibitors, whose indication required specific values of HbA1c to be prescribed; (ii) T2DM can be accurately identified both in clinical and administrative databases, since every clinical process (drug prescriptions, outpatient visits, clinical examinations, hospital admissions) related to this condition can be retrieved in these data sources; (iii) HbA1c values are expectedly well-registered in clinical data source (i.e., missing values [n around 30%]) for most of the T2DM patients, so allowing the use of multiple imputation (MI) methods; (iv) this patients category is featured by comorbidities which can be commonly defined in clinical and administrative databases to form the covariates vector for the model imputing HbA1c values. Although this algorithm was not developed for prognostic purpose, we were compliant with Transparent Reporting of Multivariable Prediction Model for Individual Prognosis and Diagnosis (TRIPOD) statements. To develop a model to estimate HbA1c values to identify the diabetes patients being eligible to SGLT-2 inhibitors (ATC: A10BK*; A10BD*), in both data sources, we excluded those already prescribed with these medications in the overall look-back period. Still in both databases, we included those prescribed (i.e., at least two prescriptions) with metformin in 2018 and adherent to this medication as per a variable medicine possession ratio (VMPR)≥80%. Namely,
VMPR was operationally defined as the cumulative number of days for each prescription (i.e., the number of Prescribed Daily Dosages) divided by the number of variable days of follow-up of each drug users. Finally, only for HSD, the date of highest values of HbA1c after metformin use, during 2018, was the study event date. Thus, according to the eligibility criteria for SGLT-2 inhibitors, HSD was used to develop and test the algorithm estimating HbA1c values ≥7%, which are not available in administrative data source. Given the presence of common covariates in HSD and ReS database, the combination of beta coefficients, composing the algorithm
obtained with HSD, was adopted to estimate the missing values of HbA1c in the ReS data source. The demographics and clinical determinants used to develop and apply (to ReS database) the imputation algorithm were operationally defined using ICD-9-CM and ATC codes in keeping with the same harmonization process previously described.
Data management specifications that apply for the data source

Data source refresh

Yearly

Informed consent for use of data for research

Possibility of data validation

Can validity of the data in the data source be verified (e.g., access to original medical charts)?

No

Data source preservation

Are records preserved in the data source indefinitely?

No

Data source preservation length

The records are preserved until the agreement with local/regional health authorities is renewed years

Approval for publication

Is an approval needed for publishing the results of a study using the data source?

No

Data source last refresh

Common Data Model (CDM) mapping

CDM mapping

Has the data source been converted (ETL-ed) to a common data model?

No