Intervention Export

event

The event represents the type of transaction that occured in the system for this information to be saved.

procedure_basedOn_0_serviceRequestId

The CIE Hub Service Request ID. This is the ID that is passed from the Hub when the referral is initially created. This will connect the intervention with the corresponding referral.

servicerequest_identifiers_intake_id

It can be passed with client's "Referral ID" to link up their Referral ID to the CIE Hub.  The advantage to this is that the client may want this on their reporting side to easily match up the referrals and person’s to resources that are generated in the CIE Hub.

procedure_subject_patientId

The CIE Hub Patient Id. This is the unique identifier that ties together all the information about the patient in the hub. This will be used, in this file, to connect the intervention(s) with the Patient.

procedure_code_coding_0_code

Identification of the intervention that was given to the patient using a coding system. This represents the code. For example, a Gravity intervention code such as I-113, Provision of Food Voucher.

procedure_code_coding_0_display

Identification of the intervention that was given to the patient using a coding system. This represents the human readable display of that code.

procedure_code_coding_0_system

Identification of the intervention that was given to the patient using a coding system. This represents the system of the code. (for example, LOINC or Gravity)

procedure_code_text

Free text that can be added to futher describe the type of intervention that took place.

procedure_category_coding_0_code

Classification or metadata code associated with the intervention using a coding system.

procedure_category_coding_0_display

Classification or metadata associated with the intervention using a coding system. This represents the human readable text.

procedure_category_coding_0_system

Classification or metadata associated with the intervention using a coding system. This represents the system of the code. (for example, LOINC or Gravity)

procedure_note_0_text

The text of a note that is associated with the Intervention.

procedure_note_0_time

The time and date of the creation of the note

procedure_note_0_author_reference_display

The name of the author of the note.

procedure_recorder_display

The name of the system, organization, or person that recorded this intervention

procedure_performed_dateTime

The date and time the intervention took place

patient_identifiers_clientid

This is the patients client id that was supplied in the patient identifiers field when the service request was supplied.

patient_name_given

The given name of the patient.

patient_name_family

The family name of the patient.

patient_name_middle

The middle name of the patient

patient_gender

The gender of the patient

patient_mobile_phone

The mobile phone of the patient

patient_home_phone

The home phone number of the patient

patient_email

The email of the patient

patient_sms

The mobile phone number for texting with the patient

patient_address_x_line_0*

The address of the patient and the first line of the address. This is an array which has been flattened. So if there are more then one then it will have a address_1 and so on.

patient_address_x_line_1*

The address of the patient and the second line of the address. This is an array which has been flattened. So if there are more then one then it will have a address_1 and so on.

patient_address_x_city*

The city of the patient. This is an array which has been flattened. So if there are more then one then it will have a address_1 and so on.

patient_address_x_state*

The state of the patient. This is an array which has been flattened. So if there are more then one then it will have a address_1 and so on.

patient_address_x_postalcode*

The postal code of the patient. This is an array which has been flatten. So if there are more then one then it will have a address_1 and so on.

patient_birthDate

The birth date of the patient