FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
mCSD Endpoint
A profile on the mCSD Endpoint.
An Organization may be reachable through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization.
Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource.
- type Profile on Endpoint
- FHIR R4
- status Active
-
version3.9.0
The canonical from this resource does not match any claims.
Canonical claims are used to verify ownership of your canonical URLs.
MCSDEndpoint (Endpoint) | I | Endpoint | There are no (further) constraints on this element Element idEndpoint The technical details of an endpoint that can be used for electronic services DefinitionThe technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idEndpoint.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idEndpoint.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..0 | uri | There are no (further) constraints on this element Element idEndpoint.implicitRules A set of rules under which this content was created DefinitionA 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. 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 it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idEndpoint.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idEndpoint.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. Contained resources do not have 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.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idEndpoint.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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.
| |
extension | I | 0..* | Extension | Element idEndpoint.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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 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. 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. Unordered, Open, by url(Value) Constraints
|
purposeOfUse | I | 0..* | Extension(CodeableConcept) | Element idEndpoint.extension:purposeOfUse Purpose of Use Extension Alternate namesextensions, user content DefinitionSet a purpose of use for an mCSD Endpoint or mCSD Organization. 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. https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.PurposeOfUse Constraints
|
modifierExtension | ?! I | 0..0 | Extension | There are no (further) constraints on this element Element idEndpoint.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 manageable, 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). 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. 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.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idEndpoint.identifier Identifies this endpoint across multiple systems DefinitionIdentifier for the organization that is used to identify the endpoint across multiple disparate systems.
|
status | S Σ ?! | 1..1 | codeBinding | Element idEndpoint.status represents the current status of this endpoint. Definitionactive | suspended | error | off | test. Should be updated when maintenance or other status changes happen. The status of the endpoint.
|
connectionType | Σ | 1..1 | CodingBinding | There are no (further) constraints on this element Element idEndpoint.connectionType Protocol/Profile/Standard to be used with this endpoint connection DefinitionA 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). For additional connectivity details for the protocol, extensions will be used at this point, as in the XDS example. EndpointConnectionType (extensible) Constraints
|
name | Σ | 0..1 | string | There are no (further) constraints on this element Element idEndpoint.name A name that this endpoint can be identified by DefinitionA friendly name that this endpoint can be referred to with.
|
managingOrganization | Σ | 1..1 | Reference(MCSDOrganization) | Element idEndpoint.managingOrganization Organization that manages this endpoint. DefinitionThe organization that manages this endpoint, even if technically another organization is hosting this in the cloud. This element is used when there is a technical problem with the endpoint operation, and would be used to contact for technical support. This managing organization relationship is potentially independent of if the organization is the custodian/owner of the data available thru this endpoint.
|
contact | 0..* | ContactPoint | Element idEndpoint.contact Contact details for source (e.g. troubleshooting) DefinitionContact details for a human to contact about the endpoint. The primary use of this for system administrator troubleshooting.
| |
period | S Σ | 0..1 | Period | Element idEndpoint.period Overall deployment lifetime for this endpoint. DefinitionThe interval during which the endpoint is expected to be operational. usually indicating when the endpoint was deployed, and may indicate when this endpoint will be decommissioned.
|
payloadType | Σ | 1..* | CodeableConcept | There are no (further) constraints on this element Element idEndpoint.payloadType The type of content that may be used at this endpoint (e.g. XDS Discharge summaries) DefinitionThe payload type describes the acceptable content that can be communicated on the endpoint. The payloadFormat describes the serialization format of the data, where the payloadType indicates the specific document/schema that is being transferred; e.g. DischargeSummary or CarePlan.
|
payloadMimeType | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element idEndpoint.payloadMimeType Mimetype to send. If not specified, the content could be anything (including no payload, if the connectionType defined this) DefinitionThe 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). Sending the payload has obvious security consequences. The server is responsible for ensuring that the content is appropriately secured. The mime type of an attachment. Any valid mime type is allowed.
|
address | Σ | 1..1 | url | There are no (further) constraints on this element Element idEndpoint.address The technical base address for connecting to this endpoint DefinitionThe uri that describes the actual end-point to connect to. 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/...".
|
header | 0..* | string | There are no (further) constraints on this element Element idEndpoint.header Usage depends on the channel type DefinitionAdditional headers / information to send as part of the notification. Exactly what these mean depends on the channel type. The can convey additional information to the recipient and/or meet security requirements.
|