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.

FormularyItem

A line of an institutional formulary (drug list): referenced drug, status, prescribing restrictions.

Purpose

FormularyItem captures the listing of a drug in an institutional formulary — hospital, hospital pharmacy or insurer. The listing governs what may be prescribed and with which restrictions (specialist physician required, mandatory pharmacist validation, service restriction). It is the CPOE's upstream filter for dispensing and billing.

Key elements

FieldTypeCardinalityRole
identifierIdentifier[]0..*External identifiers.
codeCodeableConcept0..1Drug code (CIP, UCD, RxNorm).
statuscode0..1`active`, `entered-in-error`, `inactive`.

JSON example

json formularyitem-example.json
{
  "resourceType": "FormularyItem",
  "id": "example-formulary-aspirin",
  "identifier": [{
    "system": "https://hospital01.example.org/formulary",
    "value": "FORM-2026-00123"
  }],
  "code": {
    "coding": [{
      "system": "http://www.ansm.sante.fr/cip",
      "code": "3400938153317",
      "display": "Aspirine 500mg, comprimé"
    }]
  },
  "status": "active"
}

Common pitfalls

  • FormularyItem confused with MedicationKnowledge: Formulary is administrative; MedicationKnowledge is clinical-pharmacological.
  • No versioning: status changes without history make audits impossible.
  • Local-only drug code not linked to a national system (CIP, RxNorm): information silos.