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.
-
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.
NPCR_Pathology_Diagnostic_Report
Pathology diagnostic report aggregating all biopsy-derived observations for prostate cancer registration (Anmälan). This profile is the first DiagnosticReport profile in the NPCR profile set, differing from the 20 existing Observation/Procedure/Condition/ServiceRequest/Encounter/Patient profiles by grouping multiple observations under a single pathology report instance.
Source variables covered (4 NPCR Variabelbeskrivning variables):
- D_PrepNr → .identifier.value (PAD/CYT-nr, text business identifier)
- D_PrepAr → .effective[x] (dateTime, year precision representing Preparatår — the year the specimen was registered at the pathology lab)
- D_PatCytLista → .performer (Reference to Organization; Organization.name carries the pathology department name per NPCR Värdedomän)
- D_PatCytKod → .performer (Reference to Organization; Organization.identifier.value carries the pathology department code)
Note on D_PatCytAvd exclusion: The NPCR variable D_PatCytAvd (free-text pathology department name) has Teknisk giltighetstid 2025-09-30, i.e., it was deprecated in September 2025 per the Variabelbeskrivning changelog ("AH 20250930: Sätter ett slutdatum. Finns inte i koden längre."). This profile reflects the post-deprecation state and does not map D_PatCytAvd.
Aggregation design .result references: .result uses FHIR's multiple-targetProfile pattern to reference any of 9 NPCR Observation profiles that can be derived from a pathology specimen: 3 BiopsyResults profiles (Targeted, Systematic, Unclear), 5 Gleason profiles (Summary, Targeted, Systematic, Unclear, TURP/Cysto), and WHOGrade. This creates the first explicit inter-profile dependency in the NPCR profile set, representing NPCR's "one-report → many-observations" clinical model.
Design rationale .code binding (documentation gap fallback): FHIR R4 mandates DiagnosticReport.code (1..1), but NPCR documentation does not specify a terminology binding for pathology report identification. This profile applies LOINC 60568-3 "Pathology synoptic report" as an internationally recognized, domain-appropriate fallback. This pattern, bridging NPCR documentation gaps with FHIR-recommended terminology, is consistent with other NPCR profiles in this set (e.g., Observation.category using FHIR observation-category CodeSystem).
Design rationale .category binding: .category uses HL7 v2 Table 0074 (Diagnostic Service Section ID) code "PAT" (Pathology), which is FHIR R4's default CodeSystem for the diagnostic-service-sections ValueSet bound to DiagnosticReport.category.
Design rationale radiology/pathology asymmetry (Discussion finding): The NPCR profile set currently includes this pathology DiagnosticReport profile but no corresponding radiology DiagnosticReport profile, because NPCR captures explicit pathology report metadata (PAD/CYT-nr, Preparatår, Patologavdelning) enabling report-level aggregation, whereas no analogous radiology report metadata exists in NPCR Anmälan (only D_MRdatum, insufficient for report identification). This asymmetry is a documented feasibility finding.
Conditional requirements (per NPCR Beteende/logik) — documented but not enforced:
- D_PrepNr, D_PrepAr, D_PatCytLista are obligatoriskt when D_Diagr != 1 (i.e., when diagnosis involves pathology)
- D_PatCytKod is obligatoriskt for monitors when D_Diagr != 1
- type Profile on DiagnosticReport
- FHIR R4
- status Draft
-
version...
The canonical from this resource does not match any claims.