An attributed note recorded on a resource with no note element of its own, such as the comment thread on a DocumentReference. Each repeat is one note in the Task Note turn shape -- author and time required, markdown text, machine authors as identifier-only logical references -- so every thread in the EMR reads and validates identically. A note's text may be corrected in place, under the author and time it was recorded with, and readers order the thread by the value's time, oldest first. Where a resource defines a native note element, that element is the home and this extension is not used. Only the note's author corrects it; time stays the time it was first recorded, and the earlier text survives only in version history, which a store holding these threads SHALL keep. Each note SHOULD carry an id, unique within the resource and unchanged by a correction. It is equivalent to HL7's http://hl7.org/fhir/StructureDefinition/note from the extensions pack, with the value constrained to the Task Note shape; an export to a system that uses that extension maps one to the other.
An attributed note on the resource (ordered by time)
Definition
One note recorded on the resource: who said it, when, and what they said. Repeats form the resource's thread, ordered by the value's time, oldest first. A note's text may be corrected in place; its author and time stay as recorded.
Comments
Only for resources without a native note element. Where R4 defines one (Task, Observation, and the rest), the native element is the home and this extension is not used there.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.