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.
Jurisdiction
United Kingdom
Package
spire-healthcare.prod 1.3.0-beta
Query
-
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
-
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.
API
-
Embed
Embed this resource in your own website. How?
Tools
-
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.
Download
Compare
- Set as file A
- Set as file B
- A: not set
- B: not set
- Compare A ↔ B
- Clear selection
SpireCore Hospital Location
A Spire hospital as a physical place. One instance per row of the RDS LocationHospital table. The hospital is also a legal and ODS entity; that aspect is represented by a SpireCore Organization referenced from managingOrganization, and the two are loaded together from the same RDS row. A hospital is the top of the Spire location hierarchy, so partOf is not permitted; sites hang beneath it through SpireCore Site Location. Identifiers: HospitalID (8 characters, the RDS key) and HospitalCode (up to 4 characters, the business key used in SAP-HMS RFC calls); the UK Core ODS site code slice is inherited unchanged and is not populated from the RDS. Naming: name carries the public name, alias carries the internal name. Lifecycle: status is derived from the RDS StartDate and EndDate, which are also carried verbatim in the validity period extension. Address and contact details map one to one onto the RDS columns.
- type Profile on Location
- FHIR R4
- status Draft
-
version0.1.0
Unregistered conflicting canonical
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
https://www.spirehealthcare.com/
Canonical claims are used to verify ownership of your canonical URLs.
Canonical
File:
package/StructureDefinition-SpireCore-HospitalLocation.json