Skip to content

Contribution Channels

Archived contribution channels

The Health-RI Semantic Interoperability Initiative has been discontinued. The contribution channels documented on this page are no longer active project intake mechanisms. New submissions are not reviewed, curated, or integrated into project releases.

This page is retained to document how contributions were organized during the active initiative. See Initiative Status.

Outside specific Calls for Community Review, the initiative accepted several types of structured community input.

Report an Error in the OntoUML or gUFO Ontology

Contributors could report errors, inconsistencies, ambiguities, or omissions in HRIO artifacts, including diagrams, models, and OWL files.

Typical reports included:

  • incorrect use of stereotypes or relations;
  • mislabeled or ambiguous classes;
  • discrepancies between diagrams and OWL implementation; and
  • logical contradictions or violations of ontological principles.

Request a New Concept to Be Added

Contributors could propose concepts that they considered missing from the Health-RI Ontology (HRIO).

Requests were expected to include, where possible:

  • a clear label and definition for the proposed concept;
  • its relevance within the Health-RI context; and
  • references, standards, or examples supporting the need for the concept.

Other Contributions or Collaboration Requests

A general-purpose contribution route covered documentation suggestions, collaboration offers, use-case proposals, and questions about modeling and alignment.

Examples included:

  • proposing a new use case to guide modeling efforts;
  • requesting clarification about specific OntoUML patterns;
  • suggesting improvements to model documentation; and
  • offering to align a dataset with the Health-RI Ontology (HRIO).

Contribute SSSOM Mappings

During active development, candidate additions to the manually curated Health-RI SSSOM mapping set could be submitted through a structured GitHub Issue form or an Excel template.

Archived mapping assistant

The HRIO Mapping Assistant (GPT) was provided as an optional drafting aid for candidate predicates, targets, and evidence snippets.

If the assistant remains accessible, treat it as archived and non-maintained. Its outputs are not reviewed or integrated by this discontinued initiative.

The historical mapping workflow required compliance with the Mapping Set documentation and Mapping Governance, including role separation, validation, provenance, and supersession rules.

Historical submission checklist

  • All mandatory fields were present and correctly formatted.
  • Optional values, when provided, used valid identifiers (e.g., ORCID IDs, resolvable URIs, SEMAPV terms).
  • When pinning a version, object_source used a specific version URI rather than a generic/latest URI.

Submission Process

The forms used during the initiative guided contributors through required fields, and submissions were publicly visible as GitHub Issues.

Existing submissions remain part of the repository history, but no new review, response, integration, or release commitment applies after discontinuation.