The Choreography Layer: ConCOREdance as an Intelligent Coordination Platform

Core Principle

The clinician owns the data.

The clinician owns the documents.

The clinician owns the calendar.

The clinician owns the relationships.

The clinician chooses the infrastructure.

ConCOREdance should coordinate systems without requiring clinicians to surrender ownership.

Architectural Direction

Instead of a monolithic platform, establish provider abstraction layers:

• Identity Provider
• Storage Provider
• Calendar Provider
• Email Provider
• Signature Provider
• Telehealth Provider
• Task Provider

ConCOREdance becomes the orchestration layer above these systems.

Platform Partners

First-class support should be planned for:

Google Workspace

• Gmail
• Google Calendar
• Google Drive
• Google Docs
• Google eSignature
• Google Contacts

Microsoft 365

• Outlook Mail
• Outlook Calendar
• OneDrive
• SharePoint
• Word
• Microsoft Identity

The therapist should not be required to migrate into a proprietary ecosystem.

Calendar Intelligence Layer

A major discovery of this transmission is that scheduling chaos is fundamentally a coordination problem.

Current state:

• Headway publishes events
• Sondermind publishes events
• Personal calendars publish events
• Google and Outlook publish events

No system understands the intentions of the others.

Proposed Solution

Create a Master Schedule within conCOREdance.

The Master Schedule should:

• Aggregate events from multiple systems
• Detect duplicates
• Detect conflicts
• Detect impossible scheduling situations
• Publish availability intelligently
• Become a scheduling authority rather than a passive calendar

Semantic Scheduling

Traditional systems ask:

'Is this slot available?'

ConCOREdance should eventually ask:

'Is this slot appropriate?'

Future considerations:

• Session type awareness
• Therapist preferences
• Fatigue management
• Buffer recommendations
• Intake complexity
• Couples-session requirements
• Clinical workflow optimization

Data Sovereignty Initiative

Guiding principle:

Your data stays where you put it.

Potential supported repositories:

• Google Drive
• OneDrive / SharePoint
• Dropbox Business
• Box
• Self-hosted storage
• Synology
• QNAP

ConCOREdance should coordinate data rather than requiring custody of data whenever possible.

Signature Architecture

Develop a Signature Provider Layer.

Potential providers:

• Google eSignature
• Microsoft ecosystem solutions
• BoldSign
• Dropbox Sign
• DocuSign
• Future Native conCOREdance Signature Engine

Goal:

A clinician chooses a provider while maintaining a consistent workflow.

Canonical Observation

The architecture may have been embedded in the name from the beginning.

ConCOREdance.

Not records. Not storage. Not repository.

The choreography.

The movement of independent systems around a common center.