Resource Profile: Endpoint
General information
See HL7 Endpoint for more information about the base resource Endpoint.
Scope and Usage
This profile holds information about a technical address to an API. The information can include what protocol it follows, what security method it uses, the URL to the authorization server and what API specifications it adheres to. This is to facilitate the integrating of external systems with the endpoint.
Boundaries and Relationships
The healthcare providers as Organizations that make available patient data at a given Endpoint have references to the Endpoint in the Organization.endpoint element.
To express what API specification the Endpoint implements there is an extension "apiSpecification" on the Endpoint.payload element that references the canonical URL of an API Specification.
The search operation Search Endpoint can be used to query the Endpoints that healthcare providers (Organization) use to make patient data available, given that the supplied patient is registered at the healthcare providers. The result can be filtered by whether the Endpoints have declared to be implementing any given API Specifications in their payloads.
Background and Context
Profile
| EndpointEr (Endpoint) | C | Endpoint | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | C | 0..1 | Narrative |
| contained | C | 0..* | Resource |
| extension | C | 0..* | Extension |
| associatedServer | S C | 0..1 | Extension(Complex) |
| id | 0..1 | string | |
| extension | C | 2..* | Extension |
| associatedServerType | S C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..0 | Extension |
| url | S | 1..1 | uriFixed Value |
| value[x] | S C | 1..1 | CodingBindingFixed Value |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | codeFixed Value |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| serverURL | S C | 1..1 | Extension |
| id | 0..1 | string | |
| extension | C | 0..0 | Extension |
| url | S | 1..1 | uriFixed Value |
| value[x] | S C | 1..1 | |
| valueUrl | url | ||
| url | 1..1 | uriFixed Value | |
| value[x] | C | 0..0 | |
| modifierExtension | Σ ?! C | 0..* | Extension |
| identifier | Σ C | 0..* | Identifier |
| status | S Σ ?! | 1..1 | codeBinding |
| connectionType | S Σ | 1..* | CodeableConcept |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| securityMethod | S Σ | 0..1 | CodeableConceptBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| protocol | S Σ | 0..1 | CodeableConceptBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| name | S Σ C | 1..1 | string |
| description | Σ | 0..1 | string |
| environmentType | Σ | 0..* | CodeableConceptBinding |
| managingOrganization | Σ C | 0..1 | Reference(Organization) |
| contact | C | 0..* | ContactPoint |
| period | Σ C | 0..1 | Period |
| payload | S | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 1..* | Extension |
| apiSpecification | S C | 1..1 | Extension(canonical(APISpecificationEr)) |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | Σ | 0..* | CodeableConcept |
| mimeType | Σ | 0..* | codeBinding |
| address | S Σ | 1..1 | url |
| header | 0..* | string |
| Endpoint | C | |
| Short | The technical details of an endpoint that can be used for electronic services | |
| Definition | The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b, a REST endpoint for another FHIR server, or a s/Mime email address. This may include any security context information. | |
| Cardinality | 0..* | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.id | Σ | |
| Short | Logical id of this artifact | |
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | |
| Cardinality | 0..1 | |
| Type | id | |
| Summary | True | |
| Comments | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.meta | Σ | |
| Short | Metadata about the resource | |
| Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |
| Cardinality | 0..1 | |
| Type | Meta | |
| Summary | True | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.implicitRules | Σ ?! | |
| Short | A set of rules under which this content was created | |
| Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. | |
| Cardinality | 0..1 | |
| Type | uri | |
| Modifier | True | |
| Summary | True | |
| Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.language | ||
| Short | Language of the resource content | |
| Definition | The base language in which the resource is written. | |
| Cardinality | 0..1 | |
| Type | code | |
| Binding | IETF language tag for a human language | |
| Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.text | C | |
| Short | Text summary of the resource, for human interpretation | |
| Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | |
| Cardinality | 0..1 | |
| Type | Narrative | |
| Alias | narrative, html, xhtml, display | |
| Comments | Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-6 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.contained | C | |
| Short | Contained, inline Resources | |
| Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. | |
| Cardinality | 0..* | |
| Type | Resource | |
| Alias | inline resources, anonymous resources, contained resources | |
| Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. | |
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 | |
| Mappings |
| |
| Endpoint.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer | S C | |
| Short | Endpoint Associated Server (ER) | |
| Definition | Associated server of this endpoint. | |
| Cardinality | 0..1 | |
| Type | Extension(Complex) | |
| Must Support | True | |
| Alias | extensions, user content | |
| 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. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 2..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType | S C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 1..1 | |
| Type | Extension | |
| Must Support | True | |
| Alias | extensions, user content | |
| 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. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.url | S | |
| Short | identifies the meaning of the extension | |
| Definition | Source of the definition for the extension code - a logical name or a URL. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| 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. | |
| Fixed Value | associatedServerType | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x] | S C | |
| Short | Value of extension | |
| Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | |
| Cardinality | 1..1 | |
| Type | Coding | |
| Binding | ||
| Must Support | True | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ext-1 | |
| Constraints |
| |
| Fixed Value | {
"system": "http://electronichealth.se/CodeSystem/associated-server-types",
"code": "authorization"
} | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].system | S Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Fixed Value | http://electronichealth.se/CodeSystem/associated-server-types | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].code | S Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Fixed Value | authorization | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:associatedServerType.value[x].userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..1 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:serverURL | S C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 1..1 | |
| Type | Extension | |
| Must Support | True | |
| Alias | extensions, user content | |
| 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. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:serverURL.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:serverURL.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..0 | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:serverURL.url | S | |
| Short | identifies the meaning of the extension | |
| Definition | Source of the definition for the extension code - a logical name or a URL. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| 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. | |
| Fixed Value | serverURL | |
| Mappings |
| |
| Endpoint.extension:associatedServer.extension:serverURL.value[x] | S C | |
| Short | Value of extension | |
| Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | |
| Cardinality | 1..1 | |
| Type | url | |
| Must Support | True | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ext-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.extension:associatedServer.url | ||
| Short | identifies the meaning of the extension | |
| Definition | Source of the definition for the extension code - a logical name or a URL. | |
| Cardinality | 1..1 | |
| Type | uri | |
| 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. | |
| Fixed Value | http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-associated-server-er | |
| Mappings |
| |
| Endpoint.extension:associatedServer.value[x] | C | |
| Short | Value of extension | |
| Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). | |
| Cardinality | 0..0 | |
| Type | Address | Age | Annotation | Attachment | Availability | base64Binary | boolean | canonical | code | CodeableConcept | CodeableReference | Coding | ContactDetail | ContactPoint | Count | DataRequirement | date | dateTime | decimal | Distance | Dosage | Duration | Expression | ExtendedContactDetail | HumanName | id | Identifier | instant | integer | integer64 | markdown | Meta | Money | oid | ParameterDefinition | Period | positiveInt | Quantity | Range | Ratio | RatioRange | Reference | RelatedArtifact | SampledData | Signature | string | time | Timing | TriggerDefinition | unsignedInt | uri | url | UsageContext | uuid | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ext-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored | |
| Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.identifier | Σ C | |
| Short | Identifies this endpoint across multiple systems | |
| Definition | Identifier for the organization that is used to identify the endpoint across multiple disparate systems. | |
| Cardinality | 0..* | |
| Type | Identifier | |
| Summary | True | |
| Comments | The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.status | S Σ ?! | |
| Short | active | suspended | error | off | entered-in-error | test | |
| Definition | The endpoint status represents the general expected availability of an endpoint. | |
| Cardinality | 1..1 | |
| Type | code | |
| Binding | The status of the endpoint. | |
| Must Support | True | |
| Modifier | True | |
| Summary | True | |
| Comments | This element is labeled as a modifier because the status contains codes that mark the endpoint as not currently valid. Temporary downtimes or other unexpected short-term changes in availability would not be represented in this property. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType | S Σ | |
| Short | Protocol/Profile/Standard to be used with this endpoint connection | |
| Definition | A coded value that represents the technical details of the usage of this endpoint, such as what WSDLs should be used in what way. (e.g. XDS.b/DICOM/cds-hook). | |
| Cardinality | 1..* | |
| Type | CodeableConcept | |
| Binding | ||
| Must Support | True | |
| Summary | True | |
| Comments | For additional connectivity details for the protocol, extensions will be used at this point, as in the XDS example. If there are multiple payload types or mimetypes they are all applicable for all connection types, and all have the same status. | |
| Slicing | Unordered, Open, by $this(Value) Slice on connectionType based on value set binding | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding | S Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..1 | |
| Type | Coding | |
| Must Support | True | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.system | S Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.code | S Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..1 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod | S Σ | |
| Short | Protocol/Profile/Standard to be used with this endpoint connection | |
| Definition | A coded value that represents the technical details of the usage of this endpoint, such as what WSDLs should be used in what way. (e.g. XDS.b/DICOM/cds-hook). | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | ||
| Must Support | True | |
| Summary | True | |
| Comments | For additional connectivity details for the protocol, extensions will be used at this point, as in the XDS example. If there are multiple payload types or mimetypes they are all applicable for all connection types, and all have the same status. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding | S Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..1 | |
| Type | Coding | |
| Must Support | True | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.system | S Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Fixed Value | http://hl7.org/fhir/restful-security-service | |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.code | S Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..1 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:securityMethod.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol | S Σ | |
| Short | Protocol/Profile/Standard to be used with this endpoint connection | |
| Definition | A coded value that represents the technical details of the usage of this endpoint, such as what WSDLs should be used in what way. (e.g. XDS.b/DICOM/cds-hook). | |
| Cardinality | 0..1 | |
| Type | CodeableConcept | |
| Binding | ||
| Must Support | True | |
| Summary | True | |
| Comments | For additional connectivity details for the protocol, extensions will be used at this point, as in the XDS example. If there are multiple payload types or mimetypes they are all applicable for all connection types, and all have the same status. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType:protocol.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding | S Σ C | |
| Short | Code defined by a terminology system | |
| Definition | A reference to a code defined by a terminology system. | |
| Cardinality | 1..1 | |
| Type | Coding | |
| Must Support | True | |
| Summary | True | |
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | |
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 0..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.system | S Σ | |
| Short | Identity of the terminology system | |
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | |
| Cardinality | 1..1 | |
| Type | uri | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | |
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.version | Σ | |
| Short | Version of the system - if relevant | |
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.code | S Σ C | |
| Short | Symbol in syntax defined by the system | |
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | |
| Cardinality | 1..1 | |
| Type | code | |
| Must Support | True | |
| Summary | True | |
| Requirements | Need to refer to a particular code in the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.display | Σ C | |
| Short | Representation defined by the system | |
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.coding.userSelected | Σ | |
| Short | If this coding was chosen directly by the user | |
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | |
| Cardinality | 0..1 | |
| Type | boolean | |
| Summary | True | |
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | |
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.connectionType:protocol.text | Σ | |
| Short | Plain text representation of the concept | |
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | |
| Comments | Very often the text is the same as a displayName of one of the codings. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.name | S Σ C | |
| Short | A name that this endpoint can be identified by | |
| Definition | A friendly name that this endpoint can be referred to with. | |
| Cardinality | 1..1 | |
| Type | string | |
| Must Support | True | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.description | Σ | |
| Short | Additional details about the endpoint that could be displayed as further information to identify the description beyond its name | |
| Definition | The description of the endpoint and what it is for (typically used as supplemental information in an endpoint directory describing its usage/purpose). | |
| Cardinality | 0..1 | |
| Type | string | |
| Summary | True | |
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.environmentType | Σ | |
| Short | The type of environment(s) exposed at this endpoint | |
| Definition | The type of environment(s) exposed at this endpoint (dev, prod, test, etc.). | |
| Cardinality | 0..* | |
| Type | CodeableConcept | |
| Binding | ||
| Summary | True | |
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.managingOrganization | Σ C | |
| Short | Organization that manages this endpoint (might not be the organization that exposes the endpoint) | |
| Definition | The organization that manages this endpoint (even if technically another organization is hosting this in the cloud, it is the organization associated with the data). | |
| Cardinality | 0..1 | |
| Type | Reference(Organization) | |
| Summary | True | |
| Comments | This property is not typically used when searching for Endpoint resources for usage. The typical usage is via the reference from an applicable Organization/Location/Practitioner resource, which is where the context is provided. Multiple Locations may reference a single endpoint, and don't have to be within the same organization resource, but most likely within the same organizational hierarchy. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.contact | C | |
| Short | Contact details for source (e.g. troubleshooting) | |
| Definition | Contact details for a human to contact about the endpoint. The primary use of this for system administrator troubleshooting. | |
| Cardinality | 0..* | |
| Type | ContactPoint | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.period | Σ C | |
| Short | Interval the endpoint is expected to be operational | |
| Definition | The interval during which the endpoint is expected to be operational. | |
| Cardinality | 0..1 | |
| Type | Period | |
| Summary | True | |
| Comments | Temporary downtimes or other short-term changes in availability would not be represented in this property. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload | S | |
| Short | Set of payloads that are provided by this endpoint | |
| Definition | The set of payloads that are provided/available at this endpoint. | |
| Cardinality | 0..* | |
| Type | BackboneElement | |
| Must Support | True | |
| Comments | Note that not all mimetypes or types will be listed under the one endpoint resource, there may be multiple instances that information for cases where other header data such as the endpoint address, active status/period etc. is different. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload.id | ||
| Short | Unique id for inter-element referencing | |
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
| Cardinality | 0..1 | |
| Type | string | |
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |
| Mappings |
| |
| Endpoint.payload.extension | C | |
| Short | Additional content defined by implementations | |
| Definition | 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 managable, 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. | |
| Cardinality | 1..* | |
| Type | Extension | |
| Alias | extensions, user content | |
| 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. | |
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload.extension:apiSpecification | S C | |
| Short | Endpoint Payload Actor Definition (ER) | |
| Definition | ActorDefinition that this payload is implementing. | |
| Cardinality | 1..1 | |
| Type | Extension(canonical(APISpecificationEr)) | |
| Must Support | True | |
| Alias | extensions, user content | |
| 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. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload.modifierExtension | Σ ?! C | |
| Short | Extensions that cannot be ignored even if unrecognized | |
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | |
| Cardinality | 0..* | |
| Type | Extension | |
| Modifier | True | |
| Summary | True | |
| Alias | extensions, user content, modifiers | |
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | |
| 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. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload.type | Σ | |
| Short | The type of content that may be used at this endpoint (e.g. XDS Discharge summaries) | |
| Definition | The payload type describes the acceptable content that can be communicated on the endpoint. | |
| Cardinality | 0..* | |
| Type | CodeableConcept | |
| Binding | ||
| Summary | True | |
| Comments | The mimeType describes the serialization format of the data, where the payload.type indicates the specific document/schema that is being transferred; e.g. DischargeSummary or CarePlan. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.payload.mimeType | Σ | |
| Short | Mimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this) | |
| Definition | The mime type to send the payload in - e.g. application/fhir+xml, application/fhir+json. If the mime type is not specified, then the sender could send any content (including no content depending on the connectionType). | |
| Cardinality | 0..* | |
| Type | code | |
| Binding | BCP 13 (RFCs 2045, 2046, 2047, 4288, 4289 and 2049) | |
| Summary | True | |
| Comments | Sending the payload has obvious security consequences. The server is responsible for ensuring that the content is appropriately secured. | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.address | S Σ | |
| Short | The technical base address for connecting to this endpoint | |
| Definition | The uri that describes the actual end-point to connect to. | |
| Cardinality | 1..1 | |
| Type | url | |
| Must Support | True | |
| Summary | True | |
| Comments | For rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since there may be more than one, clients should avoid using relative URIs) This address will be to the service base, without any parameters, or sub-services or resources tacked on. E.g. for a WADO-RS endpoint, the url should be "https://pacs.hospital.org/wado-rs" and not "https://pacs.hospital.org/wado-rs/studies/1.2.250.1.59.40211.12345678.678910/series/1.2.250.1.59.40211.789001276.14556172.67789/instances/...". | |
| Constraints |
| |
| Mappings |
| |
| Endpoint.header | ||
| Short | Usage depends on the channel type | |
| Definition | Additional headers / information to send as part of the notification. | |
| Cardinality | 0..* | |
| Type | string | |
| Comments | Exactly what these mean depends on the channel type. The can convey additional information to the recipient and/or meet security requirements. | |
| Constraints |
| |
| Mappings |
| |
Details
The red must-support flag ("S") indicates that the element is expected in some use cases, and a missing flag that the element is never used.
Security and authorization
The extension "associatedServer" is used for URLs to associated servers. The extension requires a server type code and a URL. This profile currently only supports using the extension for authorization server URLs by setting the server type code to "authorization".
The security method is supplied in the connectionType element by using a code from the Restful Security Service value set.
Validation rules
The table below contains validation rules for the format of a Endpoint along with corresponding error messages. The error messages are returned in an OperationOutcome. An OperationOutcome contains an array of issues where each issue has a details element containing an error message and when relevant an expression element containing the path to the element which the error pertains to.
Value set bindings
The following table shows the elements in the profile that should be populated with codes as well as what value sets contain the valid codes for the respective elements. The strength indicates whether it is recommended or required to choose a code from the defined value set.
| Path | Strength | ValueSet |
|---|---|---|
| Endpoint.status | required | http://electronichealth.se/fhir/NDI/ValueSet/er-endpoint-statuses |
| Endpoint.connectionType | required | http://hl7.org/fhir/ValueSet/restful-security-service |
| Endpoint.connectionType | required | http://electronichealth.se/fhir/NDI/ValueSet/er-endpoint-connection-type |
Extensions
| Path | URL |
|---|---|
| Endpoint.extension | http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-associated-server-er |
| Endpoint.payload.extension | http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-payload-actor-definition-er |
Mapping
| AndpunktLogicalEr (andpunkt-logical-er) | Base | ||
| id | C | 1..1 | Identifier |
| status | C | 1..1 | Coding |
| namn | 1..1 | string | |
| adress | 1..1 | url | |
| giltigFrom | 1..1 | time | |
| giltigTom | 0..1 | time | |
| protokoll | C | 0..* | Coding |
| sakerhetsmetod | C | 1..1 | Coding |
| urlTillAuktorisationsserver | 0..1 | url | |
| forvaltasAv | C | 1..1 | Reference(Organization) |
| tillgangliggor | C | 0..* | Reference(APILogicalEr) |
Examples
FHIR based endpoint
The following example shows an endpoint that uses OAuth as security method, as seen in one of the connectionType elements. The other connectionType element contains the connection type of the endpoint, which is "hl7-fhir-rest". To show which API specification the endpoint adheres to, the payload has an extension that points to an API Specification (ActorDefinition) with an url "http://electronichealth.se/ntk/ActorDefinition/HL7Europe/LabReportRepos-1" as canonical identifier. The ActorDefinition contains information about the specification. See the corresponding example of API Specification.
| Endpoint |
| id : 93bc44b7-f6e2-4204-a2da-b1454d4f274f |
| meta |
| profile : http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-er |
| status : active |
| connectionType |
| coding |
| system : http://hl7.org/fhir/restful-security-service |
| code : OAuth |
| connectionType |
| coding |
| system : http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
| code : hl7-fhir-rest |
| name : Region Kalmar FHIR-API |
| payload |
| extension |
| url : http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-payload-actor-definition-er |
| value : http://electronichealth.se/ntk/ActorDefinition/HL7Europe/LabReportRepos-1 |
| address : https://api.regionkalmar.se/fhir |
Rivta based endpoint
The following example shows an endpoint that uses certificates as security method, as seen in one of the connectionType elements. The other connectionType element contains the connection type of the endpoint, which is "inera-soap-tk". To show which API specification the endpoint adheres to, the payload has an extension that points to an API Specification (ActorDefinition) with an url "http://electronichealth.se/ntk/ActorDefinition/IneraAB/GetCareContact-3" as canonical identifier. The ActorDefinition contains information about the specification. See the corresponding example of API Specification.
| Endpoint |
| id : 4811e99e-12d3-464d-8310-e8707c7b9f34 |
| meta |
| profile : http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-er |
| status : active |
| connectionType |
| coding |
| system : http://hl7.org/fhir/restful-security-service |
| code : Certificates |
| connectionType |
| coding |
| system : http://electronichealth.se/CodeSystem/endpoint-connection-types |
| code : inera-soap-tk |
| name : Region Kalmar Inera TK |
| payload |
| extension |
| url : http://electronichealth.se/fhir/NDI/StructureDefinition/endpoint-payload-actor-definition-er |
| value : http://electronichealth.se/ntk/ActorDefinition/IneraAB/GetCareContact-3 |
| address : https://api.regionkalmar.se/inera |
Supported operations
HTTP methods
| Operation | Supported | Comment |
|---|---|---|
| Search (GET, POST) | yes | |
| Insert (POST) | no | |
| Update (PUT) | no | |
| Delete (DEL) | no | |
| Operation (GET, POST) | yes |
Query operations
Supported Queries
GET [base]/Endpointreturns a Bundle with all Endpoints.GET [base]/Endpoint/[LogicalId]returns a Endpoint if found, otherwise a 404 Not Found.GET [base]/Endpoint?[parameters]returns a Bundle with Endpoints in the entry element that meet the search criterias. If no Endpoints meet the search criterias the Bundle will be empty.
Search parameters
| Parameter | Description | Example |
|---|---|---|
| _id | Logical ID of Endpoint | [base]/Endpoint?_id=625aac66-a744-472c-8496-417fce2ada44 |
| _revinclude=Organization.endpoint | Includes all Organizations that reference to a Endpoint in the Organization.endpoint element | [base]/Endpoint?_id=625aac66-a744-472c-8496-417fce2ada44&_revinclude=Organization:endpoint |
| actor | Canonical URL of ActorDefinition - API Specification that Endpoint adheres to | [base]/Endpoint?actor=http://electronichealth.se/ntk/ActorDefinition/HL7Europe/LabReportRepos-1 |
Extended operations
Add/Remove Organization
Adds or removes a Organization to a Endpoint, by adding Endpoint to the Organization.endpoint element. Adding a Organization to a Endpoint means that patient data owned by the Organization can be found at the endpoint. One Organization can use zero to many Endpoints. One Endpoint can be used by zero to many Organizations.
Invocations
Add: POST [base]/Endpoint/[id]/$add-organization
Remove: POST [base]/Endpoint/[id]/$remove-organization
Parameters (In)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| id | 1..1 | string | Logical ID (UUID) of Endpoint, supply as part of invocation address. |
| organization | 1..1 | Identifier (system and value) | Organization identifier. Supply in request body. |
Valid organization identifiers:
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, eg 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, eg 201903682399
- Organization identifier (sv: organisationsnummer)
- system: urn:oid:2.5.4.97
- value format: 10 digits without hyphen, eg 5560269986
Return Values (Out)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| return | 1..1 | OperationOutcome | OperationOutcome with result of operation |
Validation messages
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome.
| Message | Severity | Parameter | Comment |
|---|---|---|---|
| 2-38-1: Required parameter missing. | Error | id, organization | Parameters with cardinality 1..N must be supplied |
| 2-38-8: Endpoint not found. | Error | id | |
| 2-38-9: Invalid parameter. Valid parameters are id, organization. | Error | ||
| 2-38-4: Invalid system. Valid systems are http://electronichealth.se/identifier/personnummer, urn:oid:2.5.4.97 | Error | organization.valueIdentifier.system | The Identifier.system value of parameter organization must be be from list of valid systems (see section Parameters (In) above) |
| 2-38-2: Invalid format of personal identity number. Submit the personal identity number using 12 digits with or without hyphen, e.g. 198001032385. | Error | organization.valueIdentifier.value | |
| 2-44-X: Invalid format of coordination number. Submit the coordination number using 12 digits with or without hyphen, e.g. 201903682399. | Error | organization.valueIdentifier.value | |
| 2-38-7: Invalid format of organization identifier. Submit the organization identifier using 10 digits without hyphen, e.g. 5560269986. | Error | organization.valueIdentifier.value | |
| 4-38-301: Organization was successfully added to the endpoint. | Success | ||
| 4-38-302: Organization was successfully removed from the endpoint. | Success | ||
| 4-38-303: Organization has already been added to the endpoint. | Information | ||
| 4-38-304: Organization has already been removed from the endpoint. | Information |
Examples
Request body
The following example shows the request body for adding or removing an organization with organization identifier 5560269986 to an endpoint. The parameter "organization" is supplied inside a Parameters resource together with the value of the parameter in the valueIdentifier element.
Successful operation response
If the operation succeeds, the response will be an OperationOutcome where the issue element is populated with a "success" code and severity. The details element contains a validation code and message, in this case explaining that the organization got added to the endpoint successfully.
Organization already added/removed response
If the organization was already added when calling $add-organization, the response will be an OperationOutcome where the issue elment is populated with severity set to "information" and code to "duplicate".
If the organization already did not exist on the endpoint when calling $remove-organization, the response will be an OperationOutcome where the issue element is populated with severity set to "information" and code to "not-found".
Failed operation response
If the operation fails, the response will be an OperationOutcome where the issue element is populated with severity set to "error". The code element details what kind of issue caused the error, for example "value" if the error was caused by invalid value format. The details element contains an error code and message, in this case explaining that the operation failed because of invalid format of organization identifier value.