Virtual Health · Microsoft Teams consult

Virtual Health

Postoperative Teams visit

Secure video consultations and telehealth visits (Microsoft Teams in Cloud for Healthcare).

Visit OR-4412 · Vargas, MD
Observability

Identity → Graph → media join path

Channel: Microsoft Teams (Cloud for Healthcare telehealth).

Join path: identity → Graph meeting → media session.

Security

Who is allowed to join this consult

Attendee: Rivera (patient) with Vargas, MD. A billing service account on the same meeting is a SIEM problem, not jitter.

What Elastic is doing here
Search

After-visit summary and wound-photo metadata lookup

The visit note is searchable in surgical-capd-notes instead of scraping Teams chat.

Observability

Start visit writes the identity → Graph → media join path

Join latency, Graph errors, and QoS warnings land in the same APM trace family.

Security

Who joined this consult, and from where

A non-clinical identity joining the same Teams meeting as Rivera is a SIEM finding.

service.name = vincari-telehealth