Communications
Secure threads, visit media state and language access — one shared messaging record with operations.
Secure threads
5 open of 5 in this view
Your lipid results
Same MessageThread record operations sees. Replying here is the existing clinician path.
care-team
Your cholesterol panel is back and one value is higher than we'd like. I've suggested a repeat in 12 weeks — can you tell me about your current diet and activity?system
Result released to patient portal (synthetic).Admin-owned action. Scheduled sends, media session control, notification consent and interpreter requests are raised from the operations messaging queue, not from the clinician role.
Phone calls
Patient-specific review of existing synthetic phone sessions.
Synthetic demo records only. Session states do not confirm a telephone call took place.
Loading phone history…
Visit media sessions
Read-only state. No join URL exists and no call is placed from this screen.
Recording unavailable · captions off · reconnects 0
Channel readiness
What is internal synthetic versus vendor-gated.
Secure in-app threads are internal and synthetic — they run on this project's own records. Every row below is an adapter boundary, not a named vendor.
Waiting-room placeholder only. No video vendor, join URL, or recording.
Stub only. No translation vendor or locale pipeline is configured.
No live email, SMS, or push. Delivery attempts stay synthetic.
Language access
Preferences and interpreter requests are read-only here.
Harold Nkemelu
preferred en · SETUP_REQUIRED
Jules Barrow
preferred es · interpreter needed · SETUP_REQUIRED
Translation adapter: en → es · unreviewed · accuracy promise none · translatedText null