Smart Health Hub
Context:ChristianaCare▼Dr. Wilson ▼⚙?

PROVIDER ENTERPRISE ACCOUNT · ChristianaCare

Welcome back, Dr. Wilson

Attending Radiologist, ChristianaCare Health System

ChristianaCare via substrate-fiduciary-managed handle · PPIA-attested[hash: 0x4a8fd2e1]· Active

SUBSTRATE OPERATIONS · SANDBOX TIER

Substrate operational visibility for ChristianaCare

Read-only operational view across the four substrate primitives + Smart MCP Server Pattern (e) endpoint + Smart ID three-layer composition + audit-ledger query surface. Hub payload-blindness preserved at every layer; you observe operational health without seeing payload content per ADR-031 + ADR-032 NO-SHT-BACKDOOR.

Smart Gateway

healthy

per-operation authority evaluation per ADR-031

Audit-ledger

active

two-views audit chain per ADR-022

Pattern 2 deployment

operational

sandbox CA service per Sprint 8 v1.0 LOCK

Smart MCP Server

healthy

Pattern (e) at sandbox.smarthealthhub.net/mcp

Smart ID three-layer composition

Per CSO Smart ID v0.3 three-layer architecture (LOCKED 2026-05-10): Layer 1 Substrate routing (payload-blind) + Layer 2 Smart Match (Council-certified bounded service) + Layer 3 PCI Registry (per ADR-008; Smart ID Option (c) Hybrid).

  • Layer 1 Substrate routingpayload-blind operation routinghealthy
  • Layer 2 Smart MatchCareEvolution + Verato via DHIN/HIEhealthy
  • Layer 3 PCI Registryper ADR-008; Smart ID Option (c) Hybridhealthy
Matched once across systems by a Council-certified service[How does this work?]

When your records exist across multiple providers, payers, or HIEs under different identifiers, Smart Match resolves them to a single bilateral identifier. SHN PBC operates Smart Match under Smart Health Council certification; CareEvolution is the primary technology subcontractor, with Verato (via DHIN) and other HIE/QHIN MPI vendors composing per catchment. Match-once-route-forever: once matched, the bilateral identifier is stable until you elect to sunset it.

Substrate primitive: Smart Match service (Smart ID Layer 2)

Smart MCP Server · Pattern (e)

AI agent integration via standard MCP protocol

Per-tenant integration (ChristianaCare): 3 active AI agents · 47 invocations today

Endpoint canonical · sandbox

https://sandbox.smarthealthhub.net/mcp

Active AI agents

  • Claude Desktop (Dr. Wilson)Claude Desktop23 today
  • Custom radiology assistantCustom enterprise AI18 today
  • OpenAI agent (PA filing)OpenAI agent6 today

Audit-ledger query · recent substrate-event records

api: sandbox.smarthealthhub.net/audit

Pattern (a-e) audit-record canonical cryptographically distinguishable per ADR-022. Filter by invocation pattern at the audit-ledger query API; substrate-event records attest invocation type without exposing payload content.

  • Federated Prior Auth substrate-event-record (UC22) emitted
    Pattern (c) Smart Widget · two-views audit chain bound · cross-party Merkle anchor 60s cadence per ADR-023
  • Smart MCP Server invocation substrate-event-record emitted
    Pattern (e) Smart MCP Server · cryptographically distinguishable from Pattern (c) at audit-record canonical
  • Federated Patient Access substrate-event-record (§164.524) emitted
    Pattern (c) Smart Widget Mode C patient-embedded · PPIA-attested
  • Federated Eligibility Verification substrate-event-record (270/271) emitted
    Pattern (b) TypeScript SDK consumption · X12 transaction shape
  • Federated Quality Measurement substrate-event-record (HEDIS) emitted
    Pattern (c) Smart Widget · institutional quality reporting authority binding
  • Federated Public Health Reporting substrate-event-record (§164.512(b)) emitted
    Pattern (c) Smart Widget · §164.512(b) public health authority