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.
Schedule
A container for slots of time that may be available for booking appointments.
- type Profile on Schedule
- FHIR R4
- status Draft
-
version4.6.0
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
http://hl7.org/fhir
Canonical claims are used to verify ownership of your canonical URLs.
You're probably missing a package or made a typo in your canonical.
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Base
Schedule | DomainResource | There are no (further) constraints on this element Element idSchedule A container for slots of time that may be available for booking appointments Alternate namesAvailability DefinitionA container for slots of time that may be available for booking appointments.
| ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idSchedule.identifier External Ids for this item DefinitionExternal Ids for this item.
|
active | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idSchedule.active Whether this schedule is in active use DefinitionWhether this schedule record is in active use or should not be used (such as was entered in error). This element is labeled as a modifier because it may be used to mark that the resource was created in error. This resource is generally assumed to be active if no value is provided for the active element
|
serviceCategory | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idSchedule.serviceCategory High-level category DefinitionA broad categorization of the service that is to be performed during this appointment.
|
serviceType | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idSchedule.serviceType Specific service DefinitionThe specific service that is to be performed during this appointment.
|
specialty | Σ | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idSchedule.specialty Type of specialty needed DefinitionThe specialty of a practitioner that would be required to perform the service requested in this appointment. Additional details about where the content was created (e.g. clinical specialty).
|
actor | Σ | 1..* | Reference(Patient | Practitioner | PractitionerRole | CareTeam | RelatedPerson | Device | HealthcareService | Location) | There are no (further) constraints on this element Element idSchedule.actor Resource(s) that availability information is being provided for DefinitionSlots that reference this schedule resource provide the availability details to these referenced resource(s). The capacity to support multiple referenced resource types should be used in cases where the specific resources themselves cannot be scheduled without the other, and thus only make sense to the system exposing them as a group. Common examples of this are where the combination of a practitioner and a room (Location) are always required by a system. Reference(Patient | Practitioner | PractitionerRole | CareTeam | RelatedPerson | Device | HealthcareService | Location) Mappings
|
planningHorizon | Σ | 0..1 | Period | There are no (further) constraints on this element Element idSchedule.planningHorizon Period of time covered by schedule DefinitionThe period of time that the slots that reference this Schedule resource cover (even if none exist). These cover the amount of time that an organization's planning horizon; the interval for which they are currently accepting appointments. This does not define a "template" for planning outside these dates.
|
comment | 0..1 | string | There are no (further) constraints on this element Element idSchedule.comment Comments on availability DefinitionComments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated.
|