Contacts

Keep the right people visible

flowchart LR
    Scattered[Scattered stakeholder context] --> Contact[Contact record]
    Contact --> Role[Role clarity]
    Contact --> Qualification[Qualification evidence]
    Contact --> Coordination[Operational coordination]

Teams rarely fail because they have no knowledge of the people involved. They fail because identity, role, and qualification context lives in scattered documents with no single governed record.

A contact record gives the team one durable place to answer questions such as:

• who is this person and what name should be used
• what role and employment status do they hold
• how do we reach them and what is their preferred contact method
• what qualifications, licenses, certifications, and training do they hold
• which organizations, sites, and trials connect back to this person

That matters because trial execution depends on whether a person is qualified and reachable, not just whether their name appears somewhere.

Track more than an address book

flowchart LR
    Contact[Contact] --> Identity[Identity and role]
    Contact --> Qualifications[Qualifications and credentials]
    Contact --> Connections[Organization, site, and trial links]

A contact is not just a name and email. The page holds identity context alongside structured credential history — education, experience, licenses, certifications, memberships, and training — so qualification questions can be answered from the record itself.

Put contacts to work

flowchart LR
    Contact[Contact record] --> Identify[Establish identity]
    Contact --> Qualify[Prove qualifications]
    Contact --> Locate[Pin location]
    Contact --> Connect[Link to organizations, sites, trials]
    Contact --> Audit[Review credential history]

The page is especially useful when a team needs to:

• establish a clear identity with name, role, title, and employment status
• prove qualifications through structured education, license, and certification rows
• pin location with full address and timezone
• connect the person to organizations, sites, and trials
• review credential history when changes need scrutiny

On the page

The contact page is section-based. It is built around nine sections that move from personal details through location, identifiers, and six structured credential tables.

Surface	Purpose	What users do there
Summary	Maintain person identity and qualification record	Capture name, role, contact info, credentials, training
Relationship tabs	Keep operational connections visible	Review linked organizations, sites, trials, media

classDiagram
    class ContactPage {
        +Summary
        +RelationshipTabs
    }

    class Summary {
        +Details
        +Location
        +Identifiers
        +Education
        +Experience
        +Licenses
        +Certifications
        +Memberships
        +Training
    }

    class RelationshipTabs {
        +Organizations
        +Sites
        +Trials
        +Media
    }

    ContactPage *-- Summary
    ContactPage *-- RelationshipTabs

What to capture

mindmap
  root((Strong contact records))
    Clear personal identity
    Reachable contact channels
    Professional role and competencies
    Structured credential history
    Physical location and timezone
    Governed identifier tracking

A strong contact record is not just an address book entry. It makes clear whether the person is qualified, reachable, and properly connected to the work that depends on them.

Good contact records usually do six things well:

• they establish a clear personal identity with legal name, display name, and role
• they provide reliable contact channels with preferred method and best time
• they describe professional competencies and therapeutic expertise
• they preserve structured credential history across six qualification tables
• they pin location with address and timezone for coordination
• they track professional identifiers like NPI and ORCID

That is why only First Name and Last Name are required. The point is to capture the context that supports real downstream decisions, not to force every credential into place upfront.

Details

mindmap
  root((Details))
    Names
    Contact channels
    Role and employment
    Competencies
    Notes

This section holds the core person record — identity, communication channels, role, and professional context.

Label	Description	Type
First Name	Legal first name	Text
Last Name	Legal last name	Text
Display Name	Preferred name for operational use	Text
Email	Primary email address	Email
Phone	Primary phone number	Phone
Mobile Phone	Mobile or secondary phone	Phone
Title	Professional title or position	Text
Role	Functional role within the workflow	Text
Employment Status	Current employment status	Select
Website	Personal or professional website	URL
Primary Language	Primary language spoken	Select
Languages	Additional languages supported	Multi-select
Preferred Contact Method	How the person prefers to be contacted	Select
Best Time to Contact	Preferred window for communication	Text
Last Contacted At	Date of most recent contact	Date
Therapeutic Areas	Disease or therapy expertise	Multi-select
Competencies	Professional competency tags	Tags
Notes	Free-form notes about the contact	Rich text

Competency suggestions

The competency tags field provides suggestions for common clinical trial competencies:

Clinical Research, Regulatory Affairs, Data Management, Biostatistics, Medical Writing, Pharmacovigilance, Quality Assurance, Project Management, Site Management, Patient Recruitment, Medical Monitoring, Clinical Operations, Drug Safety.

Location

mindmap
  root((Location))
    Address autocomplete
    Street and city
    State and postal code
    Country
    Timezone

This section locates the contact physically. An address autocomplete field can populate the individual fields automatically.

Label	Description	Type
Address Autocomplete	Type-ahead search that populates address fields from selected result	Address autocomplete
Address Line 1	Primary street address	Text
Address Line 2	Secondary address detail such as suite or floor	Text
City	City or municipality	Text
State / Province	State, province, or region	Text
Postal Code	ZIP or postal code	Text
Country	Country — searchable dropdown	Select
Timezone	IANA timezone for scheduling and coordination	Select

Identifiers

mindmap
  root((Identifiers))
    Type badge
    Value
    State

This section tracks professional identifiers such as NPI numbers, ORCID identifiers, or medical license references. Rows can be reordered.

Label	Description	Type
Type	Identifier type such as NPI, ORCID, Medical License	Select badge
Value	The identifier value	Text
State	Jurisdiction or state the identifier belongs to	Text

Education

mindmap
  root((Education))
    Institution
    Degree
    Field of study
    Dates and status

This section preserves education history as structured rows. Each row maps a degree at an institution with date and completion context.

Label	Description	Type
Institution	Name of the educational institution	Text
Degree	Degree type or level	Text
Field of Study	Area of study or specialization	Text
Start Date	Date education began	Date
End Date	Date education ended	Date
Status	Completion status	Select
Country	Country of the institution	Select
Notes	Additional context	Text

Experience

mindmap
  root((Experience))
    Organization
    Title
    Dates
    Description

This section captures professional experience history as structured rows.

Label	Description	Type
Organization	Employer or organization name	Text
Title	Job title or position held	Text
Start Date	Date the role began	Date
End Date	Date the role ended	Date
Is Current	Whether this is the current position	Toggle
Country	Country of the role	Select
Description	Role description and responsibilities	Text

Licenses

mindmap
  root((Licenses))
    License type
    Issuing authority
    Number and jurisdiction
    Dates and status

This section tracks professional licenses as structured rows.

Label	Description	Type
License Type	Type of license	Text
Issuing Authority	The body that issued the license	Text
License Number	Official license number	Text
Jurisdiction	State, province, or country of issuance	Text
Issue Date	Date the license was issued	Date
Expiration Date	Date the license expires	Date
Status	Current license status	Select
Specialty	Licensed specialty or discipline	Text
Country	Country of licensure	Select
Notes	Additional context	Text

Certifications

mindmap
  root((Certifications))
    Certification name
    Issuing body
    Number and dates
    Status

This section tracks professional certifications as structured rows.

Label	Description	Type
Certification Name	Name of the certification	Text
Issuing Body	The organization that issued the certification	Text
Certification Number	Official certification number	Text
Issue Date	Date the certification was issued	Date
Expiration Date	Date the certification expires	Date
Status	Current certification status	Select
Country	Country of certification	Select
Notes	Additional context	Text

Memberships

mindmap
  root((Memberships))
    Organization
    Membership type
    Dates and status

This section tracks professional memberships as structured rows.

Label	Description	Type
Organization	Professional body or society	Text
Membership Type	Type or level of membership	Text
Member ID	Membership identifier	Text
Start Date	Date membership began	Date
End Date	Date membership ended	Date
Status	Current membership status	Select
Country	Country of the organization	Select
Notes	Additional context	Text

Training

mindmap
  root((Training))
    Training name
    Provider
    Dates and status

This section tracks training records as structured rows.

Label	Description	Type
Training Name	Name or title of the training	Text
Provider	Organization or body that provided the training	Text
Completion Date	Date the training was completed	Date
Expiration Date	Date the training certification expires	Date
Status	Completion or validity status	Select
Country	Country where training took place	Select
Notes	Additional context	Text