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
The project FHIR API endpoint is not yet available for DSTU2 FHIR version.
-
Simplifier FHIR API
The global FHIR API endpoint is not yet available for DSTU2 FHIR version.
C-CDA on FHIR Care Plan
CARE PLAN FRAMEWORK
A Care Plan (including Home Health Plan of Care (HHPoC)) is a consensus-driven dynamic plan that represents a patient’s and Care Team Members’ prioritized concerns, goals, and planned interventions. It serves as a blueprint shared by all Care Team Members (including the patient, their caregivers and providers), to guide the patient’s care. A Care Plan integrates multiple interventions proposed by multiple providers and disciplines for multiple conditions.
A Care Plan represents one or more Plan(s) of Care and serves to reconcile and resolve conflicts between the various Plans of Care developed for a specific patient by different providers. While both a plan of care and a care plan include the patient’s life goals and require Care Team Members (including patients) to prioritize goals and interventions, the reconciliation process becomes more complex as the number of plans of care increases. The Care Plan also serves to enable longitudinal coordination of care.
The Care Plan represents an instance of this dynamic Care Plan at a point in time. The composition itself is NOT dynamic.
Key differentiators between a Care Plan profile and CCD profile (another “snapshot in time” document):
• Requires relationships between various acts:
o Health Concerns
o Problems
o Interventions
o Goals
o Outcomes
• Provides the ability to identify patient and provider priorities with each act
• Provides a header participant to indicate occurrences of Care Plan review
- type Profile on Composition
- FHIR DSTU2
- status Active
-
versionnone
The canonical from this resource has been determined to conflict with a claim reserved by a different user or organization.
This is not an official source.
http://hl7.org/
Canonical claims are used to verify ownership of your canonical URLs.