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.
-
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.
Plan of Treatment Section
This section captures planned, pending, active, or completed orders, interventions, encounters, services, and procedures relevant to a patient’s care. It may also include or reference existing problems or conditions that inform ongoing care planning. While entries typically represent prospective or in-progress actions (as indicated by their @moodCode), completed activities of clinical significance may be included to maintain continuity and context. The section may contain information about ongoing or anticipated care, clinical reminders, and overarching goals, along with the patient’s values, beliefs, preferences, and care expectations that shape care decisions. Examples include reminders for preventive services, values such as quality of life over longevity, beliefs such as refusal of blood transfusions, or preferences regarding care modalities or provider characteristics.
Previously defined entry templates remain valid for compatibility. The Care Plan Act entry template provides a structured way to represent a snapshot of a dynamic, consensus-driven care plan that captures prioritized concerns, goals, and planned interventions. This entry reflects the current state of the care plan as managed in the source system and supports exchange across systems for coordinated, longitudinal care.
When additional context appears in the section narrative (section.text) but not in discrete entries, it is recommended to encapsulate the text in a Note Activity to support ingestion and preserve meaning.
- type LogicalModel
- FHIR R5
- status Draft
-
version5.0.0-ballot
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
http://hl7.org/