KCE Trial - Order sets for lab tests GPs - General practitioner (KCELABGP_GP)
- Status: active
- How to create a CSV file for this data collection?
- Start date: 31/05/2017
1 Patient identification
National registry ID of the patient
Help
Please encode a social security identification number (SSIN). Please note that the patient ID is always pseudonymised before being transferred to Healthdata.
Technical specs
CSV column name:
patient_id
Required:
false
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
Please encode a social security identification number (SSIN). Please note that the patient ID is always pseudonymised before being transferred to Healthdata.
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)
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Patient
Data element:
LastName
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 of birth
Technical specs
Format:
DD/MM/YYYY
CSV column name:
patient_id|date_of_birth
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:
DateOfBirth
Validation
- The date of birth cannot be in the future (error)
- Date of birth cannot be after date of death (error)
Sex
Technical specs
CSV column name:
patient_id|sex
Required:
noSSIN(Needed only if no national register number is entered)
Options
| Label | Value |
| Female | F |
| Male | M |
| Unkown | U |
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Patient
Data element:
Gender
Place of residence
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
Deceased?
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
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
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Patient
Data element:
DateOfDeath
Validation
- The date of death cannot be in the future (error)
- Date of birth cannot be after date of death (error)
Telephone number
This is a container for multiple answers. See the reference documentation for more details. Below you can find the information about the fields of the container
List items
Telephone number
Help
If both a landline and a mobile number are available, please provide both.
Technical specs
CSV column name:
telephone_number|telephone_number
Length:
20
Required:
true
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Patient
Data element:
TelephoneNumber
2 Physician identification
RIZIV/INAMI-code of the treating physician
Technical specs
CSV column name:
physician
Length:
100
Reference list:
PHYSICIAN
Required:
true
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Caregiver
Data element:
CareGiverIdentificationNumber
3 Reason for ordering tests
Date of laboratory test order
Technical specs
Format:
DD/MM/YYYY
CSV column name:
date_of_laboratory_test_order
Required:
true
Validation
- The date of laboratory test order cannot be before 01/10/2017 (error)
- The date of laboratory test order cannot be in the future (error)
Why were you ordering this test/ these test(s)
Technical specs
CSV column name:
why_were_you_ordering_this_test_these_tests
Required:
true
Options
| Label | Value |
| To exclude a specific disease | to_exclude_a_specific_disease |
| To confirm diagnosis | to_confirm_diagnosis |
| At patient's request | at_patients_request |
| To reassure the patient | to_reassure_the_patient |
| Because I was no sure what the matter was | because_i_was_no_sure_what_the_matter_was |
| To help me decide on treatment | to_help_me_decide_on_treatment |
| As a check-up for the patients known condition or for screening | as_a_checkup_for_the_patients_known_condition_or_for_screening |
| Other reason | other_reason |
Nested option fields
- When other_reason Is selected:text
Other reason
Technical specs
CSV column name:
why_were_you_ordering_this_test_these_tests|other_reason_1
Length:
100
Required:
false
Did you suspect - at the moment you ordered these tests - that the patient had a somatic disease
Technical specs
CSV column name:
did_you_suspect__at_the_moment_you_ordered_these_tests__that_the_patient_had_a_somatic_disease
Only when:
Required:
true
Options
| Label | Value |
| Certainly not | 1 |
| Probably not | 2 |
| Maybe | 3 |
| Probably yes | 4 |
| Certainly yes | 5 |
4 New diagnoses
New diagnoses
This is a container for multiple answers. See the reference documentation for more details. Below you can find the information about the fields of the container
Element conditions
| Message | Expression |
| Date of new diagnosis is before date of laboratory test order | typeof $$.document.target.value.date_of_laboratory_test_order === 'string' && typeof $.date_of_new_diagnosis === 'string'?$.date_of_new_diagnosis >= $$.document.target.value.date_of_laboratory_test_order:true |
| The date of new diagnosis cannot be in the future | typeof $.date_of_new_diagnosis=== 'string'?new Date($.date_of_new_diagnosis) |
Mapping of the clinical building blocks (indicative only)
Concept:
be.en.hd.Problem
Data element:
List items
New diagnosis (ICPC-2 code)
Help
In this field, select the name of the new diagnosis from the thesaurus. Do this for all new diagnoses or problems that have developed since the laboratory test order
Technical specs
CSV column name:
new_diagnoses|0|new_diagnosis
Length:
100
Required:
false
New diagnosis (ICD-10 code)
Technical specs
CSV column name:
new_diagnoses|0|new_diagnosis_icd10_code
Length:
100
Required:
false
New diagnosis (text)
Technical specs
CSV column name:
new_diagnoses|0|new_diagnosis_text
Length:
100
Required:
false
Date of new diagnosis
Technical specs
Format:
DD/MM/YYYY
CSV column name:
new_diagnoses|0|date_of_new_diagnosis
Required:
false
Relation to laboratory test order
Help
In your opinion, is this new diagnosis related to the laboratory test order?
Technical specs
CSV column name:
new_diagnoses|0|relation_to_laboratory_test_order
Required:
false
Options
| Label | Value |
| Yes | TRUE |
| No | FALSE |
Relation to lab test results
Help
Was this new diangosis discovered with the results of the laboratory test order?
Technical specs
CSV column name:
new_diagnoses|0|relation_to_lab_test_results
Only when:
Required:
false
Options
| Label | Value |
| Yes | TRUE |
| No | FALSE |
If applicable, did you diagnose this problem timely and correctly as a result of the laboratory test order?
Help
Answer with ‘no’ if a different set of tests would have allowed you to diagnose this problem sooner or more correctly.
Technical specs
CSV column name:
new_diagnoses|0|diagnosis_correct_timely
Only when:
Required:
false
Options
| Label | Value |
| Yes | TRUE |
| No | FALSE |
5 Downstream activities
1. Downstream investigations
This is a container for multiple answers. See the reference documentation for more details. Below you can find the information about the fields of the container
List items
Did you order extra investigations in follow-up of these labresults? If so, please specifiy them all below. (Add a new item for each additional investigation) .
Technical specs
CSV column name:
downstream_investigations|0|investigation_type
Required:
false
Options
| Label | Value |
| Follow-up laboratory tests | 1 |
| Imaging or endoscopies | 2 |
| Function tests (e.g. spirometry, ECG, EMG …) | 3 |
Specification of investigation type
Help
Please specify the type of follow-up investigation that was ordered (e.g. rx thorax, gastroscopy, colonoscopy, haemoglobinelectophoresis or …) .
Technical specs
CSV column name:
downstream_investigations|0|specification_of_investigation_type
Length:
200
Only when:
Required:
false
2. Did you refer this patient to a specialist doctor or other health professional in follow up of these labresults? If so, please add them all below. (Add a new item for each additional referral). If you referred the patient only because of a medical investigation (e.g. gastroscopy), with no need for a specialist’s consult, please only add the medical investigation higher.
This is a container for multiple answers. See the reference documentation for more details. Below you can find the information about the fields of the container
List items
Referral specialty
Technical specs
CSV column name:
did_you_refer_this_patient_to_a_specialist_doctor_or_other_health_professional_in_follow_up_of_these_labresults__if_so_please_add_them_all_below|referral_specialty
Length:
20
Reference list:
KCELAB_SPECIALTY
Required:
false
3. Did you START, STOP or CHANGE any TREATMENT in this patient in follow up of these labresults?
Technical specs
CSV column name:
did_you_start_stop_or_change_any_treatment_in_this_patient_in_follow_up_of_these_labresults
Required:
false
Options
| Label | Value |
| Yes | 1 |
| No | 2 |
Please add them all below.
Technical specs
CSV column name:
please_add_them_all_below
Only when:
Required:
false
Options
| Label | Value |
| Drug treatment – start | drug_treatment__start |
| Drug treatment – stop | drug_treatment__stop |
| Drug treatment – change (e.g. other posology) | drug_treatment__change_eg_other_posology |
| Blood transfusion | blood_transfusion |
| Surgery | surgery |
| Oncologic treatment (chemotherapy, radiotherapy, immunotherapy …) | oncologic_treatment_chemotherapy_radiotherapy_immunotherapy_ |
| Physiotherapy or occupational therapy | physiotherapy_or_occupational_therapy |
| Psychotherapy | psychotherapy |
| Other | other |
Nested option fields
- When other Is selected:text
Please specify
Technical specs
CSV column name:
please_add_them_all_below|please_specify
Length:
100
Required:
false