Onconova Implementation Guide
0.2.0 - ci-build

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

CapabilityStatement: Onconova FHIR REST Server Capability Statement

Official URL: http://onconova.github.io/fhir/CapabilityStatement/onconova-capability-statement Version: 0.2.0
Draft as of 2025-09-25 Computable Name: OnconovaCapabilityStatement

Supports the retrieval of the mCODE Patient Bundle containing all relevant mCODE resources (provided by Onconova) for a given patient. It also supports CRUD interactions on all Onconova profiles defined in this Implementation Guide.

Raw OpenAPI-Swagger Definition file | Download

Onconova FHIR REST Server Capability Statement

  • Implementation Guide Version: 0.2.0
  • FHIR Version: 4.0.1
  • Supported Formats: json, application/fhir+json
  • Published on: 2025-09-25
  • Published by: Onconova

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement imports the CapabilityStatement mCODE Data Sender: Get Bundle for a Patient

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

As an mCODE-compliant server, the Onconova FHIR server SHALL:

  1. Support all profiles defined in this Implementation Guide.
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Return the following response classes:
    • (Status 400): Invalid parameter or data
    • (Status 401): Unauthorized request
    • (Status 403): Insufficient permissions
    • (Status 404): Unknown resource
    • (Status 405): HTTP method not allowed/supported
    • (Status 410): Deleted resource
    • (Status 500): Internal server error
  4. Support JSON source formats for all Onconova interactions.
  5. Identify the Onconova profiles supported as part of the FHIR meta.profile attribute for each instance.
  6. Support the searchParameters on each profile individually and in combination.

The Onconova FHIR server MAY:

  1. Support XML source formats for its interactions.
Security
  1. See the General Security Considerations section for requirements and recommendations.
  2. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.
  3. A server SHALL reject any requests with insufficient permissions by returning an HTTP 403 forbidden response code.
Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$mcode-patient-bundle

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCDSearches_include_revincludeOperations
Patienthttp://onconova.github.io/fhir/StructureDefinition/onconova-cancer-patientyyyy
ConditionSupported Profiles
  Primary Cancer Condition Profile
  Secondary Cancer Condition Profile		yyyy
ObservationSupported Profiles
  Tumor Marker Profile
  Cancer Risk Assessment Profile
  Genomic Variant Profile
  Tumor Mutational Burden Profile
  Microsatellite Instability Profile
  Loss of Heterozygosity Profile
  Homologous Recombination Deficiency Profile
  Tumor Neoantigen Burden Profile
  Aneuploid Score Profile
  Comorbidities Profile
  Lifestyle Profile
  ECOG Performance Status Profile
  Karnofsky Performance Status Profile
  Cancer Stage Profile
  TNM Stage Group
  Lymphoma Stage
  Imaging Disease Status Profile
  Vital Signs Panel Profile		yyyy
ProcedureSupported Profiles
  Surgical Procedure Profile
  Radiotherapy Summary Profile
  Tumor Board Review Profile
  Molecular Tumor Board Review Profile		yyyy
MedicationAdministrationSupported Profiles
  Medication Administration Profile		yyyy
AdverseEventSupported Profiles
  Adverse Event Profile		yyyy
FamilyHistorySupported Profiles
  Cancer Family Member History Profile		yyyy
EpisodeOfCareSupported Profiles
  Therapy Line Profile		yyyy
Base System Profile
Cancer Patient Profile
Profile Conformance
SHALL
Reference Policy
literal

Interaction summary
  • Supports create, read, update, delete.

Core FHIR Resource
Condition
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Primary Cancer Condition Profile
Secondary Cancer Condition Profile

Core FHIR Resource
Procedure
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Surgical Procedure Profile
Radiotherapy Summary Profile
Tumor Board Review Profile
Molecular Tumor Board Review Profile

Core FHIR Resource
MedicationAdministration
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Medication Administration Profile

Core FHIR Resource
AdverseEvent
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Adverse Event Profile

​Core FHIR Resource
FamilyHistory
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Cancer Family Member History Profile

Core FHIR Resource
EpisodeOfCare
Reference Policy
literal
Interaction summary
  • Supports create, read, update, delete.

Supported Profiles

Therapy Line Profile