Healthcare answers, not healthcare tables.
QOPE connects public CMS, FDA, NPPES and HRSA data so you can see who prescribes a drug, which patents expire next, and which companies pay a physician, then act on the answer.
- Start from the answer
Ranked answers like the top prescribers of a drug, upcoming patent expiries, and active shortages, before you build a single filter. - One profile per provider or drug
Provider profiles show Medicare procedures, prescribing, and industry payments. Drug profiles show patent protection, generic competition, recalls, and pricing. - Act on it
Save providers to lead lists, watch drugs and markets for changes, export CSV or Excel, or pull JSON through the API.
Public healthcare data is available. Making it usable is the hard part.
Healthcare information exists across government datasets, public registries, and regulatory databases — but it is distributed across separate systems, structured differently, and updated on different schedules.
Before meaningful research, analysis, or product development can begin, users often need to locate the right sources, understand unfamiliar schemas, clean inconsistent fields, compare identifiers, and reconcile records across datasets.
Too much time is spent preparing the data before the work that creates value can begin.
Start from organized healthcare data, not disconnected files.
QOPE brings supported public healthcare datasets into one structured environment. It organizes records consistently, connects related information where available, and preserves source context so users can begin with more usable data.
Bring public sources together.
QOPE collects supported datasets from public healthcare registries, government sources, and regulatory databases into one maintained environment.
Work with a more consistent structure.
Fields, identifiers, and record formats are organized using predictable conventions across supported datasets.
Explore related healthcare records.
Where supported connections are available, QOPE helps users move between related providers, organizations, facilities, networks, programs, drugs, and regulatory records.
Twenty-eight public datasets, one search.
Search across supported healthcare datasets without navigating separate portals, downloading individual files, or learning a completely different workflow for every source.
Move from public records to useful answers faster.
Search, filter, open a prepared view, save, export, and integrate supported public healthcare data without repeating the same preparation work for every project.
Find records and narrow them fast.
Search supported providers, facilities, drugs, networks, and public programs, then filter by specialty, taxonomy, location, identifiers, status, and regulatory details.
Start from a view, not a blank table.
Open the patent cliff for loss-of-exclusivity timing and generic competition, a full drug profile, the shortage tracker, the map, or a territory brief.
See more context around each record.
Move between related records where supported connections are available in QOPE.
Keep research organized and watch what moves.
Add providers to saved lists with notes and statuses, and watch drugs, manufacturers, markets, or counties for recall and pricing signals.
Take structured results into your workflow.
Export table results as CSV or JSON, and provider, facility, ACO, and drug profiles as Excel workbooks, for research, analysis, reporting, and operational use.
Build with public healthcare data.
Access supported records programmatically as structured JSON through the QOPE API.
Keep your provider research organized.
Add providers to a saved list, note where each one stands, and pick up your research later without rebuilding the search that got you there.
Built for professionals and organizations working with public healthcare data.
From one-time research and provider verification to recurring analysis, product development, and data integration, QOPE supports different ways of working with public healthcare information.
Find and verify healthcare information faster.
Search providers, organizations, facilities, drugs, networks, and public programs without navigating multiple public portals or preparing raw datasets manually.
Build a clearer view of the healthcare landscape.
Use structured public records to research providers, organizations, facilities, networks, drugs, and regulatory activity.
Start client work from organized public data.
Build focused datasets and research views without repeating the same collection, cleaning, and reconciliation process for every engagement.
Integrate public healthcare data into products and workflows.
Access supported records through search, CSV exports, and JSON API workflows instead of maintaining separate pipelines for every public source.
Whether you are answering a single question or supporting an ongoing data workflow, QOPE helps reduce the preparation required before useful work can begin.
Built on authoritative public healthcare data.
QOPE organizes supported records from government agencies, public registries, and regulatory databases into one structured environment.
Source references and dataset context are presented where available to help users better understand where supported information originated and how it should be interpreted.
QOPE is an independent platform and is not affiliated with or endorsed by CMS, the FDA, NPPES, or any government agency.
The data preparation happens before you run a search.
QOPE does more than present links to public healthcare datasets. It collects and organizes supported records before they reach the user, creating a more consistent starting point for research, analysis, and integration.
Work with predictable data conventions.
Explore available relationships between records.
Understand where the information originated.
Start from data organized around the source.
QOPE transforms fragmented public healthcare records into a more structured and connected foundation designed to be easier to search, understand, and build on.
Plans and pricing.
Every plan includes search, exports, and API access. Premium datasets unlock on Pro. Monthly or annual billing — annual saves two months.
- Core datasets
- 10,000 credits / mo
- CSV + Sheets export
- 1 seat
- Email support
- Everything in Regular
- 250,000 credits / mo
- Premium datasets + intelligence tools
- 1 seat
- Priority support · 24h
- Everything in Pro
- 1,000,000 credits / mo
- Team dashboard
- 5 seats included, up to 15
- Slack channel + dedicated account manager
Explore QOPE on your own or talk to us about a specific workflow.
Start with the platform or tell us what you are trying to research, analyze, or integrate.
Have a specific data or workflow question?
Tell us what you are trying to research, build, or integrate. Our team can help you understand which QOPE datasets, access methods, and plan options may be relevant to your needs.
Frequently asked questions.
What is QOPE?
QOPE is a Healthcare Intelligence Platform that makes fragmented public healthcare data easier to search, understand, and use.
Where does QOPE's data come from?
QOPE works with supported public healthcare sources, including government agencies, regulatory databases, and public registries such as CMS, FDA, NPPES, and OpenFDA.
Is QOPE affiliated with government agencies?
No. QOPE is an independent platform and is not affiliated with or endorsed by CMS, the FDA, NPPES, or any government agency.
Who is QOPE for?
QOPE is designed for individual professionals, researchers, healthcare and life sciences organizations, consulting teams, and product or data teams working with public healthcare information.
How can I access QOPE data?
Supported records can be explored through the QOPE platform, exported as CSV, JSON, or Excel, or accessed as structured JSON through the API, depending on the available capabilities of your plan.
Does QOPE contain protected health information?
QOPE works with public healthcare information and is not designed to collect or provide protected health information. Users should not submit PHI or sensitive personal data through QOPE forms or support channels.
How often is the data updated?
Supported datasets are refreshed based on the availability and publication schedules of their underlying public sources. Update frequency may vary by dataset.
Can I try QOPE before subscribing?
QOPE offers a free trial so users can explore the platform before choosing a paid plan. Current trial conditions are presented during signup.
Providers
Search public provider records
Finding reliable information about a healthcare provider should not require downloading a national data file and working through thousands of unfamiliar columns.
The Providers database brings public CMS NPPES records into QOPE, where they can be searched through a familiar interface. Start with a provider's name, National Provider Identifier (NPI), specialty, taxonomy or location. From there, use the available filters to narrow the results.
You might look for dentists in a particular state, compare specialists across a market or confirm that a provider record matches the person or organization you are researching. Each result can be opened for a closer look at the details and source context available in QOPE.
Continue working with your results
A useful search does not have to disappear when you close the page. Providers from a filtered result set can be saved to a named list, allowing you to continue the same work later. Inside that list, you can add notes, update a provider's status and set a follow-up date. Shared access can also be enabled when teammates need to work from the same list.
The workspace then shows how many entries sit in each state:
Built for repeat research, not one-off lookups
Instead of repeating the same search or maintaining a separate spreadsheet from the beginning, teams can keep the relevant records and their research notes together. Supported results may also be exported or accessed through the QOPE API when those features are included in the user's plan.
The underlying records come from CMS NPPES. QOPE organizes this public information for easier searching and use, but it is an independent platform and is not affiliated with or endorsed by CMS, NPPES or any government agency.
Provider Summary
Start with a provider's reported Medicare totals
Sometimes the first question is not which individual service was reported, but what the provider's activity looks like overall. The Provider Summaries database gives users a higher-level view of supported public Medicare measures before they move into more detailed Provider Services or Provider Drugs records.
Search by provider, NPI or an available activity category. A summary may include beneficiary measures, utilization totals, costs and other published indicators for a defined reporting period. This makes it easier to identify providers or categories worth examining without beginning with thousands of service- or drug-level rows.
Compare like with like
The measures in a summary are related, but they are not interchangeable. Submitted charges, allowed amounts, Medicare payments, service totals and beneficiary counts answer different questions. A larger submitted charge does not mean Medicare paid that amount, and a smaller beneficiary figure may be affected by privacy-suppression rules.
Reporting period matters as well. Comparisons are most useful when they use the same year, population and methodology. An absent value should not automatically be read as zero activity, particularly when the source applies suppression to protect beneficiary privacy.
Use the summary as a starting point
A market analyst could compare reported activity across a selected provider group. A researcher could identify an unusual utilization pattern and then open the corresponding service records. A business-development team could define a provider cohort for closer investigation. Supported results may be exported or accessed through the QOPE API where available.
The underlying information comes from public CMS Medicare datasets. These are aggregated reporting measures, not individual patient claims, complete clinical histories, real-time activity or automatic quality rankings. QOPE makes the summaries easier to search while preserving the limitations of the original reporting period, population and methodology.
Provider Services
Explore Medicare services by provider
The Provider Services database connects healthcare providers with publicly reported Medicare Part B service activity. It allows users to move beyond a provider's basic identity and examine the types of services associated with that provider in a published reporting period.
Records are organized using the provider's NPI, a Healthcare Common Procedure Coding System (HCPCS) code and place of service. Available fields may include the service description, beneficiary count, number of services, submitted charges, allowed amount and Medicare payment. Search and filtering make it possible to focus on a provider, procedure, specialty, location or combination of relevant fields rather than working through the complete source file.
Understand charges, use and payments
The measures answer different questions. A submitted charge is not the same as the amount Medicare allows or pays, and a service count is not necessarily a count of individual patients. Reporting years are published as separate resources, so comparisons should be made across matching periods and with attention to the source methodology.
This database can support service-line research, provider activity analysis, market comparisons and territory planning. For example, an analyst could review which HCPCS-coded services appear for a provider or compare reported service patterns across a defined group. It provides a useful starting point before deeper analysis, while keeping provider and service identifiers together. Supported records may be exported or accessed through the QOPE API where available.
This focused view can also help teams define a reproducible provider cohort before moving the records into a larger analytical workflow.
The data comes from public CMS Medicare Physician and Other Practitioners resources. It does not contain individual patient claims, represent every payer or provide a provider quality ranking. Suppression and eligibility rules can affect what appears. QOPE organizes the published records for search and analysis without changing their original scope.
Provider Drugs
Examine prescribing activity by provider and drug
The Provider Drugs database brings public Medicare Part D prescribing information into a searchable provider-and-drug view. It helps users examine which drugs are associated with a prescriber in a published period and how the reported activity is distributed across products.
Search by provider NPI, brand name, generic name or other available fields. Records may include claim or fill measures, days supplied, total drug cost and beneficiary counts. Filters can narrow a national file to one provider, one product or a relevant group, making it easier to investigate a question without downloading and preparing the complete source dataset.
Read the measures in context
The rows summarize Medicare Part D activity. They do not represent every prescription written in the United States, and they do not reveal an individual patient's treatment. Privacy suppression and population rules may prevent some activity from appearing. Total drug cost, prescription fills and beneficiary counts are separate measures and should be compared using the same reporting period and methodology.
The database is useful for prescriber research, product utilization analysis, market exploration and identifying patterns that deserve closer review. A user might compare reported activity for a generic and branded product, examine the drug mix associated with a provider or identify providers connected to a selected product in the available data. Supported results can be exported or accessed through the QOPE API when included in the user's plan.
Keeping drug names, provider identifiers and reporting measures together also makes follow-up research easier to document and repeat.
The underlying information comes from public CMS Medicare Part D Prescribers data. A prescribing record does not establish a diagnosis, prove that treatment was appropriate or describe all of a provider's work. QOPE makes the public records easier to search while preserving their reporting-period and source limitations.
Facilities
Build a focused view of healthcare facilities
A facility name alone rarely answers a research question. Users may also need to know what kind of facility it is, where it operates, who owns it and which public certification or capacity details are attached to the record. The Facilities database brings supported CMS facility information into one searchable QOPE view.
Search and filters can narrow records by location, facility type, ownership or another available attribute. Fields may include a facility identifier, name, address, ownership details, bed measures, emergency-service indicators and certification information. Opening a result keeps those details together, making it easier to understand why a facility appeared in the search.
Use concrete questions to narrow the data
A market analyst might identify supported facilities of one type across a state. A business-development team might compare ownership categories in a territory. A researcher could review ownership effective dates before examining how a group of facilities changed over time. Where QOPE supports relationships with other datasets, a facility record may also provide useful context for related organizations, providers or certified health IT.
The resulting list can be exported or accessed through the QOPE API when those features are available, giving teams a defined starting point for mapping, analysis or follow-up verification.
Check dates before relying on a record
Facility information is published and updated on schedules determined by its source; it is not a real-time operating feed. Ownership, certification and service details can change. A certification field also does not guarantee quality or a particular patient outcome, and the supported data does not represent every healthcare facility.
The underlying records come from supported public CMS facility resources, including ownership information. QOPE prepares the records for easier searching but remains independent from CMS. Current operating details should be confirmed with the facility or the latest official source when they affect a decision.
Laboratories
Find CLIA-certified laboratory records
The Laboratories database provides a searchable view of public information associated with laboratories covered by the Clinical Laboratory Improvement Amendments, commonly known as CLIA. It helps users locate laboratory records and understand the certification and organizational details available for each entry.
Search and filter using fields such as the laboratory identifier, laboratory type, location, ownership, accreditation and certificate type. Depending on the source record, users may also see enforcement information or indicators connected to testing capacity. Opening a result keeps the laboratory details and available source context together.
Understand the certification context
CLIA regulates human laboratory testing in the United States, with requirements that vary according to the complexity of the testing performed. Certificate types therefore have specific meanings and should be interpreted using CMS guidance. A listed certificate does not mean that the laboratory performs every kind of test, and certification alone is not a guarantee of the quality of every result.
The database can support laboratory market research, geographic analysis, accreditation review, organization discovery and compliance-oriented research. For example, a user might identify laboratories with a selected certificate type in a region or compare public attributes across laboratory groups. Supported results can be exported or accessed programmatically through QOPE where the user's plan provides those features.
Researchers can preserve the resulting cohort for comparison while keeping the certificate and location fields attached to every selected laboratory.
The underlying information comes from public CMS CLIA resources. Laboratory status, ownership, accreditation and enforcement information can change, so the relevant dates matter. The records should not be treated as a real-time operating directory or as proof that a laboratory currently offers a particular test. QOPE organizes the published information to make research easier but is not affiliated with or endorsed by CMS.
ACO Networks
See how Medicare ACO networks change over time
An Accountable Care Organization is not a fixed list of providers. Participation, program tracks, covered geography and published performance can change from one reporting period to another. The ACO Networks database helps users explore supported Medicare Shared Savings Program records while keeping that time context visible.
Search by organization, geography, program or reporting period. Available fields may include an ACO identifier, program track, participating providers, counties, beneficiary measures, quality measures and shared-savings information. A user could examine which providers appear in a selected year's network file, compare counties associated with different ACOs or review published performance for a defined period.
Keep network and performance records separate
Network files describe participation; performance files report measures calculated under the program's methodology. They answer related but different questions. A provider listed for one year should not automatically be described as a current participant, and membership does not prove that a referral relationship exists. Shared savings also should not be presented as proof that the ACO alone caused a financial or quality outcome.
QOPE keeps the relevant identifiers, dates and source context with the records so researchers can document which public file supported a conclusion.
Where this view is useful
The database can support network mapping, provider-organization research, market analysis and historical program comparisons. A team might define an ACO cohort for one performance year, export the supported results and revisit the same organizations when later data becomes available. API access may also be available under the selected QOPE plan.
The records come from public CMS Medicare Shared Savings Program resources. Participation and performance claims should always include their applicable year or reporting period. QOPE makes the files easier to explore but does not certify current membership, referral activity or causal performance.
Certified Health IT
Search certified health IT products
The Certified Health IT database provides a searchable view of products and modules listed through the Office of the National Coordinator for Health Information Technology certification program. It helps users research certified products, their developers and the public certification details attached to them.
Records may include a CHPL product number, developer, product name, certification body, certification status, inactive or decertification indicators and surveillance information. Search and filters can narrow the catalog by developer, product, status or other available criteria. Opening a record provides the relevant product details and source context without requiring the user to interpret the entire Certified Health IT Product List independently.
Understand what certification means
Certification applies to health IT products or modules tested against defined criteria and approved procedures. It should not be interpreted as a guarantee that every deployment is secure, fully interoperable or appropriate for every organization. Status can also change, so inactive, withdrawn, decertified and current records need to be distinguished using the associated dates and program definitions.
This database can support vendor research, product comparison, EHR-market exploration, procurement preparation and technical due diligence. A user might review products associated with a developer, identify certification status for a specific edition or examine available surveillance records. Supported results may be exported or accessed through the QOPE API when those features are available.
The search results can serve as a documented shortlist before a team verifies technical, contractual and deployment details directly with the relevant developer.
The information comes from the public Certified Health IT Product List and related HealthIT.gov resources. The records describe certification against program criteria, not provider performance or the configuration of a product at a particular site. QOPE organizes the published information for easier searching but is independent from ONC and government certification bodies.
NHSC Sites
Find NHSC sites in a specific area
The NHSC Sites database lets users search public National Health Service Corps records by details such as site name, site type, address, county, phone number and site identifier.
A workforce planner could look for participating sites in one county. A researcher could compare the kinds of facilities represented across several rural areas. Someone exploring a possible placement could begin with a focused set of locations rather than searching the complete national file. Each result keeps the available site details together and provides a path back to the public source.
Know what the listing actually means
NHSC works within a federal program designed to support healthcare delivery in shortage areas. Sites connected with the program may host clinicians who are fulfilling service commitments, but the listing has limits. It does not mean that every underserved facility participates in NHSC. It also does not confirm that a listed site currently has a vacancy, accepts every type of participant or remains eligible for a particular program action.
Those details can change, so the record's update date matters. Treat the QOPE result as a research starting point, then confirm employment, eligibility and current participation through the site or official NHSC resources.
Use the results in a wider access study
A focused list of NHSC sites can add useful context to workforce, safety-net and geographic access research. Users can compare site locations with supported shortage-area, health-center or provider records, while keeping the different source dates visible. Where available under the selected plan, results can also be exported or accessed through the QOPE API for further analysis.
The underlying records come from public HRSA National Health Service Corps resources. QOPE makes those records easier to search, but it does not administer NHSC or verify current vacancies and eligibility.
Health Centers
Separate health center organizations from service sites
A health center organization and the places where it delivers care are related, but they are not the same record. The Health Centers database brings supported HRSA awardee and service-site information into QOPE while preserving that distinction.
Users can search available fields such as site name, location, site type, operating status, operator, hours and NPI. A community-health researcher might find service sites in a county. A market analyst could compare site settings across a region. Someone reviewing an organization could identify the delivery locations associated with it, then open individual records for the available details and source context.
Understand what the record does not promise
A listed service site should not be assumed to offer every possible service, and not every safety-net provider is represented as a federally supported health center. Operating hours, status and organizational relationships can also change between published updates. Before using a record for outreach, travel or an operational decision, confirm the current details through the site or official HRSA resources.
The distinction between an awardee organization and a service-delivery location is especially important when counting records. Treating both as interchangeable can overstate the number of independent organizations or obscure how one organization operates through several locations.
Add context to access and market research
A focused site list can support safety-net analysis, community mapping, territory planning and service-access research. Users can compare the records with supported shortage-area, underserved-area or provider data while preserving the source dates and geographic levels. Export and QOPE API options may be available under the selected plan.
The information comes from public HRSA health-center awardee and service-site resources. HRSA publishes the two record types separately and reports a regular refresh cycle for site data. QOPE makes the records easier to search but does not verify real-time operations or administer the health-center program.
EHR Linkage
Connect hospitals with certified EHR products
The EHR Linkage database brings together supported public hospital reporting information and certified health IT product records. It is designed to help users explore which EHR developer or product has been linked to a facility in the available source data, without manually reconciling hospital identifiers and certification records.
Fields may include a facility identifier, Promoting Interoperability reporting criteria, EHR developer, EHR product, Certified EHR Technology or CHPL identifier and relevant reporting dates. Search and filters can narrow the records by hospital, developer, product or reporting period. Opening a result provides the available linkage details and the context needed to understand where the connection came from.
Interpret a linkage carefully
A linked record describes a relationship reported or derived for a particular period. It does not prove that the product remains installed today, that it is the facility's only health IT system or that every module is configured in the same way. An unmatched facility should not be treated as evidence that the organization has no EHR. Certification also describes product conformance with defined criteria, not the quality or performance of the hospital using it.
The database can support health IT market research, vendor analysis, hospital technology mapping and integration planning. A user might examine facilities associated with a developer, compare reported products across a region or identify records that require further verification. Supported results may be exported or accessed through the QOPE API when available under the selected plan.
The underlying information comes from supported HealthIT.gov, CHPL and hospital reporting resources. Reporting dates and matching methodology matter, particularly when attempting to estimate adoption or market share. QOPE organizes the available public records for research but does not certify a current installation or complete vendor relationship.
Shortage Areas
Explore designated healthcare shortage areas
The Shortage Areas database organizes public Health Professional Shortage Area records published by HRSA. HPSA designations identify areas, populations or facilities with a documented shortage of primary care, dental health or mental health professionals under federal criteria.
Search and filter by designation type, geography, discipline, rural status or other available attributes. Records may include an HPSA score, population measures, provider-shortage estimates, population-to-provider ratios and designation dates. Opening a result helps users review the available measures together rather than moving between separate public files and lookup tools.
Understand what a designation shows
An HPSA designation does not mean that no healthcare professionals are present. It reflects a shortage measured under a defined methodology, and the score is used within that program rather than as a direct rating of healthcare quality. Designations can also change, be updated or be withdrawn, making the effective and update dates important.
The database can support access-to-care research, workforce planning, geographic analysis, site selection and public-program research. A user might compare primary care and dental designations across counties, identify high-scoring areas for closer study or examine whether a specific location falls within a supported designation. Structured results may be exported or accessed through the QOPE API where available.
Combining the designation fields with other public workforce or facility data can add context, provided the different dates and geographic levels remain visible.
The underlying information comes from public HRSA HPSA resources. Geographic, population and facility designations represent different scopes and should not be combined without checking their definitions. The records are not permanent declarations and should not be treated as real-time descriptions of local provider availability. QOPE makes the public data easier to search but is independent from HRSA and does not issue shortage designations.
Underserved Areas
Search medically underserved areas and populations
The Underserved Areas database organizes public HRSA records for Medically Underserved Areas and Medically Underserved Populations, commonly shortened to MUA and MUP. These designations identify geographic areas or population groups that meet federal measures of medical underservice.
Available fields may include the designation type, Index of Medical Underservice score, poverty measure, age measure, infant-mortality measure, location and designation dates. Search and filtering can narrow records by geography, designation type or other supported criteria. This provides a practical way to examine a community or compare designated areas without preparing the complete source file first.
Read the measures in context
The Index of Medical Underservice combines several factors used for the MUA and MUP program. It is not a hospital quality score, and a designation does not mean that no care is available in the area. MUA and MUP also refer to different scopes: one may describe a geographic area while the other focuses on a population group with barriers to care. Designations and their status can change over time.
The database can support community-health analysis, access research, workforce planning, grant preparation and geographic market studies. A user might determine whether an address is associated with a designation, compare underserved areas within a state or combine the records with other public data for a broader view of access conditions. Supported results may be exported or accessed through the QOPE API when available.
The selected records can then form a documented geographic cohort for comparison with facilities, providers or other access indicators.
The records come from public HRSA MUA and MUP resources. Users should check designation type, methodology and date before treating a record as current. QOPE organizes the public information for easier research but does not create the designations or guarantee current program eligibility.
Clinical Trials
Find registered studies without losing trial context
Clinical-trial searches often begin with a straightforward question—such as which studies are active in a therapeutic area—but the answer depends on several pieces of study information. The Clinical Trials database brings supported ClinicalTrials.gov records into QOPE so users can search registered interventional and observational studies through a consistent interface.
Results can be narrowed using available fields such as study status, phase, allocation, masking and sponsor. The National Clinical Trial identifier, or NCT number, anchors each study and gives users a reliable way to return to its complete official record. This is more dependable than relying on a study title, which may be similar to other registrations.
Understand who is connected to a study
ClinicalTrials.gov records can name investigators, sponsors, responsible parties and study contacts. These roles are different and should not be collapsed into a single “study owner.” Investigator information may include separate name, affiliation and role fields, and not every registration identifies a principal investigator. A matching name also does not prove that two study records refer to the same person.
Keeping these distinctions visible is important when researching investigator networks, sponsor activity or study responsibility. QOPE does not create investigator identifiers when they are absent from the source.
Move from discovery to closer review
The database can help users build a focused study list, compare design characteristics or examine sponsor activity across a selected topic. For example, a researcher could narrow studies by phase and status, then open the relevant records to review their reported design and responsible organizations. Supported results may be exported or accessed through the QOPE API when available.
The records come from NIH ClinicalTrials.gov and reflect submitted registration information. Registration does not establish that an intervention is safe, effective or FDA-approved. Study details and status can change, so important conclusions should be checked against the current official record.
FDA Approvals
Follow drug applications and FDA decisions
The FDA Approvals database organizes public Drugs@FDA application, product and submission records into a searchable view. It helps users examine the regulatory history connected to an approved drug application without manually joining multiple FDA tables.
Available fields may include the application number, product number, submission number, submission type, action date, status, sponsor, dosage form, route and strength. Search and filters can narrow the records by product, applicant, application type, date or other supported criteria. Opening a result provides the available application and submission context attached to that regulatory record.
Keep applications, products and submissions separate
An FDA application can contain multiple products and a history of submissions. Those records answer different questions and should not be treated as interchangeable. A submission status or action date belongs to a specific submission, while product details describe a particular dosage form, route or strength under the application. Not every submission listed in a regulatory history is itself an approval.
The database can support regulatory research, product-history analysis, sponsor tracking and competitive landscape work. A user might trace changes associated with an application, compare approved strengths or review regulatory activity within a time period. Supported results may be exported or accessed through the QOPE API when included in the user's plan.
Maintaining these identifiers together helps users return to the correct application history when a product name alone would be ambiguous.
The underlying information comes from the FDA's Drugs@FDA resources. An approval record does not prove that one product is clinically superior to another, and marketing or regulatory status can change. Dates, submission types and record relationships should be checked before drawing conclusions. QOPE organizes the public data for easier use but is independent from and not endorsed by the FDA.
Orange Book
Explore approved small-molecule drug products
The Orange Book database organizes public FDA records for approved drug products evaluated under the relevant application pathways. It brings product, therapeutic-equivalence, reference-drug, patent and exclusivity information into a searchable view.
Search and filter by ingredient, application number, product number, dosage form, route, strength or other available fields. Records may include therapeutic-equivalence codes, reference listed drug status, reference-standard status, approval dates and associated patent or exclusivity entries. Opening a result helps users examine these related regulatory details without moving through separate Orange Book files.
Understand the regulatory distinctions
Several fields that look similar serve different purposes. A Reference Listed Drug and a reference standard are distinct FDA designations. Therapeutic-equivalence codes carry defined regulatory meanings, but they do not guarantee identical outcomes for every patient. Patent and exclusivity records also describe different forms of protection, and their presence should not be interpreted as legal advice or as a complete freedom-to-operate analysis.
The database can support generic-drug research, regulatory intelligence, product comparison and loss-of-exclusivity investigation. A user might compare products sharing an ingredient and strength, identify reference-product designations or review listed patent and exclusivity dates. Supported records may be exported or accessed through the QOPE API where available.
The structured view can also help teams build a reproducible product cohort before checking the latest official records or beginning a more detailed regulatory review.
The information comes from the FDA publication commonly known as the Orange Book. Its scope does not include every marketed drug, and marketing, patent and exclusivity circumstances may change. Users should verify current records and consult qualified professionals for regulatory or legal decisions. QOPE organizes the public information for research but is independent from and not endorsed by the FDA.
Purple Book
Research licensed biological products
The Purple Book database organizes public FDA information about licensed biological products, including reference products, biosimilars and products determined to be interchangeable. It provides a searchable view of regulatory relationships that can otherwise require moving across multiple FDA resources.
Available fields may include the biologics license application number, license number, product and proper names, applicant, submission type, approval date, reference product, biosimilar status, interchangeability, exclusivity and listed patent information. Search and filters can narrow results by product, applicant, regulatory relationship or date. Opening a record shows the available details and source context together.
Separate biosimilarity from interchangeability
Biosimilarity and interchangeability are different FDA determinations. A biosimilar product should not automatically be described as interchangeable, and each relationship must be read from the applicable regulatory record. Entries are also tied to submissions and dates, so a listing by itself does not prove current market availability. Patent information is useful for research but should not be treated as legal advice.
The database can support biologics landscape research, biosimilar competition analysis, regulatory tracking and product comparison. A user might identify products related to a reference biologic, compare approval dates or examine which records carry an interchangeability determination. Supported results may be exported or accessed through the QOPE API when available under the selected plan.
Preserving the application, submission and reference-product relationships makes later verification more reliable than working from product names alone.
The underlying information comes from the FDA Purple Book and related public regulatory records. Product status, exclusivity and patent information can change and should be checked as of the relevant date. QOPE organizes the public records for easier analysis but does not provide legal advice, confirm commercial availability or replace the official FDA source.
NDC Directory
Search listed drug products and packages
The NDC Directory database organizes public FDA drug-listing information using National Drug Code identifiers. It helps users research marketed product and package records, labelers, ingredients and presentation details without working directly from the complete directory files.
Search and filter by product NDC, package NDC, proprietary name, nonproprietary name, labeler, active ingredient, dosage form, route or marketing category. Records may also include relevant marketing start and end dates. Opening a result provides a closer view of the product and package information associated with the submitted listing.
Understand the code structure
An NDC is built from labeler, product and package code segments. Product NDC and package NDC values therefore represent different combinations and should not be used interchangeably. The information in the directory is submitted by labelers. Assignment of an NDC or appearance in the directory does not mean that the FDA approved the product, independently verified every submitted detail or confirmed that the product is currently marketed.
The database can support product matching, labeler research, portfolio analysis and data normalization. A user might find package configurations connected to a product, compare dosage forms or connect an NDC with other public drug records. Supported results may be exported or accessed through the QOPE API where available.
A structured result set can also provide the identifier foundation needed before matching products with labels, pricing or rebate-program records.
The underlying records come from the FDA National Drug Code Directory. Marketing dates, listing status and product details may change, and some products listed under an NDC are not approved drugs. Users should check the marketing category and applicable regulatory source before drawing conclusions. QOPE organizes the public listings for easier search but is independent from and not endorsed by the FDA.
FDA Labels
Find the right drug label—and the right revision
Drug labels are not static documents. Warnings, indications, adverse reactions and other sections can change as labeling is revised. The FDA Labels database helps users search supported public Structured Product Labeling records while keeping document identifiers and revision information attached to the result.
Search by brand name, generic name, active ingredient, manufacturer, route or another available field. Records may include the label set identifier, document identifier, indications, contraindications, warnings, adverse reactions and revision date. Opening a result allows users to review the available sections and distinguish similarly named products or different versions of a label.
Use identifiers, not names alone
A product name may appear in several records, and the newest-looking search result is not necessarily the correct document for every question. Set identifiers, document identifiers and revision dates help establish which label is being reviewed. Harmonized openFDA fields can make products easier to connect across datasets, but those fields are not present in every record.
A missing harmonized field should not be interpreted as proof that information is missing from the underlying label. Users may need to review the full document and its source version.
Where this view helps
The database can support label comparison, regulatory research, product intelligence and document discovery. A researcher might compare revisions, locate labels connected to an ingredient or review warning sections across a defined product group. Supported results can be exported or accessed through the QOPE API when available.
The information comes from public FDA Structured Product Labeling and openFDA resources. Label content does not replace current official product information, medical advice or prescribing judgment, and openFDA does not independently verify every submission. QOPE makes the public documents easier to find but remains independent from the FDA.
Substances
Identify ingredients and chemical substances
The Substances database organizes public FDA substance records used to describe ingredients and other defined materials consistently. It helps users move between names, identifiers and classifications that may refer to the same underlying substance.
Search and filter by Unique Ingredient Identifier, preferred name, substance class, status or an available external identifier. Records may include a UNII, CAS number, EC number, RxCUI, National Cancer Institute code or International Nonproprietary Name. Opening a result brings these identifiers and mappings together so users can examine how a substance is represented across supported terminology systems.
Distinguish substances from products
A substance record is not the same thing as a finished drug product. A UNII identifies a defined substance, but it does not mean that the substance has been approved for a particular clinical use. Names and external identifiers may also have multiple mappings, historical forms or context-specific relationships. Users should not assume that every identifier is one-to-one or interchangeable in every system.
The database can support ingredient normalization, terminology mapping, product-data integration and regulatory research. A user might resolve alternate names, find identifiers connected to an ingredient or use a UNII to connect substance information with supported drug and labeling records. Structured results may be exported or accessed through the QOPE API where available.
This makes the database especially useful as a reference layer when several product or research datasets use different names for related substances.
The underlying information comes from public FDA substance resources and connected terminology references. Substance records support identification and linking; they do not establish clinical use, safety, efficacy or approval. Names, status and external mappings can be revised over time. QOPE organizes the public records for easier discovery but does not replace the official terminology authorities or independently certify every mapping.
Drug Manufacturers
Research registered drug establishments
The Drug Manufacturers database organizes public FDA establishment-registration information for companies and sites involved in drug-related operations. It helps users find registered establishments, examine their reported business activities and distinguish a physical establishment from other company or product identities.
Available fields may include the FDA Establishment Identifier, firm name, address, country, reported business operations and registration-expiration date. Search and filters can narrow records by company, geography, operation type or other supported attributes. Opening a result provides the public establishment details and available source context in one place.
Understand what registration represents
An FEI identifies an establishment. It is not the same as an NDC labeler code, and a registered establishment is not necessarily the manufacturer named on every product connected to a company. Establishments may report manufacturing, repackaging, relabeling, analysis or other operations. Registration does not mean that the FDA approved the establishment's products, guarantee compliance or confirm that every listed operation remains current.
The database can support manufacturer landscape research, supply-chain investigation, establishment matching and portfolio analysis. A user might identify registered operations associated with a firm, compare geographic footprints or connect an establishment record with supported drug-product and recall information. Results may be exported or accessed through the QOPE API when included in the user's plan.
The selected establishment records can provide a documented starting point before users verify present operations, corporate relationships or regulatory standing from current sources.
The underlying information comes from public FDA drug-establishment registration resources. Registration and expiration dates matter because status and reported operations can change. The word “manufacturer” is used as a convenient catalog label, but not every establishment performs manufacturing. QOPE organizes the public records for research and is independent from and not endorsed by the FDA.
Adverse Events
Explore reported drug adverse events
The Adverse Events database organizes public post-market safety reports involving drugs and therapeutic products. It helps users search reported reactions, outcomes and product information while keeping the limitations of spontaneous reporting visible.
Records may include a case identifier, report identifier, report type, report source, drug, active ingredient, route, reaction, outcome, patient demographics, country and received date. Search and filters can narrow reports by product, reaction, outcome, geography, time period or other supported fields. Opening a result provides the available report details and source context together.
Read reports without assuming causation
An adverse-event report describes a reported experience; it does not prove that a product caused the event. Reports may be incomplete, duplicated or influenced by reporting patterns. The number of reports cannot be used as an incidence rate because the total number of exposed patients and the likelihood of reporting are generally unknown. Likewise, an absence of reports does not establish that a product is safe.
The database can support pharmacovigilance research, signal exploration, product monitoring and the identification of questions that deserve deeper review. A user might examine reactions reported with a selected product, compare report sources or review how outcomes are distributed over time. Supported results may be exported or accessed through the QOPE API where available.
Results are best treated as leads for investigation, not conclusions, with duplicate handling, reporting dates and product identification reviewed before comparisons are made.
The information comes from public FDA adverse-event reporting resources, including FAERS and the agency's transition toward AEMS. Reporting systems and field availability can change, so dates and source definitions matter. QOPE organizes the public reports for research but does not determine causality, calculate clinical risk or replace FDA safety communications and professional medical judgment.
Drug Recalls
Search public drug recall records
The Drug Recalls database organizes FDA enforcement reports related to recalled drug products. It allows users to research recall actions, the companies involved and the public reasons provided for those actions without manually working through the full enforcement-report files.
Available fields may include the recall number, event identifier, status, classification, recalling firm, product description, reason for recall, distribution pattern, initiation date, report date and termination date. Search and filters can narrow records by company, product, classification, status, location or time period. Opening a result shows the available details attached to that enforcement record.
Follow classification and status
FDA recall classifications and status terms have defined meanings. A Class I, II or III classification reflects the agency's assessment of the potential health consequences under its recall framework; it should not be reduced to a simple product-quality score. A public enforcement report also does not prove that every distributed unit caused harm. Status and termination dates matter, and historical records should not automatically be described as active recalls.
The database can support safety monitoring, manufacturer research, product-history review and supply-chain investigation. A user might find recalls connected to a firm, examine stated reasons across a product category or track reported activity within a period. Supported results may be exported or accessed through the QOPE API where available.
Keeping event and recall identifiers together also helps distinguish separate actions involving products or firms with similar names.
The underlying information comes from public FDA enforcement-report resources. Recall information may develop over time, and source status conventions should be reviewed before drawing current conclusions. The absence of a matching record does not prove that a product has never been recalled. QOPE organizes the public data but does not issue recalls or replace official FDA notices.
Drug Shortages
Monitor reported drug shortages
The Drug Shortages database organizes public FDA information about national drug supply disruptions. It helps users review shortage status, company-level availability and reported reasons without navigating separate product updates individually.
Records may include a generic name, brand name, company, shortage status, presentation, availability information, reason, initial posting date and update date. Search and filters can narrow the results by product, company, therapeutic category, status or time period. Opening a record provides the available shortage details and the context attached to the latest published update.
Treat availability as time-sensitive
Shortage information can change quickly. A listed shortage does not necessarily mean that no supply exists anywhere in the country, and availability may differ among companies, presentations and locations. A resolved status does not guarantee that every pharmacy or facility has immediate stock. Dates are therefore essential whenever shortage or availability information is displayed or compared.
The database can support supply monitoring, product research, market analysis and operational planning. A user might identify products with an active reported shortage, compare company-level availability or examine reasons associated with shortages over time. Structured results may be exported or accessed through the QOPE API when those features are available under the selected plan.
For recurring monitoring, users can return to a defined product group and compare later updates without rebuilding the same search. This is particularly useful when different presentations or companies report different availability conditions for the same generic product.
The underlying information comes from public FDA Drug Shortages resources. FDA uses defined categories for shortage reasons and updates records as conditions change. QOPE organizes the published information for easier search but does not maintain inventory, predict local availability or replace confirmation from manufacturers, distributors, pharmacies or the official FDA source.
Drug Pricing
Compare public pharmacy acquisition-cost data
The Drug Pricing database organizes National Average Drug Acquisition Cost information published by CMS. NADAC provides a public reference for estimating what retail community pharmacies pay to acquire covered outpatient drugs, expressed as a per-unit amount.
Search and filter by NDC, drug name, classification, pricing unit, over-the-counter indicator, pharmacy type, explanation code, effective date or as-of date. This makes it possible to focus on a product or group of products and compare published per-unit values across relevant periods. Opening a record provides the pricing measure and the fields needed to interpret it.
Understand what NADAC is—and is not
NADAC is an acquisition-cost reference based on a defined CMS methodology. It is not the price a patient pays at the pharmacy, a manufacturer's list price or a guarantee of the acquisition cost experienced by every pharmacy. Pricing units and effective dates must match before values are compared. CMS publishes updates regularly, and each historical catalog resource covers a defined calendar period.
The database can support reimbursement research, pricing analysis, product comparison and historical trend work. A user might review how a per-unit value changed, compare generic and brand classifications or connect an NDC with supported product records. Results may be exported or accessed through the QOPE API where available.
Keeping the NDC, unit and date together makes a comparison easier to audit and reduces the risk of placing unlike pricing records side by side.
The underlying information comes from public CMS NADAC resources. Prices are time-sensitive and should always be presented with an effective or as-of date. NADAC alone does not describe rebates, dispensing fees, patient cost sharing or every component of a transaction. QOPE organizes the public reference data for research but does not calculate actual pharmacy or patient prices.
Medicaid Rebate Drugs
Explore products reported under the Medicaid Drug Rebate Program
The Medicaid Rebate Drugs database organizes public product records associated with the Medicaid Drug Rebate Program. It helps users research labelers, product characteristics and reporting status across defined quarters without preparing the complete program files independently.
Available fields may include NDC, product name, labeler, drug category, drug type, unit type, FDA application number, therapeutic-equivalence information, covered outpatient drug status, clotting-factor indicator, pediatric indicator, line-extension information, quarter and year. Search and filters can narrow the records by product, labeler, category, status or reporting period. Opening a result keeps the product attributes and time context together.
Keep program status tied to its period
Covered outpatient drug status has a specific meaning within the Medicaid Drug Rebate Program. A product's appearance in the data does not guarantee coverage by every state Medicaid program, and a rebate amount cannot be calculated from the listing alone. Quarterly fields are essential because product status and reported characteristics can change over time.
The database can support Medicaid market research, labeler analysis, product-history review and program-data integration. A user might compare products reported by a labeler, examine status changes by quarter or connect an NDC with related pricing and regulatory records. Supported results may be exported or accessed through the QOPE API when available.
The quarterly structure also allows teams to preserve a historical product cohort and document exactly which reporting period supported a later analysis or business question.
The underlying information comes from public CMS Medicaid Drug Rebate Program resources. Users should preserve the quarter and year whenever interpreting status. The records do not describe state-specific formulary coverage, patient eligibility or the confidential components required to determine rebates. QOPE organizes the published product information but does not administer Medicaid or the rebate program.
Genetic Variants
Search submitted genetic-variant interpretations
The Genetic Variants database organizes supported public ClinVar records describing genetic variants and submitted interpretations of their clinical significance. It helps users search variant, gene and condition information while preserving the review context attached to each record.
Available fields may include the ClinVar variation identifier, gene, variant type, clinical significance, review status, condition, origin, genome assembly, coordinates, dbSNP identifier and submitter count. Search and filters can narrow records by gene, condition, classification, review status or genomic location. Opening a result brings the available identifiers and interpretation details together.
Keep interpretation and evidence visible
ClinVar aggregates submissions from laboratories, researchers and other contributors. Different submitters may provide conflicting interpretations, and classifications can change as evidence develops. Review status communicates the level and type of review associated with a record; it should not be ignored or treated as equivalent across every entry. Not every submission has expert-panel review.
The database can support variant research, terminology mapping, evidence review and the connection of genomic identifiers across public resources. A user might locate interpretations connected to a gene, compare review status across variants or identify records with conflicting classifications for closer study. Supported results may be exported or accessed through the QOPE API where available.
Keeping the variation identifier, assembly and review status together is particularly important when records are compared or connected with other genomic resources. It provides a clearer path back to the precise ClinVar entry.
The information comes from public NIH ClinVar resources. ClinVar does not provide a medical diagnosis, and a database classification is not permanent. Results should be interpreted by qualified professionals together with current evidence, patient context and appropriate clinical guidance. QOPE organizes the public records for easier research but does not independently adjudicate variant significance.
MeSH Terms
Navigate biomedical concepts and vocabulary
The MeSH Terms database organizes the National Library of Medicine's Medical Subject Headings vocabulary into a searchable QOPE view. MeSH provides standardized concepts used to index, organize and discover biomedical literature and related information.
Search and filter by MeSH unique identifier, preferred name, record type, tree number, synonym or other available mappings. Records may also include scope notes, pharmacological actions, registry numbers, frequency information and relevant dates. Opening a result helps users see the preferred concept, alternative terms and hierarchical positions together.
Understand a concept's place in the hierarchy
MeSH is a controlled vocabulary rather than a clinical diagnosis system. A descriptor can appear in more than one branch of the hierarchy because the same concept may be relevant in several contexts. Its tree position does not establish clinical importance, and a synonym should not automatically be treated as interchangeable in every search, dataset or professional setting. Vocabulary records are revised as terminology develops.
The database can support literature-search preparation, terminology normalization, concept mapping and data integration. A user might identify the preferred term for a concept, explore broader and narrower categories or connect biomedical records that use different names. Supported results may be exported or accessed through the QOPE API when available under the user's plan.
The structured vocabulary can also provide a shared reference layer when separate datasets or teams use different wording for the same biomedical concept.
The underlying information comes from the NIH National Library of Medicine MeSH vocabulary. Identifiers, hierarchy positions, synonyms and scope notes should be interpreted according to the applicable vocabulary release. QOPE makes the public terminology easier to explore but does not replace official MeSH documentation or determine how a term should be used in clinical care.