PatientPoint is a point-of-care marketing company specializing in delivering patient and physician education. They have an extensive library of patient education content that they use to build education playlists delivered to more than 51,000 physician offices, 1,000 hospitals and 140,000 Healthcare providers — and they are still growing.

PatientPoint serves a wide range of content to a variety of devices. They need a canonical database to store all of their content and serve it to their endpoint devices. To get there, they needed to develop a content model that:

• Captures key content types and their relationships

• Creates a standardized structure for content, including fields that make it simple to serve content variations based on end-point devices and localization.

• This structure should be scalable for future, currently unknown end points

• Incorporates a taxonomy that enables content admins to quickly filter and select content relevant to their needs and device

In this session, attendees will walk away with an understanding of:

• How a master content model can enable scalable growth by allowing new products to be added and old products deprecated without restructuring content

• How to create a standardized structure for content, including fields that enable serving content variations based on end-point devices and localization

• How Drupal can function as a content repository that serves other products via API