Katie Alison Lapsa, PA

  • Tacoma, WA
  • Physician assistant
NPI1659564656
Hospital affiliations
1
Medical groups
2
State license
1
Year NPI issued
2007
Practice address
1717 South J Street, Tacoma, WA 98405
Practice phone
Call (253) 627-4101
Professional email
Get professional email
Personal email
Get personal email
Mobile number
Get mobile number
Social profiles

Primary practice

St. Joseph Medical Center

Hospital · Tacoma, Washington

See all 3 affiliations

Find Katie Lapsa'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

Katie Alison Lapsa is a physician assistant in Tacoma, Washington

Katie Lapsa practices at St. Joseph Medical Center in Tacoma, Washington, part of CommonSpirit Health.

Katie Lapsa's NPI, 1659564656, was assigned on August 22, 2007. Katie Lapsa holds Washington license PA 60091446.

NPI and contact details
NPI enumeration date
August 22, 2007
NPI status
Active
Practice phone
(253) 627-4101
Professional email
Get email
Personal email
Get email
Mobile number
Get number
Sex
Female

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

Katie Alison Lapsa practices at St. Joseph Medical Center in Tacoma, Washington

Katie Lapsa's primary practice is St. Joseph Medical Center, at 1717 South J Street, Tacoma, WA 98405 in Pierce County. The practice phone is (253) 627-4101.

Source: Dmand AI Affiliation Data

Katie Alison Lapsa is affiliated with 1 site of care and 2 medical groups

Katie Lapsa's primary practice is St. Joseph Medical Center in Tacoma, Washington, part of CommonSpirit Health. The medical group on file is Washington Permanente Medical Group, P.C. Dmand AI also links Katie Lapsa to 1 more medical group, named with a free account.

See all 3 affiliations for Katie Lapsa

Sources: Dmand AI Affiliation Data; and Dmand AI Org Hierarchy Data

Dmand AI tracks the EHR system at Katie Alison Lapsa's practice

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

EHR by site
SiteEHR vendor and product
St. Joseph Medical CenterAvailable with a free account
+1 medical groupAvailable with a free account

Source: Dmand AI Technology Install Data

For health IT teams

See the EHR and IT leaders at every hospital where Katie Lapsa practices

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

Katie Alison Lapsa is one of 3,005 physician assistants in Washington

Physician assistant is Katie Lapsa's primary specialty in the NPI Registry, under taxonomy code 363A00000X. Katie Lapsa is licensed in Washington.

Specialties and state licenses

  • Physician assistant, WashingtonPrimaryLicense PA 60091446 · taxonomy 363A00000X

Physician assistants near Katie Lapsa

Counts of physician assistants 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

Katie Alison Lapsa's patients have a median age of 43

Across all payers, Dmand AI patient panel data puts Katie Lapsa's median patient age at 43, with 25% women.

Katie Lapsa's patients across all payers

Dmand AI patient panel data covers Medicare, Medicaid and commercial patients.

Patient panel by age, all payers

Median age 43

Patient panel by sex, all payers

  • Women25%
  • Men75%

Source: Dmand AI Patient Panel Data

Sources for Katie Alison Lapsa'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 phoneDmand AI Affiliation Data
Primary practice, affiliations and health systemDmand AI Affiliation DataDmand AI Org Hierarchy Data
Medicare patients and the all-payer patient panelDmand AI Patient Panel 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 Katie Alison Lapsa

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

What is Katie Alison Lapsa's NPI number?

Katie Alison Lapsa's NPI number is 1659564656. It was assigned on August 22, 2007, and it is active in the NPI Registry.

What does Katie Alison Lapsa specialize in?

Katie Alison Lapsa is a physician assistant in Tacoma, Washington. The primary specialty in the NPI Registry is Physician Assistant (taxonomy code 363A00000X).

Where does Katie Alison Lapsa practice?

Katie Lapsa practices at 1717 South J Street, Tacoma, WA 98405. Katie Lapsa's primary practice is St. Joseph Medical Center in Tacoma, Washington, part of CommonSpirit Health. Dmand AI also links Katie Lapsa to 1 medical group.

What is Katie Alison Lapsa's office phone number?

The practice phone on file for Katie Lapsa is (253) 627-4101.

What is Katie Alison Lapsa's medical license number?

Katie Lapsa holds Washington license PA 60091446.

Which hospitals is Katie Alison Lapsa affiliated with?

Katie Lapsa practices at St. Joseph Medical Center in Tacoma, Washington.

What medical group is Katie Alison Lapsa part of?

Katie Lapsa is linked to Washington Permanente Medical Group, P.C. Dmand AI links Katie Lapsa to 1 more medical group.

How long has Katie Alison Lapsa been practicing?

Katie Lapsa's NPI was assigned in 2007.

Selling to physician assistant practices?

See physician assistants in Washington 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)