ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

Evidence — Statistical result of a PICO question

The elementary grain of a systematic review in FHIR: for a given PICO question, the observed statistical result, its confidence interval and its GRADE certainty.

Purpose of the resource

Evidence carries the formal statistical result of a research question framed as a PICO (Population, Intervention, Comparator, Outcome) model. It references the EvidenceVariable resources that define these components, declares the observed statistic (mean, OR, RR, HR), carries the certainty per GRADE, and indicates risk of bias.

Key fields

FieldTypeCardinalityRole
urluri0..1Canonical URL.
identifierIdentifier[]0..*Business identifiers.
titlestring0..1Title.
citeAs[x]Reference(Citation) | markdown0..1Recommended citation.
statuscode1..1draft | active | retired | unknown.
useContextUsageContext[]0..*Clinical context.
approvalDate | lastReviewDatedate0..1Quality cycle.
publisher | contact | author | editor | reviewer | endorserstring / ContactDetail[]0..*People & roles.
relatedArtifactRelatedArtifact[]0..*Related artefacts.
descriptionmarkdown0..1Description.
assertionmarkdown0..1Textual assertion.
variableDefinitionBackboneElement[]1..*Population, Exposure, Outcome (reference to EvidenceVariable).
synthesisTypeCodeableConcept0..1Statistical synthesis type.
studyDesignCodeableConcept[]0..*RCT, cohort, case-control.
statisticBackboneElement[]0..*Result (Mean, OR, RR, HR…).
certaintyBackboneElement[]0..*GRADE certainty.

JSON example

json evidence-example.json
{
  "resourceType": "Evidence",
  "id": "example-anticoag-stroke",
  "url": "http://example.org/Evidence/anticoag-stroke",
  "status": "active",
  "useContext": [{
    "code": {
      "system": "http://terminology.hl7.org/CodeSystem/usage-context-type",
      "code": "focus"
    },
    "valueCodeableConcept": {
      "coding": [{
        "system": "http://snomed.info/sct",
        "code": "266257000",
        "display": "Atrial fibrillation"
      }]
    }
  }],
  "variableDefinition": [{
    "variableRole": {
      "coding": [{
        "system": "http://terminology.hl7.org/CodeSystem/variable-role",
        "code": "outcome"
      }]
    },
    "observed": {
      "reference": "EvidenceVariable/stroke-event"
    }
  }],
  "statistic": [{
    "statisticType": {
      "coding": [{
        "system": "http://terminology.hl7.org/CodeSystem/statistic-type",
        "code": "C44256",
        "display": "Mean Difference"
      }]
    },
    "quantity": {
      "value": -0.47,
      "unit": "RR"
    }
  }],
  "certainty": [{
    "rating": {
      "coding": [{
        "system": "http://terminology.hl7.org/CodeSystem/certainty-rating",
        "code": "high",
        "display": "High quality"
      }]
    }
  }]
}

Linkage with GRADE

The certainty field is aligned with the GRADE methodology:

  • high — strong evidence, unlikely to change.
  • moderate — moderate evidence.
  • low — limited evidence.
  • very-low — very limited evidence.

Domains (Risk of Bias, Consistency, Precision…) are carried by certainty.rating.subcomponent.

Common pitfalls

  • Statistic without unit — RR/OR/HR must be explicit.
  • Incomplete variableDefinition — at minimum, Population and Outcome are required for a valid PICO question.
  • Certainty without rationale — prefer to decompose into GRADE sub-domains.