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.
Advance Directive Organizer (deprecated)
The Advance Directive Organizer includes information about who verified the content available in each advance healthcare directive source document or other verified source documentation. When documenting the existence of advance healthcare directive document(s), the organizer contains an observation which includes information about the kind of advance healthcare directive source document (e.g., Living Will, Personal Advance Care Plan, Portable Medical Order). This observation provides identifier references to the external source advance healthcare directive document.
If a person has appointed healthcare agent(s), the organizer includes the current healthcare agent(s) information, and a reference to the external document which contains the healthcare agent appointment decisions. Additional observations summarizing the type of content included in the advance directive source documents also can be included. Treatment Intervention Preferences, Care Experience Preferences, Upon Death Preferencesand Personal Health Goals may be considered relevant by the organization rendering care services to the patient and included in the organizer as well although duplicating information is discouraged.
When the existing advance healthcare directive document is a portable medical order, Advance Directive Observations are used to summarize the types of portable orders in the verified document. This provides new summary “structured data” for portable medical orders that often are still exchanged as scanned images.
Provenance information such as author, performer, informant and participant can be used with the Organizer to minimize redundancy on each component Observation.
Templates Used
Although open templates may contain any valid CDA content, the following templates are specifically called out by this template:
Required Components: AdvanceDirectiveObservation
- type LogicalModel
- FHIR R5
- status Retired
-
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/