Generated Narrative: StructureDefinition base-ext-associatedServers Name Flags Card. Type Description & Constraints <a href="StructureDefinition-base-ext-associatedServers-definitions.html#Extension" title="This extension is designed to store information about servers that may be associated with the current endpoint. It defines a set of servers that #xA;could be linked to this endpoint. If a server is associated, the server's type and URL will be included. For example, if your system features two types of endpoints: #xA;a standard endpoint and a proxy endpoint associated with the server. For example, the proxy endpoint can be configured to interface with AEGIS software, #xA;allowing the software to record transactions and ensure compliance with pertinent standards or regulations. Implementing such a configuration in a production#xA;environment would offer the flexibility to switch between standard and proxy modes (associated server) as necessary. Consequently, it is essential to have both#xA;standard and proxy endpoints readily available for seamless transitions as required.">Extension 0..* Extension NDH Associated Servers #xD; extension 1..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:associatedServersType S 1..1 Extension Associated Server Type #xD; extension 0..0 Extension #xD; url 1..1 uri "associatedServersType" #xD; value[x] 1..1 CodeableConcept Value of extension Binding: Associated Servers Type Value Set (extensible) #xD; extension:serverURL S 0..1 Extension Binary #xD; extension 0..0 Extension #xD; url 1..1 uri "serverURL" #xD; value[x] 1..1 string Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/us/ndh/StructureDefinition/base-ext-associatedServers" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
HL7 International / Patient Administration
This extension is designed to store information about servers that may be associated with the current endpoint. It defines a set of servers that could be linked to this endpoint. If a server is associated, the server's type and URL will be included. For example, if your system features two types of endpoints: a standard endpoint and a proxy endpoint associated with the server. For example, the proxy endpoint can be configured to interface with AEGIS software, allowing the software to record transactions and ensure compliance with pertinent standards or regulations. Implementing such a configuration in a production environment would offer the flexibility to switch between standard and proxy modes (associated server) as necessary. Consequently, it is essential to have both standard and proxy endpoints readily available for seamless transitions as required.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Source of the definition for the extension code - a logical name or a URL.
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.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).