Organizations

Know who you are working with

flowchart LR
    Scattered[Fragmented institutional context] --> Org[Organization record]
    Org --> Identity[Clear identity]
    Org --> Reach[Reachable contacts]
    Org --> Credentials[Verifiable credentials]

Teams rarely struggle because they have no institutional data. They struggle because the same sponsor, hospital, or CRO appears differently across trials, sites, and contacts with no single governing record.

An organization record gives the team one durable place to answer questions such as:

• what is this institution, where is it, and what does it do
• how do we reach it and what are its identifiers
• what accreditations validate its operational capability
• which trials, sites, contacts, systems, and media connect back to it

That matters because almost every other operational relationship in TrialStack — sites, contacts, computerized systems, interventions — traces back to an organization.

Keep context connected

flowchart LR
    Org[Organization] --> Trials[Trials]
    Org --> Sites[Sites]
    Org --> Contacts[Contacts]
    Org --> Media[Media]
    Org --> Systems[Computerized Systems]

Organizations connect to nearly everything. A sponsor funds trials, a hospital hosts sites, a CRO manages contacts, and a vendor supplies computerized systems. Keeping one clean organization record avoids duplicating institutional context across those surfaces.

Put organizations to work

flowchart LR
    Org[Organization record] --> Identity[Establish identity]
    Org --> Profile[Describe capabilities]
    Org --> Locate[Provide location]
    Org --> Reach[Enable contact]
    Org --> Verify[Track credentials]

The page is especially useful when a team needs to:

• establish the institutional identity before connecting sites, contacts, and trials
• describe the operational scope — therapeutic areas, size, operating countries
• provide a locatable address with timezone for coordination
• enable reliable communication with email, phone, and website
• track external identifiers and accreditations for regulatory and compliance reference

On the page

The organization page is section-based. It is built around six sections that move from identity through profile, location, contact details, and structured credentials.

Surface	Purpose	What users do there
Summary	Maintain the organization identity and verifiable credentials	Capture name, type, profile, address, contact, identifiers, accreditations
Relationship tabs	Keep operational context visible	Review linked trials, sites, contacts, media, computerized systems

classDiagram
    class OrganizationPage {
        +Summary
        +RelationshipTabs
    }

    class Summary {
        +Information
        +Profile
        +Address
        +Contact
        +Identifiers
        +Accreditations
    }

    class RelationshipTabs {
        +Trials
        +Sites
        +Contacts
        +Media
        +ComputerizedSystems
    }

    OrganizationPage *-- Summary
    OrganizationPage *-- RelationshipTabs

What to capture

mindmap
  root((Strong organization records))
    Clear institutional identity
    Operational scope and capability
    Accurate physical location
    Reliable contact details
    External identifiers for cross-referencing
    Verifiable accreditations

A strong organization record is not just a name and address. It gives the team an institutional anchor they can actually make cross-cutting decisions with.

Good organization records usually do five things well:

• they establish a clear legal and operating identity with type classification
• they describe operational scope — therapeutic areas, employee count, operating countries
• they provide an accurate, locatable address with timezone
• they make the institution reachable with verified contact details
• they hold structured identifiers and accreditations that support regulatory and compliance workflows

That is why only Legal Name is required. The point is not to force completion. The point is to capture the information that supports real downstream decisions.

Information

mindmap
  root((Information))
    Legal name
    Operating name
    Organization type
    Description

This section establishes the foundational organizational identity.

Label	Description	Type
Legal Name	The registered legal name of the organization	Text
Operating Name	Commonly used name if different from the legal name	Text
Organization Type	Classification such as sponsor, CRO, hospital, lab, regulatory body	Select
Description	Free-form description of the organization, its role, and operational focus	Rich text

Profile

mindmap
  root((Profile))
    Year established
    Employee count
    Therapeutic areas
    Operating countries

This section describes the operational scope and capabilities.

Label	Description	Type
Year Established	When the organization was founded or incorporated	Number
Employee Count	Approximate number of employees	Number
Therapeutic Areas	Disease or therapy categories the organization focuses on	Multi-select
Operating Countries	Countries where the organization actively operates	Multi-select

Address

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

This section locates the organization 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 coordination	Select

Contact

mindmap
  root((Contact))
    Email
    Phone
    Fax
    Website

This section provides the communication details needed to reach the organization.

Label	Description	Type
Email	Primary organizational email address	Email
Phone	Primary phone number	Phone
Fax	Fax number if applicable	Phone
Website	Organization website	URL

Identifiers

mindmap
  root((Identifiers))
    Type
    Value

Identifiers capture external reference numbers used for cross-system tracking and regulatory submissions. Rows are reorderable.

Label	Description	Type
Type	Kind of identifier such as DUNS, FDA Establishment, or internal	Select (badge)
Value	The identifier value	Text

Accreditations

mindmap
  root((Accreditations))
    Type
    Issuing body
    Certificate number
    Expiration date

Accreditations track certifications and quality credentials that validate the organization’s operational capability. Rows are reorderable.

Label	Description	Type
Type	Kind of accreditation such as ISO, AAHRPP, or GCP certification	Select
Issuing Body	Name of the authority that issued the accreditation	Text
Certificate Number	Certificate or accreditation reference number	Text
Expiration Date	When the accreditation expires	Date