Task Note (one conversation turn) Profile¶
| Canonical | https://fhir.apps.health/StructureDefinition/nexus-emr-task-note |
|---|---|
| Status | draft · 1.33.0 |
| Base | Annotation (constraint) |
| Source | FSH · JSON |
One turn in a task's conversation: who said it, when, and what they said. Both people and machine actors (harness graphs, decision-support rules, first-party EMR automation) author turns. Because R4 does not permit Device as an Annotation.author target and a profile cannot widen it, a machine-authored turn is an identifier-only logical reference under the nexus-harness-graph, nexus-cds-rule or nexus-automation NamingSystem, carrying a display and no literal reference; the identifier's system is what says which kind of machine the author is. Human authors use the element normally.
Salient fields
No salient fields have been declared for this profile yet — nothing states which few values represent a Annotation in charts, summaries, and LLM contexts. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.