Configuring Outreach-Related Data

Several data elements are configurable to help health centers make the most effective use of Relevant Outreach.

Note: This article is intended for technical Relevant users such as data pipeline administrators. Please refer your data pipeline administrators to this page or reach out to support@relevant.healthcare for assistance.

Patients data element

The following patient columns must be mapped:

  • preferred_phone:  varying character - This column determines where to send a patient’s outreach messages.

  • do_not_contact: boolean

    • This column should be set to TRUE for patients who have not consented to receive text messages
    • Patients where do_not_contact equals FALSE can be included in outreach audiences
    • Note: patients may opt out of receiving messages by replying STOP or similar keywords. Twilio (Relevant Outreach’s SMS service provider) will not deliver messages to these patients, regardless of the value of the do_not_contact column. Patients can opt back into your messaging services by texting START.

  • deceased: boolean - This column should be set to FALSE for patients to appear in outreach audiences.

The following patient columns may be required depending on how audiences and message template parameters are configured. They are mapped during Relevant’s initial implementation.

  • primary_care_giver_id: integer, FK to providers - This column joins with providers to determine the value of the {{pcp}} message template parameter.
  • primary_location_id: integer, FK to locations - This column joins with locations to determine the value of the {{loc}}, {{loc_phone}}, and {{loc_addr}} message template parameters.
  • first_name: character varying - This column determines the value of the {{first_name}} message template parameter.

Locations data element

The following location columns may be required depending on how audiences and message template parameters are configured. Many of them are mapped during Relevant’s initial implementation.

  • phone_number: character varying
    • This column determines the value of {{loc_phone}} and {{next_appt_loc_phone}} message template parameters.

  • address: character varying

    • This column determines the value of {{loc_addr}} and {{next_appt_loc_addr}} message template parameters.
  • name: character varying
    • This column determines the value of {{loc}} and {{next_appt_loc}} message template parameters.

Appointments data element

The following appointment columns may be required depending on how audiences and message template parameters are configured. Many of them are mapped during Relevant’s initial implementation.

  • patient_id: integer, FK to patients
  • provider_id: integer, FK to providers - This column joins with providers to determine the value of the {{next_appt_provider}} message template parameter.
  • location_id: integer, FK to locations - This column joins with locations to determine the value of the {{next_appt_loc}}, {{next_appt_loc_phone}}, and {{next_appt_loc_addr}} message template parameters.
  • visit_type: character varying - This column determines the value of the {{next_appt_type}} message template parameter.

  • appointment_date: date & appointment_time: time

    • These columns determine the values of the {{next_appt_date}} and {{next_appt_time}} message template parameters.

Care Gaps, Populations, Quality Measures, Risk Models

Any enabled care gaps, populations, quality measures and risk models with risk levels set will be able to be added as a rule on an outreach campaign audience.

Populations must be configured to “Show on Outreach audiences”.