Search Health Library

This section contains examples of certain scenarios when using the EBSCOhost Integrated Toolkit (EIT) API to retrieve content in Health Library. This page will help you by offering applicable sample scenarios that you can use to configure your own applications.

For additional help with query syntax, refer to the Health Library Query Syntax guide.

Back to Top

Scenario 1 - A Basic Search

 

Get articles restricted to Natural & Alternative Treatments that have the word "diabetes" in the Title

Web Service method to use

Search

Parameters

query: PT "natural & alternative treatment*" AND TI diabetes

Database code

hlt

NOTE: The tags PT (Publication Type) and TI (Title) used in this scenario is described in the info Web Service.
Scenario 11 listed below shows how to attain a complete list of publication types that can be used in searching the Health Library database.
Back to Top

Scenario 2 - Retrieving a Single Article

 

Get a single article based on chunkid

Web Service method to use

Search

Parameters

query: AN 38323

Database code

hlt, hls

NOTE: The tag AN (assession number) used in this scenario is described in the info Web Service.
Each chunkid is a constant datum associated with one article and is located in the header element of each record. ( header/controlInfo/artinfo/ui[@type='chunkID'] )
Back to Top

Scenario 3 - Searching by Subject Meta

 

Get all articles having a subject term that includes the word "alzheimer's"

Web Service method to use

Search

Parameters

query: SU alzheimer's

Database code

hlt

NOTE: There are multiple meta-types which can be used as search criteria; for instance an ICD-10 can be searched with a query of CD [ICD-10 Code].
Back to Top

Scenario 4 - Utilizing Existing Index Pages

 

Get the existing index page listing all conditions in alphabetical order

Web Service method to use

Search

Example

query: AN 33341

format: Full

Database code

hlt, hls

NOTE: Chunkid 33341 (Disease, Condition, & Injury Fact Sheets) is one of several index pages available so as to present an alphabetical listing that includes titles and synonyms. Other existing index pages include 33342 (Procedure & Surgery Fact Sheets), 248916 (Disease & Condition Information Centers) etc.
Back to Top

Scenario 5 - Retrieving All Index Pages

 

Returns a complete list of all index pages.

Web Service method to use

Search

Parameters

query: PT [Publication Type]

Example

query: PT "index page"

Database code

hlt, hls

NOTE: The hlt (proprietary Health Library database) includes index pages. The drug databases and Health News databases do not contain index pages.
Back to Top

Scenario 6 - Retrieving Health News Articles

 

Get the last 10 HealthDay News articles

Web Service method to use

Search

Parameters

query: "HealthDay News"

numrec: 10

sort: date

Database code

nrcn, hns

Back to Top
Back to Top

Scenario 7 - Listing Drugs Alphabetically

 

Render a listing of drugs (brand names and generic names)

Web Service method to use

Browse

Parameters

query: A

Index: ZH

Database code

lpe

NOTE: The browse method is not a search. It does not resrict the results, but instead begins a list of names based on the query and runs to the limit of 200. To continue browsing to the next 200, the last term may be used as the starting point of the next query. The listing of drug names from this browse method includes both generic and brand names. Every brand name can be identified by the inclusion of the registered trademark ® in the name.
Back to Top

Scenario 8 - Retrieving One Drug Article Using a Brand Name.

 

Retrieve an exact drug article using a brand name

Web Service method to use

Search

Parameters

query: ZQ “tylenol®”

Database code

lpe

Back to Top

Scenario 9 - Retrieving One Drug Article Using a Generic Name.

 

Retrieve an exact drug article using a generic name

Web Service method to use

Search

Parameters

query: ZM "acetaminophen"

Database code

lpe

Back to Top

Scenario 10 - Geting Database Tags Information

 

Tags (associated with various metadata) that can be used for restricting searches in each database are retrieved using the info Web Service. For instance the tag TI for Title, can be used in any database, and is listed in the info method as one of the dbTag elements as follows: <dbTag name="TI" description="Title"/>

Web Service method to use

Info

Parameters

No search or browse input parameters required

Database code

No database codes are required

NOTE: The tags (dbTag elements) are used in the search Web Service and cannot be used as indicies (dbIndex) in the browse method. The indicies are meant for use with the browse method index field.
Back to Top

Scenario 11 - Getting All Publication Types that Can be Used in Health Library Searches

 

In Scenario 1, the tag PT was used to restrict the search results to only articles of the publication type natural & alternative treatment. A complete list of publication types that can be used as search criteria can be retrieved using the browse method.

Web Service method to use

Browse

Parameters

term: a*

numrec: 200

index: ZT

Database code

hlt

Back to Top

Scenario 12 - Listing New/Updated Articles

 

Retrieve list of articles that have been added or updated from a specified date.

Web Service method to use

Search

Parameters

query: RD > [yyyymmdd]

Examples

query: RD > 20140401

Database code

hlt

Back to Top

Scenario 13 - Cross-database Searches

 

Cross-database searches are possible in the EIT Web Services. The database for each record returned in this type of search must be considered in the application design and XSL transformation, so as to form links that can be properly interpreted by the background methods or code-behind.

Web Service method to use

Search

Examples

query: Codeine

Database code

lpe,nrcn,hlt

NOTE: The search shown here uses no tag, and so is a broad-scoped search. Using a tag peculiar to one database such as DG (peculiar to lpe/lps) will exclude results from hlt and nrcn as they do not recognize the DG tag.

To learn more about how EBSCO can serve all of a corporation's electronic information needs click here.