ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
TableAvailable since versionFieldField descriptionComment
2
prescription_code
3
2codeCTPC Code16 alphanumeric characters
4
2ssinSSIN of the patient11 numeric characters
5
2first_nameFirst name of the patient
6
2last_nameLast name of the patient
7
2phone_numberFirst phone number of the patient - FormattedFormatted as used to send the SMS
8
2source_phone_numberFirst phone number of the patient
9
2contact_dateDate of the contact with the patientThe contact with the patient can be done before the record is created (contact center call done before the creation in the database). New flows tends to be synchrone (API calls) => contact date will be the same as the 'timestamp' field
10
2timestampTechnical timestamp of the record creation
11
2sms_message_idAcknowledgment that the patient received a SMS on the given phone number 1If the SMS could not be delivered, this field remains empty. The field 'sms_sending_error' will be filled with the error code of our SMS provider.
12
2test_taken_dateDate the CPTC code was used to take a test
13
2sms_sending_errorSMS provider error code in case of delivery failure for phone number 1
14
2phone_number_2Second phone number of the patient - FormattedFormatted as used to send the SMS
15
2source_phone_number_2Second phone number of the patient
16
2sms_message_id_2Acknowledgment that the patient received a SMS on the given phone number 2Same as for phone number 1
17
2sms_sending_error_2SMS provider error code in case of delivery failure for phone number 2Same as for phone number 1
18
2consulted_dateTimestamp the record was the last time consultedThis field's goal is to extract KPIs
19
2prescription_sourceSource that created the CPTC.
This source is function of the business context in which the CTPC code is created.

New integrators that will create CTPC code must ask eHealth project leader which source to use during the onboarding phase.
SCRIPTS: Contact center scripts
SCRIPTS_COLLECTIVITY_DOCTORS: Contact center scripts used by collectivity doctors that use 2A script from scratch
EFORM_LABO_TEST_PRESCRIPTION: Created after an eform labo test prescription has been created by a GP (general practitioner).
HOLIDAY_RETURN: Created after a PLF (Passenger Locator Form) has been submitted
SAT: Self Assessment tool.
CORONA_ALERT_APP: Contact center inbound call for script 2C after a Corona Alert App alert.
APP_COLLECTIVITY_ENTERPRISE_DOCTOR: Created by the PCR Test prescription app frontend used by a collectivity or a company doctor.
CLB: CLB/PMS center for schools
PHARMACIST: Pharmacist's software
MOBILE_TESTING: Mobile application to create CTPC code for cluster discovery
SCRIPTS_SELF_TESTING: Contact center scripts used for self testing input.
PSE: Promotion sociale de la santé
SCRIPTS_YOUTH_CAMP: Contact center scripts used for youth camps.
CITIZEN: Created by the citizen him self.
20
2test_prescribed_reasonTP code that indicates the reason of the prescriptionSee TP code list. This field is encrypted in the database
21
2first_symptoms_dateDate when the first symptoms occurred (if any)This field is encrypted in the database
22
2correlation_idTechnical identifier for PLF forms
23
2test_scheduled_dateDate the test was scheduled by the reservation tool
24
2prescriber_nihiiNihii number of the doctor that created the CTPCOnly if a doctor created the CTPC via the web application
25
2prescriber_ssinSSIN of the doctor that created the CTPCOnly if a doctor created the CTPC via the web application
26
2prescriber_firstnameFirst name of the doctor that created the CTPCOnly if a doctor created the CTPC via the web application
27
2prescriber_lastnameLast name of the doctor that created the CTPCOnly if a doctor created the CTPC via the web application
28
2linked_entity_typeType of collectivity for which the doctor actedOnly if a doctor created the CTPC via the web application: COLLECTIVITY, COMPANY
29
2linked_entity_collectivity_authentic_sourceAuthentic source of the collectivityOnly present if 'linked_entity_type' is COLLECTIVITY
30
2linked_entity_collectivity_idThe internal identifier of the collectivity inside its authentic sourceOnly present if 'linked_entity_type' is COLLECTIVITY
31
2linked_entity_cbe_numberThe company id of the linked entityOnly present if 'linked_entity_type' is COMPANY
32
2linked_entity_used_with_explicit_declarationFlag that indicate if the doctor explicitly stated that he acts for the choosen collectivityIf the link between a doctor and a collectivity cannot be made through the collectivtiy database, the doctor can declare explicitly acting for a given collectivity and creating CTPC for that collectivity.
33
2mobile_app_test_idCode generated by the coronalert mobile app (Test request). 17 numeric characters
34
2mobile_app_date_patient_infectiousDate shown by the coronalert mobile app.6 numeric characters YYMMDD
35
2mobile_app_alertFlag that indicates if the patient was alerted by the coronalert mobile app
36
2emailEmail address of the patient
37
2health_care_workerFlag that indicates if the patient is working in health care sector
38
2reason_for_non_employeeThe reason why the prescriber created a CTPC for someone not working in its company.

Only valable for prescription created with the tool for company doctors.
Values are CONSULTANT, SERVICE_COMPANY, OTHER
39
2justification_for_non_employeeTextual justification if reason_for_non_employee is present and has value OTHER.
Only valable for prescription created with the tool for company doctors.
40
2.4last_high_risk_contact_dateThe moment of the last high risk contact
41
2.4validity_start_dateValidity start date of the CTPC. Optional because some scenario don't imply a validity period.
42
2.4validity_end_dateValidity end date of the CTPCOptional because some scenario don't imply a validity period.
43
2.5suggested_test_typeIndication on the type of test that should be performed. It's just an indication because the type of test can be changed during the sampling phase (decision of the sample taker).
Available values are : PCR, ANTIGEN, ANTIBODY, PCR_OR_ANTIGEN
44
45
test_result_recipients
This table is an extension of the prescription_code table. It's a separate table because it's possible to indicate multiple test result's recipient
46
2prescription_codeLink to a CTPC record
47
2nihii_numberNihii number of the doctor that should receive the test result
48
laboratory_test_request
This table is an extension of the prescription_code table and contains dataset 2 of this table
49
2codeCTPC Code
50
2executor_nihii_nbrNihii number of the executor of the sampling
51
2laboratory_nihii_nbrNihii number of the laboratory that will receive the sample
52
2sampling_idIdentification number of the sample
53
2sampling_dateDate of the sampling
54
2sample typeType of the sampleOROPHARYNGEAL_SWAB, NASOPHARYNGEAL_SWAB, SALIVA_SPITTING, SALIVA_SWAB
55
2.5sample_type_concept_codeType of the sample.The type of sample. Available values are SNOMED code from Sciensano's collection data. see https://www.dropbox.com/s/szddzuuzaqjk3mj/SpecimenMaterialCodelist.xlsx?dl=0
56
2test_typeType of test to be performedOnly PCR for now
57
2.5test_concept_codeAccurate type of test that will be performedTestCode list from Sciensano's data collection (https://www.dropbox.com/s/g97ntmaci4bp87x/TestCodeCodelist.xlsx?dl=0 )
58
59
sampling
60
2.5codeCTPC code
61
2.5executor_nihii_nbrNihii number of the executor of the sampling
62
2.5executor_ssin_nbrSsin number of the executor of the samplingIf the executor doesn't have a valid nihii number.
63
2.5sampling_idIdentification number of the sample
64
2.5sampling_dateDate of the sampling
65
2.5test_codeAccurate type of test that will be performedTestCode list from Sciensano's data collection (https://www.dropbox.com/s/g97ntmaci4bp87x/TestCodeCodelist.xlsx?dl=0 )
66
2.5sample_typeType of the sample.The type of sample. Available values are SNOMED code from Sciensano's collection data. see https://www.dropbox.com/s/szddzuuzaqjk3mj/SpecimenMaterialCodelist.xlsx?dl=0
67
2.5place_of_analysisWhere the sampling was executedAllowed values: ON_SITE, LABORATORY
68
69
test_execution
70
2.5codeCTPC code
71
2.5test_execution_dateDate of the test execution
72
2.5send_result_to_sciensano
Flag that indicates if the use asked CTPC application to send the result to sciensano.
Only available for the Collectivity Tool (won't be available on public API).
Integrators must send themself the results to sciensano.
73
2.5result_sent_to_sciensano
Date when the result was sent to sciensano.
Only filled if send_result_to_sciensano flag was true.
Audit field.
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100