> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/guides/write-a-search-query/europepmc.md).

# EuropePMC

Learn how to write a EuropePMC search query.

EuropePMC combines PubMed and PMC with two sources PubMed alone doesn't cover: the [Agricola](https://agricola.nal.usda.gov/) agricultural literature index, and preprints from 24 life-sciences preprint servers.&#x20;

Choose EuropePMC over PubMed when your review needs preprint coverage, agricultural literature, or full-text search rather than title/abstract/keyword search alone.&#x20;

### Write A Boolean Query

Use AND, OR, and NOT to combine search terms, quotation marks for an exact phrase, and parentheses to group terms and set priority order. For example:

```
stroke AND (trevo OR solitaire) AND "modified Rankin Scale"
```

retrieves publications with the word stroke, either trevo or solitaire, and the exact phrase "modified Rankin Scale," anywhere in title, abstract, or keywords.

### Search Specific Fields

EuropePMC's field syntax differs from PubMed's: use `(FIELD:term)` rather than `term[FIELD]`. A query built for PubMed needs these tags rewritten before it will run correctly here — see EuropePMC's [full field list](https://europepmc.org/searchsyntax#field-search) for everything beyond what's covered below.

#### Keyword Fields

EuropePMC doesn't apply MeSH terms automatically, but you can search attached keywords directly with `(KW:term)`.

#### Author, Journal, And Other Named Fields

* Author — `(AUTH:name)`
* Journal — `(JOUR:name)`
* Volume — `(VOLUME:number)`
* Issue — `(ISSUE:number)`

#### Filter By Study Traits

* Publication type — one of EuropePMC's supported types, for example `(PUB_TYPE:review)`
* Abstract available — append `(HAS_ABSTRACT)`
* PDF full text available — append `(HAS_PDF)`
* Publication date — `FIRST_PDATE:[YYYY-MM-DD TO YYYY-MM-DD]`, or `PUB_YEAR:YYYY` for a single year. EuropePMC treats 3000 as "through the present" — for example, `FIRST_PDATE:[2015 TO 3000]`
* Language — `(LANG:language)`
* Open access only — `(OPEN_ACCESS)`

#### Filter By Study Contents

* Title only — `(TITLE:text)`
* Abstract only — `(ABSTRACT:text)`
* Body text only — `(BODY:text)`

### Build A Strong Search

PICO, Automatic Term Mapping, and expanding-or-narrowing guidance apply the same way here as on PubMed — see [PubMed](/guides/write-a-search-query/pubmed.md) for the full explanation, and Best Search Practices for more depth.

### FAQs

<details>

<summary>Can I reuse a PubMed query in EuropePMC without changes?</summary>

No — the field syntax differs (`term[FIELD]` versus `(FIELD:term)`), so a query needs its field tags rewritten before it runs correctly here.

</details>

<details>

<summary>Does EuropePMC cover the same records as PubMed?</summary>

It includes PubMed and PMC, plus Agricola and life-sciences preprints, so EuropePMC's results are a superset for most biomedical topics — but coverage isn't identical concept-for-concept, since term mapping and indexing differ between the two.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nested-knowledge.com/guides/write-a-search-query/europepmc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
