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.
-
FHIR
Get this resource using a FHIR client.
-
Embed
Embed this resource in your own website. How?
-
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.
ILHDP Encounter Inpatient Care Segment Profile
Child encounter representing a distinct period or event within the overall hospitalization. In most cases it denotes care by a specific clinical unit (e.g., ER, internal medicine ward, orthopedics), but it MAY also represent a significant event during care (e.g., emergency surgical intervention, resuscitation, specialist consultation, imaging procedure). When representing care by a clinical unit, this encounter SHALL reference the top-level ILHDPEncounterHospitalization via partOf. When representing a significant event, this encounter SHALL reference either the top-level ILHDPEncounterHospitalization or the relevant ILHDPEncounterInpatientCareSegment via partOf. It is recommended to link significant-event encounters to the segment representing the responsible clinical unit. This profile captures both the clinical unit providing care (serviceProvider) and the nursing unit/physical location (location). A new segment encounter SHALL be created when the clinical unit (serviceProvider) changes (e.g., transfer). If only the nursing unit/bed changes, a new encounter SHALL NOT be created; update location and/or location:nursing-unit instead. The choice of what constitutes a 'significant event' is left to the organization; however, to avoid overwhelming consumers, create event segments only for clinically meaningful events where associating participants and artifacts (Conditions, Observations, Medications, Procedures, etc.) to that event is important.
- type Profile on Encounter
- FHIR R4
- status Draft
-
version0.4.0
The canonical from this resource does not match any claims.