NPI | Name | Type | Address |
---|---|---|---|
Cittlaly Zepeda |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Paula Stewart |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Henry Merring |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Carla Zaragoza |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Kristin Torres |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Alexa Noriega |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Kira Lipson |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Hannah Johnson |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Priscilla Castaneda |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Jocelyn Nguyen |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Jennifer Ventura |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
|
Reanne Eames |
Individual |
125 Bethany Dr Ste C Scotts Valley, CA |
Every health care provider, whether it’s a hospital, pharmacy, or individual specialist, must obtain their own NPI number. This identification number is unique and is assigned upon application. In tod...
Taxonomy Code | 106S00000X |
Display Name | Behavior Technician |
Taxonomy Group | Behavioral Health & Social Service Providers |
Taxonomy Classification | Behavior Technician |
Definition | The behavior technician is a paraprofessional who practices under the close, ongoing supervision of a behavior analyst or assistant behavior analyst certified by the Behavior Analyst Certification Board and/or credentialed by a state (such as through licensure). The behavior technician is primarily responsible for the implementation of components of behavior-analytic treatment plans developed by the supervisor. That may include collecting data on treatment targets and conducting certain types of behavioral assessments (e.g., stimulus preference assessments). The behavior technician does not design treatment or assessment plans or procedures but provides services as assigned by the supervisor responsible for his or her work. |
Effective Date | September 30, 2009 |