How a record was linked to or unlinked from its target -- automatic, confirmed or manual -- qualifying the ISO 21089 link or unlink event in Provenance.activity. Recorded, never inferred from which agents are present.
How the link was made: automatic, confirmed or manual
Definition
How the record was linked to (or unlinked from) its target: by a matching service with no human
decision (automatic), by a matching service whose proposal a person accepted (confirmed), or by a
person (manual).
It qualifies the ISO 21089 link or unlink event that Provenance.activity carries, and is present
exactly when that event is. A reader takes the method from here and never deduces it from which
agents the Provenance names.
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.