Shared Managament of Radiation Treatments
0.0.1-current - ci-build International flag

Shared Managament of Radiation Treatments, published by IHE Radiation Oncology Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/RO.SMRT/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

ToDo Actor

CapabilityStatement for Client Actor

Explain

  • blah
  • blah
ToDo Server Actor

CapabilityStatement for Server Actor.

Explain

  • blah
  • blah

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Approval Notification MessageHeader Profile

The Approval Notification MessageHeader Profile builds on the Notifications MessageHeader Profile and sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for SMRT approval notification messaging scenario. The event code is "notification-plan-approval" and the focus of the event is the provenance resource.
Notifications Bundle Profile

The Notifications Bundle Profile constrains the FHIR Bundle resource to the SMRT notification messaging framework.
Notifications MessageHeader Profile

The Notifications MessageHeader Profile sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for SMRT notification messaging using FHIR resources. It references the focus of the use case event or request as well as other information related to the action typically transmitted in a Bundle resource in which the MessageHeader resource instance is the first resource in the Bundle.
Planning Artifacts Notification MessageHeader Profile

The Planning Artifacts Notification MessageHeader Profile builds on the Notifications MessageHeader Profile and sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for SMRT planning artifacts notification messaging scenario. The event code is "notification-planning-artifacts" and the focus of the event are the planning artifacts.
SMRT Endpoint

SMRT Endpoint
SMRT ImagingStudy Profile

The SMRT ImagingStudy Profile defines expectations for the FHIR ImagingStudy resource to represent DICOM SOP Instances (such as RT (Ion) Plan, RT Structure Set, RT Dose, etc.) exchanged within SMRT workflows.
SMRT Plan Approval Provenance Profile

Represents the approval of a treatment plan. The profile is intended to be used as the focal resource of a FHIR Message Bundle conveying a Plan Approved event.
SMRT Plan ImagingStudy Profile

The SMRT Plan ImagingStudy Profile defines expectations for the FHIR ImagingStudy resource to represent a DICOM RT (Ion) Plan SOP Instance exchanged within SMRT workflows.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

DICOM Endpoint ConnectionType ValueSet
Plan Approval Activity ValueSet
RT Plan SOP Class ValueSet

DICOM SOP Classes allowed for RT Plan instances (RT Plan Storage and RT Ion Plan Storage).

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

DICOM Endpoint Connection Type

Concepts describing the connection types for DICOM endpoints.
Event Notification CodeSystem

Concepts describing the purpose of the SMRT Event Notification. Note these concepts are 'pre-coordinated' to represent the concept of notification message AND the event that triggers the notification.
Plan Approval Activity Codesystem

Concepts describing the activities related to plan approval.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Example DICOM Endpoint

An example of a DICOM endpoint.
Example Patient

The patient from which all the examples relate
Example Plan Imaging Study

Example of an Imaging Study for a DICOM RT Plan.