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_ProposeCondition_In
Parameters wrapper for the Condition/$propose operation (write-back of an ICD-10-GM diagnosis into the PVS). Carries exactly one Mxx_HealthHub_Condition instance in the 'resource' slice plus explicit context parameters: the submitting partner system ('proposingSystem', 1..1), the performing physician ('performer', 1..1), an optional pre-read case ('account', 0..1, a Schein previously read via Account/$searchScheine), the optional billing context ('versicherungsart' / 'versorgungsform') that refines the case matching, the mandatory diagnosis category ('diagnosisType', D/DD/DAN), an optional transient worklist hint for the physician ('worklistHint') and an optional partner-generated idempotency/correlation key ('requestId'). The supplementary diagnosis explanation (Diagnoseerlaeuterung) is not a parameter: it is carried on the embedded Condition as Condition.note (persisted diagnosis content, round-trips via SearchConditions). PVS user and establishment are derived from the context tokens (X-USER-CONTEXT / X-SYSTEM-CONTEXT) and are not part of the body. This same wrapper is used for both create (type-level $propose) and update (instance-level $propose on Condition/{id}): on an update only the allow-list fields apply and the create-only case-matching context ('account', 'versicherungsart', 'versorgungsform') is rejected with 400 (locked fields) because the case is already linked.
- type Profile on Parameters
- FHIR R4
- status Active
-
version1.5.0
This resource matches a canonical claim from this project.
Claim: https://fhir.medatixx.de/HealthHub