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
-
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.
- Set as file A
- Set as file B
- A: not set
- B: not set
- Compare A ↔ B
- Clear selection
Mxx_HealthHub_ProposeConditionOutcome
OperationOutcome returned by Condition/$propose when a proposal is routed to the practice worklist (HTTP 202) and, in the exception case of automatic filing despite a triggered coding rule, as the optional 'outcome' part of Mxx_HealthHub_ProposeCondition_Out (HTTP 201). Carries exactly one issue with issue.code fixed to 'informational'. issue.severity is 'information' for a plain worklist acceptance and 'warning' only when a coding-rule hint was triggered; in the latter case issue.diagnostics carries the fixed placeholder text ('Zur Diagnose liegt ein Kodierregelhinweis vor, bitte im PVS pruefen.') - never the actual hint text - and issue.details.coding carries the machine-readable IDs of the triggered coding rules (references into Mxx_HealthHub_CS_Kodierregel, not the hint text) so the partner can react to or look up a rule. On the 202 worklist response there is no conditionId to correlate on, so a partner-supplied requestId is echoed back via the optional Mxx_HealthHub_RequestId extension.
- type Profile on OperationOutcome
- FHIR R4
- status Active
-
version1.5.0
This resource matches a canonical claim from this project.
Claim: https://fhir.medatixx.de/HealthHub