Cert++
Close

Visit and Provider Visit data model

Key Takeaway

A visit is a pair of records: a standard Visit for the event and a Provider Visit for the life sciences details, linked one-to-one. A group visit adds a parent visit for the main event and a child Visit and Provider Visit pair for each attendee.

Visit Management in Life Sciences Cloud records a field rep's interaction with a health care provider using a pair of objects. The standard Visit object is shared across Salesforce clouds and holds the general event details. The Provider Visit extension object holds the details specific to life sciences. Child objects around this pair capture what happened during the visit, such as product detailing, samples, expenses and signatures. For group visits with several attendees, a parent-child structure gives each attendee their own records. Knowing which object holds which detail tells you where to find any part of a visit.

Visit and Provider Visit

A visit is stored as two records with a strict one-to-one relationship. Visit holds the event itself. Provider Visit extends it with industry-specific data.

VisitProvider Visit
Object typeStandard object, available across Salesforce cloudsExtension object
Holds details such asAccount, Place, Planned Start and End Time, ChannelSignature status, confirmation flags, compliance details
Side of the linkMasterDetail, through the VisitId field

Keeping industry data on a separate object lets Visit Management meet industry requirements while staying compatible with the standard Salesforce data model.

The VisitId field on Provider Visit enforces the one-to-one link. VisitId is:

  • required
  • unique within the org
  • a master-detail relationship, with Visit as the master

Several Provider Visit fields are derived from the related Visit instead of being captured independently:

  • Account
  • Channel
  • Planned Start Time
  • Planned End Time
  • Status
  • Territory (a Territory2 reference)

Maria, a field rep, plans a visit with Dr. Chen at Lakeside Clinic for next Tuesday at 9:00. The Visit record holds the event: Dr. Chen's account, the place, the planned start and end time, and the channel. The visit's Provider Visit record is linked to it through VisitId. Account, Channel, the planned times and Status on the Provider Visit come from the Visit, so Maria doesn't enter them twice. The Provider Visit holds the life sciences details, such as whether Dr. Chen confirmed the time and the signature status.

Agentforce Life Sciences Consultant Study Guide

Checklist progress

0/279Learned

Manage the end-to-end visit lifecycle

0/24

Visit and Provider Visit data model

Learn this concept

Surveys launched during HCP visits

Learn this concept

Capturing next visit objectives

Learn this concept

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Agentforce Life Sciences Consultant studiers. 757 members and growing.