Updated May 2021

Entity File Names

File naming convention mask: EntityName_EffectiveDate<any Suffix>.csv

Examples:

<EntitiyName>_<EffectiveDate>-<VisitDate>.csv (added or updated records)
<EntitiyName>_<EffectiveDate>-<VisitDate>.
del (deleted records)

Where:  EntityName is the name of the corresponding Data Book Entity.
EffectiveDate
is the date that the data was extracted on (format: YYYYMMDD).

VisitDate
is the Visit Year and Month of the activity data in the package (format: YYYYMM).

Valid entity names are:

patient

disease

healthcare_professional

clinic_visit

rad_plan_treat_activity

syst_drug_delivery_event

smoking_cessation

chart_number_mapping


Examples:
 

patient_20080505.csv
disease_20080401.del
healthcare_professional_20080610.csv

syst_drug_delivery_event_20080722-200806.csv
  

If you are including more than one file for the same entity in a package (for example, if different portions of your data are extracted from different systems into different CSV files that you want to send in the same package), you should add a suffix to the date portion of the filename to differentiate the files.

Examples: 

patient_20080503a.csv
patient_20080503b.csv
 

NOTE:  Activity csv files (ie. Clinic Visit, Systemic, Radiation) should only contain one month of data per zip package. Zip packages can contain multiple csv files (for a single or multiple entities), however, all csv files must be for the same month of data.

Note: .del files are optional files that can be used to indicate record deletions for the patient and disease entities. They are also CSV (comma separated value) format files that contain only the business identifiers for the records that have been deleted. The following data elements are defined as the business identifiers for each entity:

patient - patient_chart_number, submitting_hospital_number 

disease - patient_chart_number, submitting_hospital_number, registration_date, disease_sequence number

Note:  For patient.del, disease.del and chart_number_mapping.csv files, once submitted, this process cannot be reversed, as this is applied directly to the tables in Production.

 

Print This Page