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
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
-
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.
Condition
Base StructureDefinition for Condition Resource
- type Profile on Condition
- FHIR STU3
- status Maturity Level 3
-
versionnone
This resource matches a canonical claim from this project.
Claim: http://hl7.org/fhir
Canonical claims are used to verify ownership of your canonical URLs.
You're probably missing a package or made a typo in your canonical.
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Identifier
- Could not resolve: http://hl7.org/fhir/StructureDefinition/code
- Could not resolve: http://hl7.org/fhir/StructureDefinition/CodeableConcept
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Reference
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Element
- Could not resolve: http://hl7.org/fhir/StructureDefinition/dateTime
- Could not resolve: http://hl7.org/fhir/StructureDefinition/BackboneElement
- Could not resolve: http://hl7.org/fhir/StructureDefinition/Annotation
Condition | I | DomainResource | Element idCondition Detailed information about conditions, problems or diagnoses DefinitionA clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idCondition.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. id |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idCondition.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. Meta |
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idCondition.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. uri |
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idCondition.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). code BindingA human language. ?? (extensible) | |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idCondition.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Narrative Mappings
|
contained | 0..* | Resource | There are no (further) constraints on this element Element idCondition.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
extension | 0..* | Extension | There are no (further) constraints on this element Element idCondition.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
modifierExtension | ?! | 0..* | Extension | There are no (further) constraints on this element Element idCondition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idCondition.identifier External Ids for this condition DefinitionThis records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). Need to allow connection to a wider workflow. Identifier Mappings
|
clinicalStatus | Σ ?! I | 0..1 | codeBinding | There are no (further) constraints on this element Element idCondition.clinicalStatus active | recurrence | inactive | remission | resolved DefinitionThe clinical status of the condition. This element is labeled as a modifier because the status contains codes that mark the condition as not currently valid or of concern. code BindingThe clinical status of the condition or diagnosis. ?? (required)Mappings
|
verificationStatus | Σ ?! I | 0..1 | codeBinding | There are no (further) constraints on this element Element idCondition.verificationStatus provisional | differential | confirmed | refuted | entered-in-error | unknown DefinitionThe verification status to support the clinical status of the condition. verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status. This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid. code BindingThe verification status to support or decline the clinical status of the condition or diagnosis. ?? (required)Default value unknown
|
category | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCondition.category problem-list-item | encounter-diagnosis DefinitionA category assigned to the condition. The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts. CodeableConcept BindingA category assigned to the condition. ?? (example)Mappings
| |
severity | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idCondition.severity Subjective severity of condition DefinitionA subjective assessment of the severity of the condition as evaluated by the clinician. Coding of the severity with a terminology is preferred, where possible. CodeableConcept BindingA subjective assessment of the severity of the condition as evaluated by the clinician. ?? (preferred)Mappings
| |
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idCondition.code Identification of the condition, problem or diagnosis Alternate namestype DefinitionIdentification of the condition, problem or diagnosis. 0..1 to account for primarily narrative only resources. CodeableConcept BindingIdentification of the condition or diagnosis. ?? (example)Mappings
|
bodySite | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCondition.bodySite Anatomical location, if relevant DefinitionThe anatomical location where this condition manifests itself. Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. May be a summary code, or a reference to a very precise definition of the location, or both. CodeableConcept BindingCodes describing anatomical locations. May include laterality. ?? (example)Mappings
|
subject | Σ | 1..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element idCondition.subject Who has the condition? Alternate namespatient DefinitionIndicates the patient or group who the condition record is associated with. Group is typically used for veterinary or public health use cases.
|
context | Σ | 0..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idCondition.context Encounter or episode when condition first asserted Alternate namesencounter DefinitionEncounter during which the condition was first asserted. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known". Reference(Encounter | EpisodeOfCare) Mappings
|
onset[x] | Σ | 0..1 | There are no (further) constraints on this element Element idCondition.onset[x] Estimated or actual date, date-time, or age DefinitionEstimated or actual date or date-time the condition began, in the opinion of the clinician. Age is generally used when the patient reports an age at which the Condition began to occur.
| |
onsetDateTime | dateTime | There are no (further) constraints on this element Data type dateTime | ||
onsetAge | Age | There are no (further) constraints on this element Data type Age | ||
onsetPeriod | Period | There are no (further) constraints on this element Data type Period | ||
onsetRange | Range | There are no (further) constraints on this element Data type Range | ||
onsetString | string | There are no (further) constraints on this element Data type string | ||
abatement[x] | I | 0..1 | There are no (further) constraints on this element Element idCondition.abatement[x] If/when in resolution/remission DefinitionThe date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.
| |
abatementDateTime | dateTime | There are no (further) constraints on this element Data type dateTime | ||
abatementAge | Age | There are no (further) constraints on this element Data type Age | ||
abatementBoolean | boolean | There are no (further) constraints on this element Data type boolean | ||
abatementPeriod | Period | There are no (further) constraints on this element Data type Period | ||
abatementRange | Range | There are no (further) constraints on this element Data type Range | ||
abatementString | string | There are no (further) constraints on this element Data type string | ||
assertedDate | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idCondition.assertedDate Date record was believed accurate DefinitionThe date on which the existance of the Condition was first asserted or acknowledged. The assertedDate represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified. The date of the last record modification can be retrieved from the resource metadata. dateTime Mappings
|
asserter | Σ | 0..1 | Reference(Practitioner | Patient | RelatedPerson) | There are no (further) constraints on this element Element idCondition.asserter Person who asserts this condition DefinitionIndividual who is making the condition statement. Reference(Practitioner | Patient | RelatedPerson) Mappings
|
stage | I | 0..1 | BackboneElement | There are no (further) constraints on this element Element idCondition.stage Stage/grade, usually assessed formally DefinitionClinical stage or grade of a condition. May include formal severity assessments. BackboneElement Constraints
|
evidence | I | 0..* | BackboneElement | There are no (further) constraints on this element Element idCondition.evidence Supporting evidence DefinitionSupporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. BackboneElement Constraints
|
note | 0..* | Annotation | There are no (further) constraints on this element Element idCondition.note Additional information about the Condition DefinitionAdditional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. Annotation Mappings
|