Stax Digital Garden

YMN-1007 - Clinical and Provider Relations

2 min read

Living Document Notice
Published 2026-09-17. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

Clinical and Provider Relations

Clinical and Provider Relations: Dual-trace Phosphor P31 emerald green and P4 paper white vector CRT macro showing WebAssembly SQLite recursive tree traversals and OPFS virtual filesystem access handles

Summary

Health telemetry and medical histories must be strictly partitioned from general social contacts while preserving doctor-patient relational continuity. Yeoman interfaces with Pratique health logs through audited provider relations.

Specializing Contacts for Clinical Care

Personal medical records require higher confidentiality guarantees and domain-specific metadata than standard professional acquaintances. When logging vital signs, blood panels, or physical therapy regimens, users must track which licensed practitioner prescribed or reviewed each metric.

Realm 13 (Pratique) records clinical observations and telemetry data in strict Parquet schemas. Yeoman serves as the directory of human caregivers, linking medical events to verified medical provider dossiers.

+-------------------------------------------------------------+
|              Clinical Care Graph Integration                |
|                                                             |
|   +---------------------------+                             |
|   | Pratique Vitals Record:   |                             |
|   | Systolic / Diastolic BP   |                             |
|   +---------------------------+                             |
|                 │                                           |
|       [consultedProvider]                                   |
|                 ▼                                           |
|   +---------------------------+   +-----------------------+ |
|   | Yeoman Provider Dossier:  |   | Clinical Fields:      | |
|   | Dr. Elena Vance, MD       |-> | - NPI / License       | |
|   | (Cardiology Practice)     |   | - Hospital Affiliation| |
|   +---------------------------+   | - Emergency Line      | |
|                                   +-----------------------+ |
+-------------------------------------------------------------+

Provider Schema Extensions

Medical provider notes extend standard contact frontmatter with credentialing and institutional details:

---
title: "Provider: Dr. Elena Vance, MD"
cadence_days: 180
specialty: cardiology
npi: "1982736450"
facility: "St. Jude Medical Pavilion"
channels:
  - kind: phone
    value: "+15550198822"
    label: clinic_direct
  - kind: portal
    value: "https://myhealth.stjude.org/provider/evance"
    label: secure_messaging
last_contact_date: "2026-06-15"
$pkm:
  id: "urn:uuid:0191fa30-1003-7000-8000-000000000003"
  realm: yeoman
---

Linking Vitals Observations to Caregivers

When biometric anomalies occur—such as elevated resting heart rate or erratic sleep telemetry—Pratique generates a clinical inquiry note bound to Dr. Vance’s URN:

---
title: "Clinical Observation: Elevated Tachycardia Cluster"
observed_at: "2026-09-15T04:12:00Z"
$pkm:
  id: "urn:uuid:0191fa30-1301-7000-8000-000000000012"
  realm: pratique
  relations:
    consultedProvider: "urn:yeoman:contact:0191fa30-1003-7000-8000-000000000003"
---

Privacy Boundaries and Access Control

Because clinical provider notes reference health concerns, Yeoman prevents these dossiers from being exported to public digital gardens. Digital garden static site generators automatically enforce realm-level exclusion rules:

  • 02-yeoman/contacts/ General contacts (Subject to PII scrubbing).
  • 02-yeoman/providers/ Quarantined locally; strictly excluded from public Quartz builds.
  • Directus Target: yeoman
  • Garden Source Reference: MOC - Bosun PKM Tools, MOC - Fleet Operations
  • Garden Source Reference: [YMN-1007 - Clinical and Provider Relations](YMN-1007 - Clinical and Provider Relations)

Graph View