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.

MedicationKnowledge — Drug knowledge base

The pharmaceutical reference seen by pharmacists and drug databases (First Databank, Multum, Lexicomp, Vidal, BCB, Thésorimed): monograph, indicative dosing, contraindications, costs.

Purpose of the resource

MedicationKnowledge describes a medication as it exists in theory: its monograph, routes of administration, typical dosing, contraindications, price, generic equivalents and required monitoring. It is the FHIR analogue of a drug monograph card in a medication database.

It does not represent a physical drug in stock: for that, see Medication. MedicationKnowledge serves as a canonical anchor reused by Medication, MedicationRequest and MedicationDispense for code consistency.

Key fields

FieldTypeCardinalityRole
identifierIdentifier[]0..*Business identifiers (CIS, CIP, NDC, GTIN).
codeCodeableConcept0..1Drug code (RxNorm, ATC, CIS, SNOMED CT).
statuscode0..1active | entered-in-error | inactive.
authorReference(Organization)0..1Source of knowledge (Vidal, BCB…).
intendedJurisdictionCodeableConcept[]0..*Jurisdictions targeted.
namestring[]0..*Commercial synonyms.
relatedMedicationKnowledgeBackboneElement[]0..*Links (generic, brand, therapeutic equivalent).
associatedMedicationReference(Medication)[]0..*Medications associated to the catalogue.
productTypeCodeableConcept[]0..*Product type.
monographBackboneElement[]0..*Monograph (attached DocumentReference).
preparationInstructionmarkdown0..1Preparation instructions.
costBackboneElement[]0..*Cost by jurisdiction / plan.
monitoringProgramBackboneElement[]0..*Surveillance programmes (REMS…).
indicationGuidelineBackboneElement[]0..*Indications and indicative dosing.
medicineClassificationBackboneElement[]0..*ATC, EPC, MoA classifications.
packagingBackboneElement[]0..*Available packagings.
regulatoryBackboneElement[]0..*Regulatory status by authority.
definitionalBackboneElement0..1Definition: composition, doseForm, route.

JSON example

json medicationknowledge-example.json
{
  "resourceType": "MedicationKnowledge",
  "id": "example",
  "code": {
    "coding": [{
      "system": "http://www.nlm.nih.gov/research/umls/rxnorm",
      "code": "476040",
      "display": "Acetaminophen 500 MG Oral Tablet"
    }]
  },
  "status": "active",
  "doseForm": {
    "coding": [{
      "system": "http://snomed.info/sct",
      "code": "385055001",
      "display": "Tablet"
    }]
  },
  "intendedRoute": [{
    "coding": [{
      "system": "http://snomed.info/sct",
      "code": "26643006",
      "display": "Oral route"
    }]
  }],
  "indicationGuideline": [{
    "indication": [{
      "concept": {
        "coding": [{
          "system": "http://snomed.info/sct",
          "code": "25064002",
          "display": "Headache"
        }]
      }
    }]
  }]
}

MedicationKnowledge vs Medication

AspectMedicationKnowledgeMedication
NatureKnowledge, monographInstance, batch, presentation
SourceDrug database (Vidal, RxNorm, FDB)Pharmacy stock, prescription Bundle
BatchesNoYes (batch)
CostTheoretical catalogueNot in Medication
Referenced byMedication, MedicationRequestMedicationRequest, MedicationDispense, MedicationAdministration

Common pitfalls

  • Code without system — always qualify RxNorm, ATC, CIS, CIP.
  • Confusion with Medication — do not store a batch here.
  • Monograph as plain text — prefer a DocumentReference with controlled MIME type.