|Table||Available since version||Field||Field description||Comment|
|2||code||CTPC Code||16 alphanumeric characters|
|2||ssin||SSIN of the patient||11 numeric characters|
|2||first_name||First name of the patient|
|2||last_name||Last name of the patient|
|2||phone_number||First phone number of the patient - Formatted||Formatted as used to send the SMS|
|2||source_phone_number||First phone number of the patient|
|2||contact_date||Date of the contact with the patient||The 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|
|2||timestamp||Technical timestamp of the record creation|
|2||sms_message_id||Acknowledgment that the patient received a SMS on the given phone number 1||If 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.|
|2||test_taken_date||Date the CPTC code was used to take a test|
|2||sms_sending_error||SMS provider error code in case of delivery failure for phone number 1|
|2||phone_number_2||Second phone number of the patient - Formatted||Formatted as used to send the SMS|
|2||source_phone_number_2||Second phone number of the patient|
|2||sms_message_id_2||Acknowledgment that the patient received a SMS on the given phone number 2||Same as for phone number 1|
|2||sms_sending_error_2||SMS provider error code in case of delivery failure for phone number 2||Same as for phone number 1|
|2||consulted_date||Timestamp the record was the last time consulted||This field's goal is to extract KPIs|
|2||prescription_source||Source 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.
|2||test_prescribed_reason||TP code that indicates the reason of the prescription||See TP code list. This field is encrypted in the database|
|2||first_symptoms_date||Date when the first symptoms occurred (if any)||This field is encrypted in the database|
|2||correlation_id||Technical identifier for PLF forms|
|2||test_scheduled_date||Date the test was scheduled by the reservation tool|
|2||prescriber_nihii||Nihii number of the doctor that created the CTPC||Only if a doctor created the CTPC via the web application|
|2||prescriber_ssin||SSIN of the doctor that created the CTPC||Only if a doctor created the CTPC via the web application|
|2||prescriber_firstname||First name of the doctor that created the CTPC||Only if a doctor created the CTPC via the web application|
|2||prescriber_lastname||Last name of the doctor that created the CTPC||Only if a doctor created the CTPC via the web application|
|2||linked_entity_type||Type of collectivity for which the doctor acted||Only if a doctor created the CTPC via the web application: COLLECTIVITY, COMPANY|
|2||linked_entity_collectivity_authentic_source||Authentic source of the collectivity||Only present if 'linked_entity_type' is COLLECTIVITY|
|2||linked_entity_collectivity_id||The internal identifier of the collectivity inside its authentic source||Only present if 'linked_entity_type' is COLLECTIVITY|
|2||linked_entity_cbe_number||The company id of the linked entity||Only present if 'linked_entity_type' is COMPANY|
|2||linked_entity_used_with_explicit_declaration||Flag that indicate if the doctor explicitly stated that he acts for the choosen collectivity||If 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.|
|2||mobile_app_test_id||Code generated by the coronalert mobile app (Test request).||17 numeric characters|
|2||mobile_app_date_patient_infectious||Date shown by the coronalert mobile app.||6 numeric characters YYMMDD|
|2||mobile_app_alert||Flag that indicates if the patient was alerted by the coronalert mobile app|
|2||Email address of the patient|
|2||health_care_worker||Flag that indicates if the patient is working in health care sector|
|2||reason_for_non_employee||The 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|
|2||justification_for_non_employee||Textual justification if reason_for_non_employee is present and has value OTHER.|
Only valable for prescription created with the tool for company doctors.
|2.4||last_high_risk_contact_date||The moment of the last high risk contact|
|2.4||validity_start_date||Validity start date of the CTPC.||Optional because some scenario don't imply a validity period.|
|2.4||validity_end_date||Validity end date of the CTPC||Optional because some scenario don't imply a validity period.|
|2.5||suggested_test_type||Indication 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
|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|
|2||prescription_code||Link to a CTPC record|
|2||nihii_number||Nihii number of the doctor that should receive the test result|
|This table is an extension of the prescription_code table and contains dataset 2 of this table|
|2||executor_nihii_nbr||Nihii number of the executor of the sampling|
|2||laboratory_nihii_nbr||Nihii number of the laboratory that will receive the sample|
|2||sampling_id||Identification number of the sample|
|2||sampling_date||Date of the sampling|
|2||sample type||Type of the sample||OROPHARYNGEAL_SWAB, NASOPHARYNGEAL_SWAB, SALIVA_SPITTING, SALIVA_SWAB|
|2.5||sample_type_concept_code||Type 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|
|2||test_type||Type of test to be performed||Only PCR for now|
|2.5||test_concept_code||Accurate type of test that will be performed||TestCode list from Sciensano's data collection (https://www.dropbox.com/s/g97ntmaci4bp87x/TestCodeCodelist.xlsx?dl=0 )|
|2.5||executor_nihii_nbr||Nihii number of the executor of the sampling|
|2.5||executor_ssin_nbr||Ssin number of the executor of the sampling||If the executor doesn't have a valid nihii number.|
|2.5||sampling_id||Identification number of the sample|
|2.5||sampling_date||Date of the sampling|
|2.5||test_code||Accurate type of test that will be performed||TestCode list from Sciensano's data collection (https://www.dropbox.com/s/g97ntmaci4bp87x/TestCodeCodelist.xlsx?dl=0 )|
|2.5||sample_type||Type 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|
|2.5||place_of_analysis||Where the sampling was executed||Allowed values: ON_SITE, LABORATORY|
|2.5||test_execution_date||Date of the test execution|
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.
Date when the result was sent to sciensano.
Only filled if send_result_to_sciensano flag was true.