Patient-level "Summary" Gleason score observation, representing the overall Gleason assessment of a patient's prostate cancer regardless of the specimen source. This is the primary Profile in the NPCR Gleason score observation family and the Observation a clinician would reference when answering "what is this patient's Gleason score?".

Source variables covered (4 NPCR Variabelbeskrivning variables, dual-role):

• D_GleasSakn → component:missingFlag
• D_GleasEtt → component:primaryGrade
• D_GleasTva → component:secondaryGrade
• D_GleasSa → component:gleasonSum

Relationship to source-specific Gleason observations: A Summary Gleason Observation (this Profile) is conceptually derived from one or more source-specific Gleason observations. FHIR's Observation.derivedFrom element represents this relationship, referencing instances of:

• NPCRGleasonScoreTargetedBiopsyObservation
• NPCRGleasonScoreSystematicBiopsyObservation
• NPCRGleasonScoreUnclearBiopsyObservation
• NPCRGleasonScoreTURPCystoObservation

Derivation logic (per NPCR INCA) — documented but outside this Profile's enforcement scope:

• D_Vavn = 1 (core needle biopsy): INCA automatically derives Summary from source observations by priority: first available of Systematic → Unclear → Targeted. When this Profile is used, derivedFrom should reference the chosen source.
• D_Vavn = 2 (Cystoprostatektomi) or 5 (TUR-P): Registrar directly enters Summary from the pathology report. derivedFrom may reference the corresponding NPCRGleasonScoreTURPCystoObservation, or the relationship may be implicit (Summary is the primary representation in these scenarios).

The derivation rule itself is implementation logic belonging to the INCA integration layer or a downstream transformation, beyond the scope of this pre-implementation feasibility study. This Profile provides the structural capability to represent both the Summary value and its derivation relationship; the derivation process is left to implementers.

Terminology binding — documentation gap (Observation.code): NPCR Informationsspecifikation §7 does not provide a section for Gleason score identification. Observation.code is Must Support but without fixed value or terminology binding, consistent with other NPCR observation profiles. Resource identification relies on meta.profile.

Rationale for a dedicated Summary Profile: Every NPCR-registered prostate cancer case has a patient-level Gleason assessment (when histopathology is available). Separating this from the source-specific observations allows clinical queries and downstream reporting systems to work with a single canonical Gleason value per patient, while preserving the ability to audit the underlying source data. This design aligns with FHIR's Observation.derivedFrom usage pattern ("Related resource that the observation is made from ... a transformation or translation of the source observations to the observation").