CareStack — Implementation Playbook (DSO)

CareStack Implementation Playbook for DSOs

Enterprise Practice Management System Deployment Guide

---

1. Executive Summary

What CareStack Does CareStack is a cloud-based, all-in-one practice management platform that unifies scheduling, clinical charting, billing, patient engagement, analytics, and multi-location management into a single system. It eliminates the need for fragmented point solutions by providing enterprise-grade functionality with real-time data synchronization across unlimited locations.

Why DSOs Specifically Benefit Practice management at scale demands what CareStack was architected to deliver: true multi-location visibility, standardized workflows that reduce operational variance, and centralized data aggregation that enables portfolio-wide decision-making. Unlike legacy PMS solutions designed for single practices and retrofitted for groups, CareStack's cloud-native architecture means your regional managers can view real-time production across 30 locations from a single dashboard while maintaining granular location-level control. The platform's unified database eliminates the data reconciliation nightmares that plague DSOs running multiple PMS instances. Standardization becomes achievable—not aspirational—when every location operates on identical infrastructure. AI-powered features (automated eligibility verification, smart scheduling optimization, predictive analytics) compound value at scale: a 2% efficiency gain across 40 locations delivers 80x the impact of a single-practice improvement.

Expected Timeline: Decision to Full Deployment

DSO Size	Timeline
15–25 locations	4–6 months
26–40 locations	6–9 months
41–50 locations	9–12 months

Timeline assumes 3–5 location waves with 2–3 week buffers between waves for optimization.

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware Standards (Per Location)

☐ Workstations: Windows 10/11 Pro (64-bit), minimum 8GB RAM, SSD storage ☐ Monitors: 1920x1080 minimum resolution (dual monitors recommended for clinical ops) ☐ Barcode scanners (if using CareStack inventory management) ☐ Signature pads (Topaz recommended for digital consent capture) ☐ Document scanners for legacy record digitization ☐ Credit card terminals compatible with CareStack Payments (verify specific models with vendor)

Network Standards (Enterprise-Wide)

☐ ⚠️ Minimum 100 Mbps dedicated internet per location (CareStack is cloud-dependent; this is non-negotiable) ☐ Redundant ISP or failover connection for high-volume locations ☐ Static IP addresses if utilizing IP whitelisting for security ☐ QoS configuration prioritizing CareStack traffic over streaming/downloads ☐ Firewall rules allowing outbound HTTPS to CareStack domains ☐ Verify VPN compatibility if using site-to-site tunnels to central office

Software Prerequisites

☐ Modern browser (Chrome recommended; Edge acceptable) ☐ PDF reader for report exports ☐ Any integration middleware identified (see Integration section)

Enterprise-Level Requirements

Hosting & Architecture

☐ 🟣 Decision Required: Centralized SSO implementation via SAML 2.0/OAuth (Azure AD, Okta, Google Workspace) ☐ 🔵 Vendor coordination: Request CareStack's SSO configuration documentation ☐ Determine role-based access control (RBAC) structure mapped to organizational hierarchy ☐ Define data residency requirements (CareStack uses AWS; confirm regional compliance needs) ☐ Establish centralized credentialing workflow vs. location-level provider management

Integration Inventory (Complete Before Vendor Kickoff)

System Type	Current Vendor	Integration Priority	API Available?
Imaging/Sensors		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
Patient Communication		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
Clearinghouse		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
Accounting/ERP		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
HR/Payroll		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
Analytics/BI		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No
Labs		☐ High ☐ Medium ☐ Low	☐ Yes ☐ No

Vendor Onboarding Steps

☐ 🔵 Execute enterprise contract (confirm per-location vs. enterprise pricing structure) ☐ 🔵 Schedule kickoff call with CareStack enterprise implementation team ☐ 🔵 Establish key vendor contacts:

• Implementation Project Manager: _______________
• Technical Integration Lead: _______________
• Training Coordinator: _______________
• Executive Sponsor (CareStack side): _______________
• After-hours escalation contact: _______________ ☐ 🔵 Receive access to CareStack Partner Portal ☐ 🔵 Obtain sandbox/test environment credentials ☐ Sign BAA (Business Associate Agreement) for HIPAA compliance ☐ Confirm SLA terms (uptime guarantees, response times, escalation paths)

Data/Access Prerequisites

☐ Complete inventory of existing PMS systems per location ☐ Export patient demographic data in CareStack's specified format (request template from vendor) ☐ ⚠️ Export or archive historical clinical records per your retention policy ☐ Obtain historical financial data for baseline comparisons ☐ Create master user list with roles per location ☐ Document current fee schedules per location/provider ☐ Compile insurance payer IDs and clearinghouse credentials ☐ 🔵 Request API keys for approved integrations

Stakeholder Alignment Map

Stakeholder Level	Who	Needs to Know	Needs to Approve	When to Engage
Board/Investors		ROI projections, strategic rationale	Major budget decisions	Pre-contract
C-Suite	CEO, CFO, COO, CDO	Full implementation plan, resource requirements	Budget, timeline, vendor selection	Pre-contract & weekly during rollout
Regional Managers		Location sequencing, support structure, escalation paths	Wave composition, go-live dates	Week 1, ongoing
Office Managers	Per location	Training schedule, workflow changes, go-live date	N/A (informed)	4 weeks before location go-live
Providers	Per location	Clinical workflow impacts, charting changes	N/A (informed)	2 weeks before location go-live
IT Leadership		Architecture, security, integration requirements	Technical architecture	Pre-contract & ongoing
Compliance/Legal		BAA, data handling, HIPAA implications	BAA, contracts	Pre-contract
HR		Training time allocation, change management support	Training schedules	Week 2

Baseline Metrics to Capture

⚠️ Critical: These metrics must be captured identically across all locations BEFORE any location goes live. This is your ROI measurement foundation.

Operational Metrics

Metric	Definition	How to Measure	Target Source
Average daily patient volume	Unique patients seen per day	Current PMS reports	Last 90 days
Schedule utilization rate	Filled appointments ÷ Available slots	Current PMS	Last 90 days
No-show rate	No-shows ÷ Scheduled appointments	Current PMS	Last 90 days
Average check-in to chair time	Minutes from arrival to operatory	Manual or current PMS	Sample 2 weeks
Front desk FTE per location	Staff hours dedicated to front desk	HR/Scheduling	Current state

Clinical Metrics

Metric	Definition	How to Measure	Target Source
Treatment case acceptance rate	Accepted $ ÷ Presented $	Current PMS	Last 90 days
Average treatment plan completion time	Days from presentation to completion	Current PMS	Last 6 months
Hygiene reappointment rate	% of hygiene patients rebooked at checkout	Current PMS	Last 90 days
Production per provider hour	Gross production ÷ Clinical hours	Current PMS	Last 90 days

Financial Metrics

Metric	Definition	How to Measure	Target Source
Claim denial rate	Denied claims ÷ Submitted claims	Clearinghouse/PMS	Last 90 days
Days in A/R	Average age of outstanding receivables	Current PMS	Current snapshot
Collection rate	Collections ÷ Net production	Current PMS	Last 90 days
Time to first claim submission	Days from DOS to claim drop	Current PMS	Last 90 days
Patient statement cost per location	Monthly cost for statements/postage	Vendor invoices	Last 3 months

DSO-Specific Aggregation

☐ Create standardized metric definitions document distributed to all office managers ☐ 🟣 Decision Required: Establish tolerance ranges for metric variation (e.g., "collection rate" calculation methodology must match within 0.5%) ☐ Assign central analyst to validate baseline data quality before go-live ☐ Store baseline data in centralized repository (not in individual location PMS that will be replaced)

---

3. Location Readiness Assessment

Scoring Framework

Score each factor 1–5 using the criteria below. Sum for composite score (maximum 25 points).

Factor 1: IT Infrastructure Maturity

Score	Criteria
1	Internet < 50 Mbps, hardware > 5 years old, no IT support presence
2	Internet 50–75 Mbps, hardware 4–5 years old, ad-hoc IT support
3	Internet 75–100 Mbps, hardware 2–4 years old, managed IT services
4	Internet 100–200 Mbps, hardware < 2 years old, dedicated IT contact
5	Internet > 200 Mbps with redundancy, modern hardware, on-call IT support

Factor 2: Staff Tenure & Adaptability

Score	Criteria
1	Annual turnover > 50%, no recent tech implementations, documented resistance
2	Turnover 35–50%, limited tech exposure, skeptical culture
3	Turnover 20–35%, some tech experience, neutral to change
4	Turnover 10–20%, recent successful tech adoption, positive culture
5	Turnover < 10%, tech-savvy team, actively request new tools

Factor 3: Patient Volume Impact/Risk

Score	Criteria
1	< 15 patients/day (low impact, good for pilot)
2	15–25 patients/day (manageable)
3	25–40 patients/day (moderate)
4	40–60 patients/day (higher impact, higher risk)
5	> 60 patients/day (highest impact, highest risk—pilot only if strong readiness elsewhere)

Note: For this factor, middle scores indicate ideal pilot candidates. Extreme low or high volumes create different challenges.

Factor 4: Existing Tech Stack Compatibility

Score	Criteria
1	Paper-heavy, no digital imaging, outdated/unsupported PMS
2	Basic PMS, limited integrations, analog imaging
3	Standard PMS with digital imaging, basic integrations
4	Modern PMS, digital imaging, multiple integrations working
5	Cloud-based current systems, API-connected, integration-mature

Factor 5: Local Champion Availability

Score	Criteria
1	No identified champion, leadership gap, manager overloaded
2	Possible champion but unconfirmed availability/interest
3	Willing champion identified (office manager or provider)
4	Strong champion + backup champion, both engaged
5	Proven champion (led past implementations), protected time allocated

Composite Score Interpretation

Score Range	Readiness Tier	Rollout Recommendation
21–25	Tier 1: High Readiness	Prioritize for Wave 1 pilot
16–20	Tier 2: Moderate-High	Strong Wave 2 candidate
11–15	Tier 3: Moderate	Wave 2 or early Wave 3
6–10	Tier 4: Low-Moderate	Later waves; address gaps first
1–5	Tier 5: Low	Remediate before scheduling

Location Assessment Template

Location	Factor 1: IT	Factor 2: Staff	Factor 3: Volume	Factor 4: Tech Stack	Factor 5: Champion	Total	Tier	Recommended Wave

Rollout Sequence Recommendations

Wave 1 Selection Criteria (2–3 locations)

Select locations that are:

• Tier 1 readiness (score 21+)
• Representatively diverse: Include at least one high-volume and one moderate-volume location
• Specialty representative: If your DSO includes GP and specialty, include both in pilot
• Geographic diversity: Different regions test different regional manager support models
• Not your highest-revenue location: Pilot locations absorb learning curve—protect your top performers for Wave 2

Wave 2 Selection (5–8 locations)

• Tier 1 and Tier 2 locations
• Locations whose workflows most closely match Wave 1 pilot locations
• Include remaining high-revenue locations
• Fill in geographic gaps

Wave 3 and Beyond

• Remaining Tier 2 and Tier 3 locations
• Locations requiring remediation between waves

---

4. Rollout Strategy

Recommended Wave Structure

For a 30-location DSO, the following structure is recommended:

Wave	Locations	Duration	Purpose
Wave 1: Pilot	2–3	Weeks 5–8	Validate configuration, train trainers, identify issues
Buffer 1	—	Weeks 9–10	Document learnings, refine workflows
Wave 2: Early Majority	5–8	Weeks 11–16	Scale validation, stress-test support model
Buffer 2	—	Weeks 17–18	Adjust training, update documentation
Wave 3: Expansion	8–10	Weeks 19–26	Full acceleration
Buffer 3	—	Week 27	Final adjustments
Wave 4: Final	Remaining	Weeks 28–32	Complete rollout

Adjust location counts proportionally for your DSO size.

Wave 1 Pilot Location Selection Criteria

☐ Composite readiness score ≥ 21 ☐ Office manager tenure ≥ 2 years ☐ At least one provider willing to champion ☐ Not currently undergoing other major changes (renovation, provider transition) ☐ Moderate patient volume (25–40/day ideal) ☐ Mix of GP and specialty if applicable to portfolio ☐ Geographic proximity to central support (if possible) ☐ Current PMS represents the most common system in your portfolio

Timeline Per Wave

Day	Activity
Day -21	Champion training begins
Day -14	Staff training begins
Day -7	Test environment validation complete
Day -3	Data migration finalized, parallel systems ready
Day -1	Final systems check, go/no-go decision
Day 0	Go-live
Days 1–5	Intensive support period (daily check-ins)
Days 6–14	Stabilization (every-other-day check-ins)
Days 15–21	Optimization (weekly check-ins)
Day 21	Wave complete; document lessons learned

Go/No-Go Criteria for Wave Advancement

🟣 Executive Decision Point

Proceed to next wave if ALL are true: ☐ ≥ 90% of scheduled appointments successfully processed through CareStack ☐ Claims submission operational with < 5% error rate attributable to system ☐ No unresolved critical (P1) issues open > 48 hours ☐ Staff satisfaction pulse survey ≥ 60% positive ☐ No patient-facing system outages > 30 minutes ☐ Champion attestation that location is "stable and manageable"

Pause and remediate if ANY are true: ☒ > 3 unresolved P1 issues ☒ Claims submission failure rate > 10% ☒ Staff satisfaction < 40% positive ☒ Champion requests delay ☒ Revenue cycle disruption exceeding 10% of baseline collections

Rollback Plan

If a wave must be paused:

1. Immediate (Same Day)

   • Regional manager notifies central PMO
   • Vendor escalation initiated (P1 incident)
   • Location reverts to legacy PMS for patient-facing operations
   • CareStack remains accessible for data sync/troubleshooting

2. Short-Term (48–72 hours)

   • Root cause analysis meeting (DSO + vendor)
   • Remediation plan with timeline documented
   • Subsequent wave locations notified of potential delay
   • Affected staff communicated to (emphasize temporary nature)

3. Longer-Term (1+ week)

   • 🟣 Executive decision: Remediate and retry vs. skip location to later wave
   • Formal lessons-learned document created
   • Training or configuration adjustments applied to remaining waves

Critical: Rollback does NOT mean other waves stop. A single-location issue should not cascade unless it reveals a systemic problem (in which case, pause all waves for remediation).

---

5. Configuration & Integration (Weeks 2–3)

Integration with Legacy Practice Management Systems

⚠️ Data Migration Complexity Warning: This is the highest-risk phase of implementation. Budget 40% more time than you estimate.

Data Migration Approach

🟣 Decision Required: Full historical data migration vs. clean-start with archived access to legacy systems.

Approach	Pros	Cons	Recommended For
Full Migration	Complete continuity, no toggling between systems	Complex, higher error risk, longer timeline	Locations with < 5 years data, clean data quality
Clean Start + Archive	Faster, cleaner, lower risk	Staff must reference old system for history	Locations with legacy data quality issues
Hybrid (Recent Data Only)	Balance of speed and continuity	Requires defining cutoff logic	Most DSOs (migrate 2–3 years)

Step-by-Step: Dentrix Enterprise Migration

Step	Action	Owner	Time	Notes
1	🔵 Obtain Dentrix data export specifications from CareStack	Vendor	Day 1	Request migration playbook
2	Install Dentrix data extraction utility	DSO IT	Day 2	May require Dentrix support
3	⚠️ Full backup of Dentrix database	DSO IT	Day 2	Non-negotiable—verify backup integrity
4	Export patient demographics	DSO IT	Day 3	Validate record count
5	Export insurance/payer information	DSO IT	Day 3	Include plan details
6	Export clinical notes and history	DSO IT	Days 4–5	Largest data set
7	Export treatment history	DSO IT	Day 5	May require manual formatting
8	Export appointment history	DSO IT	Day 6	For continuity reporting
9	Export account balances/ledger	DSO IT	Day 6	Reconcile to A/R report
10	🔵 Submit exported data to CareStack migration team	DSO IT	Day 7	Via secure file transfer
11	🔵 CareStack validates and maps data	Vendor	Days 8–12	Expect clarification questions
12	Review mapping validation report	DSO IT + Ops	Day 13	Verify sample records
13	🔵 Execute test migration to sandbox	Vendor	Day 14
14	⚠️ UAT: Verify 10 patient records end-to-end	DSO Team	Days 15–16	Include complex cases
15	Document discrepancies; submit for remediation	DSO Team	Day 16
16	🔵 Remediation and re-migration	Vendor	Days 17–19	May require iteration
17	Final UAT sign-off	DSO Ops	Day 20	Documented approval
18	🔵 Production migration (go-live dependent)	Vendor	Go-live -2 days

Step-by-Step: Eaglesoft Migration

Step	Action	Owner	Time	Notes
1	🔵 Obtain Eaglesoft export specifications from CareStack	Vendor	Day 1
2	⚠️ Verify Eaglesoft version compatibility for export	DSO IT	Day 1	Older versions may require upgrade
3	Run Eaglesoft database integrity check	DSO IT	Day 2	Resolve errors before export
4	Export using Patterson-approved methodology	DSO IT	Days 2–5	May require Patterson support
5	Follow steps 9–18 above

Step-by-Step: Open Dental Migration

Step	Action	Owner	Time	Notes
1	🔵 Obtain Open Dental MySQL export script from CareStack	Vendor	Day 1	Open Dental uses MySQL—exports cleaner
2	Execute database export via MySQL tools	DSO IT	Day 2	Export as CSV or SQL dump
3	Export image references (if storing locally)	DSO IT	Day 3	Images may need separate migration
4	Follow steps 9–18 above

Imaging System Integration

Supported Direct Integrations

☐ 🔵 Confirm your imaging system is on CareStack's supported list ☐ Common supported systems: Dexis, Schick, Carestream, XDR, Apteryx

Bridge Integration Setup

Step	Action	Owner	Time
1	🔵 Request CareStack Imaging Bridge installer	Vendor	Day 1
2	Install bridge software on imaging workstation	DSO IT	Day 2
3	Configure bridge connection parameters	DSO IT	Day 2
4	⚠️ Test image capture from CareStack patient chart	DSO Team	Day 3
5	Verify images appear in CareStack clinical record	DSO Team	Day 3
6	Test from multiple workstations	DSO IT	Day 4
7	Document workflow for clinical staff	DSO Ops	Day 4

Historical Image Migration

🟣 Decision Required: Migrate images to CareStack cloud storage vs. maintain local image archive with pointer references.

• Cloud storage: Full centralization, but significant storage costs and migration time
• Local archive + pointers: Faster, cheaper, but requires maintaining legacy infrastructure

Test Environment Setup

☐ 🔵 Request sandbox environment from CareStack (one per region recommended) ☐ Load test patient data (de-identified production sample or synthetic) ☐ Configure sandbox to mirror production settings ☐ Assign test user accounts with appropriate roles ☐ Document test scenarios covering:

• New patient registration
• Returning patient check-in
• Treatment planning and presentation
• Claim submission
• Payment posting
• Report generation
• Provider schedule management

Validation Checklist

☐ Patient search returns accurate results ☐ Insurance eligibility verification completes in < 10 seconds ☐ Treatment codes map correctly to CDT ☐ Fee schedules display correctly by payer ☐ Claims generate with correct provider NPI and taxonomy ☐ Appointment scheduling displays correctly across time zones (if applicable) ☐ Role-based permissions restrict access appropriately ☐ Reports match expected calculations

Enterprise Configuration

Standardized Configuration Template

Setting Category	Standardize Centrally	Allow Local Variation
Fee schedules (base)	✓
CDT code descriptions	✓
Insurance plan templates	✓
User role definitions	✓
Appointment types	✓
Clinical note templates	✓
HIPAA/consent forms	✓
Recall intervals	✓
Claim submission rules	✓
Provider-specific fee adjustments		✓
Provider schedule templates		✓
Location-specific payers		✓
Marketing source codes		✓
Location hours		✓
Operatory naming		✓

Centralized Test Environment Strategy

Recommended Approach: One central test environment with location-specific configurations loaded.

• Central IT owns test environment
• Each wave creates location-specific test "instance" within environment
• Champions validate their location's configuration before go-live
• Post-go-live, test environment resets for next wave

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ 🔵 Signed BAA on file with CareStack ☐ 🔵 Confirm CareStack's SOC 2 Type II certification ☐ 🔵 Confirm data encryption at rest (AES-256) and in transit (TLS 1.2+) ☐ 🔵 Review CareStack's incident response and breach notification procedures ☐ Document data backup and recovery procedures ☐ Verify audit logging is enabled (user access, record modifications) ☐ Configure session timeout policies (recommend 15 minutes) ☐ Implement minimum necessary access principle via role-based permissions ☐ Configure IP whitelisting if required by security policy ☐ ⚠️ Verify SSO integration includes MFA (multi-factor authentication) ☐ Document data retention settings align with state regulations ☐ Verify patient consent workflows are enabled ☐ Test access revocation workflow (off-boarding) ☐ Complete vendor security questionnaire per your risk management policy

Access Control Matrix

Role	Patient Demographics	Clinical Records	Financial Data	Reports	Admin Settings
Provider	View/Edit	View/Edit	View	View	None
Hygienist	View	View/Edit (limited)	None	Limited	None
Front Desk	View/Edit	View	View/Edit	Limited	None
Billing	View	View	View/Edit	View	None
Office Manager	View/Edit	View	View/Edit	Full	Limited
Regional Manager	View	View	View	Full	Limited
Central Admin	Full	View	Full	Full	Full

---

6. Team Training Plan

Train-the-Trainer Model

Overview

CareStack's enterprise implementation uses a cascaded training model:

1. CareStack trains your central implementation team (2–3 people)
2. Central team trains location champions (1 per location)
3. Champions train their local staff

This model scales efficiently and creates local expertise that persists beyond implementation.

Champion Selection Criteria

Criteria	Ideal Profile
Role	Office manager, lead hygienist, or tech-forward associate
Tenure	≥ 1 year at location
Tech comfort	Comfortable learning new software; not intimidated by troubleshooting
Influence	Respected by peers; can drive adoption
Availability	Can dedicate 15–20 hours over 3 weeks to training
Communication	Clear communicator; patient with frustrated colleagues

☐ Each location identifies primary champion ☐ Each location identifies backup champion ☐ Champions approved by regional manager ☐ Champions complete attestation of commitment

Champion Responsibilities

• Complete CareStack certification training (8–12 hours)
• Customize training materials for their location's workflows
• Deliver role-specific training to all staff
• Serve as first point of contact for staff questions post-go-live
• Participate in daily check-ins during go-live week
• Escalate issues appropriately
• Provide feedback to central team for process improvement

Standardized Training Materials

Create Centrally:

• Role-specific training slide decks
• Workflow quick-reference guides (laminated for ops use)
• Video library of common workflows (screen recordings)
• FAQ document
• Troubleshooting decision tree
• "Day 1 Cheat Sheets" per role
• Assessment quizzes to verify comprehension

Champions Customize Locally:

• Location-specific provider preferences
• Local payer nuances
• Operatory-specific workflows
• Location team norms (meeting rhythms, communication preferences)

Role-Specific Training Outlines

Dentists/Providers

Learning Objectives:

• Navigate patient chart efficiently
• Document clinical notes using CareStack templates
• Present treatment plans and capture acceptance
• Understand AI-assisted features (if enabled: risk assessment, treatment suggestions)
• Access imaging from within clinical workflow
• Override or adjust AI recommendations when clinically appropriate

Training Format: 2-hour live demo + 1-hour hands-on practice Estimated Time: 3–4 hours total Delivered By: Champion

Module Breakdown:

Module	Duration	Content
1. Chart Navigation	30 min	Finding patients, chart sections, customizing view
2. Clinical Documentation	45 min	Odontogram, perio charting, notes, templates
3. Treatment Planning	45 min	Creating plans, phasing, presenting to patients, acceptance tracking
4. Imaging Access	15 min	Launching images, annotating, comparing
5. AI Features	30 min	Understanding AI suggestions, when/how to override
6. Hands-On Practice	60 min	Create chart, plan, document, close

Common Resistance Points & Responses:

Resistance	Response
"My old system was faster"	"There's a learning curve, but in 2 weeks, you'll be faster. Let's identify your 3 most-used workflows."
"I don't trust AI recommendations"	"You're always in control. AI suggests—you decide. Let's practice accepting and overriding."
"I don't have time to learn this"	"Your champion can do quick refreshers between patients. We've built this into the schedule."

Day 1 Cheat Sheet: Providers

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CARESTACK PROVIDER QUICK REFERENCE
━━━━━━