Radiation Oncology Workflow Exchange with HIS

1. Proposed Workitem: Radiation Oncology Workflow Exchange with HIS

• Proposal Editor: Sam Brain
• Editor: Sam Brain
• Date: N/A (Wiki keeps history)
• Version: N/A (Wiki keeps history)
• Domain: Radiation Oncology

2. The Problem

This use case addresses three areas where problems arise because of lack of information exchange between the Radiation Oncology Information System (ROIS) and the Hospital Information System (HIS). These are: (1) Patient Registration, (2) Billing, and (3) Radiation Oncology scheduling and treatment summary.

1. Patient Registration. During the Radiation Oncology clinical process, clinical staff typically enter patient demographic data multiple times. For example: into the ROIS at the patient's initial visit to the Radiation Oncology department; at the imaging modality; at the treatment planning workstation.

The patient information is often read manually from patient demographics displayed by the HIS application, and then typed into the Radiation Oncology application, a time-consuming and error-prone process.

In addition, if any of the patient's information changes in the HIS (for instance, medical record number), there is no well-defined mechanism for propagating those changes to the ROIS.

2. Billing. Billing information is often generated when scheduled procedures are manually or automatically completed, for example at modality, simulator, or accelerator. The billing information is stored in the Archive.

The billing staff extract this billing information from the Archive, review it for accuracy, and enter it manually into the Hospital Billing system, often a component of the HIS.

This method of manual data entry is error-prone and such errors can lead to loss of revenue or cause the claim to be queried or refused by the medical insurance provider.

3. Rad Onc schedule, and Treatment summary. The schedule of Radiation Oncology treatments reside only in the Archive Actor, and are not available to other departments on the hospital. This can lead

3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>

<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>

4. Standards & Systems

Existing HL7 transactions types for ADT and Billing

5. Discussion

This use case is similar to proposal Radiation Oncology Schedule Work Flow (ROSWF) (from IHE-JRO)

<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>

<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>

<What are some of the risks or open issues to be addressed?>

<This is the brief proposal. Try to keep it to 1 or at most 2 pages>