IE Medication Events Implementation Guide
0.1.0 - Nostalgic IE (draft) Ireland flag

IE Medication Events Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Simplifier Publishing

Not yet published. This page describes how to publish this IG on Simplifier.net. The IG's author does the Simplifier steps: creating the project, uploading content and releasing a package. A released package version can never be deleted, only unlisted.

What gets published

Item Value
Package id nostalgic-ie.fhir.medication-events (the FHIR package specification reserves hl7.* for HL7; ADR-001)
Release name Nostalgic IE (draft)
Version from sushi-config.yaml (currently 0.1.0, draft)
FHIR version 4.0.1
Canonical https://hl7-ie.github.io/medication-events/fhir
Content conformance resources (profiles, extensions, the HIQA logical model, ValueSets, CodeSystems, NamingSystems) and every example
Dependencies listed in the bundle's package.json, taken from sushi-config.yaml (HL7 Europe Base, MPD and Extensions R4; IHE MPD; FHIR Extensions R4)

The IG Publisher site stays on GitHub Pages. Simplifier hosts the package.

The bundle

SUSHI output is not committed, so publishing starts from the Simplifier bundle, built from a fresh SUSHI run:

sushi .
python scripts/simplifier/build_bundle.py      # -> build/simplifier-upload.zip

CI builds it on every pull request and on main (the simplifier-bundle artifact). The script fails if the package id starts with hl7., if a dependency is missing from package.json, if two resources share an id, or if a conformance resource sits outside the canonical.

Upload from CI (Project ZIP API)

The Simplifier publish workflow (Actions tab, manual) builds the bundle from main, runs the gates the content depends on, and in upload mode sends the conformance resources and examples to a Simplifier project with PUT https://api.simplifier.net/<project>/zip, authenticated with a token from POST https://api.simplifier.net/token. The default mode, dry-run, only builds and attaches the zip.

One-time set-up in the repository settings:

Setting Value
Environment simplifier, with required reviewers, so every upload is approved
Environment secrets SIMPLIFIER_EMAIL, SIMPLIFIER_PASSWORD (an account with write access to the project; a dedicated account is best)
Repository variable (optional) SIMPLIFIER_PROJECT: the project's URL key

The same upload runs locally: python scripts/simplifier/upload_project_zip.py <project> [--upload], with the credentials in the environment.

For a Simplifier Team plan, the Simplifier sync branch workflow instead pushes the bundle to a simplifier-sync branch that Simplifier's GitHub integration can import.

Release (manual, in Simplifier)

Simplifier has no API for creating a package ("It is not possible to create a package using the API"), and a released version is permanent, so releasing stays a deliberate manual step:

  1. In the project's Dependencies, add every package in the bundle's package.json, at the same versions.
  2. Run Simplifier's quality control and fix anything it reports.
  3. Releases → Create → Create new package: name nostalgic-ie.fhir.medication-events, version as in sushi-config.yaml, marked prerelease. The release notes say it is a proof of concept, not endorsed by HIQA, the HSE, HL7 Ireland or HL7 Europe, and not for clinical use.

Simplifier lists a project under a country, and returns its package in search, only after a package is released.

Sources: FHIR package naming · Simplifier packages · Simplifier API