Clinical trials tell us what can happen when a medication is studied under carefully designed conditions. Healthcare data can help answer a different question: what is actually happening once treatment reaches the real world?
Every day, healthcare systems generate enormous amounts of information. Insurance claims record diagnoses, procedures, and prescriptions. Electronic health records capture laboratory values, medication histories, and clinical encounters. Disease registries follow specific patient populations over time.
Someone has to turn all of that information into useful evidence.
That work has created an entire career field around real-world data and real-world evidence, often shortened to RWD and RWE. Pharmacists may be particularly useful in this field because a database can show what happened, but understanding why it happened often requires clinical context.
A current Norstella opening makes that opportunity unusually visible. The company is recruiting a remote Clinical Consulting Manager, Real-World Data & Evidence. The position specifically requires an MD or PharmD. The person works across claims data, EHRs, registries, medications, laboratory information, epidemiology, biostatistics, data engineering, health economics, and life-sciences consulting.
The pharmacist is not being hired to dispense medications.
They are being hired to help turn healthcare data into evidence that people can actually use.
First, understand the difference between data and evidence
Real-world data and real-world evidence sound interchangeable, but FDA draws an important distinction.
Real-world data are routinely collected information about patient health or healthcare delivery. FDA lists electronic health records, medical claims, disease and product registries, and certain digital health technologies among common sources. Real-world evidence is the clinical evidence about a medical product’s use, benefits, or risks that researchers generate by analyzing those data.
In other words, the database is not the answer.
It is the raw material.
Imagine a claims database containing millions of prescription transactions. Those records can show when a medication was filled, whether another drug appeared later, which diagnoses were recorded, and what healthcare services the patient used.
However, those data do not automatically tell you what any of it means.
A researcher still needs to define the patient population, identify the right variables, choose an appropriate study design, account for limitations, and interpret the findings within the clinical context.
That is how data become evidence.
The pharmacist can help explain what the dataset is actually showing
Consider a simple example.
A dataset shows that a patient stopped filling Drug A and began Drug B.
Why?
Maybe Drug A did not work. Perhaps the patient developed an adverse effect. The formulary may have changed. A hospitalization could have altered the treatment plan. The disease may have progressed. Cost could have become a barrier.
The same pattern in the data can represent several completely different clinical stories.
That is where domain expertise matters.
A pharmacist understands how medications move through a patient’s treatment journey. They know which drugs commonly appear together, which therapies usually follow treatment failure, which medications require monitoring, and which changes might signal disease progression.
They can also recognize when the data do not make clinical sense.
That knowledge becomes valuable when pharmacists work with people who bring different expertise. A biostatistician may understand the analytical method. A data engineer knows how to structure the information. An epidemiologist understands study design and bias.
The pharmacist helps make sure the clinical story underneath the variables is credible.
Sometimes the job begins by translating medicine into code
Norstella’s posting gives a fascinating example of what this work looks like.
One of the role’s major responsibilities is building and validating codebooks and data dictionaries. The Clinical Consulting Manager translates diagnoses, procedures, medications, and laboratory concepts into standardized coding logic that an analytical dataset can use. That can include ICD-10 diagnosis codes, CPT procedure codes, NDC drug identifiers, LOINC laboratory codes, and other healthcare taxonomies.
Suppose a life-sciences company wants to study patients with a particular disease who received a specific therapy.
A human understands that sentence.
A database does not.
The analytical team has to define exactly what counts as the disease, which codes represent the therapy, how long treatment must continue, what laboratory values matter, and which healthcare events should qualify or exclude someone from the analysis.
Small errors can change the study population.
If the team misses a relevant code, patients may disappear from the dataset. If it includes an inappropriate code, the analysis may capture patients who do not actually have the condition being studied.
Clinical knowledge therefore becomes part of data quality.
This is where pharmacy knowledge meets data science
The Norstella role does not expect the PharmD to become the team’s primary programmer.
That is important.
The position requires comfort with structured healthcare data even without a technical programming background. However, Norstella also prefers candidates with a basic understanding of SQL, R, and Python. The role collaborates with data scientists and engineers on database queries, data pipelines, processing workflows, and advanced analytics.
That combination provides pharmacists with a useful career lesson.
You do not always need to become the data scientist.
You may need enough technical fluency to work effectively with one.
A pharmacist who understands how a claims database works can ask better questions. Someone who understands basic SQL can communicate more clearly with an analyst pulling the data. Familiarity with R or Python can make it easier to understand how analytical workflows operate.
Meanwhile, the pharmacist brings something the technical team may not have: deep medication and therapeutic context.
The value sits at the intersection.
Real-world evidence asks questions clinical trials cannot answer alone
Randomized clinical trials remain essential for determining whether treatments are safe and effective. However, even excellent trials cannot answer every question that appears after a medication enters broader use.
Trial populations may differ from everyday patients. Follow-up periods can be limited. Researchers may study one comparator even though clinical practice includes several alternatives.
Real-world evidence can help explore what happens in larger and more varied populations.
Researchers might study how long patients remain on therapy, how treatments perform across different groups, which adverse outcomes appear in practice, or how healthcare utilization changes after treatment begins.
FDA has used real-world data for years in postmarket safety work. The agency also continues developing ways to use fit-for-purpose RWD to support regulatory decisions across a medical product’s lifecycle.
Life-sciences companies, health plans, consultants, and other organizations also use real-world analyses to answer commercial, access, outcomes, and strategy questions.
That creates a broad career ecosystem around evidence generation.
A medication can look different when you study what happens after launch
Imagine a pharmaceutical company launches a new medication.
Clinical trials showed that the therapy worked. Now the company wants to understand what happens in routine practice.
Who actually receives it?
How quickly do patients start therapy after diagnosis? How long do they remain on treatment? What therapies did they use before it? What happens after they discontinue? Do certain populations use the medication differently?
These questions can influence many parts of the organization.
Medical teams may want to better understand treatment patterns. Health economics teams may study utilization and outcomes. Market-access teams may need evidence that helps payers evaluate the therapy’s role.
Researchers may also identify gaps that deserve further study.
The important point is that drug development does not stop producing questions once FDA approves the medication.
A different kind of evidence journey begins.
Coverage decisions also depend on understanding value
Real-world evidence can become especially important when healthcare organizations are deciding how treatments fit into actual populations and budgets.
A payer may know what a clinical trial showed. However, it may also want to understand which patients receive the therapy in practice, how treatment affects healthcare utilization, how long people remain on therapy, and what outcomes occur outside the original trial.
Norstella’s role specifically asks the Clinical Consulting Manager to monitor both FDA real-world-evidence guidance and payer evidence requirements. The position also supports Norstella’s Health Economics and Outcomes Research, real-world data, and commercial analytics consulting groups.
That shows how broad the work can become.
Evidence may support a scientific question in one project and a business question in another.
The pharmacist has to understand both without confusing them.
A statistically interesting finding may not be clinically meaningful. Meanwhile, a clinically important outcome may require careful interpretation before anyone can translate it into a coverage or commercial strategy.
That ability to connect evidence with decisions is part of the job.
The career is much bigger than one Norstella posting
Norstella’s careers page currently shows an entire group of jobs built around real-world data. Alongside the Clinical Consulting Manager opening, the company has recently listed RWD Analytic Consultant, RWD Engagement Manager, VP of Strategic Accounts RWD, and other data-focused positions.
That is useful because it shows the career neighborhood rather than one isolated title.
Real-world evidence can connect with health economics and outcomes research, often called HEOR. It can overlap with pharmacoepidemiology, which studies medication use and effects across populations.
Other adjacent functions include outcomes research, market access, epidemiology, data analytics, evidence generation, and life-sciences consulting.
The titles vary because organizations structure the work differently.
One company may hire a Real-World Evidence Scientist. Another may use RWE Consultant, HEOR Manager, Epidemiologist, Outcomes Researcher, or Evidence Generation Lead.
Searching only for “pharmacist” could miss most of them.
This is another example of the PharmD becoming domain expertise
Pharmacists often think about their medication knowledge in the context of direct patient care.
Is the dose correct? Is the medication appropriate? Is there an interaction? Does the patient understand how to use it?
Those questions matter.
However, the same knowledge can operate at a much larger scale.
Suppose an analytical project includes 500,000 patients and millions of medication records. The pharmacist is no longer helping interpret one patient’s regimen.
They may be helping define the logic that determines how the analytical system interprets medication use across the entire population.
That is leverage.
Your pharmacology and therapeutics knowledge becomes part of the infrastructure used to generate evidence.
The output might eventually help a pharmaceutical company decide which research question to pursue. It could help an evidence team understand treatment patterns or support a payer-facing strategy.
The PharmD still matters because the subject is medication.
The unit of work has changed.
Communication may matter almost as much as analytics
There is another clue in Norstella’s job description that pharmacists should notice.
The role requires strong written and verbal communication. The Clinical Consulting Manager supports client presentations, proposals, RFP responses, scientific narratives, white papers, conference abstracts, and thought leadership.
That means the job is not finished when the analysis is complete.
Someone has to explain what the evidence means.
A client does not necessarily want a 500-row spreadsheet or a statistical output table. They want to know what the findings say about their question, how confident they should be, and what they should do next.
The pharmacist therefore needs to translate in both directions.
They translate clinical concepts into data definitions so the technical team can analyze them. Later, they translate analytical findings back into clinical and strategic language for the client.
That is a valuable skill in almost every healthcare business.
The person who understands both sides can become a bridge between teams that otherwise speak very different languages.
This is not an easy jump directly from retail pharmacy
The PharmD requirement is exciting, but the rest of the posting deserves just as much attention.
Norstella asks for three to five years of professional consulting experience after clinical training. It also wants comfort with healthcare datasets, project-management tools, cross-functional work, and complex analytical problems.
Preferred experience includes health economics, outcomes research, epidemiology, public health, clinical coding systems, RWD sources, publication experience, and basic SQL, R, or Python.
That makes this an excellent destination role.
It does not make it an entry-level escape hatch from retail.
That distinction helps pharmacists build more realistic career plans.
If this type of work interests you, the question should not be whether you can apply tomorrow.
Ask what experiences would move you closer.
There are several possible bridges into this world
A pharmacist could approach real-world evidence through different directions.
Someone working in managed care may already understand claims data, formulary decisions, and population-level medication use. A specialty pharmacist may bring therapeutic expertise and experience following complex patient journeys.
A research pharmacist might develop exposure to study design and evidence generation. Pharmaceutical industry roles can provide experience with HEOR, medical affairs, market access, or clinical research.
Others may enter through consulting, analytics, epidemiology, or graduate training in public health and outcomes research.
There is no single required path.
The goal is to begin accumulating the experiences that repeatedly appear in job descriptions.
That might include working with claims data, learning basic epidemiology, contributing to a research project, understanding common healthcare coding systems, improving statistical literacy, or learning enough SQL to query a simple dataset.
Each skill makes the next move more plausible.
Do not start by trying to become a programmer
Seeing SQL, R, and Python in a job posting can intimidate pharmacists.
It can also create the wrong career plan.
A pharmacist may conclude that the first step is spending six months learning advanced programming. However, Norstella lists basic understanding of those tools as a preferred qualification. The required foundation remains the PharmD, consulting experience, clinical communication, healthcare-data literacy, and analytical problem solving.
That tells you how to prioritize.
Start by understanding the field.
Learn what claims data contain. Understand how EHR data differ from claims. Learn what ICD-10, CPT, NDC, LOINC, and RxNorm represent.
Then explore the basic logic of SQL.
You do not need to build a machine-learning model on day one.
The goal is enough technical literacy to understand how clinical questions become data questions.
After that, deeper technical skills can become useful if the jobs you want repeatedly ask for them.
The job description can become your learning plan
This is another career where pharmacists can reverse-engineer the destination.
Open five RWE or HEOR job postings.
Do not ask whether you qualify yet.
Instead, create a list of the skills that appear repeatedly.
You may see epidemiology, healthcare claims, EHR data, statistical analysis, SQL, study design, pharmacoeconomics, scientific writing, coding systems, client communication, or therapeutic-area expertise.
Now compare that list with your current experience.
Maybe you already have the clinical knowledge but no data exposure. Perhaps you use healthcare data regularly but need stronger research-methodology skills.
Another pharmacist may have publications and research experience but lack business or consulting communication.
The gaps will be different for everyone.
Once you can name the gap, you can work on it intentionally.
Healthcare has plenty of data. Context is what makes it useful.
The healthcare system is not struggling to generate information.
Every claim, prescription, laboratory result, diagnosis, encounter, wearable device, and health record can create another data point.
The harder problem is knowing what those data represent.
A medication disappears from the claims record.
Did the patient stop therapy, change insurance, enter the hospital, receive samples, switch medications, or lose access?
A patient never fills a prescription.
Was it unaffordable? Did the prescriber change the treatment? Was the diagnosis wrong? Did the patient decide against therapy?
A hospitalization occurs after treatment begins.
Is there any relationship to the medication, or is it simply part of the patient’s underlying disease?
Data alone cannot answer every question.
Clinical context helps determine which questions should be asked in the first place.
That is why healthcare still needs domain experts even as analytics and AI become more powerful.
AI may make this skill set even more valuable
Healthcare data analysis will almost certainly become more automated.
Norstella’s posting already mentions collaboration with data science and engineering teams on workflows that incorporate AI and machine-learning methods.
That does not eliminate the need for clinical expertise.
It may increase it.
An AI system can identify patterns across millions of records. Someone still needs to determine whether those patterns make biological and clinical sense.
Algorithms can group medications, diagnoses, and outcomes. A domain expert still needs to notice when the model has misunderstood how treatment actually works.
As analytical tools become faster, the bottleneck may increasingly shift toward asking the right question and interpreting the answer correctly.
Pharmacists can contribute there.
The advantage will not come from competing with data scientists at data science.
It will come from understanding enough data science to combine it with expertise that the data scientist may not have.
Search the career neighborhood, not one title
If this field sounds interesting, spend some time searching these terms: Real-World Evidence, RWE, Real-World Data, HEOR, Pharmacoepidemiology, Outcomes Research, Evidence Generation, and Health Data Consulting.
Do not filter for the word pharmacist.
Open five roles.
Look at the companies. Study the departments. Notice which degrees appear. Pay attention to the tools and methods they mention.
Then identify one repeated skill you do not currently have.
Maybe it is SQL.
Perhaps it is claims-data literacy.
It could be epidemiology, research methods, scientific writing, or pharmacoeconomics.
Choose one and begin there.
That process turns an unfamiliar career into something concrete.
Your PharmD can help explain the story behind the data
There is a powerful lesson inside this career.
Healthcare is producing more data than ever before. AI will make it easier to analyze those data. Better infrastructure will connect more sources, while researchers will continue developing new ways to generate evidence from routine healthcare.
Still, someone has to understand what the numbers mean in the context of actual treatment.
That is where the PharmD can become valuable.
A pharmacist understands that a prescription claim is not simply a transaction. It represents one moment inside a medication journey.
A drug discontinuation can have several explanations. A treatment switch can signal many things. A diagnosis code may not tell the complete clinical story.
Knowing those possibilities helps turn a dataset into a better question.
Better questions produce better evidence.
Better evidence can lead to better decisions.
That is the career opportunity.
The pharmacist is no longer standing at the end of the medication journey dispensing the drug.
They may be sitting inside a consulting or evidence-generation team, looking across millions of patient journeys and helping organizations understand what those journeys are telling them.
That is another way a PharmD becomes more than a job title.
It becomes domain expertise.
Resources & Citations
- Norstella. “Clinical Consulting Manager, RWD.” Current remote U.S. job posting, published October 16, 2026. The position requires an MD or PharmD and three to five years of professional consulting experience. Responsibilities include real-world-data consulting, clinical codebook development, client work, claims and EHR data, clinical coding, collaboration with epidemiologists and data teams, and thought leadership. Preferred qualifications include familiarity with SQL, R, Python, HEOR, epidemiology, and major RWD sources.
- U.S. Food and Drug Administration. “Real-World Evidence.” FDA defines real-world data as routinely collected information about patient health or healthcare delivery and real-world evidence as clinical evidence about a medical product’s use and potential benefits or risks derived from analyzing RWD. FDA identifies EHRs, medical claims, registries, and certain digital health technologies among potential RWD sources.
- U.S. Food and Drug Administration, Center for Biologics Evaluation and Research and Center for Drug Evaluation and Research. “Real-World Evidence.” FDA describes the expanding use of reliable and relevant RWD to generate evidence that can potentially inform regulatory decisions about medical-product safety and effectiveness.
- Norstella. Current RWD/IHD career listings, accessed November 1, 2026. Norstella currently lists several roles across its real-world-data organization, including Clinical Consulting Manager, RWD Analytic Consultant, Engagement Manager, and other RWD-focused positions, illustrating the broader career ecosystem around real-world evidence and analytics.