TikaMSL is the CRM for medical science liaisons. It holds the KOL plan, the record of a scientific visit, and the inquiry captured next to that HCP. It runs beside the CRM the company already uses.
The HCP, the tier, and the plan for the relationship sit on one record. The next visit starts from that plan. It does not start from a list rebuilt over the weekend.
Finding who might matter is a different job. Publications, trials, and congress roles are signals. They are not the relationship. KOL identification is that upstream cut. TikaMSL holds the person after it: the tier, and what the next scientific conversation is for.
Tier definitions stay in the KOL tiering glossary. This page does not add a second model. KOL engagement is the plan for that relationship.
HCPActive
SH
Sample HCPCardiology
KOL Tier · EmergingKOL Stage · Collaborate
KOL FlagYes
QTD calls14
LTD calls15
StatusActive
Beside the crm
Beside the CRM already in place
TikaMSL does not replace the CRM the company already runs. That includes Veeva and Salesforce. Medical Affairs keeps its own record of the scientific relationship next to that system.
The commercial CRM can stay. Replacing it is a different project. This page is for the KOL, the visit, and the inquiry captured while the MSL is still with that HCP.
Two recordsSide by side
CRM already in placeStays
TikaMSLKOL plan
On the visitScientific exchange
Captured with the HCPeMIRF
The visit
The visit
The interaction stores the scientific exchange and the outcome. It is not a sales call with a medical label.
Before the meeting, the MSL opens the plan already on that HCP. After the meeting, the record has to say what was discussed and what came of it. A line that only says the visit went well is not an outcome.
TikaMSL can turn a spoken note into text in about 60 seconds. The MSL checks that text before it is the record. It is not filed until they do.
InteractionSubmitted
Face to FaceSubmitted
SourceHCP
CRMMSL
TypeFace to Face
StatusSubmitted
The inquiry
The inquiry next to the HCP
An MSL can capture a medical information request on the visit, while they are still with that HCP. That field capture is eMIRF. It stays on the visit.
eMIRF is not the case. The case, the response, and the person who sends it are TikaMedInfo, a separate product. A question captured in the field can enter that queue. The two products are not sold as one, and a field note is not a completed response.
eMIRFOn the HCP
Saved
Request date—
Product—
StatusSaved
TabeMIRF
Separate products
Separate products that can run with it
None of these is included just because the CRM is on.
Congress session coverage is TikaConference. It can run with TikaMSL, or beside the CRM the company already uses. It is the grid of who is in which room, and the note from that session. It is not the CRM.
Company-run speaker programs are TikaSpeaker Bureau. The speaker, the contract, and the fair-market-value cap live there. They are not a tab inside TikaMSL.
TikaInsights can run with TikaMSL or on its own. It coaches an insight while it is written, groups the theme, and keeps an action until a manager verifies it. A visit note does not become that record on its own.
TikaEvidence and Studies is opt-in. It stays off until a customer turns it on. When it is on, it can run inside TikaMSL or as its own application. It holds the study. It is not the field CRM, and it is not part of every TikaMSL agreement.
How to judge
How to judge a medical affairs CRM
There is no single best one. Use four questions, and write the answer while the vendor is still on the screen.
01
Is Medical Affairs the primary user, or is this a sales CRM with a medical label?
02
Are the KOL and the scientific exchange native records?
03
Does the field inquiry stay on that visit, with the medical information case kept as its own product?
04
Can the system sit beside the CRM the company already runs?
A yes that depends on a services project later is a no for this decision.
Questions
Questions medical affairs leaders ask
What is TikaMSL?
TikaMSL is the CRM for medical science liaisons. It holds the KOL plan, the record of a scientific visit, and the inquiry captured next to that HCP. It runs beside the CRM the company already uses.
Does TikaMSL replace Veeva or Salesforce?
No. Medical Affairs keeps its own record next to the CRM the company already runs. Replacing that CRM is a different project.
What is eMIRF?
eMIRF is the field capture of a medical information request on the visit, next to that HCP. The case itself is TikaMedInfo, a separate product.
How do you judge a medical affairs CRM?
There is no single best one. The test is whether Medical Affairs is the primary user, whether the KOL and the scientific exchange are native records, whether the field inquiry stays on that visit, and whether the system can sit beside the CRM the company already runs.
