How do I set up an MSL CRM for tracking advisory boards and field medical follow-ups in a rare disease team?

Here’s a practical way to set up an MSL CRM so it supports both advisory boards and field medical follow-ups for a rare disease team.

1) Start with the use cases

Define the workflows you want the CRM to manage:

Advisory boards

Track:

• Planning, approval, and budget
• HCP/KOL selection and affiliations
• Invitations, RSVPs, attendance
• Topics/objectives
• Materials shared
• Insights captured and action items
• Compliance documentation
• Follow-up commitments

Field medical follow-ups

Track:

• HCP interactions and scientific exchange
• Unmet medical questions
• Requests for data or literature
• Follow-up tasks and due dates
• Insight themes and escalation
• Referral to medical information, clinical development, or HEOR
• Repeat engagement cadence
• Impact/outcomes of follow-up

2) Build the core data model

You’ll want CRM objects that can connect people, meetings, and outcomes.

Core entities

• Account / Institution: hospital, clinic, center of excellence, academic site
• HCP / Contact: individual MSL stakeholders
• Team / Territory: MSL coverage area
• Interaction / Activity: call, email, virtual meeting, in-person visit
• Advisory Board Event: one record per board
• Insight / Medical Insight: key scientific or unmet-need findings
• Follow-up Task: action item with owner/due date/status
• Document / Material: deck, agenda, minutes, approved materials
• Request / Medical Inquiry: optional, if you want to link to med info
• Affiliation / Relationship: role, site, specialty, KOL status

Key relationships

• One Advisory Board → many attendees
• One Interaction → one or more insights
• One Insight → one or more follow-up tasks
• One HCP → many interactions
• One Account → many HCPs

3) Define the advisory board workflow

Use status stages so the process is structured:

1. Proposed
2. Business/medical approval
3. Planning
4. Invites sent
5. Confirmed
6. Completed
7. Insights reviewed
8. Closed

Fields to include

• Board name / therapeutic area
• Indication / subpopulation
• Date/time / location / virtual link
• Objective(s)
• Moderator
• HCP list and roles
• Budget code / approval ID
• Agenda
• Required pre-reads
• Attendance
• Insights summary
• Action items and owners
• Compliance sign-off

Helpful CRM features

• Template-based event creation
• Auto-generated invite/attendance lists
• Approval workflow
• Required fields before closure
• Upload area for agendas, minutes, and disclosures

4) Define the follow-up workflow

A good field medical follow-up process usually looks like this:

1. Interaction logged
2. Need/insight identified
3. Follow-up created
4. Assigned owner
5. Due date set
6. Completed
7. Outcome recorded
8. Closed or escalated

Fields to include

• Interaction date and channel
• HCP question or topic
• Follow-up type:
  • scientific data request
  • literature
  • med info referral
  • internal escalation
  • investigator/site support
• Priority
• Due date
• Owner
• Completion date
• Outcome
• Link to relevant interaction and insight

5) Create insight capture standards

For rare disease teams, insights are especially valuable because the patient populations are small and the same stakeholders may generate repeated intelligence.

Standardize insight fields:

• Insight category:
  • disease burden
  • diagnosis challenges
  • testing/access barriers
  • patient journey
  • unmet need
  • trial interest
  • treatment sequencing
• Theme
• Importance/urgency
• Source interaction
• Stakeholder type
• Geographic relevance
• “Actionable?” yes/no
• Escalation pathway
• Status

This makes it easier to identify patterns across a small, distributed network.

6) Configure dashboards and reports

Set up dashboards for both execution and impact.

Advisory board dashboards

• Boards planned vs completed
• Attendance rate
• Top insight themes
• Follow-up completion rate
• Time to close insights
• HCP participation by institution/specialty
• Budget/utilization, if relevant

Field medical dashboards

• Interactions by MSL and territory
• Follow-ups open/overdue
• Insights by theme
• Time from interaction to follow-up closure
• HCPs with no recent engagement
• Repeat topics by account
• Escalations completed

7) Set permissions carefully

MSL CRM data can be sensitive. Use role-based access.

Typical roles:

• MSLs: create/edit interactions, follow-ups, insights
• MSL managers: view team performance and approve certain records
• Medical affairs: aggregate insight review
• Compliance/Legal: audit access and approved materials
• Admins: configuration only

Consider restricting:

• Budget fields
• Personally sensitive HCP data
• Draft advisory board notes
• Approval records

8) Add compliance controls

For a rare disease team, compliance matters because advisory boards are heavily scrutinized.

Build in:

• Required disclosures
• Transfer-of-value tracking if needed
• Approved content library only
• Meeting approval workflow
• Audit trail for edits
• Reason codes for follow-up closure
• Separation of promotional vs medical content
• Consent/privacy handling for HCP and patient-related info

9) Integrate with other systems

To avoid duplicate entry, connect the CRM with:

• Email/calendar
• Document repository
• Medical information system
• Approved content/asset management
• ERP or finance for budgeting
• BI/reporting tools
• Veeva/Salesforce equivalents, if applicable

10) Build rare disease-specific logic

Rare disease teams often need special fields and views:

• Very small HCP universe and frequent cross-site affiliations
• Center of excellence flags
• Disease expertise level
• Subspecialty or phenotype focus
• Pediatric/adult transition care
• Genetic testing/testing pathway knowledge
• Trial referral interest
• Multidisciplinary team involvement

Useful segmentation:

• Treating physician
• Diagnostician/geneticist
• Site investigator
• Lab/pathology contact
• Nurse coordinator
• Advocate/educator partner

11) Keep the process simple for the field

MSLs will only use the CRM if it’s fast.

Best practices:

• 1–2 minute interaction logging
• Drop-downs instead of free text where possible
• Auto-populate account/HCP details
• Use templates for board planning and follow-up creation
• Mobile-friendly entry
• Mandatory fields only where truly needed

12) Roll out in phases

A simple implementation sequence:

1. Map workflows
2. Define data fields
3. Configure advisory board objects
4. Configure interaction and follow-up objects
5. Create insight taxonomy
6. Set permissions and compliance rules
7. Build reports/dashboards
8. Pilot with 2–3 MSLs
9. Refine
10. Scale team-wide

Suggested minimum viable setup

If you want a lean first version, include:

• HCP/account profiles
• Interaction logging
• Advisory board event record
• Insight capture
• Follow-up task tracking
• Dashboards for overdue items and insight themes
• Document upload and approval status

If you want, I can also help you with either:

1. a sample CRM data model,
2. a field-by-field setup template, or
3. a workflow diagram for advisory boards and follow-ups.