The platform tenant that owns this resource, stamped by the FHIR Gateway. PRIVATE INFRASTRUCTURE: it is not client-writable, the value is an opaque platform tenant id that resolves to nothing fetchable, and external consumers must not depend on it. Declared here because it appears on stored resources and is therefore part of what an implementer sees on the wire.
Elements / Details
Every element this profile touches, with its full definition. Element names in the tables link here.
The platform tenant that owns this resource, stamped by the FHIR Gateway. PRIVATE INFRASTRUCTURE: it is not client-writable, the value is an opaque platform tenant id that resolves to nothing fetchable, and external consumers must not depend on it. Declared here because it appears on stored resources and is therefore part of what an implementer sees on the wire.
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.