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.

ClinicalUseDefinition

An indication, contra-indication, interaction, adverse effect or warning for a pharmaceutical product. The structured SmPC on the FHIR side.

Purpose

ClinicalUseDefinition wraps a regulatory clinical fact associated with a medicinal product: indication, absolute or relative contra-indication, drug-drug interaction, pharmacovigilance-observed adverse effect, or warning. It is dimensioned to carry the FHIR equivalent of the SmPC (Summary of Product Characteristics) and is used by the EMA in the SPOR project (Substance, Product, Organisation, Referential).

Key elements

FieldTypeCardinalityRole
identifierIdentifier[]0..*External identifiers (SPOR PCID).
typecode1..1`indication`, `contraindication`, `interaction`, `undesirable-effect`, `warning`.
categoryCodeableConcept[]0..*Sub-category (e.g. moderate or severe interaction).
subjectReference(MedicinalProductDefinition | Medication | ...)[]0..*Concerned product, substance or device.
statusCodeableConcept0..1Status (current, retired, draft).
contraindicationBackboneElement0..1Detail when type=contraindication: disease, comorbidity, comedication.
indicationBackboneElement0..1Detail when type=indication: target disease, duration, comorbidity.
interactionBackboneElement0..1Detail when type=interaction: interacting substance, mechanism, effect.
undesirableEffectBackboneElement0..1Adverse effect detail: frequency, affected organ.
warningBackboneElement0..1General warning (at-risk population, pregnancy).

JSON example

json clinicalusedefinition-example.json
{
  "resourceType": "ClinicalUseDefinition",
  "id": "example-contraindication-aspirin",
  "type": "contraindication",
  "subject": [{
    "reference": "MedicinalProductDefinition/aspirin-300"
  }],
  "contraindication": {
    "diseaseSymptomProcedure": {
      "concept": {
        "coding": [{
          "system": "http://snomed.info/sct",
          "code": "37796009",
          "display": "Migraine syndrome"
        }]
      }
    },
    "comorbidity": [{
      "concept": {
        "coding": [{
          "system": "http://snomed.info/sct",
          "code": "13200003",
          "display": "Peptic ulcer"
        }]
      }
    }]
  }
}

Common pitfalls

  • Confusing `indication` and `subject.indication` (CarePlan): ClinicalUseDefinition is for regulation, CarePlan for patient follow-up.
  • Type=interaction without specifying the interacting substance: useless info.
  • Maturity 1 — the API may evolve before R6.