Understanding the ScriptSure Account Hierarchy (DAW → Vendor → Organization → Business Unit → Practice → User)

Modified on Fri, 11 Jul at 5:03 PM

To manage users, permissions, and integrations effectively within ScriptSure, it’s important to understand how the platform’s account structure is organized. ScriptSure operates on a multi-tiered hierarchy that supports scalability, access control, and streamlined administration.



1. DAW Systems (Top-Level Infrastructure)

DAW Systems is the parent company and the provider of the ScriptSure platform. All data, features, and services are hosted and managed within DAW’s infrastructure. This is the top-level entity overseeing platform-wide policies, vendor access, and system architecture.




2. Vendor

A Vendor is a third-party company or technology partner authorized to manage or integrate ScriptSure into client organizations.


Common Roles of a Vendor:

    - Sets up and manages organizations and practices for their clients.

    - Works with ScriptSure support to configure integrations, onboarding, and custom features.

    - May be granted Full Admin access to oversee multiple accounts under their scope.




3. Organization

An Organization represents a healthcare entity or group operating under a single legal or administrative structure.


Characteristics:

    - Houses one or more business units.

    - Oversees top-level configuration such as EPCS registration, ID.me integrations, and system-wide credentials.

    - Access is typically granted to Full Admins and vendors.




4. Business Unit

A Business Unit is a sub-division within an organization, often used to group related practices or locations.


Characteristics:

    - Helps organize multiple practices within the same organization.

    - Useful for reporting, user access control, and management workflows.




5. Practice

The Practice is the level at which care is delivered and where most day-to-day operations occur.


Key Functions:

    - Houses providers and supporting users.

    - Holds practice-specific settings, such as licensing, service levels, and DEA registration.

    - Can be integrated with third-party systems (e.g., EHRs, PMP).

    - Each user is tied to a specific practice or multiple practices.




6. User

The User is the end-level account in the ScriptSure hierarchy.


Two User Types:

a. Provider – Licensed to prescribe medications and linked to EPCS/ID.me.

b. Supporting User – Non-provider staff with roles such as admin, nurse, or front desk.


User Details:

    - Assigned to one or more practices.

    - Can be given Basic or Full Admin privileges based on their role.

    - Has individual credentials and identifiers (e.g., email, DEA, state license).



Example Flow:


 





Why This Hierarchy Matters?

  • Ensures clean data flow and access control across large organizations.
  • Helps vendors and admins manage multiple practices efficiently.
  • Allows accurate integration setup, licensing validation, and user-level permissions.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article