PATIENT DATA EXPORT FORMAT

Product: BluVault

Section I: SINGLE PATIENT DATA EXPORT

When a request is made in BluVault to export all data for a single patient using the patient export feature, the user is prompted to select the folder to which he or she would like to save the exported files. BluVault creates a folder named 'Patient_Export_<YYYYMMDDHHMMSS>' under the selected folder where the time string is the current date-time.

The following files are created in that export folder containing all of the selected patient's data:

1. 'patient_header'

This file is a text file containing basic patient demographics in JSON format. The fields contained in this file are as follows:

- The patient id in BluVault

- Patient's first name

- Patient's last name

- Patient's middle name

- Patient's date of birth in the format 'MM/DD/YYYY'

- Patient's gender. The field can contain 'M' for male, 'F' for female and 'O' for other.

2. ‘patient_records’

This file is a text file containing header data for all patient records contained in BluVault in JSON format.

The fields contained in this file are as follows:

- record_id: A unique id assigned to each data item in BluVault.

- capture_time: The exact time when this data was entered into BluVault. It's format is YYYYMMDDHHMMSS.

- patient_id: This is the same unique patient id that is contained in the 'patient_header' file.

- data_type_indicator: This can be either 'Text' or 'Image'.

- item_name: This is the name given to this record in BluVault. It is not a mandatory field and can be blank.

- data_source: This field contains freeform text indicating the external source, if any, from which this data was obtained. It is not a mandatory field and can be blank.

3. A number of text files with the extension, '.txt'

These files contain the text data corresponding to the records in the file in #2 above which have data_type_indicator = 'Text'.

The name of these files is <record_id>.txt where record_id is a field in the file in #2 above. So if a patient data item with data_type_indicator = 'Text' has record_id = 32, the contents of that record are contained in the file named '32.txt'

4. A number of text files with the extension, '.jpg'

These files contain the images corresponding to the records in the file in #2 above which have data_type_indicator = 'Image'.

The name of these files is <record_id>.jpg where record_id is a field in the file in #2 above. So if a patient data item with data_type_indicator = 'Image’ has record_id = 21, the image for that record is contained in the file named ’21.jpg’.

Section II: EXPORTING PATIENT POPULATION DATA

Data for a patient population can be exported using the same patient export feature by selecting multiple patients from the patient selection screen. The data is exported in the same format as that used for a single patient.

Please note the following with respect to the files created for patient populations:

- The ‘patient_header’ and ‘patient_records’ files (refer to the ‘Single Patient Data Export’ section), created for patient populations, will contain data for multiple, unique patient ids.

- For example, if patient ids 12, 23 and 48 are extracted, the ‘patient_header’ file will contain demographics of those three patients. The ‘patient_records’ file will contain records for those three patient ids.

- Note that the record_id is unique across patients. For example, if the record_ids for patient_id = 12 are 2, 4, 5 and 6, these record_ids will not repeat for patient_id = 23 or patient_id = 48. For instance, patient_id = 23 may have record_ids = 12, 13, 14, 15 and 16.

- The files in #3 and #4 above (refer to the ‘Single Patient Data Export’ section) will serve the same purpose in the patient population export context. Since the record_id is unique across patients, the file names in #3 and #4 will be unique and can be linked to the patient using the record_id since the JSON format also contains the patient_id as one of the fields.

Last updated: 4/15/2025