Data as a Product

Reduce, Reuse, and Recycle Scripts and Schemas.

Background

While contract performance is important, it's nothing without accurate reporting that tells a full story. As the Principal Product Manager on a lean team, I also served as the data analyst for the organization. What's captured here is only part of the data contract picture.

It's worth reading the go-to-market strategy for this org before diving into data.

External Reporting: Patient Report

Report Goals:

  • Provide updated patient profile information back to the client, such as a change of address.
  • Indicate which patients have had either of the two contact goals completed: Health Needs Assessment (HNA) collected and Appointment Scheduled.
  • Report details as they pertain to the contract goals. For the HNA, this means reporting patient responses to the assessment. For the HNA, this means reporting patient responses to the assessment.

Note: Each row should correspond to a single patient.

SQL Script:

Entity Relationship Diagram:

High five if you've made it this far!


Now take a deep breath and keep scrolling.

External Reporting: Engagement Report

Report Goals:

  • Show the patient journey as it pertains to contact attempts and contract goals achieved. Even though the collection of appointment preferences isn’t an explicit contract goal, it is a key part of the patient journey. Preferences are required to book the appointment, which is an explicit goal.
  • Indicate which contacts successfully engaged the patient and further, which led to the completion of the contract goals. Some contact attempts aren’t associated with any contract goals but all contract goals are associated with a contact attempt.

Note: Each row should correspond to a single contact.

SQL Script:

Entity Relationship Diagram:

Scalability = 

All of the organization's contracts were supported by either one or two of these reports, regardless of which use case or segment was applicable. 2 stones and many, many birds.