NSIH - Hospital associated bloodstream infections - Clinical data (NSIH-BSI_Clinical data)
- from 01/01/2026 - 31/03/2026
- Status: active
- Unique ID: patient ID, date of infection and infection source
- How to create a CSV file for this data collection?
- Start date: 05/02/2026
Start date
Not to be included in the CSV.
Technical specs
Format:
DD/MM/YYYY
CSV column name:
start_date
Default value:
2026-01-01
Only when:
Required:
false
Read only
Validation
- The date of infection must be during the data collection period (error)
End date
Not to be included in the CSV.
Technical specs
Format:
DD/MM/YYYY
CSV column name:
end_date
Default value:
2026-03-31
Only when:
Required:
false
Read only
Validation
- The date of infection must be during the data collection period (error)
1 Patient
Responsible infection control physician
Technical specs
CSV column name:
responsible_infection_control_physician
Length:
11
Reference list:
PHYSICIAN
Required:
true
National registry ID of the patient
Help
Unique identifier of the national registry (nn.nn.nn-nnn.nn). Can be found on the back of the patient's identity card and starts with year of birth (yy) / month (mm) / day (dd). This information is never transferred to Sciensano. In case the patient does not have a national registry id or the id is not known, an identifier can be automatically generated based on the 'name', 'first name', 'date of birth' and 'sex'. In this case, these four fields are mandatory.
Technical specs
CSV column name:
patient_id
Required:
true
Validation
The validity of the national register number is checked with the mod97 check.
Fields
Section help
Unique identifier of the national registry (nn.nn.nn-nnn.nn). Can be found on the back of the patient's identity card and starts with year of birth (yy) / month (mm) / day (dd). This information is never transferred to Sciensano. In case the patient does not have a national registry id or the id is not known, an identifier can be automatically generated based on the 'name', 'first name', 'date of birth' and 'sex'. In this case, these four fields are mandatory.
Internal patient ID
Help
This field can be used to enter an internal ID or reference number. It is available for internal use only and is not transferred to Healthdata. If there is an integration between HD4DP and your organisation's patient administration system, additional patient identification information such as date of birth, sex and SSIN can be automatically enriched based on this internal patient ID. Please do not encode the social security identification number (SSIN) in this field. The SSIN must be encoded in the field 'National registry ID of the patient'.
Technical specs
CSV column name:
patient_id|internal_patient_id
Length:
50
Required:
false
Generated
Help
The patient_id|generated column can be set to 'TRUE' for an automatically generated patient_id.This column should only be added in case the patient_id is empty. If the column is set to 'TRUE', a patient_id is automatically generated based on the name, first name, date of birth and sex of the patient.
Technical specs
CSV column name:
patient_id|generated
Required:
false
Options
| Label | Value |
| Yes | TRUE |
| No | FALSE |
Name
Help
The name of the patient is never transferred to Healthdata and is available for your information only.
Technical specs
CSV column name:
patient_id|name
Length:
50
Required:
noSSIN(Needed only if no national register number is entered)
First name
Help
The first name of the patient is never transferred and is available for your information only.
Technical specs
CSV column name:
patient_id|first_name
Length:
50
Required:
noSSIN(Needed only if no national register number is entered)
Date of birth
Help
If a national registry ID has been encoded, the date of birth is automatically extracted.
Technical specs
Format:
DD/MM/YYYY
CSV column name:
patient_id|date_of_birth
Required:
true
Validation
- Date of birth cannot be in the future (error)
Sex
Technical specs
CSV column name:
patient_id|sex
Required:
true
Options
| Label | Value |
| Female | F |
| Male | M |
| Unknown | U |
Place of residence
Help
This field is automatically filled in in case of a computerised link with the national registry. Only to be filled in manually if the patient does not have a Belgian national registry number.
Technical specs
CSV column name:
patient_id|place_of_residence
Length:
5
Reference list:
POSTAL_CODE
Required:
false
Deceased?
Help
This field is automatically filled in in case of a computerised link with the national registry. Only to be filled in manually if the patient does not have a Belgian national registry number.
Technical specs
CSV column name:
patient_id|deceased
Required:
false
Options
| Label | Value |
| Yes | TRUE |
| No | FALSE |
Date of death
Technical specs
Format:
DD/MM/YYYY
CSV column name:
patient_id|date_of_death
Only when:
Required:
false
2 Stay
Admission ID
Technical specs
CSV column name:
admission_id
Required:
false
Validation
- Admission ID cannot be longer than 50 characters (error)
Admission date in hospital
Technical specs
Format:
DD/MM/YYYY
CSV column name:
admission_date
Required:
true
Validation
- Admission date in hospital cannot be after admission date in ward (error)
- Admission date in ward cannot be after infection date (error)
- Admission date in hospital cannot be after end date of follow-up (error)
- Admission date in ward cannot be after end date of follow-up (error)
- Admission date in hospital cannot be after infection date (error)
- Admission date in ward cannot be in the future (error)
- Admission date in hospital is more than one year ago (warning)
- Admission date in ward is more than one year ago (warning)
Admission date in ward where bloodstream infection occurred
Help
Only if different from admission date in hospital
Technical specs
Format:
DD/MM/YYYY
CSV column name:
ward_admission_date
Required:
false
Validation
- Admission date in hospital cannot be after admission date in ward (error)
- Admission date in ward cannot be after infection date (error)
- Admission date in ward cannot be after end date of follow-up (error)
- Admission date in ward cannot be in the future (error)
- Admission date in ward is more than one year ago (warning)
NIHDI-code of the data provider institution
Not to be included in the CSV.
Technical specs
CSV column name:
installation_id
Length:
100
Computed:
Required:
false
Read only
Campus number
Help
If you have communicated you do not longer wish to register per campus, then only the main campus is automatically listed here. If you still register per campus, you have to select the correct campus from the drop-down list. If you want to stop registering per campus, please create Jira Service Management ticket for healthdata support (https://healthdatabe.atlassian.net/servicedesk/customer/portals
Technical specs
CSV column name:
site_number
Length:
100
Reference list:
SITE
Required:
true
ID of ward where bloodstream infection occurred
Help
If the ward ID does not appear in the drop-down list (e.g. in case of reorganization or moving of wards or hospital) please create a Jira Service Management ticket for healthdata support (https://healthdatabe.atlassian.net/servicedesk/customer/portals) to add this/these ward ID(s) and if necessary to remove old ward ID(s).
Technical specs
CSV column name:
ward_id
Length:
100
Reference list:
WARD
Required:
nosocomial
Specialty of the ward where bloodstream infection occurred
Help
If the specialty of ward does not appear in the drop-down list please create a Jira Service Management ticket for healthdata support (https://healthdatabe.atlassian.net/servicedesk/customer/portals) to add this specialty.
Technical specs
CSV column name:
ward_type
Length:
200
Reference list:
SPECIALTY_DETAILED
Required:
nosocomial
Status end follow-up
Technical specs
CSV column name:
efu_st
Required:
false
Options
| Label | Value |
| Death | 1 |
| Still admitted at the hospital | 2 |
| Discharged from the hospital | 3 |
| Unknown | 9 |
Discharge date from hospital or end date of follow-up
Help
Date the patient was discharged from the hospital (alive or deceased). Date of end of follow-up if the patient was still hospitalised and alive at the end of the surveillance period (maximum one month after the end of the surveillance period).
Technical specs
Format:
DD/MM/YYYY
CSV column name:
efu_dt
Required:
false
Validation
- Admission date in hospital cannot be after end date of follow-up (error)
- Admission date in ward cannot be after end date of follow-up (error)
- Infection date cannot be after end date of follow-up (error)
- End date of follow-up cannot be in the future (error)
- End date of follow-up is more than one year ago (warning)
3 Infection
Date of infection
Help
Date of first positive hemoculture.
Technical specs
Format:
DD/MM/YYYY
CSV column name:
infection_date
Required:
true
Validation
- Admission date in ward cannot be after infection date (error)
- Infection date cannot be after end date of follow-up (error)
- Admission date in hospital cannot be after infection date (error)
- Date of insertion CVC cannot be after infection date (error)
- Date of infection cannot be in the future (error)
- Infection date is more than one year ago (warning)
- The date of infection must be during the data collection period (error)
- Date of insertion PVC cannot be after infection date (error)
Is this a HABSI?
Technical specs
CSV column name:
CD_HABSI
Only when:
Required:
true
Options
| Label | Value |
| Yes, infection occurring >= 48 hours after hospital admission | 1 |
| Yes, infection occurring >= 48 hours after hospital admission and >= 48 hours after ICU admission | 2 |
| No, infection occurring < 48 hours after hospital admission | 3 |
Classification of bloodstream infection episodes OTHER than those appearing 48 hours or more after common hospital admission (non-HABSI)
Technical specs
CSV column name:
sep_cl
Only when:
Required:
false
Options
| Label | Value |
| Bloodstream infections acquired during a previous medical consultation or hospitalisation | 5 |
| Community-acquired bloodstream infection | 3 |
| Bloodstream infections acquired at the beginning of the hospital stay (hospitalisation day 1 or day 2) | 6 |
| Other (specify) | 7 |
Classification of episode
Technical specs
CSV column name:
sep_cl|specify
Only when:
Required:
true
For non-HABSI declared in previous variable, specify type of patient or BSI
Technical specs
CSV column name:
CD_NON_SEP
Only when:
Required:
false
Options
| Label | Value |
| Infection in a TPN patient (Total Parenteral Nutrition) | 1 |
| Infection in an OPAT patient (Outpatient Parenteral Antimicrobial Therapy) | 2 |
| Urosepsis in dialysis patients | 3 |
| Post-operative BSI resulting from surgery during a prior hospitalisation | 4 |
| Other, specify | 5 |
| Unknown | 9 |
Classification of non-HABSI
Technical specs
CSV column name:
TX_NON_SEP_SPECIF
Only when:
Required:
true
Case definition of bloodstream infection
Help
*Adherence to or deviation from the use of clinical signs or symptoms should be declared in Form H
Technical specs
CSV column name:
case_def
Required:
true
Options
| Label | Value |
| At least one blood culture positive for a possible pathogen not included in the list of commensal organisms | 1 |
| At least two different blood cultures positive* for the same commensal microorganism (2 different samples taken within 2 days) AND clinical signs or symptoms* | 2 |
| Only for patients at neonatology (<= 28 days): a positive blood culture for a coagulase-negative staphylococci AND clinical signs or symptoms* AND laboratory criteria | 3 |
| Unknown | 9 |
Validation
- If case definition is unknown, this episode should not be registered (error)
Suspected source of origin of bloodstream infection
Help
• Only one choice possible. If several suspected origins: in case of a single MO, choose the most striking and / or most coherent origin for the isolated MO, in case of multiple MO, choose the origin for which antibiotic treatment seems most appropriate. Ultimately, the clinician makes the final choice. • CVC: see protocol. • Mucositis: see protocol.
Technical specs
CSV column name:
infection_source
Required:
true
Options
| Label | Value |
| Peripheral catheter (PVC) | 2 |
| Other catheter and similar | 3 |
| Invasive non-surgical handling | 4 |
| Urinary tract | 5 |
| Pleuropulmonary | 6 |
| Digestive / abdominal | 7 |
| Surgical site (deep infection, organ or space) | 8 |
| Skin / soft tissues | 9 |
| Central venous catheter (CVC) | 13 |
| Digestive Mucosal barrier injury (MBI) | 14 |
| Other (specify) | 11 |
| Unknown | 10 |
Specify infection source
Technical specs
CSV column name:
infection_source|specify
Only when:
Required:
true
In case of invasive non-surgical handling, suspected invasive manipulation as cause of bloodstream infection
Technical specs
CSV column name:
inv_man
Only when:
Required:
false
Options
| Label | Value |
| Prostate biopsy | 1 |
| Double J probe | 2 |
| Cystoscopy | 3 |
| Cardiac catheterisation | 4 |
| Bronchoscopy | 5 |
| Endoscopic retrograde cholangiopancreatography (ERCP) | 8 |
| Other (specify) | 9 |
Specify invasive non-surgical handling
Technical specs
CSV column name:
inv_man|specify
Only when:
Required:
false
In case of urinary tract source, did the patient have a probe or was the patient probed in the 2 days preceding the infection?
Technical specs
CSV column name:
inv_dev1
Only when:
Required:
true
Options
| Label | Value |
| No | 1 |
| Yes: Transurethral-indwelling without continuous irrigation | 3 |
| Yes: Transurethral-indwelling with continuous irrigation | 4 |
| Yes: Transurethral-intermittent | 5 |
| Yes: Other (Nephrostomy, Urostomy, Suprapubic) | 7 |
| Unknown | 9 |
Specify other (Nephrostomy, Urostomy, Suprapubic)
Technical specs
CSV column name:
inv_dev1|specify
Only when:
Required:
false
In case of pleuropulmonary source, was the patient tracheotomised or intubated in the 2 days preceding the infection?
Technical specs
CSV column name:
inv_dev2
Only when:
Required:
true
Options
| Label | Value |
| Yes | 2 |
| No | 1 |
| Unknown | 9 |
If suspected origin CVC or unknown, CVC used when infection is encountered or within 2 days preceding infection?
Technical specs
CSV column name:
CD_CVCATH_UNK
Only when:
Required:
true
Options
| Label | Value |
| Yes | 1 |
| No | 0 |
| Unknown | 9 |
Date of insertion CVC
Technical specs
Format:
DD/MM/YYYY
CSV column name:
cvc_dt
Only when:
Required:
false
Validation
- Date of insertion CVC cannot be after infection date (error)
- Date of insertion CVC cannot be in the future (error)
Type of CVC
Help
Type of CVC: *CVCs of the types used for haemodialysis in hospitalised patients are also included in the surveillance, with the exception of permanent haemodialysis catheters of the specific type arteriovenous fistula or graft. See section 8.2 of Form C for the variables "type of CVC" and "Use of CVC for haemodialysis" as part of specifying the origin of a BSI episode. *The following catheters are not considered CVCs, as they are not used for infusion or blood sampling but for therapeutic procedures: extracorporeal membrane oxygenation (ECMO), femoral, radial, and umbilical arterial catheters, intra-aortic balloon pump, subcutaneous and intraosseous catheters.
Technical specs
CSV column name:
cvc_type
Only when:
Required:
false
Options
| Label | Value |
| Non-tunnelled catheter | 1 |
| Tunnelled catheter (Hickman tunnelled catheter with or without cuff) | 2 |
| Peripherally inserted central catheter (PICC) non-tunnelled | 3 |
| Peripherally inserted central catheter (PICC) tunnelled | 4 |
| Implanted catheter (includes implantable chambers) | 5 |
| Umbilical catheter (newborns) | 446476009 |
| Other (specify) | 7 |
| Unknown | 9 |
Specify type of CVC
Technical specs
CSV column name:
cvc_type|specify
Only when:
Required:
false
Location of CVC
Help
Location of CVC: It's not where the catheter is inserted, or what type of device it is, but where it ends (one of the below-mentioned vessels or the heart) that counts.
Technical specs
CSV column name:
CD_CVCATH_LOC
Only when:
Required:
false
Options
| Label | Value |
| Jugular vein | 63190004 |
| Subclavian vein | 9454009 |
| Femoral vein | 83419000 |
| Other (specify) | 74964007 |
| Unknown | 261665006 |
Specify location of CVC
Technical specs
CSV column name:
TX_CVCATH_LOC_SPECIF
Only when:
Required:
false
CVC used for haemodialysis
Technical specs
CSV column name:
CD_CVCATH_HEMDIAL
Only when:
Required:
false
Options
| Label | Value |
| Yes | 1 |
| No | 0 |
| Unknown | 9 |
If suspected origin PVC or unknown, PVC used when infection is encountered or within 2 days preceding infection?
Technical specs
CSV column name:
CD_PVC_UNK
Only when:
Required:
true
Options
| Label | Value |
| Yes | 1 |
| No | 0 |
| Unknown | 9 |
Date of insertion PVC
Technical specs
Format:
DD/MM/YYYY
CSV column name:
DT_PVC
Only when:
Required:
false
Validation
- Date of insertion PVC cannot be after infection date (error)
- Date of insertion PVC cannot be in the future (error)
Type of PVC
Help
Type of PVC: a PVC is an intravascular catheter inserted into a superficial vein or a deep peripheral vein, while remaining within the peripheral venous system. It is indicated for the administration of infusions, blood sampling, transfusions, chemotherapy, and other drug treatments.
Technical specs
CSV column name:
CD_PVC_TPE
Only when:
Required:
false
Options
| Label | Value |
| Short (<6cm) | 1 |
| Long peripheral catheter 'Mini-Midline' (6-15cm) | 2 |
| Midline (>15cm) | 3 |
| Other (specify) | 4 |
| Unknown | 9 |
Specify type of PVC
Technical specs
CSV column name:
TX_PVC_TPE_SPECIF
Only when:
Required:
false
Suspected source with microbiological documentation
Help
'Yes' if the same microorganism is found both in the blood culture or blood cultures and at the level of the source of origin; ‘no’ if the same microorganism is not found both in the blood culture or blood cultures and at the level of the source of origin; ‘unknown’ if no sample was taken at the level of the suspected source of origin, or if the result of the sample is unknown, or if the source of origin is unknown.
Technical specs
CSV column name:
mo_doc
Required:
true
Options
| Label | Value |
| Yes | 1 |
| No | 0 |
| Unknown | 9 |
Sample ID
Help
Please make sure this corresponds with the sample ID from the NSIH-BSI laboratory form
Technical specs
CSV column name:
TX_SAMPLE_ID
Length:
100
Required:
true