NSIH - Clostridium difficile (NSIH-CDIF)

  • Start date: 30/06/2025
date

Start date

Not to be included in the CSV.

Technical specs

Format:

DD/MM/YYYY

CSV column name:

start_date

Default value:

2025-07-01

Only when:

Required:

false

Read only

Validation
  • The date of onset of CDI symptoms must be during the data collection period (error)
  • If symptoms (diarrhea) present upon admission=1/yes, then date of admission must be during the data collection period (error)
  • Admission date in hospital needs to be during the data collection period (warning)
  • Admission date in ward needs to be during the data collection period (warning)
date

End date

Not to be included in the CSV.

Technical specs

Format:

DD/MM/YYYY

CSV column name:

end_date

Default value:

2025-12-31

Only when:

Required:

false

Read only

Validation
  • The date of onset of CDI symptoms must be during the data collection period (error)
  • If symptoms (diarrhea) present upon admission=1/yes, then date of admission must be during the data collection period (error)
  • Admission date in hospital needs to be during the data collection period (warning)
  • Admission date in ward needs to be during the data collection period (warning)
text

Automatically generated code for the reference laboratory

Not to be included in the CSV.

Help

This ID is automatically generated and is composed of (a part of) the NIHDI number of your institution and an incremental number.

Technical specs

CSV column name:

id_for_reference_centre

Computed:

Required:

false

1 Patient

text

Responsible infection control physician

Help

This is a purely operational question, which is not scientifically required.

Technical specs

CSV column name:

responsible_infection_control_physician

Length:

11

Reference list:

PHYSICIAN

Required:

true

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Caregiver

Data element:

CareGiverIdentificationNumber

patient identificator

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 WIV-ISP. 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

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

PatientIdentificationNumber

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 WIV-ISP. 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.

text

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

Mapping of the clinical building blocks (indicative only)

Concept:

na

Data element:

na

boolean

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
LabelValue
YesTRUE
NoFALSE
text

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)

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

LastName

text

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)

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

FirstNames

date

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

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

DateOfBirth

choice

Sex

Technical specs

CSV column name:

patient_id|sex

Required:

true

Options
LabelValue
MaleM
FemaleF
UnknownU
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

Gender

text

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 useful for internal use.

Technical specs

CSV column name:

patient_id|place_of_residence

Length:

5

Reference list:

POSTAL_CODE

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

Postcode

boolean

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 useful for internal use.

Technical specs

CSV column name:

patient_id|deceased

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

DeathIndicator

Validation
  • The patient outcome is not valid for a patient who is still alive (warning)
  • The patient outcome is not valid for a patient who is dead (warning)
Options
LabelValue
YesTRUE
NoFALSE
date

Date of death

Help

Only to be filled in if useful for internal use.

Technical specs

Format:

DD/MM/YYYY

CSV column name:

patient_id|date_of_death

Only when:

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Patient

Data element:

DateOfDeath

2 Stay

text

Admission ID

Help

Only to be filled in if useful for internal use.

Technical specs

CSV column name:

admission_id

Length:

100

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

na

Data element:

na

date

Admission date in hospital

Technical specs

Format:

DD/MM/YYYY

CSV column name:

admission_date

Required:

true

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Contact

Data element:

StartDateTime

Validation
  • If symptoms (diarrhea) present upon admission=1/yes, then date of admission must be during the data collection period (error)
  • Admission date in hospital cannot be after admission date in ward (error)
  • Admission date in hospital cannot be after discharge date (error)
  • Admission date in hospital cannot be after date of onset of CDI symptoms (error)
  • Admission date in ward cannot be in the future (error)
  • Admission date in hospital cannot be in the future (error)
  • Admission date in hospital needs to be during the data collection period (warning)
  • Admission date in ward needs to be during the data collection period (warning)
date

Admission date in ward where CDI occurred

Help

Only if different from admission date in hospital

Technical specs

Format:

DD/MM/YYYY

CSV column name:

ward_admission_date

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Contact

Data element:

StartDateTime

Validation
  • Admission date in hospital cannot be after admission date in ward (error)
  • Admission date in ward cannot be in the future (error)
  • Admission date in ward needs to be during the data collection period (warning)
text

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

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.HealthcareProvider

Data element:

HealthcareProviderIdentificationNumber

text

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 contact support.healthdata@wiv-isp.be.

Technical specs

CSV column name:

site_number

Length:

100

Reference list:

SITE

Required:

true

text

ID of ward where CDI 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 contact Healthdata Support (Support.Healthdata@wiv-isp.be, tel. 02/793 01 42) 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

Mapping of the clinical building blocks (indicative only)

Concept:

na

Data element:

na

text

Specialty of ward where CDI occurred

Help

If the specialty of ward does not appear in the drop-down list please contact Healthdata Support (Support.Healthdata@wiv-isp.be, tel. 02/793 01 42) to add this specialty.

Technical specs

CSV column name:

ward_type

Length:

200

Reference list:

SPECIALTY_DETAILED

Required:

nosocomial

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.HealthcareProvider

Data element:

DepartmentSpecialty

date

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:

discharge_date

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.Contact

Data element:

EndDateTime

Validation
  • Admission date in hospital cannot be after discharge date (error)
  • Date of onset of CDI symptoms cannot be after discharge date (error)
  • Discharge date cannot be in the future (error)
  • Discharge date is more than one year ago (warning)

3 Infection

choice

Symptoms (diarrhea) present upon admission

Technical specs

CSV column name:

symptoms_diarrhea_present_upon_admission

Required:

true

Options
LabelValue
Yes1
No0
Unknown9
Validation
  • The date of onset of CDI symptoms must be during the data collection period (error)
  • If symptoms (diarrhea) present upon admission=1/yes, then date of admission must be during the data collection period (error)
date

Date of onset of diarhea/symptoms

Help

This is mandatory if symptom onset was during current hospitalisation, but not recorded if signs/symptoms were present on admission.

Technical specs

Format:

DD/MM/YYYY

CSV column name:

infection_date

Only when:

Required:

true

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferConcern

Data element:

ProblemStartDate

Validation
  • The date of onset of CDI symptoms must be during the data collection period (error)
  • Date of onset of CDI symptoms cannot be after discharge date (error)
  • Admission date in hospital cannot be after date of onset of CDI symptoms (error)
  • Date of onset of CDI symptoms cannot be after sampling date (error)
  • Date of onset of CDI symptoms cannot be in the future (error)
  • Date of onset of CDI symptoms is more than one year ago (warning)
choice

Recurrent case

Help

Choose yes if positive laboratory tests for CDI in diarrhoeal stools after the end of treatment for CDI occurring > 2 weeks and < 8 weeks following the onset of a previous episode.

Technical specs

CSV column name:

recurrent_case

Required:

true

Options
LabelValue
Yes1
No0
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

na

Data element:

na

choice

Presumed case origin

Help

o Care facility (acute or chronic) if onset of symptoms more than 2 days after admission to this facility, OR within 4 weeks after leaving this facility. o Other healthcare facility e.g. ambulatory patient, dialysis patient, or patient having regular contacts with care facility. o Community: A case with onset of symptoms outside of a care facility, for a patient who has not been admitted to a care facility in the previous 12 weeks. o Origin undetermined: In case of a patient discharged from the hospital 4 to 12 weeks before the onset of symptoms. o Origin unknown: Insufficient information to answer this question.

Technical specs

CSV column name:

infection_source

Required:

true

Options
LabelValue
Community1
Acute care facility2
Origin undetermined3
Long-term care facility4
Other healthcare facility (e.g. outpatient)5
Origin unknown6
Mapping of the clinical building blocks (indicative only)

Concept:

na

Data element:

na

choice

Complicated CDI

Help

Yes, if the CDI has one or more of the following consequence(s) : o Admission to a healthcare facility for treatment of community-onset CDI. o Admission to an intensive care unit for treatment of CDI or its complications (eg: shock). o Surgery (colectomy) for toxic megacolon, perforation or refractory colitis. o Death within 30 days, if CDI is the first cause, or contributed to death.

Technical specs

CSV column name:

complicated_course_of_cdi

Required:

true

Options
LabelValue
Yes1
No0
Unknown9
choice

Patient outcome

Help

o Alive, end of follow-up : The patient is still hospitalised at the end of the follow-up period (one month after the end of the surveillance period). o Death, CDI definitely contributed to death : If a causal relationship between CDI and death has been established. o Death, CDI possibly contributed to death : A causal relationship between CDI and death cannot be established, but it is plausible that CDI contributed to the death. o Death, no relation to CDI : It has been established that the cause of death is not related to CDI. o Death, relationship to CDI unknown : If lack of evidence that CDI contributed to death. o Unknown : Unknown patient outcome

Technical specs

CSV column name:

patient_outcome

Required:

true

Options
LabelValue
Discharged alive1
Alive, end of follow-up2
Death, CDI definitely contributed to death3
Death, CDI possibly contributed to death4
Death, no relation to CDI5
Death, relationship to CDI unknown6
Unknown9
Validation
  • The patient outcome is not valid for a patient who is still alive (warning)
  • The patient outcome is not valid for a patient who is dead (warning)

4 Laboratory

text

Sample ID

Help

Only to be filled in if useful for internal use.

Technical specs

CSV column name:

sample_id

Length:

100

Required:

false

date

Sampling date

Help

Date of first positive stool sample.

Technical specs

Format:

DD/MM/YYYY

CSV column name:

sample_date

Required:

false

Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

DrawingDateTime

Validation
  • Date of onset of CDI symptoms cannot be after sampling date (error)
  • Sampling date cannot be in the future (error)
  • Sampling date is more than one year ago (warning)
fieldset

Test results

Fields
choice

Glutamate dehydrogenase (GDH)

Technical specs

CSV column name:

test_result|glutamate_dehydrogenase_gdh

Required:

false

Options
LabelValue
Positive1
Negative0
Not executed5
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

Result

Validation
  • Test results: At least one of the test results must be positive. (error)
  • Test results: A positive culture must be accompanied by another positive test result. (error)
choice

Enzyme Immuno assay (EIA) – toxin on stool

Technical specs

CSV column name:

test_result|enzyme_immuno_assay_eia__toxin__on_stool

Required:

false

Options
LabelValue
Positive1
Negative0
Not executed5
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

Result

Validation
  • Test results: At least one of the test results must be positive. (error)
  • Test results: A positive culture must be accompanied by another positive test result. (error)
choice

Nucleic acid amplification testing (NAAT) (PCR) – on stool

Technical specs

CSV column name:

test_result|nucleic_acid_amplification_testing_naat__on_stool

Required:

false

Options
LabelValue
Positive1
Negative0
Not executed5
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

Result

Validation
  • Test results: At least one of the test results must be positive. (error)
  • Test results: A positive culture must be accompanied by another positive test result. (error)
choice

Culture

Technical specs

CSV column name:

test_result|culture

Required:

false

Options
LabelValue
Positive1
Negative0
Not executed5
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

Result

Validation
  • Test results: At least one of the test results must be positive. (error)
  • Test results: A positive culture must be accompanied by another positive test result. (error)
  • Test results: It is not possible to encode the result of EIA (toxin on culture) if no culture has been done (error)
choice

Enzyme Immuno assay (EIA) – toxin on culture

Technical specs

CSV column name:

test_result|toxin_culture

Required:

false

Options
LabelValue
Positive1
Negative0
Not executed5
Unknown9
Mapping of the clinical building blocks (indicative only)

Concept:

be.en.hd.TransferLaboratoryResult

Data element:

Result

Validation
  • Test results: At least one of the test results must be positive. (error)
  • Test results: A positive culture must be accompanied by another positive test result. (error)
  • Test results: It is not possible to encode the result of EIA (toxin on culture) if no culture has been done (error)
choice

Strain transferred to Reference Laboratory UCL

Technical specs

CSV column name:

strain_transferred_to_reference_laboratory_ucl

Required:

false

Options
LabelValue
Yes1
No0
Unknown9