Dr. May Loo, MD

  • San Jose, CA
  • Pediatrician
NPI1356400188
Publications
1
State license
1
Year NPI issued
2006
Practice address
751 S Bascom Ave, San Jose, CA 95128-2604
Practice phone
Call (408) 793-6788
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Find Dr. Loo's professional email, personal email and mobile number

Dmand AI checks each channel through healthcare-specific waterfall enrichment. See what is on file with a free account, with practice phones, licenses and affiliations.

View contacts for free

Dr. May Loo is a pediatrician in San Jose, California

Dr. Loo practices in San Jose, California.

Dr. Loo's NPI, 1356400188, was assigned on December 7, 2006. Dr. Loo graduated from UCSF School of Medicine in 1973. Dr. Loo's California license number on file is A26011.

NPI and contact details
NPI enumeration date
December 7, 2006
NPI status
Active
Practice phone
(408) 793-6788
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Medical school graduation
1973

Sources: NPPES NPI Registry (CMS); and Dmand AI Professional Profile Data

Dr. May Loo's practice address is in San Jose, California

Dr. Loo's practice address in the NPI Registry is 751 S Bascom Ave, San Jose, CA 95128-2604. The practice phone is (408) 793-6788.

  • NPI Registry address
    751 S Bascom Ave, San Jose, CA 95128-2604Phone(408) 793-6788

Sources: NPPES NPI Registry (CMS); and Dmand AI Practice Data

Dmand AI tracks the EHR system at Dr. May Loo's practice

Dmand AI tracks the electronic health record (EHR) system at each site where Dr. Loo practices. Vendor and product names are available with a free account.

EHR by site
SiteEHR vendor and product
Dr. Loo's practiceAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every site where Dr. Loo practices

Dmand AI maps EHR vendors, IT decision makers and buying committees across each health system and 6.2K+ hospitals, with verified contacts in the same login.

Dr. May Loo is one of 8,236 pediatricians in California

Pediatrics is Dr. Loo's primary specialty in the NPI Registry, under taxonomy code 208000000X. Dr. Loo is board certified in pediatrics by the American Board of Pediatrics. Dr. Loo has a license on file in California.

Specialties and state licenses

  • Pediatrics, CaliforniaPrimaryLicense A26011 · 1974 to 2016 · taxonomy 208000000X

Pediatricians near Dr. Loo

Counts of pediatricians with a Dmand AI profile, by place and practice. Each opens the list.

Sources: NPPES NPI Registry (CMS); Dmand AI Professional Profile Data; and Dmand AI Peer Benchmarks

Dr. May Loo has 1 publication on record

Dmand AI links 1 paper to Dr. Loo in 2025. Dr. Loo's most frequent co-authors are Brenda Golianu, MD and James Junning Xie, MD.

Papers1

Dr. Loo's most frequent co-authors

Recent publications by Dr. Loo

See all 1 publications and co-authors

See who Dr. Loo researches with

Physician Network Discovery turns co-authorship, shared hospitals and shared groups into a map of who Dr. Loo works with, so you can find a warm path to the right pediatricians.

How network discovery works

Sources: PubMed (National Library of Medicine); and Dmand AI Research Linkage

Dr. May Loo graduated from UCSF School of Medicine

Dr. Loo graduated from UCSF School of Medicine in 1973.

  1. Medical schoolUCSF School of Medicine
  2. Board certified in pediatricsAmerican Board of Pediatrics

Source: Dmand AI Professional Profile Data

Sources for Dr. May Loo's profile data

Sources for the data on this page
Data on this pageSource
NPI, name, sex, specialty and licensesNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Professional Profile Data
Practice locations and phoneNPPES NPI Registry (CMS) (opens in a new tab)Dmand AI Practice Data
Publications, topics and co-authorsPubMed (National Library of Medicine) (opens in a new tab)Dmand AI Research Linkage
Training, board certification and membershipsDmand AI Professional Profile Data
EHR at each practice siteDmand AI Technology Install Data
Similar physiciansDmand AI Affiliation Data

Data last refreshed October 2026Report an inaccuracyRemove my information

FAQ

Frequently asked questions about Dr. May Loo

Spotted something out of date? Email hello@dmand.ai and we will check the record. Contact details live in the free trial.

What is Dr. May Loo's NPI number?

Dr. May Loo's NPI number is 1356400188. It was assigned on December 7, 2006, and it is active in the NPI Registry.

What kind of doctor is Dr. May Loo?

Dr. May Loo is a pediatrician in San Jose, California. The primary specialty in the NPI Registry is Pediatrics Physician (taxonomy code 208000000X).

Where does Dr. May Loo practice?

Dr. Loo practices at 751 S Bascom Ave, San Jose, CA 95128-2604.

What is Dr. May Loo's office phone number?

The practice phone on file for Dr. Loo is (408) 793-6788.

What is Dr. May Loo's medical license number?

Dr. Loo's California license number on file is A26011.

Is Dr. May Loo board certified?

Yes. Dr. Loo is board certified in pediatrics by the American Board of Pediatrics.

Where did Dr. May Loo go to medical school?

Dr. Loo graduated from UCSF School of Medicine in 1973.

How long has Dr. May Loo been practicing?

Dr. Loo graduated from medical school in 1973, 53 years ago.

Does Dr. May Loo do research?

Dmand AI links 1 publication to Dr. Loo.

Who does Dr. May Loo publish with?

Dr. Loo's most frequent co-authors are Brenda Golianu, MD (1 shared paper) and James Junning Xie, MD (1 shared paper).

Selling to pediatrics practices?

See pediatricians in California by site of care and group

Find the practices, groups and hospitals they work with, and the right people to contact at each.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)