Skip to Content
United States National Library of Medicine National Institutes of Health

U.S. National Library of Medicine ®
MEDLINE® Distributed in XML Format

Last modified: June 30, 2004

This document is prepared for those who lease MEDLINE® from NLM and other interested parties. Other sections will be added in the future and revisions will be made as needed.

  1. Overview
  2. MEDLINE XML Element Descriptions and their Attributes
    1. Alphabetical List of the Elements
    2. MedlineCitationSet (MedlineCitation, DeleteCitation)
  3. Creation of Journal Source at NLM
  4. Additional Sources of Information

OVERVIEW

The initial baseline MEDLINE database is distributed to licensees in several hundred files via ftp or, alternatively, on a DLT tape. The baseline files also include completed and quality reviewed non-MEDLINE records found in PubMed (MedlineCitation Status = PubMed-not-MEDLINE). Files containing other non-MEDLINE records in PubMed (MedlineCitation Status = In-process or In-Data-Review) are distributed via ftp as part of the MEDLINE daily update files that are available after the baseline files are generated. Update files containing new, maintained, and deleted MEDLINE and non-MEDLINE records picking up from the baseline records are distributed via ftp each Tuesday through Saturday except there is a hiatus during November and December as NLM makes the transition to a new year of Medical Subject Headings (MeSH®) vocabulary used to index the articles.

MEDLINE XML ELEMENT DESCRIPTIONS AND THEIR ATTRIBUTES

[Last Modified: October 8, 2004]

THE ELEMENTS AND THEIR ATTRIBUTES IN MEDLINECITATIONSET

The MEDLINE elements and their attributes are presented in this section in the order they appear in the distributed MEDLINE record, per the DTD. An alphabetical list of all element names is at http://www.nlm.nih.gov/bsd/licensee/elements_alphabetical.html. Information on the elements used at NLM to create the journal source is also available.

USE OF LISTS AND ATTRIBUTE "CompleteYN"
Three of the MEDLINE elements (<AuthorList>, <GrantList>, and <DataBankList>) use "lists" with the corresponding attribute of "CompleteYN". 'Y', meaning Yes, represents that NLM has entered all list items that appear in the published journal article. 'N', meaning No, represents that NLM has not entered all list items that appear in the published journal article. The latter case (incomplete list) occurs on records indexed during periods of time when NLM policy was to enter fewer than all items that qualified. NLM recommends the following when encountering 'N' for the element lists:
<AuthorList> when attribute = N, then supply the literal "et al." after last author name
<GrantList> when attribute = N, then supply the literal "etc." after the last grant number
<DataBankList> when attribute = N, then supply the literal "etc." after the last occurrence
Other MEDLINE elements possibly containing multiple values use 'lists'; however, they do not use attributes to indicate completeness. For those elements, all lists are complete.

  1. <MedlineCitation>
    <MedlineCitation> is the top level element in MedlineCitationSet and contains one entire record. This element has two attributes: Owner and Status, as described below.

    <MedlineCitation Owner="Value"> The party responsible for creating and validating the citation is recorded as the MedlineCitation Owner attribute. Each citation has only one MedlineCitation Owner and there are eight possible values for this attribute: NLM | NASA | PIP | KIE | HSR | HMD | SIS | NOTNLM. The valid Owner values for the various NLM departments and outside collaborating data partners are:

    NLM - National Library of Medicine, Index Section (the vast majority of citations carry this value)
    NASA - National Aeronautics and Space Administration
    PIP - Population Information Program, Johns Hopkins School of Public Health (not a current value; only on older citations)
    KIE - Kennedy Institute of Ethics, Georgetown University
    HSR - National Information Center on Health Services Research and Health Care Technology, National Library of Medicine
    HMD - History of Medicine Division, National Library of Medicine
    SIS - Specialized Information Services Division, National Library of Medicine (not yet used; reserved for possible future use)
    NOTNLM - for licensees' use; NLM will never use this value on citations it exports; licensees may want to use this value if they want to adapt the MEDLINE DTD for other applications.

    Some of the above Owner attributes - NASA, PIP, and KIE - may also be used with <GeneralNote> and <KeywordList> elements if the citation has been enriched with additional data by a collaborating partner.

    <MedlineCitation Status="Value">
    The Status attribute indicates the stage of a citation. There are five possible values for the MedlineCitation Status attribute: Completed | In-Process | PubMed-not-MEDLINE | In-Data-Review | Publisher, as described below in the order in which processing at NLM occurs.

    1. MedlineCitation Status attribute: In-Data-Review
      Records submitted to NLM electronically by publishers are added to PubMed at NLM and distributed to licensees in In-Data-Review status. Records in this status have undergone review at the journal issue level; i.e., the journal title, date of publication and volume/issue elements (referred to as the source data) are checked. Before records are distributed in In-Data-Review status, the source data have either:
      1. been matched to the print copy in NLM's collection and are correct; or
      2. been matched to the online version of the journal (when NLM assigns MeSH headings from the online version) and are correct; or
      3. been compared to previously checked in issues and appear to match the pattern or have been changed to match the established pattern. In these cases, the physical item has not yet been received for NLM's collection and the data have not been positively verified and may still change during NLM's processing cycle.

      While all three reviews are at the issue level, most citations fit into the last condition above. It is possible that the source information may be changed at a later point in the NLM quality assurance cycle once the hard copy issue is available for exact comparison.

      In-Data-Review records lack the <DateCompleted> element. They are not yet MEDLINE records because they have not undergone complete quality review and MeSH indexing; thus they should not be identified as MEDLINE records in licensees' systems/products.

      The issue level review for In-Data-Review status is the first step in quality control and the records will either be typically reissued as In-process status records or go to PubMed-not-MEDLINE final record status.

      Records that are in In-Data-Review status at the beginning of a new production year are not distributed as part of the annual baseline files. They are distributed shortly after the baseline files with the remaining In-process records as the new production year begins.

    2. MedlineCitation Status attribute: In-Process
      Records in this status have undergone a citation level review; i.e., the author names, article title, and pagination are checked. All In-Data-Review records that entered the workflow via publisher electronic submission are redistributed again in In-Process status whether or not they were revised as a result of the second citation level review, and are not identified in any way as having been revised or not having been revised. Licensees will simply see that this is the second time records with the same PMID, now in In-process status, are received. The In-process version of the record replaces the In-Data-Review version. This workflow means that licensees will receive many records twice: once after the review of the issue level information of electronically submitted records (i.e., the In-Data-Review status records) and again after the review of the individual citation data (In-process status records). Records created via NLM's current other data entry mechanisms, scanning/optical character recognition (OCR), are distributed for the first time in In-Process status after their creation.

      In-process records lack the <DateCompleted> element; however, they do contain the <CitationSubset> element. They are not yet MEDLINE records because they have not undergone complete quality review and MeSH indexing; thus they should not be identified as MEDLINE records in licensees' systems/products.

      Most in-process records are eventually indexed with MeSH Headings and are elevated to completed MEDLINE status. However, some are determined to be out of scope (e.g., articles on plate tectonics or astrophysics from certain MEDLINE journals, primarily general science and chemistry journals, for which the life sciences articles are indexed for MEDLINE) and are not elevated to MEDLINE status; instead they become PubMed-not-Medline final status records. In rare cases the records are deleted and do not become PubMed-not-MEDLINE records.

      Records that are in In-process status at the beginning of a new production year are not distributed as part of the annual baseline files. They are distributed shortly after the baseline files with the remaining In-Data-Review records as the new production year begins.

    3. MedlineCitation Status attribute: Completed
      In-process records undergo rigorous quality assurance routines before they are elevated to completed MEDLINE status.

      Records in Completed status are 'true' MEDLINE records. They contain <DateCompleted> and <CitationSubset> and, in most cases, contain <MeshHeadingList>. MEDLINE records that are Retractions of Publications (see Publication Type element) are exceptions and do not contain <MeshHeadingList>. Completed MEDLINE records may be new records or existing Completed records that have been revised (see Maintenance section).

      Completed status records are distributed as part of the annual baseline files along with PubMed-not-MEDLINE records.

    4. MedlineCitation Status attribute: PubMed-not-MEDLINE
      The records in this status are not MEDLINE records but do reside in PubMed and have undergone citation level quality review. The categories of non-MEDLINE records in this status are:
      1. citations to articles that precede the date a journal was selected for MEDLINE indexing and are submitted for inclusion in PubMed after July 2003;
      2. out of scope citations to articles in journals covered by MEDLINE; and
      3. analytical summaries of articles published elsewhere (see the article, "Linking MEDLINE Citations to Evidence-Based Medicine Assessments and Summaries", in the May-Jun 2002 NLM Technical Bulletin, page e2).

      NLM first began distributing records in PubMed-not-MEDLINE status at the end of July 2003 when it ceased using the old MedlineCitation Status value of Out-of-scope. Records previously distributed in the old Out-of-scope status were converted to the more generic PubMed-not-MEDLINE status and redistributed with the 2004 baseline database.

      PubMed-not-MEDLINE records contain <DateCompleted> element and lack <CitationSubset> and <MeshHeadingList> elements.

      PubMed-not-MEDLINE status records are distributed as part of the annual reload files along with Completed records.

    5. MedlineCitation Status attribute: Publisher
      Records in Publisher status are not distributed to licensees. At this time over 98% of PubMed's content is distributed to MEDLINE licensees. There are fewer than 250,000 additional non-MEDLINE records in Publisher MedlineCitation Status in PubMed and NLM expects more of them will be exported in the future. The non-exported records contain the notation [PubMed - as supplied by publisher] in the PubMed display. At this time the records in Publisher MedlineCitation Status and not distributed to licensees are:
      1. the retrospective and prospective records for the relatively few non-MEDLINE journals in PubMed;
      2. the retrospective records for MEDLINE journals prior to date of selection for MEDLINE and that were submitted electronically by the publishers before late July 2003;
      3. the prospective records for currently indexed journals when the publisher has submitted an issue's citation data electronically and NLM still awaits its print copy or access to the electronic copy to use for issue level review (i.e., the journal title, date of publication and volume/issue elements) AND the publisher-supplied record contains a validation error of some kind that prevents it from being exported from NLM's Data Creation and Maintenance System (DCMS) along with the records not containing errors from the same issue. If there were no errors, the record would move to MedlineCitation Status In-Data-Review right away and be exported. In these cases, however, NLM staff must take corrective action before the record can be elevated to In-Data-Review status for export; and
      4. citations electronically submitted for articles that appear on the Web in advance of the journal issue's release (i.e., ahead of print citations). Following publication of the completed issue, the item will be queued for issue level review and released in In-Data-Review status.

    Note that retrospective records for currently indexed MEDLINE journals sent electronically by publishers after late July 2003 and covering publication dates prior to the journal's selection for MEDLINE are exported in In-Data-Review status and then again in In-process and finally PubMed-not-MEDLINE status; however, if NLM does not have a paper copy of the back issue in its collection, the records are exported in In-Data-Review MedlineCitation Status only, and they are not further processed for subsequent redistribution in In-process or PubMed-not-MEDLINE status. Back issue data for currently indexed MEDLINE titles for which NLM does have hardcopy back issues in its collection are subsequently exported in PubMed-not-MEDLINE MedlineCitation Status.

    Records in Completed and PubMed-not-Medline status categories reside in the annual reload files distributed via ftp or alternatively on DLT tape. Records in all but the Publisher status category may be present in update files via ftp. The update files may also contain <DeleteCitation> in which PMIDs of deleted MEDLINE records are found.

    Back to top.

  2. <PMID>
    <PMID>, the PubMed (NLM's database that incorporates MEDLINE) unique identifier, is a 1 to 8-digit accession number with no leading zeros. It is present on all records exported to licensees and is the accession number for managing and disseminating records. PMIDs are not reused after records are deleted.

    Examples are:
    <PMID>10097079</PMID>
    <PMID>6012557</PMID>
    <PMID>10</PMID>

    Additional information/background:
    Prior to the 2004 version of MEDLINE, all records contained a <MedlineID> in addition to the <PMID>. Beginning with the 2004 baseline database first distributed in December 2003, NLM no longer exports the <MedlineID>. The <PMID> has become the single element to uniquely identify the MEDLINE record.

    Back to top.

  3. <DateCreated>
    <DateCreated> is the date processing of the record begins.

    An example is:
    <DateCreated>
    <Year>2002</Year>
    <Month>05</Month>
    <Day>16</Day>
    </DateCreated>

    This is contrasted with <DateCompleted> that is the date processing ends. <DateCreated> is not the same as NLM's PubMed Entrez Date (EDAT) that is the date the record entered PubMed. The PubMed Entrez Date does not reside on records distributed to licensees as it is generated when the record gets to PubMed.

    Additional information/background:
    For citations up to about the year 2000, the Date of Entry element in NLM's legacy ELHILL® system was used to set both <DateCreated> and <DateCompleted>.Additional information/background:

    Back to top.

  4. <DateCompleted>
    <DateCompleted> is the date processing of the record ends; i.e., MeSH® Headings have been added, quality assurance validations are completed, and the completed record subsequently is distributed to PubMed and licensees. This is contrasted with <DateCreated > that is the date processing begins. In-Process records lack <DateCompleted>.

    An example is:
    <DateCompleted>
    <Year>2002</Year>
    <Month>02</Month>
    <Day>07</Day>
    </DateCompleted>

    Back to top.

  5. <DateRevised>
    <DateRevised> identifies the date a change is made to a record either as a result of individual or global maintenance. There is no indication of what the change is on the record and only the latest revision date is distributed.

    An example is:
    <DateRevised>
    <Year>2002</Year>
    <Month>03</Month>
    <Day>20</Day>
    </DateRevised>

    Additional information/background:
    When the 10 million+ MEDLINE records through the 2000 production year were converted to XML from NLM's legacy ELHILL system, all records were assigned a <DateRevised> of 20001218 (December 18, 2000). Subsequently, many of these records have been or will be maintained, thus have or in the future will have a later <DateRevised> value.

    Back to top.

  6. <ISSN>
    <ISSN> (International Standard Serial Number) is always an eight-character value that uniquely identifies the cited journal. It is nine characters long in the hyphenated form: XXXX-XXXX.

    Examples are:
    <ISSN>0017-0011</ISSN>
    <ISSN>0951-418X</ISSN>

    Some records do not contain an <ISSN> value. Some journals are published electronically (online) in addition to or instead of in print. For journals published in both media (referred to as hybrid journals), NLM chooses one version to use for MeSH indexing and the ISSN for that version appears in the MEDLINE citation. There is no indication in the MEDLINE citation whether the ISSN present is for the print or electronic version. See also <NlmUniqueID>.

    Information about journals cited in MEDLINE, including the complete title of the journal, is found in:

    1. LocatorPlus, the NLM's online catalog at http://locatorplus.gov
    2. SERFILE, another file that may be leased from NLM (see http://www.nlm.nih.gov/databases/leased.html)
    3. PubMed journals files located at http://www.nlm.nih.gov/bsd/serfile_addedinfo.html (contains limited journal information; updated daily)
    4. Entrez Journals database at http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=journals for basic journal information similar to data found in PubMed journals list (available in the Entrez Utilities at http://www.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html; updated daily)
    5. The List of Serials Indexed for Online Users available at http://www.nlm.nih.gov/tsd/serials/lsiou.html and the List of Journals Indexed in Index Medicus available at http://www.nlm.nih.gov/tsd/serials/lji.html.

    Back to top.

  7. <JournalIssue>
    This 'envelop' element contains <Volume>, <Issue>, and <PubDate> elements; data does not reside in JournalIssue itself. The attribute PrintYN on the JournalIssue element flags an issue's PubDate as being for the print issue or not. The default value is Y for Yes; this is at the issue level. Various combinations of the JournalIssue PrintYN attribute setting and the ElectronicPubDate OfficialDateYN attribute setting permit control of which dates display in the source. Click here for information on how to interpret the JournalIssue and ElectronicPubDate attribute settings to indicate print and/or electronic publication dates when creating the source.

    Examples are:
    <JournalIssue PrintYN="Y">
    <Volume>14</Volume>
    <Issue>1</Issue>
    <PubDate>
    <Year>2000</Year>
    <Month>Jan</Month>
    </PubDate>

    <JournalIssue PrintYN="N">
    <Volume>2004</Volume>
    <Issue>4</Issue>
    <PubDate>
    <Year>2004</Year>
    <Month>Jan</Month>
    <Day>28</Day>
    </PubDate>
    </JournalIssue>

    NOTE: NLM has learned from our experience with the <JournalIssue> PrintYN and <ElectronicPubDate> OfficialDateYN attributes and plans to make changes to the DTD for 2005.

    Back to top.

  8. <Volume>
    The volume number of the journal in which the article was published is recorded here.

    Examples are:
    <Volume>7</Volume>
    <Volume>5 Spec No</Volume>
    <Volume>49 Suppl 20</Volume>
    <Volume>Doc No 93</Volume>

    The last example is for a journal published electronically. This format occurs rarely, as NLM prefers to put electronic document numbers in the <Pagination> element.

    Back to top.

  9. <Issue>
    <Issue> identifies the issue, part or supplement of the journal in which the article was published.

    Examples are:
    <Issue>Pt 1</Issue>
    <Issue>Pt B</Issue>
    <Issue>3 Spec No</Issue>
    <Issue>7 Pt 1</Issue>
    <Issue>First Half</Issue>
    <Issue>3 Suppl</Issue>
    <Issue>3 Suppl 1</Issue>

    Back to top.

  10. <PubDate>
    <PubDate> contains the full date on which the issue of the journal was published. The standardized format consists of elements for a 4-digit year, a 3-character abbreviated month, and a 1 or 2-digit day. Every record does not contain all of these elements; the data are taken as they are published in the journal issue, with minor alterations by NLM such as abbreviating months.

    Examples are:
    <PubDate>
    <Year>2001</Year>
    <Month>Apr</Month>
    <Day>15</Day>
    </PubDate>

    <PubDate>
    <Year>2001</Year>
    <Month>Apr</Month>
    </PubDate>

    <PubDate>
    <Year>2001</Year>
    </PubDate>

    The date of publication for the great majority of records will reside in the separate date-related elements within <PubDate> as shown above and in these cases the record will not contain <MedlineDate>. The date of publication of the article will be found in <MedlineDate> when parsing for the separate fields is not possible; i.e., cases where dates do not fit the Year, Month, or Day pattern.

    Examples are:
    <PubDate>
    <MedlineDate>1998 Dec-1999 Jan</MedlineDate>
    </PubDate>

    <PubDate>
    <MedlineDate>2000 Spring</MedlineDate>
    </PubDate>

    <PubDate>
    <MedlineDate>2000 Spring-Summer</MedlineDate>
    </PubDate>

    <PubDate>
    <MedlineDate>2000 Nov-Dec</MedlineDate>
    </PubDate>

    <PubDate>
    <MedlineDate>2000 Dec 23-30</MedlineDate>
    </PubDate>

    Additional information/background:
    When the only date is an electronic date of publication, it goes in the regular <PubDate> field and not in the <ElectronicPubDate> field. It's only when two dates are involved that the latter comes into play.

    Back to top.

  11. <ArticleTitle>
    <ArticleTitle> contains the entire title of the journal article. <ArticleTitle> is always in English; those titles originally published in a foreign language and translated for <ArticleTitle> are enclosed in square brackets. All titles end with a period unless another punctuation mark such as a question mark or bracket is present. Explanatory information about the title itself is enclosed in parentheses, e.g.: (author's trans). Corporate/collective authors may appear at the end of <ArticleTitle> for citations up to about the year 2000. See also <AuthorList> for more information about corporate/collective authors.

    Records distributed with [In Process Citation] in <ArticleTitle> are non-English language citations in In-Process <MedlineCitation> status that do not yet have the article title translated into English.

    Examples are:
    <ArticleTitle>The Kleine-Levin syndrome as a neuropsychiatric disorder: a case report.</ArticleTitle>
    <ArticleTitle>Why is xenon not more widely used for anaesthesia?</ArticleTitle>
    <ArticleTitle>[Biological rhythms and human disease]</ArticleTitle>
    <ArticleTitle>[In Process Citation]</ArticleTitle>
    <ArticleTitle>[Anterior panhypopituitarism after sella turcica fracture (author's trans)]</ArticleTitle>
    <ArticleTitle>Prevalence of Helicobacter pylori resistance to antibiotics in Northeast Italy: a multicentre study. GISU. Interdisciplinary Group for the Study of Ulcer.</ArticleTitle>

    Back to top.

  12. <Pagination>
    <Pagination> indicates the inclusive pages for the article cited. The pagination can be entirely non-digit data and redundant digits are omitted. Document numbers for electronic articles are found here.

    The complete pagination is found in the <MedlinePgn> element. The <StartPage> and <EndPage> elements are not distributed.

    Examples are:
    <MedlinePgn>12-9</MedlinePgn>
    <MedlinePgn>304-10</MedlinePgn>
    <MedlinePgn>335-6</MedlinePgn>
    <MedlinePgn>1199-201</MedlinePgn>
    <MedlinePgn>24-32, 64</MedlinePgn>
    <MedlinePgn>34, 72, 84 passim</MedlinePgn>
    <MedlinePgn>31-7 cntd</MedlinePgn>
    <MedlinePgn>176-8 concl</MedlinePgn>
    <MedlinePgn>iii-viii</MedlinePgn>
    <MedlinePgn>XC-CIII</MedlinePgn>
    <MedlinePgn>P32-4</MedlinePgn>
    <MedlinePgn>32P-35P</MedlinePgn>
    <MedlinePgn>suppl 111-2</MedlinePgn>
    <MedlinePgn>564</MedlinePgn>
    <MedlinePgn>[6021 words; 81 paragraphs]</MedlinePgn>
    <MedlinePgn>E101-6</MedlinePgn>
    <MedlinePgn>44; discussion 44-8</MedlinePgn>
    <MedlinePgn>925; author reply 925-6</MedlinePgn>
    <MedlinePgn>e66</MedlinePgn>
    <MedlinePgn>1 p preceding table of contents</MedlinePgn>

    Additional information/background:
    Beginning in December 2002, new rules are followed for pagination for letters to the editor that include text consisting of an author reply. If the reply is written by one or more of the authors of the original article, the words "author reply" are used in the pagination field rather than the word "discussion". "Discussion" continues to be used within pagination for other types of articles, such as an article presented at a meeting that is followed by the text of a separate discussion or verbal exchange by a panel or others attending the meeting. This new rule for pagination that includes "author reply" applies only to citations with <PublicationType> Letter.

    Back to top.

  13. <Abstract>
    English-language abstracts are taken directly from the published article. If the article does not have a published abstract, the National Library of Medicine does not create one, thus the record lacks the <Abstract> element. Publishers have given the National Library of Medicine permission to use abstracts for which they claim copyright; NLM does not hold copyright on the abstracts in MEDLINE. Licensees should obtain an opinion from their legal counsel for any use they plan for the abstracts in the database. Generally, there are no abstracts for records created before 1975. All abstracts are in English. Some records may contain <OtherAbstract> in addition to or instead of <Abstract>. Because data entry policies at NLM have changed over the years, abstracts in records created before 2001 may be truncated, in which case one of the following phrases may appear at the end of the text enclosed in parentheses:
    ABSTRACT TRUNCATED AT 250 WORDS
    ABSTRACT TRUNCATED AT 400 WORDS
    ABSTRACT TRUNCATED (This message occurred infrequently once the maximum length was raised to 4,096 characters in 1996.)

    An example is:
    <AbstractText> Many disorders may result in delay of language. . . . . . . . . . . . . . The reason for suggesting this diagnostic category is to stress that these children do initially behave in a similar way to those who are peripherally deaf. (ABSTRACT TRUNCATED AT 250 WORDS)</AbstractText>

    Structured abstracts, describing key aspects of the purposes, methods, and results in a consistent way, are published in some journals. The key aspects of structured abstracts are capitalized to stand out: e.g. "BACKGROUND" OBJECTIVES, "METHOD," etc. The text is not broken into paragraphs. Structured abstracts were not truncated in the past, even if they surpassed the previous 250 or 400 word limit.

    An example is:
    <AbstractText> BACKGROUND: Superantigens produced by Staphylococcus aureus and Streptococcus pyogenes are among the most lethal of toxins. Toxins in this family trigger an excessive cellular immune response leading to toxic shock. OBJECTIVES: To design an antagonist that is effective in vivo against a broad spectrum of superantigen toxins. METHODS: Short peptide antagonists were selected for their ability to inhibit superantigen-induced expression of human genes for cytokines that mediate shock. The ability of these peptides to protect mice against lethal toxin challenge was examined. RESULTS: Antagonist peptide protected mice against lethal challenge with staphylococcal enterotoxin B and toxic shock syndrome toxin-1, superantigens that share only 6% overall amino acid homology. Moreover, . . . </AbstractText>

    Additional information/background:
    History - Original policy on inclusion of abstracts set a limit of 250 words for acceptance. Effective with the January 1984 data (i.e., NLM's ELHILL legacy system 8401 Entry Month) two changes were made in this policy: 1) the word limit was expanded to 400 words for abstracts from articles 10 pages or more in length or from articles in the core journals identified by the National Cancer Institute and 2) abstracts exceeding the 250- or 400-word limit are to be included in truncated form at the end of the sentence closest to the word limit. The percentage of records with abstracts has increased over the years as more publishers gave permission for NLM to include these data. A chart showing the number of MEDLINE records containing abstracts in various segments of MEDLINE is available at: http://www.nlm.nih.gov/bsd/medline_lang_distr.html. The maximum length of abstracts for records created after 2000 is 10,000 characters.

    <CopyrightInformation> associated with <AbstractText> was introduced in 1999, and appears on a limited but increasing number of records. This singly-occurring element contains a copyright statement provided by the publisher of the journal and appears only on records supplied electronically to NLM by the publisher. NLM suggests that licensees display this information at the end of the abstract.

    An example is:
    <Abstract>
    <AbstractText>Aphidicolin, a selective inhibitor of DNA polymerase, totally blocks DNA replication in the micronucleus but not in the macronucleus of Paramecium caudatum. The ciliates no longer divide and after 4 days the DNA content of the macronucleus has increased by 64%. Concomitantly the cell volume has increased by 53%.</AbstractText>
    <CopyrightInformation>Copyright 1999 Academic Press.</CopyrightInformation>
    </Abstract>

    Publishers or authors may still claim copyright on abstracts in records lacking <CopyrightInformation>. Per Section F3 of the NLM License to Lease NLM Databases: "The Licensee and its users shall be solely responsible for compliance with any copyright restrictions; NLM assumes no responsibility or liability associated with the Licensee's (or any of the Licensee's users') use and/or reproduction of copyrighted material. Anyone contemplating reproduction of all or any portion of any of the NLM databases should consult legal counsel."

    Back to top.

  14. <Affiliation>
    <Affiliation> is associated with author names (see <AuthorList>) and investigator names (see <InvestigatorList>).

    Regarding author affiliations:
    The affiliation of the first author resides in the separate <Affiliation> element preceding <AuthorList>. Starting in 1988, NLM began to include the address of the first author's affiliation on the record. Originally the address was intended to help differentiate between two authors of the same name, not to provide detailed mailing information. It evolved that the institution, city, and state including zip code for U.S. addresses, and country for foreign countries, were included if provided in the journal; sometimes the street address was also included if provided in the journal. In 1995, NLM began to add the designation USA at the end of <Affiliation> where the first author's affiliation is in the 50 United States or the District of Columbia. Effective January 1, 1996, NLM includes the primary author's electronic mail (e-mail) address at the end of <Affiliation>, if present in the journal. Starting in 2003 the complete first author address is entered as it appears in the article with no words omitted.

    Examples are:
    <Affiliation>Department of Anesthesiology, University of Virginia Health Sciences Center Charlottesville 22908, USA. med2p@virginia.edu</Affiliation>
    <Affiliation>Departamento de Farmacologia, Facultad de Medicina, Universidad Complutense de Madrid (UCM), 28040 Madrid, Spain.</Affiliation>
    <Affiliation>Center for Children With Special Needs, Children's Hospital, and the Department of Pediatrics, University of Washington School of Medicine, 4800 Sand Point Way NE, CM:09, Seattle, WA 98105-0371, USA. jneff@chmc.org</Affiliation>

    Regarding investigator affiliations (see <InvestigatorList>):
    The investigator affiliation identifies the organization that the researcher was affiliated with at the time the article was written and as published in the journal. Unlike <Affiliation> associated with Author names, this affiliation generally does not include detailed address information.

    Examples are:
    <Affiliation>Marquette U, Milwaukee, WI</Affiliation>
    <Affiliation>VA Med Ctr, Richmond, VA</Affiliation>

    Back to top.

  15. <AuthorList>
    Personal and collective (corporate) author names published with the article are found in <AuthorList>. Anonymous articles (including those with pseudonyms) are identified by the absence by the absence of <AuthorList>. For records created from 1966 - 1983, every author of every journal article is included in <AuthorList>. For records created from 1984 - 1995, a maximum of 10 author names was entered in the database. Beginning with journal issues published in 1996 and through 1999, a maximum of 25 author names was entered, and beginning with journal issues published in 2000 all author names published in the journal again are entered. During the 1996 - 1999 time period, when there were more than 25 authors, the first 24 were taken plus the last author as the 25th occurrence. If an article has more authors than were entered into MEDLINE then <AuthorList CompleteYN= "N"> indicates the list is not complete. This attribute, when set to "N" for No should be translated into 'et al.' for display purposes.

    Personal name <Author> data resides in the following elements:
        <LastName> contains the surname
        <ForeName> contains the remainder of name except for suffix
        <Suffix> contains a valid MEDLINE suffix (e.g., 2nd, or 3rd, etc., Jr or Sr). Honorifics (e.g., PhD, MD, etc.) are not carried in the data.
        <Initials> contains up to two initials

    Additional information about initials:
    Initials are found at the beginning of the name string or following a break. A break is a space or hyphen. Only capital letters in ForeName are candidates for initials except for the letter following a hyphen. The letter following a hyphen is a candidate for an initial unless the string following the hyphen is 'ichi'. If ForeName is only initials, there will be spaces between initials. Initial includes the following particles: de, do, da, du, del, dos, el-, le and el. All except 'el-' are followed by a space and are preceded by a space or are at the beginning of the name string. If found, all particles will be converted to lower case in <Initials>. If language is Bulgarian, Russian, Serbo-Croatian (Roman), or Ukrainian, then Initial may be a 2-4 character transliterated mixed-case initial.

    Full first and middle names, if published, are entered in <ForeName> beginning with items published in 2002. Prior to 2002 NLM did not enter full first or middle names; instead only initials were entered and pre-2002 records were not maintained to include full names. Full personal names are included, however, on all citations owned by one of NLM's collaborating data producers, the Kennedy Institute of Bioethics (KIE), (MedlineCitationOwner="KIE") regardless of year of publication. KIE also supplied full author names for some NLM-owned citations that predate 2002; those data are found in the <GeneralNote> element.

    Examples are:
    <Author>
    <LastName>Melosh</LastName>
    <ForeName>H J</ForeName>
    <Suffix>3rd</Suffix>
    <Initials>HJ</Initials>
    </Author>

    <Author>
    <LastName>Abrams</LastName>
    <ForeName>Judith</ForeName>
    <Initials>J</Initials>
    </Author>

    <Author>
    <LastName>Buncke</LastName>
    <ForeName>Gregory M</ForeName>
    <Initials>GM</Initials>
    </Author>

    <Author>
    <LastName>Amara</LastName>
    <ForeName>Mohamed el-Walid</ForeName>
    <Initials>Mel-W</Initials>
    </Author>

    <Author>
    <LastName>Gonzales-loza</LastName>
    <ForeName>María del R</ForeName>
    <Initials>Mdel R</Initials>
    </Author>

    <Author>
    <LastName>Krylov</LastName>
    <ForeName>Iakobish K</ForeName>
    <Initials>IaK</Initials>
    </Author>

    Collective or corporate name <Author> data resides in <CollectiveName>, which was introduced to MEDLINE in 2001. Prior to 2001, corporate author information was contained only at the end of <ArticleTitle>, where it remains for those retrospective records (see <ArticleTitle>). As they are encountered, these retrospective records may be individually maintained to move the collective/corporate name from <ArticleTitle> to <CollectiveName>. For records entering MEDLINE beginning in 2001, the collective/corporate name is found in <CollectiveName>. These names enter MEDLINE exactly as they appear in the journal; NLM will not edit the names to standardize them or translate them into English. NLM enters the Roman alphabet words (e.g., German, French) into <CollectiveName>. Transliterated Russian or other cyrillic names are also entered into <CollectiveName> but for Japanese, Chinese, Hebrew, and Arabic NLM puts the English translation of the name into the <CollectiveName>.

    A complete <AuthorList> example including <CollectiveName> is:
    <AuthorList CompleteYN="Y">
    <Author>
    <LastName>Gunnars</LastName>
    <ForeName>B</ForeName>
    <Initials>B</Initials>
    </Author>
    <Author>
    <LastName>Nygren</LastName>
    <ForeName>P</ForeName>
    <Initials>P</Initials>
    </Author>
    <Author>
    <CollectiveName>SBU-group. Swedish Council of Technology Assessment in Health Care</CollectiveName>
    </Author>
    </AuthorList>

    When an author's name has been corrected from a published erratum, the corrected name is placed in <AuthorList>, and the incorrect name originally published is retained in the last occurrence. In this circumstance, <ErratumIn> under <CommentsCorrections> has an associated <Note> clarifying the correct and incorrect names (see <CommentsCorrections>).

    An example is:
    <AuthorList CompleteYN="Y">
    <Author>
    <LastName>Dunkel</LastName>
    <ForeName>E C</ForeName>
    <Initials>EC</Initials>
    </Author>
    .
    .
    .
    <Author>
    <LastName>Whitley</LastName> (this is the corrected name)
    <ForeName>R J</ForeName>
    <Initials>RJ</Initials>
    </Author>
    .
    .
    .
    <Author>
    <LastName>Whitely</LastName> (this is the originally published name)
    <ForeName>R J</ForeName>
    <Initials>RJ</Initials>
    </Author>
    </AuthorList>
    .
    .
    .
    <CommentsCorrections>
    <ErratumIn>
    <RefSource>J Infect Dis 1998 Aug;178(2):601</RefSource>
    <Note>Whitely RJ[corrected to Whitley RJ]</Note>
    </ErratumIn>
    </CommentsCorrections>

    Additional information/background:
    NLM expended much effort to parse the data converted from the legacy ELHILL format at the end of the 2000 production year accurately. Many citations from the 1966-1974 timeframe were changed to follow data entry conventions established later; e.g., particles such as "van der" were moved from the suffix position to the last name, and the abbreviations 2d and 3d were changed to 2nd and 3rd. It is possible to have particles associated with initials, such as <ForeName>María del R</ForeName> <Initials>Mdel </Initials>. It is also possible to have only a <LastName>. Some occurrences of author data in this category are in error and will be corrected manually as time permits and subsequently redistributed as revised records.

    Back to top.

  16. <Language>
    The language in which an article was published is recorded in <Language>. All entries are three letter abbreviations stored in lower case, such as eng, fre, ger, jpn, etc. When a single record contains more than one language value the XML export program extracts the languages in alphabetic order by the 3-letter language value. Some records provided by collaborating data producers may contain the value und to identify articles whose language is undetermined.

    Examples are:
    <Language>eng</Language>
    <Language>rus</Language>

    A table listing all languages found in MEDLINE is at http://www.nlm.nih.gov/bsd/language_table.html. A chart showing the number of English language MEDLINE articles in various segments of MEDLINE is available at: http://www.nlm.nih.gov/bsd/medline_lang_distr.html.

    Back to top.

  17. <DataBankList>
    NLM cooperates with international efforts to collect molecular sequence data. There are, at present, 8 databanks that register molecular sequences deposited with them by researchers. In the journal literature, a reference to the databank and the accession number assigned to the sequence may accompany, or substitute for, a lengthy graphic representation of the sequence itself. NLM enters this data in the <DataBank> and <AccessionNumber> elements in <DataBankList> if this information appears in the printed journal article. If the article lists a databank but no accession number, only the abbreviation for the databank will be entered. There is no attempt to edit or verify the databank accession numbers that appear in the journal. Since sequences may be deposited with more than one databank, there may be multiple occurrences of the <DataBank> element in <DataBankList> associated with a single article. This information may appear on the article title page, in a footnote or in a statement such as:

    Sequence data from this article have been deposited with the EMBL, GenBank and DDBJ Data Libraries under Accession No. M16978.

    The 8 data banks registering molecular sequence data at the present time are:

    MEDLINE Abbreviation Databank
    CSD Complex Carbohydrate Research Center
    GDB Johns Hopkins University Genome Data Bank
    GENBANK GenBank Nucleic Acid Sequence Database
    OMIM Mendelian Inheritance in Man (McKusick)
    PDB Protein Data Bank
    PIR Protein Identification Resource
    PRFSEQDB Protein Research Foundation
    SWISSPROT Protein Sequence Database

    If an article has more databank numbers than entered into MEDLINE then <DataBank CompleteYN="N"> indicates the list is not complete in which case NLM suggests supplying the literal "etc." after the last occurrence for display purposes.

    Additional information/background:
    NLM first began to include this information with the 1988 indexing year. Prior to 2000, NLM's policy was to enter up to 30 databank accession numbers for each record. Some global maintenance was done over the years to add databank names/accession numbers whether or not the article itself contained those references. From 2000 forward, NLM enters all databank accession numbers published in the journal. <DataBank> data in <DataBankList> are sorted first by DataBank name and then by <AccessionNumber>.

    Examples are:
    <DataBankList CompleteYN="N">
    <DataBank>
    <DataBankName>GENBANK</DataBankName>
    <AccessionNumberList>
    <AccessionNumber>AF078607</AccessionNumber>
    <AccessionNumber>AF078608</AccessionNumber>
    <AccessionNumber>AF078609</AccessionNumber>
    <AccessionNumber>AF078610</AccessionNumber>
    <AccessionNumber>AF078611</AccessionNumber>
    <AccessionNumber>AF078612</AccessionNumber>
    <AccessionNumber>AF078613</AccessionNumber>
    <AccessionNumber>AF078614</AccessionNumber>
    <AccessionNumber>AF078615</AccessionNumber>
    <AccessionNumber>AF078616</AccessionNumber>
    <AccessionNumber>AF078617</AccessionNumber>
    <AccessionNumber>AF078618</AccessionNumber>
    <AccessionNumber>AF078619</AccessionNumber>
    <AccessionNumber>AF078620</AccessionNumber>
    <AccessionNumber>AF078621</AccessionNumber>
    <AccessionNumber>AF078622</AccessionNumber>
    <AccessionNumber>AF078623</AccessionNumber>
    <AccessionNumber>AF078624</AccessionNumber>
    <AccessionNumber>AF078625</AccessionNumber>
    <AccessionNumber>AF078626</AccessionNumber>
    <AccessionNumber>AF078627</AccessionNumber>
    <AccessionNumber>AF078628</AccessionNumber>
    <AccessionNumber>AF078629</AccessionNumber>
    <AccessionNumber>AF078630</AccessionNumber>
    <AccessionNumber>AF078631</AccessionNumber>
    <AccessionNumber>AF078632</AccessionNumber>
    <AccessionNumber>AF078633</AccessionNumber>
    <AccessionNumber>AF078634</AccessionNumber>
    <AccessionNumber>AF078635</AccessionNumber>
    <AccessionNumber>AF078636</AccessionNumber>
    </AccessionNumberList>
    </DataBank>
    </DataBankList>

    <DataBankList CompleteYN="Y">
    <DataBank>
    <DataBankName>GENBANK</DataBankName>
    <AccessionNumberList>
    <AccessionNumber>AF321191</AccessionNumber>
    <AccessionNumber>AF321192</AccessionNumber>
    </AccessionNumberList>
    </DataBank>
    <DataBank>
    <DataBankName>OMIM</DataBankName>
    <AccessionNumberList>
    <AccessionNumber>118200</AccessionNumber>
    <AccessionNumber>145900</AccessionNumber>
    <AccessionNumber>162500</AccessionNumber>
    <AccessionNumber>605253</AccessionNumber>
    </AccessionNumberList>
    </DataBank>
    </DataBankList>

    Back to top.

  18. <GrantList>
    This element was introduced in 1981 and contains the following elements:
    <GrantID> contains the Research grant or contract number (or both) that designates financial support by any agency of the United States Public Health Service or any institute of the National Institutes of Health. The data are recorded exactly as they appear in the published article; there is no attempt to standardize the numbers.
    <Acronym> contains the 2-letter grant acronym.
    <Agency> contains the institute acronym.

    If an article has more grant numbers than entered into MEDLINE then <GrantList CompleteYN ="N"> indicates the list is not complete in which case NLM suggests supplying the literal "etc." after the last occurrence for display purposes.

    A list of the possible values for the grant <Acronym> and <Agency> is available from the PubMed help at http://www.ncbi.nlm.nih.gov:80/entrez/query/static/help/pmhelp.html#grantacronym. Please be advised that while NLM enters the grant number, acronym and agency values are derived by using a machine algorithm against the grant number string. This may result in some inaccurate derivations, but the overall benefit of supplying the separate acronym and agency was considered to be worth the risk of some inaccuracies.

    Examples are:
    <GrantList CompleteYN="Y">
    <Grant>
    <GrantID>GM07283</GrantID>
    <Acronym>GM</Acronym>
    <Agency>NIGMS</Agency>
    </Grant>

    <GrantList CompleteYN="N">
    <Grant>
    <GrantID>DK-44935</GrantID>
    <Acronym>DK</Acronym>
    <Agency>NIDDK</Agency>
    </Grant>
    <Grant>
    <GrantID>GM-37753</GrantID>
    <Acronym>GM</Acronym>
    <Agency>NIGMS</Agency>
    </Grant>
    <Grant>
    <GrantID>GM-44100</GrantID>
    <Acronym>GM</Acronym>
    <Agency>NIGMS</Agency>
    </Grant>
    </GrantList>

    Additional information/background:
    Through 1999 NLM entered up to 3 grant numbers for each record. Beginning in 2000, NLM began to transition to an unlimited number of grant numbers or contract numbers. Some MEDLINE citations from 2000 and 2001 may still be limited to 3 grant numbers or contract numbers, but beginning in 2002 NLM does not limit the number of grant numbers or contract numbers. Some collaborating partners record grant numbers for agencies outside the U.S. Public Health Service in the <GeneralNote> element.

    Back to top.

  19. <PublicationTypeList>
    This element is used to identify the type of article indexed for MEDLINE; it characterizes the nature of the information or the manner in which it is conveyed (e.g., Review, Letter, Retracted Publication, Clinical Conference). Records may contain more than one <Publication Type> that are listed in alphabetical order. <PublicationTypeList> is always complete; there is no attribute to indicate completeness.

    An example is:
    <PublicationTypeList>
    <PublicationType>Journal Article</PublicationType>
    <PublicationType>Retracted Publication</PublicationType>
    <PublicationType>Review</PublicationType>
    <PublicationType>Review, Tutorial</PublicationType>
    </PublicationTypeList>

    The <PublicationType> values with their descriptions may be downloaded from http://www.nlm.nih.gov/mesh. The publication type headings contain the value D in the Record Type (RY) field and the value 3 in the DescriptorName Form (DF) field. A simple list of the Publication Types is available at from the PubMed online Help at http://www.ncbi.nlm.nih.gov:80/entrez/query/static/help/pmhelp.html#PublicationTypes.

    Back to top.

  20. <VernacularTitle>
    <VernacularTitle> contains the title of each item originally published in a foreign language, in that language. Non-Roman alphabet language titles are transliterated.

    Examples are:
    <VernacularTitle>Temoignages et lettres.</VernacularTitle>
    <VernacularTitle>Wplyw przebiegu rozwoju plodu i noworodka na ujawnienie sie niektórych chorób okresu doroslego.</VernacularTitle>

    Back to top.

  21. <ElectronicPubDate>
    The date in <ElectronicPubDate> is the date the publisher made an electronic version of the article. NLM includes this data only if provided along with the citation information submitted electronically to NLM by the publisher. In January 2003 global maintenance was performed to add this element retrospectively.

    The attribute OfficialDateYN on the ElectronicPubDate element flags that article's electronic date of publication as the primary date associated with citing that article or not. The default value is N for No; this is at the article level. Various combinations of the ElectronicPubDate OfficialDateYN attribute setting and the JournalIssue PrintYN attribute setting permit control of which dates display in the source. Click here for information on how to interpret the JournalIssue and ElectronicPubDate attribute settings to indicate print and/or electronic publication dates when creating the source.

    Examples are:
    <ElectronicPubDate OfficialDateYN="Y">
    <Year>2004</Year>
    <Month>01</Month>
    <Day>28</Day>
    </ElectronicPubDate>

    <ElectronicPubDate OfficialDateYN="N">
    <Year>1999</Year>
    <Month>11</Month>
    <Day>25</Day>
    </ElectronicPubDate>

    Additional information/background:
    NLM does not display the <ElectronicPubDate> if a publisher submits it and is identical to the <PubDate>. The NISO standard (Z39.29-200X Bibliographic References) stipulates display of an electronic date only when it predates a subsequent issue date. Licensees may also wish to follow this convention. Be advised that the same intellectual date may be present in both fields using slightly different formats, i.e., the use of a leading zero in the Month or Day elements.

    NOTE: NLM has learned from our experience with the <JournalIssue> PrintYN and <ElectronicPubDate> OfficialDateYN attributes and plans to make changes to the DTD for 2005.

    Back to top.

  22. <Country>
    <Country> carries the place of publication of the journal. Valid values are those country names found in the Z category of the Medical Subject Headings (MeSH) Tree Structures that may be downloaded from http://www.nlm.nih.gov/mesh. <Country> values may appear in all upper case or in mixed case. On older records, in cases where the place of publication is unknown, the <Country> value is Unknown.

    Examples are:
    <Country>United States</Country>
    <Country>UNITED STATES</Country>
    <Country>FRANCE</Country>
    <Country>Unknown</Country>

    Country data are not maintained when names may change over time. These data are where the journal is published, not where the research was conducted.

    Back to top.

  23. <MedlineTA>
    This element contains the standard abbreviation for the title of the journal in which an article appeared. See the NLM Fact Sheet "Construction of National Library of Medicine Title Abbreviations" at http://www.nlm.nih.gov/pubs/factsheets/constructitle.html which discusses the rules currently used by the National Library of Medicine (NLM) to construct title abbreviations for journals cited in MEDLINE.

    Examples are:
    <MedlineTA>JAMA</MedlineTA>
    <MedlineTA>J Pediatr</MedlineTA>
    <MedlineTA>J Comp Physiol B</MedlineTA>
    <MedlineTA>Ann Biol Clin (Paris)</MedlineTA>

    Information about journals cited in MEDLINE, including the complete title of the journal, is found in:

    1. LocatorPlus, the NLM's online catalog at http://locatorplus.gov
    2. SERFILE, another file that may be leased from NLM (see http://www.nlm.nih.gov/databases/leased.html)
    3. PubMed journals files located at http://www.nlm.nih.gov/bsd/serfile_addedinfo.html (contains limited journal information; updated daily)
    4. Entrez Journals database at http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=journals for basic journal information similar to data found in PubMed journals list (available in the Entrez Utilities at http://www.ncbi.nlm.nih.gov/entrez/query/static/eutils_help.html; updated daily)
    5. The List of Serials Indexed for Online Users available at http://www.nlm.nih.gov/tsd/serials/lsiou.html and the List of Journals Indexed in Index Medicus available at http://www.nlm.nih.gov/tsd/serials/lji.html.

    Back to top.

  24. <NlmUniqueID>
    <NlmUniqueID> may be used to locate the complete serial record for the journal cited in MEDLINE records. The element's value is the accession number for the journal's record assigned in NLM's Integrated Library System, LocatorPlus at http://locatorplus.gov/. A <NLMUniqueID> may appear as seven, eight or nine charcaters and is the preferred element to use when looking for the serial record for the journal in which the article was published.

    Examples are:
    The LocatorPlus accession number for the New England Journal of Medicine is 0255562 and the MEDLINE records contain:
    <NlmUniqueID>0255562</NlmUniqueID>.

    The LocatorPlus accession number for the Japanese Journal of Infectious Diseases is 100893704 and the MEDLINE records contain:
    <NlmUniqueID>100893704</NlmUniqueID>.

    The LocatorPlus accession number for Sicilia Sanitaria is 20740130R and the MEDLINE records contain: <NlmUniqueID>20740130R</NlmUniqueID>.

    Back to top.

  25. <ChemicalList>
    This element contains one or more <Chemical> elements that, in turn, contain <RegistryNumber> and <NameOfSubstance>. <ChemicalList> is always complete; there is no attribute to indicate completeness.

    <RegistryNumber> contains the unique 5 to 9 digit number in hyphenated format assigned by the Chemical Abstracts Service to specific chemical substances; for enzymes, the E.C. number derived from Enzyme Nomenclature is placed in this element. A zero (0) is a valid value when an actual number cannot be located or is not yet available.

    <NameOfSubstance> is the name of the substance that the registry number or the E.C. number identifies. The MeSH Vocabulary database that contains all <NameOfSubstance> values with their descriptions may be downloaded from http://www.nlm.nih.gov/mesh. These records are of two types: 1) Supplementary Concept Records in the MeSH file, identified with a Record Type of C, or 2) MeSH Category D descriptors identified with a Record Type of D and a tree number that begins with D.

    An example of a chemical list is:
    <Chemical List>
    <Chemical>
    <RegistryNumber>69-93-2</RegistryNumber>
    <NameOfSubstance>Uric Acid</NameOfSubstance>
    </Chemical>
    <Chemical>
    <RegistyNumber>6964-20-1</RegistryNumber>
    <NameOfSubstance>tiadenol</NameOfSubstance>
    </Chemical>
    <Chemical>
    <RegistryNumber>EC 3.1.1.34</RegistryNumber>
    <NameOfSubstance>Lipoprotein Lipase</NameOfSubstance>
    </Chemical>
    <Chemical>
    <RegistryNumber>EC 3.5.2.6</RegistryNumber>
    <NameOfSubstance>beta-Lactamases</NameOfSubstance>
    </Chemical>
    </ChemicalList>

    Back to top.

  26. <CitationSubset>
    <CitationSubset> identifies the subset for which MEDLINE records from certain journal lists or records on specialized topics were created. Some of these values are found on extremely small numbers of records. Citations may contain more than one occurrence of <CitationSubset>.

    The value is true at the time the record was created; if the status of a journal changes, the value on the MEDLINE record does not change.

    The values and their definitions for <CitationSubset> are as follows. Note that several are closed subsets no longer being assigned to current data):
    AIM   = citations from Abridged Index Medicus journals, a list of about 120 core clinical, English language journals.
    B   = citations from non-Index Medicus journals in the field of biotechnology (not currently used).
    C   = citations from non-Index Medicus journals in the field of communication disorders (not currently used).
    D   = citations from non-Index Medicus journals in the field of dentistry; these citations appeared in Index to Dental Literature.
    E   = citations in the field of bioethics. (includes records from the former BIOETHICS database)
    F   = older citations from one journal prior to its selection for Index Medicus; used to augment the database for NLM's International MEDLARS Centers (not currently used)
    H   = citations from non-Index Medicus journals in the field of health administration. (includes records from the former HealthSTAR database)
    IM   = citations from Index Medicus journals.
    J   = citations from non-Index Medicus journals in the field of population information. (not currently used; on records from the former POPLINE® database)
    K   = citations from non-Index Medicus journals relating to consumer health.
    N   = citations from non-Index Medicus journals in the field of nursing; these citations appeared in the International Nursing Index.
    R   = citations from non-Index Medicus journals in the field of population and reproduction; these citations appeared in Population Sciences (not currently used).
    Q   = citations in the field of the history of medicine. (includes records from the former HISTLINE® database)
    QO   is subset of Q - indicates older history of medicine journal citations that were created before the former HISTLINE file was converted to a MEDLINE-like format. (For NLM use because they require special handling at NLM).
    S   = citations in the field of space life sciences. (includes records from the former SPACELINE™ database)
    T   = citations from non-Index Medicus journals in the field of health technology assessment. (includes records from the former HealthSTAR database)
    X   = citations in the field of AIDS/HIV. (includes records from the former AIDSLINE® database)

    Examples are:
    <CitationSubset>AIM</CitationSubset>
    <CitationSubset>IM</CitationSubset>
    <CitationSubset>X</CitationSubset>

    Back to top.

  27. <CommentsCorrections>
    The data in the various <CommentsCorrections> elements listed below are citations to associated journal publications, e.g., comments, errata, or retractions. These data enable links between the record at hand and its associated citations. MEDLINE records may contain one or more of the following:
    <CommentOn> cites the reference upon which the article comments; began use with journal issues published in 1989.
    <CommentIn> cites the reference containing a comment about the article; began use with journal issues published in 1989.
    <ErratumIn> cites the reference containing a published erratum to the article; began use in 1987.
    <ErratumFor> cites the original article for which there is a published erratum.
    <RepublishedFrom> cites the original article; began use in 1987.
    <RepublishedIn> cites the reference of the corrected and republished article; began use in 1987.
    <RetractionOf> cites the article being retracted; began use in August 1984.
    <RetractionIn> cites the reference containing a retraction of the article; began use in August 1984.
    <UpdateIn> cites the reference containing an update to the article; began limited use in 2001.
    <UpdateOf> cites the article being updated; limited use; began limited use in 2001.
    <SummaryForPatientsIn> cites the reference containing a patient summary article; began use in Nov. 2001 (these records contain Publication Type, Patient Education Handout). See the article 'Patient Education Handouts in MEDLINE®/PubMed®' in the NLM Technical Bulletin at http://www.nlm.nih.gov/pubs/techbull/ma02/ma02_new_pt.html for more information.
    <OriginalReportIn> cites a scientific article associated with a patient summary.

    Each of the <CommentsCorrections> elements above will have an associated <RefSource>, usually the associated <PMID>, and possibly a clarifying <Note>.

    <RefSource> contains the citation of the associated record.
    <PMID> contains the PMID of associated record in PubMed (if available) thus providing a link between an article and its related comments, published errata, republished information, retractions, updates, or original articles and their patient summaries.
    <Note> clarifies the data in <CommentsCorrection> and is used infrequently. It is most often used with <ErratumIn> for corrected author names (see <AuthorList>). Other uses of <Note> include: correction of dosage error in abstract (with <ErratumIn>), and clarification when only one meeting abstract covered by an 'overall' citation for the entire conference is retracted (<RetractionOf> and <RetractedIn>).

    Additional information/background:
    Some <CommentCorrection> elements do not have the PMID present. For some, a PMID will never exist where there are only one-way links; for others, record maintenance must take place before NLM can supply the correct PMID and these corrected records will be eventually be distributed as Revised records. Journal title abbreviations in <CommentOn> and <CommentIn> in retrospective data through the 2000 production year end with a period whereas journal title abbreviations in other <CommentsCorrections> elements (such as <ErratumIn>) do not end with a period. This apparent discrepancy is a result of parsing the data as it moved from one field to another during conversion from the legacy system in 2000. Current data entry convention is to use a period after the journal title abbreviation. <RefSource> for <RetractionOf> and <RetractionIn> may contain author names.

    See the NLM Fact Sheet "Errata, Retraction, Duplicate Publication and Comment Policy for MEDLINE®" at http://www.nlm.nih.gov/pubs/factsheets/errata.html for additional information.

    Examples are:
    <CommentsCorrections>
    <ErratumIn>
    <RefSource>J Infect Dis 1998 Aug;178(2):601</RefSource>
    <Note>Whitely RJ[corrected to Whitley RJ]</Note>
    </ErratumIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <ErratumIn>
    <RefSource>Eur Respir J 2002 Feb;19(2):384</RefSource>
    <Note>Correction of dosage error in abstract.</Note>
    </ErratumIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <RetractionOf>
    <RefSource>Gut. 2001 Mar;48 Suppl 1:A1-124</RefSource>
    <PMID>11286195</PMID>
    <Note>abstract no. 071 only</Note>
    </RetractionOf>
    </CommentsCorrections>

    <CommentsCorrections>
    <RetractionIn>
    <RefSource>Gut. 2001 Jun;48(6):873</RefSource>
    <PMID>11411464</PMID>
    <Note>abstract no. 071 only</Note>
    </RetractionIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <ErratumIn>
    <RefSource>Mol Pharmacol 1997 Mar;51(3):533</RefSource>
    </ErratumIn>
    <RetractionIn>
    <RefSource>Wu D, Yang CM, Lau YT, Chen JC. Mol Pharmacol. 1998 Feb;53(2):346</RefSource>
    </RetractionIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <SummaryForPatientsIn>
    <RefSource>Ann Intern Med. 2002 Jun 18;136(12):I-56</RefSource>
    <PMID>12069573</PMID>
    </SummaryForPatientsIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <OriginalReportIn>
    <RefSource>Ann Intern Med. 2002 Jun 18;136(12):884-7</RefSource>
    <PMID>12069562</PMID>
    </OriginalReportIn>
    </CommentsCorrections>

    <CommentsCorrections>
    <CommentOn>
    <RefSource>Ann Intern Med. 2001 Apr 17;134(8):663-94</RefSource>
    <PMID>11304107</PMID>
    </CommentOn>
    </CommentsCorrections>

    <CommentsCorrections>
    <CommentIn>
    <RefSource>Ann Intern Med. 2002 Jun 18;136(12):926-7; discussion 926-7</RefSource>
    <PMID>12069567</PMID>
    </CommentIn>
    <CommentIn>
    <RefSource>Ann Intern Med. 2002 Jun 18;136(12):926-7; discussion 926-7</RefSource>
    <PMID>12069568</PMID>
    </CommentIn>
    </CommentsCorrections>

    The following is how NLM uses the data in these elements for display purposes after the source pagination: For each <CommentsCorrections> element which exists in the record, take the tag name and make it a constant label: for example: <RetractionIn> would produce the label 'Retraction in:' (a space is entered between the two words on the tag label and only the first word has an initial capital letter). Follow each label with a colon, space, and the content of the associated <RefSource> tag, then the contents of the associated <Note>, if present. Exception to the Label rule: Instead of the label 'Republished in:' and similarly for <RepublishedFrom>, create 'Corrected and republished from:'. If multiple occurrences exist on a label, repeat literal label and separate with a period, space.

    Examples are:
    Retraction in: Gut. 2001 Jun;48(6):873. abstract no. 071 only
    Retraction in: Wu D, Yang CM, Lau YT, Chen JC. Mol Pharmacol. 1998 Feb;53(2):346
    Original report in: Ann Intern Med. 2002 Jun 18;136(12):884-7

    Back to top.

  28. <GeneSymbolList>: not currently input
    <GeneSymbol> contains the "symbol" or abbreviated form of gene names as reported in the literature. This element resides in records processed at NLM from 1991 through 1995. <GeneSymbol> has a maximum length of 72 characters, although few, if any, gene symbols contain the maximum length. Up to 25 occurrences per record may appear; however this element is always complete in the XML record; there is no attribute to indicate completeness. NLM entered the symbols used by authors; there was no authority list or effort to standardize the data. <GeneSymbolList> is always complete; there is no attribute to indicate completeness.

    Examples are:
    <GeneSymbolList>
    <GeneSymbol>pyrB</GeneSymbol>
    <GeneSymbol>Ghox-lab</GeneSymbol>
    <GeneSymbol>pulC</GeneSymbol>
    </GeneSymbolList>

    Additional information/background:
    In the gene symbol field, SGML is used to designate Greek characters, superscripts, and subscripts that may appear as part of the gene symbol. The ampersand (&) and semicolon (;) are the respective beginning and ending delimiters for Greek characters with specified alphabetic codes to designate the appropriate letter and whether it is upper or lower case. The less than/greater than signs are used to define superscripted and subscripted regions. The beginning of a super-scripted region will be designated <up> while </up> signal its end. Similarly, <down> indicates the beginning of a sub-scripted region; while </down> indicates the end. A table, originally published on page 32 of the Sep - Oct 1990 NLM Technical Bulletin, displays the code designations for the Greek characters and may be found at http://www.nlm.nih.gov/bsd/license/greek_symbol.html.

    Back to top.

  29. <MeshHeadingList>
    NLM's controlled vocabulary, Medical Subject Headings (MeSH®), is used to characterize the content of the articles represented by MEDLINE citations. Of the various MeSH headings assigned to a record, those representing the most significant points are identified with the MajorTopic attribute set to Y for Yes. It is under those major descriptors that the citation can be located in Index Medicus. The remaining descriptors are used to identify concepts which have also been discussed in the item, but that are not the primary topics. See http://www.nlm.nih.gov/mesh/meshhome.html for information about MeSH. Only records in Completed MedlineCitation Status contain MeSH headings. Each <MeshHeading> in <MeshHeadingList> contains <DescriptorName> and often <QualifierName>. <MeshHeadingList> is always complete; there is no attribute to indicate completeness.

    The MajorTopic attribute for <DescriptorName> is set to Y (for YES) when the MeSH Heading alone is a central concept of the article (without a QualifierName).

    <QualifierName>, along with its MajorTopic attribute indicates when the combination of that <QualifierName> with its associated <DescriptorName > is a central concept of the article. Qualifiers are also known as subheadings.

    The presentation of <DescriptorName> is alphabetical. The <QualifierName> associated with a <DescriptorName> is also in alphabetical order, disregarding presence of the MajorTopic attribute.

    Examples are:
    <MeshHeadingList>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Adult</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Cardiovascular Diseases</DescriptorName>
    <QualifierName MajorTopicYN="N">etiology</QualifierName>
    <QualifierName MajorTopicYN="Y">mortality</QualifierName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">English Abstract</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Fetal Growth Retardation</DescriptorName>
    <QualifierName MajorTopicYN="N">complications</QualifierName>
    <QualifierName MajorTopicYN="Y">physiopathology</QualifierName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Human</DescriptorName>
    </MeshHeading>
    </MeshHeadingList>

    In the above example, the mortality aspect of cardiovascular diseases and the physiopathology aspect of fetal growth retardation are the central concepts of the article. Note that the MeSH Heading English Abstract (also present in above example) means that a substantive English language abstract is present in the journal or written by one of NLM's collaborating data producers. The abstract may or may not be present in the MEDLINE citation as the input policy changed over the years. There are many older non-English language citations without abstracts in MEDLINE but with the MeSH Heading English Abstract; this indicates that an English abstract is present in the journal, even if not a part of the online record.

    <MeshHeadingList>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Animal</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Dogs</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="Y">Myocardial Contraction</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Myocardium</DescriptorName>
    <QualifierName MajorTopicYN="Y">metabolism</QualifierName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="Y">Oxygen Consumption</DescriptorName>
    </MeshHeading>
    <MeshHeading>
    <DescriptorName MajorTopicYN="N">Surface Tension</DescriptorName>
    </MeshHeading>
    </MeshHeadingList>

    In the above example, myocardial contraction, the metabolism aspect of myocardium, and oxygen consumption are the central concepts of the article.

    Back to top.

  30. <NumberOfReferences>
    This element appears on records indexed with Review as a <PublicationType>; these data are not input for 'regular' journal articles. <NumberOfReferences> contains the number of bibliographic references listed in the review article.

    An example is:
    <NumberOfReferences>21</NumberOfReferences>

    Additional information/background:
    When collaborating partners recorded the number of references for non-review articles, these data are found in the <GeneralNotes> element.

    Back to top.

  31. <PersonalNameSubjectList>
    Individuals' names appear in <PersonalNameSubject> for citations that contain a biographical note or obituary, or are entirely about the life or work of an individual or individuals. Data is entered in the same format as author names in <AuthorList> including <LastName>, <ForeName>, <Suffix>, and <Initials>. See <AuthorList> for details of format. <PersonalNameSubjectList> is always complete; there is no attribute to indicate completeness.

    An example is:
    <PersonalNameSubjectList>
    <PersonalNameSubject>
    <LastName>Koop</LastName>
    <ForeName>C Everett</ForeName>
    <Initials>CE</Initials>
    </PersonalNameSubject>
    </PersonalNameSubjectList>

    Additional information/background:
    An anonymous biography or obituary has the person's name in this element but the <AuthorList> is absent.

    Back to top.

  32. <OtherID>
    <OtherID> may reside on a record owned by a collaborating partner or on an NLM-owned record to which a collaborating partner added additional information not originally included by NLM on the record. <OtherID> and its Source attribute identifies a) the organization responsible for the information on the citation or the document where the information originated, and b) a unique number for that citation or document. If a partner created the record, the <OtherID>, in that case, is also the internal tracking number for the source document located at the partner's site. For example, a partner may add <Keyword> data to an NLM owned record. In that case the <OtherID> will contain that partner's internal document number for the journal article. The field may be multiply occurring.

    The element <OtherID> has one or more of the Source attributes identifying the collaborating partner listed below. Some of the values on this list currently are not in use at this time and some may never be used.

    NASA - National Aeronautics and Space Administration
    KIE - Kennedy Institute of Ethics, Georgetown University
    PIP - Population Information Program, Johns Hopkins School of Public Health; not currently used
    POP - former NLM POPLINE database; not currently used
    ARPL - Annual Review of Population Law; not currently used
    CPC - Carolina Population Center; not currently used
    IND - Population Index; not currently used
    CPFH - Center for Population and Family Health Library/Information Program; not currently used
    CLML - Current List of Medical Literature; reserved for future use
    IM - Index Medicus; reserved for future use (intended for pre-1966 publications)
    SGC - Surgeon General's Catalog; reserved for future use
    NCT - National Clinical Trials; reserved for future use
    NRCBL - National Reference Center for Biomedical Literature (for the KIE Reference Library shelving location)

    Examples are:
    <OtherID Source="KIE">101133</OtherID>
    <OtherID Source="NRCBL">14.1</OtherID>

    Back to top.

  33. <OtherAbstract>
    NLM creates MEDLINE records without <Abstract> when the source journal article does not contain an abstract. Whether or not there is an <Abstract>, a collaborating partner (identified in the <OtherAbstract> Type attribute) may create an <OtherAbstract> for that record. If a partner creates and provides an abstract for <OtherAbstract>, the internal tracking number of the source document used by the collaborating partner resides in <OtherID>. <CopyrightInformation> to indicate authorship or editing of abstract is associated with <OtherAbstract> on a very small number of records.

    The element <OtherAbstract> can have one or more of the Type attributes listed below:
    AAMC - American Association of Medical Colleges; not currently used
    AIDS - Special HIV/AIDS publications with abstracts written by someone other than the author
    KIE - Kennedy Institute of Ethics, Georgetown University
    PIP - Population Information Program, Johns Hopkins School of Public Health
    NASA - National Aeronautics and Space Administration
    Consumer - Abstracts written for consumers; reserved for future use

    Back to top.

  34. <KeywordList>
    <KeywordList> contains controlled terms in <Keyword> that are assigned by a collaborating data producer and that describe the content of the article. Keywords, when present, appear on records in addition to MeSH Headings. Not all MEDLINE data producers supply Keywords; those that do use their own list of specialized terms which may change during the year. The same Keyword may exist in more than one Keyword List. <KeywordList> is always complete; there is no attribute to indicate completeness. The element <KeywordList> can have one or more of the Owner attributes listed in <MedlineCitation>, which identifies the organization that assigned the subject terms. Currently, relatively few records in the database contain this element and the only Owner attributes currently in use with <KeywordList> are:
    NASA - National Aeronautics and Space Administration
    PIP - Population Information Program, Johns Hopkins School of Public Health
    KIE - Kennedy Institute of Ethics, Georgetown University

    Examples:
    <KeywordList Owner="NASA">
    <Keyword MajorTopicYN="N">NASA Discipline Space Human Factors</Keyword>
    <Keyword MajorTopicYN="N">Non-NASA Center</Keyword>
    </KeywordList>

    <KeywordList Owner="KIE">
    <Keyword MajorTopicYN="N">Birth Rate</Keyword>
    <Keyword MajorTopicYN="N">Doe v. Bolton</Keyword>
    <Keyword MajorTopicYN="N">Empirical Approach</Keyword>
    <Keyword MajorTopicYN="N">New York</Keyword>
    <Keyword MajorTopicYN="N">Roe v. Wade</Keyword>
    <Keyword MajorTopicYN="Y">United States</Keyword>
    </KeywordList>

    Back to top.

  35. <SpaceFlightMission>
    <SpaceFlightMission> resides on MEDLINE citations created by one of our collaborating data producers, the National Aeronautics and Space Administration (NASA). This element contains the space flight mission name and/or number when results of research conducted in space are covered in a publication. In cases where there are multiple space flight missions, the mission name is not directly linked to the descriptive values manned/unmanned or long/short duration that also reside in the <SpaceFlightMission> element in the MEDLINE record. For records containing more than one Space Flight Mission name, see the Space Flight Mission Summary Table at http://www.nlm.nih.gov/bsd/space_flight.html that provides the manned/unmanned status and duration of each mission.

    Examples are:
    <SpaceFlightMission>Flight Experiment</SpaceFlightMission>
    <SpaceFlightMission>STS Shuttle Project</SpaceFlightMission>
    <SpaceFlightMission>manned</SpaceFlightMission>
    <SpaceFlightMission>short duration</SpaceFlightMission>

    <SpaceFlightMission>Biosatellite 2 Project</SpaceFlightMission>
    <SpaceFlightMission>Flight Experiment</SpaceFlightMission>
    <SpaceFlightMission>Project Gemini 11</SpaceFlightMission>
    <SpaceFlightMission>manned</SpaceFlightMission>
    <SpaceFlightMission>short duration</SpaceFlightMission>
    <SpaceFlightMission>unmanned</SpaceFlightMission>

    Back to top.

  36. <InvestigatorList>
    <InvestigatorList> resides on MEDLINE citations created or maintained by one of our collaborating data producers, the National Aeronautics and Space Administration (NASA). It identifies the NASA funded principal investigator(s) who conducted the research discussed in the article cited (but are not necessarily the authors). Data is entered in the same format as author names in <AuthorList> including <LastName>, <ForeName>, <Suffix>, and <Initials>. This element contains <Affiliation> that identifies the organization that the researcher was affiliated with at the time the article was written. Unlike <Affiliation> associated with Author names, this affiliation does not include detailed address information. <InvestigatorList> is always complete; there is no attribute to indicate completeness.

    An example is:
    <InvestigatorList>
    <Investigator>
    <LastName>Mortley</LastName>
    <ForeName>D G</ForeName>
    <Initials>DG</Initials>
    <Affiliation>Tuskegee U, AL</Affiliation>
    </Investigator>
    </InvestigatorList>

    Back to top.

  37. <GeneralNote>
    <GeneralNote> contains supplemental or descriptive information related to the document cited in the MEDLINE record. It is a 'catchall' for various types of information included by NLM's collaborating producers.

    <GeneralNote> can have one or more of the Owner attributes listed below, although some are not currently in use and some may never be used:
    NLM - National Library of Medicine; not used
    NASA - National Aeronautics and Space Administration
    PIP - Population Information Program; Johns Hopkins School of Health
    KIE - Kennedy Institute of Ethics, Georgetown University
    HSR - National Information Center on Health Services Research and Health Care Technology, National Library of Medicine
    HMD - History of Medicine Division, National Library of Medicine
    SIS - Division of Specialized Information Services, National Library of Medicine; not used
    NOTNLM - not used by NLM; reserved for use by licensees

    Examples are:
      <GeneralNote Owner="KIE">42 refs.</GeneralNote>
      <GeneralNote Owner="KIE">Approved by the ACP Board of Regents on 23 Mar 1992 and by the IDSA Council on 21 Mar 1993.</GeneralNote>
      <GeneralNote Owner="KIE">Adopted by the APHA Governing Council 3 Oct 1990.</GeneralNote>
      <GeneralNote Owner="KIE">KIE BoB Subject Heading: INFORMED CONSENT/INSTITUTIONALIZED PERSONS/MENTALLY ILL </GeneralNote>
      <GeneralNote Owner="KIE">KIE Bib: allowing to die/legal aspects; euthanasia/legal aspects; suicide</GeneralNote>
    **Note: BoB Subject Headings are controlled subject vocabulary terms found in the Kennedy Institute of Ethics' Bioethics Thesaurus under which citations print in their publication, Bibliography of Bioethics. The current format of these data in MEDLINE is reflected in the second example beginning with "KIE Bib".
      <GeneralNote Owner="KIE">118 fn.</GeneralNote>
    **Note: "fn" is an abbreviation for "footnotes"
      <GeneralNote Owner="KIE">Full author name: Weber, James</GeneralNote>
      <GeneralNote Owner="KIE">Broden, Melodie S; Agresti, Albert A</GeneralNote
      <GeneralNote Owner="NASA">Grant numbers: NSG 155-61, NAS-95637.</GeneralNote>

    Back to top.

  38. <DeleteCitation>
    PMIDs in DeleteCitation are for records previously distributed in any status and subsequently determined to be not within MEDLINE's or PubMed's coverage or to be duplicate citations. It is possible that a deleted citation can be distributed without a previous version ever going out. This would happen infrequently when the creation and completion of a new record, or error resolution of a previously created record, and deletion action occurs on the same day.

    Coverage deletes: Most of the citation data in PubMed is submitted to NLM electronically by journal publishers. The publishers are instructed not to submit certain types of records because they are not covered by MEDLINE or PubMed. Examples of these are: book reviews, software or equipment reviews, announcements, erratum notices without additional substantive content, and papers to appear in forthcoming issues. Contrary to instructions, publishers do sometimes submit citations outside of NLM's coverage which are distributed to licensees in In-Data-Review status. As a result of routine checks, these record types are subsequently discovered and deleted.

    Duplicate deletes: Publishers may accidentally submit citations that they have already submitted, or new records can otherwise be created for already existing citations, creating duplicate records which are also deleted as soon as they are discovered. Occasionally a publisher submits an issue electronically using incorrect volume, issue, or publication date data. These incorrect files are often deleted and resent correctly later rather than NLM trying to edit the files.

    Back to top.

CREATION OF JOURNAL SOURCE AT NLM

NLM concatenates the following elements to create the journal source:
<MedlineTA>. < PubDate>;<Volume>(<Issue>):<Pagination>.

In addition, various combinations of the attributes associated with <JournalIssue> and <ElectronicPubDate> elements are used to indicate whether the PubDate displayed in the source represents a print or an electronic publication date, and whether or not an additional Epub or Print publication date notation is needed at the end of the source.

Note there is a space after <MedlineTA>. The punctuation marks (periods, semicolon, and colon) are not found in the elements themselves as physical data but are added for display purposes by programming in NLM's search interface(s). NLM follows the national standard for the formatting of citations for display (American National Standard for Bibliographic References ANSI Z39.29-1977, developed and maintained by the National Information Standards Organization (NISO, Z39)).

Examples from NLM's PubMed summary display are:
Dermatol Surg. 2002 Oct;28(10):959-61.
J Foot Ankle Surg. 2002 Sep-Oct;41(5):320-7.
J Am Acad Dermatol. 2002 Nov;47(5 Suppl):S263-5.
Health Serv J. 2002 Nov 28;112(5833):27-9.
Lancet. 2002 Dec 21-28;360(9350):2049-50.
Nurs Times. 2002 Nov 26-Dec 2;98(48):52-3.
Int J Health Care Qual Assur Inc Leadersh Health Serv. 2002;15(6-7):303-10.
Mol Vis. 2002 Dec 20;8:483-93.
Dev Ophthalmol. 2003;36:50-5.
Health Care Financ Rev. 2000 Winter;22(2):189.
N Engl J Med. 2002 Dec 19;347(25):2082-3; author reply 2082-3.
Health Serv Res. 2002 Oct;37(5):xv-xxvi.
Am Fam Physician. 2002 Nov 15;66(10):2008, 2010, 2013.
Soins. 2002 Nov;(670):47-9.
Surg Endosc. 2000 Jan;14(1):86. Epub 1999 Nov 25.
Sci Aging Knowledge Environ. 2004 Jan 28;2004(4):nf13.
Nucleic Acids Res. 2004 Jan 15;32(1):e14.
Nucleic Acids Res. 2004 Jan 16;32(1):380-5. Print 2004.

Back to top.

ADDITIONAL SOURCES OF INFORMATION

Refer to NLM's web page for prospective licensees at http://www.nlm.nih.gov/databases/leased.html and the page for existing licensees at http://www.nlm.nih.gov/bsd/licensee.html. These pages contain links to items including:
* the standard License and non U.S. research-only License and the Intended Use Worksheet required for leasing MEDLINE and other NLM databases
* instructions on how to lease MEDLINE and other databases from NLM
* DTDs and sample MEDLINE and other database records
* specifications of DLT tape used to distribute the baseline MEDLINE file each winter as alternative to ftp
* annual MEDLINE baseline database documentation
* MEDLINE maintenance overview
* the MEDLINE character set and the MEDLINE language table
* Update/Documentation Chart for a summary of the content of the daily MEDLINE update files via ftp
* announcements to licensees
* information about journals indexed in MEDINE

NLM's MEDLINE fact sheet is available at http://www.nlm.nih.gov/pubs/factsheets/medline.html. Many NLM databases are trademarked - see the National Library of Medicine Trademarks Fact Sheet.


Return to Information for Licensees of NLM Data

Last updated: 08 October 2004
First published: 24 Febuary 2003
Metadata| Permanence level: Permanence Not Guaranteed