Demo data

Integration

Data Sources & Refresh

Every measure traces back to a governed source. Refresh cadence ranges from 15-minute near real-time pulls to nightly state file loads.

Microsoft-ecosystem architecture

Source systems

  • Case management (SQL Server)
  • Electronic Health Record
  • State systems (Crossroads, NC EDSS)
  • Spreadsheets on SharePoint/OneDrive

Ingestion

  • Secure REST APIs
  • OData feeds
  • Azure Data Factory pipelines
  • SFTP landing → ADF

Curated warehouse

  • Azure SQL / SQL Server
  • Conformed dimensions
  • Measure semantic model
  • Row-level security by role

Delivery

  • Power BI datasets & reports
  • Embedded scorecard app
  • Scheduled exports
  • Entra ID SSO
Source inventory & refresh status
SourceSystemMethodCadenceLast runRowsPHIStatus

Case Management System

Behavioral Health, Harm Reduction, Communicable Disease, Clinical Services

On-prem SQL ServerSecure APIEvery 15 minutes4 min ago184,920
PHI
healthy

Electronic Health Record

Clinical Services, Behavioral Health, Communicable Disease

EHR vendor cloudODataHourly22 min ago412,308
PHI
healthy

WIC Crossroads Extract

WIC

State systemSFTP → ADFNightly 02:0016 hr ago96,140
PHI
healthy

NC EDSS Surveillance

Communicable Disease

State systemAzure Data FactoryEvery 4 hours3 hr 40 min ago58,210
PHI
delayed

Environmental Inspections

Environmental Health

On-prem SQL ServerSecure APIEvery 30 minutes12 min ago74,180
healthy

CHIP & Survey Workbooks

CHA / CHIP, Preparedness

SharePoint / OneDriveSharePoint syncEvery 6 hours1 hr ago8,420
healthy

Finance & Cost Allocation

All programs

ERP extractAzure Data FactoryNightly 01:0017 hr ago31,280
healthy

Legacy Spreadsheet Uploads

Preparedness

OneDrive folderSharePoint syncOn upload2 days ago2,140
failed
Refresh policy

Near real-time (15 min): operational measures such as crisis encounters, inspections, and outreach contacts.

Hourly: EHR-derived clinical measures where the source system publishes incremental change feeds.

Nightly: state extracts, finance allocations, and any measure with a monthly reporting cycle.

Failed or delayed pipelines raise an operations alert and the affected tiles display a stale-data banner rather than silently showing old numbers.

Security controls in the pipeline

In transit & at rest: TLS 1.2+, private endpoints, and customer-managed keys on all PHI-bearing stores.

Minimum necessary: pipelines pull only the fields required by an approved measure definition.

Identity: managed identities for service-to-service auth; Entra ID groups drive row-level security.

BAA: processing governed by the Buncombe County Business Associate Agreement, with audit logging retained per policy.