ARIA OIS For Medical Oncology 15.5 Customer Release Note

ARIA Oncology
Information System for

Medical Oncology
CUSTOMER RELEASE NOTE
Version 15.5
P1026016-003-C APRIL 2018
L4472 Rev 06
Document ID P1026016-003-C
Document Title ARIA Oncology Information System for Medical Oncology Customer Release Note
Abstract This document provides immediate release information for using ARIA Oncology
Information System for Medical Oncology Version 15.5. This document is the English-
language original.
Manufacturers Varian Medical Systems, Inc.

3100 Hansen Way
Palo Alto, CA 94304-1038
United States of America
Notice Information in this release note is subject to change without notice and does not
represent a commitment on the part of Varian. Varian is not liable for errors contained
in this release note or for incidental or consequential damages in connection with
furnishing or use of this material.
This document contains proprietary information protected by copyright. No part of this
document may be reproduced, translated, or transmitted without the express written
permission of Varian Medical Systems, Inc.
FDA 21 CFR 820 Quality Varian Medical Systems, Oncology Systems products are designed and
System Regulation manufactured in accordance with the requirements specified within this federal
(cGMPs) regulation.
EU REACH SVHC Disclosure The link to the current EU REACH SVHC disclosure statement is:
http://www.varian.com/us/corporate/legal/reach.html
HIPAA Varian’s products and services are specifically designed to include features that help
our customers comply with the Health Insurance Portability and Accountability Act of
1996 (HIPAA). The software application uses a secure login process, requiring a user
name and password that supports role-based access. Users are assigned to groups,
each with certain access rights, which may include the ability to edit and add data or
may limit access to data. When a user adds or modifies data within the database, a
record is made that includes which data were changed, the user ID, and the date and
time the changes were made. This establishes an audit trail that can be examined by
authorized system administrators.
UMLS Vocabularies, terms and codes used within ARIA® are sourced from the National
Library of Medicine UMLS® Metathesaurus® project. ARIA® currently uses the
2009AA Release from 05/12/2014 and restricts use of the UMLS® Metathesaurus®
vocabularies to Licensing Category 0/1 or SNOMED vocabularies.
More information about the UMLS® Metathesaurus project, including relevant
licensing agreements and vocabularies may be viewed using the links below:
Primary UMLS® Information Site: http://www.nlm.nih.gov/research/umls/
License Agreement for Use of the UMLS® Metathesaurus®:
https://uts.nlm.nih.gov/help/license/LicenseAgreement.pdf
Varian Medical Systems, Inc. in no way indicates or implies that the National Library
of Medicine or any of the organizations whose vocabulary, terms or code sources are
included in the UMLS have endorsed Varian or ARIA®.
Some material in the UMLS Metathesaurus comes from copyrighted sources of the
respective copyright holders. Users of the UMLS Metathesaurus are solely
responsible for compliance with any copyright, patent, or trademark restrictions and
are referred to the copyright, patent, or trademark notices appearing in the original
sources, all of which are hereby incorporated by reference.
SNOMED CT ARIA® includes SNOMED Clinical Terms® (SNOMED CT®) which is used by
permission of the International Health Terminology Standards Development
Organization (IHTSDO). All rights reserved. SNOMED CT® was originally created by
The College of American Pathologists. “SNOMED” and “SNOMED CT” are registered
trademarks of the IHTSDO.
2 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

WHO ICD-O codes and terms used by permission of WHO, from:
International Classification of Diseases and for Oncology (ICD-O), 3rd edition,
Geneva, World Health Organization, 2000.
ICD-10 codes and terms used by permission of WHO, from:
International Statistical Classification of Diseases and Related Health Problems,
Tenth Revision (ICD-10). Vols 1–3, Geneva, World Health Organization, 1992.
ICD-9 codes and terms used by permission of WHO, from:
International Statistical Classification of Diseases, Ninth Revision, Clinical
Modification (ICD-9_CM), World Health Organization’s Ninth Revision,
International Classification of Diseases, 1999.
Electronic labeling
This symbol on the label indicates that the Instructions for Use for the corresponding
product are available at www.MyVarian.com. Access the Instructions for Use in
electronic form by logging in with your assigned MyVarian user credentials.
In compliance with EU Commission Directive No 207 / 2012, Varian will send EU
customers a free printed copy of the Instructions for Use within 7 days. Use the
“Paper Document Request” form provided on the Varian webpage to order your copy.
CAUTION US Federal law restricts this device to sale by or on the order of a

physician.
Trademarks ARIA® Oncology Information System (OIS) for Medical Oncology, ARIA® Oncology
Information System (OIS) for Radiation Oncology, and Varian® are registered
trademarks of Varian Medical Systems, Inc. Microsoft® and Windows® are registered
trademarks of Microsoft Corporation. Power Builder® and Powersoft® are registered
trademarks, and InfoMaker™ is a trademark, of Sybase, Inc. and its subsidiaries.
UpToDate® is a registered trademark of UpToDate, Inc. Medi-Span® is a registered
trademark of Wolters Kluwer, Inc. Surescripts® is a registered trademark of
SureScripts LLC. All other trademarks or registered trademarks are the property of
their respective owners.
Copyright © 2016–2018 Varian Medical Systems, Inc.

All rights reserved. Produced in the United States of America.
ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 3

Contents
Introduction ....................................................................................................8
ARIA Oncology Information System for Medical Oncology ........................ 9
System Components / Compatibility ...................................................... 9
Recommended System Requirements ................................................. 10
Changes in ARIA OIS for Medical Oncology Database Hot Fix 2 from
the Previous Release ............................................................................. 10
E-Prescribing...................................................................................... 10
Changes in ARIA OIS for Medical Oncology Database Hot Fix 1 from
the Previous Release ............................................................................. 10
Communications ................................................................................ 10
Drug Administration ............................................................................ 10
Medication Orders .............................................................................. 10
Security .............................................................................................. 11
New Features and Enhancements in ARIA OIS for Medical Oncology
Version 15.5 ............................................................................................ 11
Australian Localization ....................................................................... 11
C-CDA................................................................................................ 12
Clinical Decision Support ................................................................... 12
Clinical Quality Measures ................................................................... 13
Data Export ........................................................................................ 14
Diagnosis ........................................................................................... 14
Direct Messaging ............................................................................... 15
Data Update ....................................................................................... 15
Emergency Access ............................................................................ 15
E-Prescribing...................................................................................... 16
External Oral Liquid Agents ................................................................ 18
Implantable Devices ........................................................................... 18
MIPS ACI Dashboard ......................................................................... 19
Patient Health Information .................................................................. 21
Patient Family History ........................................................................ 21
Patient Social History ......................................................................... 21
User Mapping Utility ........................................................................... 21
User Privileges ................................................................................... 22

Changes for ARIA OIS for Medical Oncology Version 15.5 from the
Previous Release ................................................................................... 22
Agenda............................................................................................... 22
Allergies ............................................................................................. 23
Communications ................................................................................ 23
Diagnosis ........................................................................................... 23
Dispensing ......................................................................................... 23
Documents ......................................................................................... 24
E-Prescribing...................................................................................... 26
Flow Sheet ......................................................................................... 27
Installation .......................................................................................... 27
Labels ................................................................................................ 27
Manager ............................................................................................. 27
Meaningful Use .................................................................................. 28
Medications ........................................................................................ 28
Open Patient ...................................................................................... 29
Patient History .................................................................................... 29
Patient Merge ..................................................................................... 29
Physician Orders ................................................................................ 29
Plan Management .............................................................................. 29
Plan Rules .......................................................................................... 30
Planner............................................................................................... 30
Plans .................................................................................................. 30
Provider Approval ............................................................................... 30
Providers ............................................................................................ 31
Quality Measures ............................................................................... 31
Questionnaires ................................................................................... 31
Regimens ........................................................................................... 31
Registration ........................................................................................ 32
Reminders.......................................................................................... 32
Reports .............................................................................................. 32
Security .............................................................................................. 33
Service Portal ..................................................................................... 34

Settings .............................................................................................. 34
Tests / Labs ....................................................................................... 34
Toxicities ............................................................................................ 34
Users ................................................................................................. 35
Known Issues for ARIA OIS for Medical Oncology Version 15.5 ........ 35
ADT .................................................................................................... 35
Agenda............................................................................................... 35
Allergies ............................................................................................. 35
Billing ................................................................................................. 35
Communications ................................................................................ 36
Correspondence................................................................................. 38
Custom Browser................................................................................. 38
Data Update ....................................................................................... 38
Diagnosis ........................................................................................... 39
Dispensing ......................................................................................... 39
Documents ......................................................................................... 40
Education / Counseling ...................................................................... 44
E-Prescribing...................................................................................... 44
Flow Sheet ......................................................................................... 45
Impression / Plan ............................................................................... 46
Journal ............................................................................................... 46
Labels ................................................................................................ 46
License............................................................................................... 46
Manager ............................................................................................. 46
Meaningful Use .................................................................................. 47
Medications ........................................................................................ 49
Online Help ........................................................................................ 51
Open Patient ...................................................................................... 51
Patient Check-In................................................................................. 52
Patient History .................................................................................... 52
Patient Merge ..................................................................................... 53
Patient Summary................................................................................ 53
Pharmacy ........................................................................................... 53

Physician Orders ................................................................................ 53
Plan Definition .................................................................................... 54
Plan Management .............................................................................. 54
Plan Questionnaires ........................................................................... 54
Plan Rules .......................................................................................... 55
Plan Schedule .................................................................................... 55
Planner............................................................................................... 55
Plans .................................................................................................. 55
Provider Approval ............................................................................... 56
Providers ............................................................................................ 56
Questionnaires ................................................................................... 56
Regimens ........................................................................................... 57
Registration ........................................................................................ 58
Reminders.......................................................................................... 58
Reports .............................................................................................. 58
Review of Systems ............................................................................. 59
Scheduling ......................................................................................... 59
Security .............................................................................................. 60
Settings .............................................................................................. 62
Tests / Labs ....................................................................................... 62
Toxicities ............................................................................................ 63
Users ................................................................................................. 63
Vital Signs .......................................................................................... 64
Contact Varian Customer Support .............................................................. 64

Introduction
The ARIA® Oncology Information System for Medical Oncology (ARIA OIS for MO) is a
software solution that provides the tools needed to manage administrative and
financial activities in the medical oncology department. The tools provided by the ARIA
OIS for MO software are: Disease Management, Chemotherapy ordering, Drug
Ordering, non-drug physician ordering, Pharmacy, Decision Support, Clinical Trials,
Health Assessment, Data Collection and Analysis, Charge capture, Report generation.
This publication provides an overview of changes and updates in this maintenance
release of ARIA OIS for MO only. For information and release notes on previous
releases please visit http://myvarian.com. We recommend that you print this file and
keep it with the product manuals.
WARNING This customer release note is intended for medical

oncologists, nurses, pharmacists and other medical
professionals who are qualified and properly trained users of
the above-mentioned software. The users must be familiar
with all functions, the consequences of all operations, and the
potential hazards involved.
This document uses the following visual cues to help you locate and find information:
WARNING A warning describes actions or conditions that can result in

serious injury or death.
CAUTION A caution describes actions or conditions that can result in

minor or moderate injury.
Notice A notice describes a practice not related to physical injury to

include equipment, data, and other issues.
Note A note describes information that may pertain to only some

conditions, readers, or sites.

Tip A tip describes useful but optional information such as a
shortcut, reminder, or suggestion, to help get optimal
performance from the equipment or software.
ARIA Oncology Information System for Medical

Oncology
This section describes the following for ARIA Oncology Information System for Medical
Oncology (ARIA OIS for MO):
• System Components / Compatibility
• Recommended System Requirements
• Changes in ARIA OIS for Medical Oncology Database Hot Fix 2 from the
Previous Release
• Changes in ARIA OIS for Medical Oncology Database Hot Fix 1 from the
Previous Release
• New Features and Enhancements in ARIA OIS for Medical Oncology Version
15.5
• Changes for ARIA OIS for Medical Oncology Version 15.5 from the Previous
Release
• Known Issues for ARIA OIS for Medical Oncology Version 15.5
System Components / Compatibility

This Customer Release Note describes the state of the software, which contains the
following components, and their compatibility:
ARIA OIS for MO Version 15.5 is compatible with the following ARIA OIS software in a
CCS environment:
 ARIA Oncology Information System (OIS) for Radiation Oncology Version 15.5
 Information Exchange Manager (IEM) Version 15.5
ARIA OIS for MO requires the following additional software:
 .NET 4.5.2 Framework
 Windows® Internet Explorer 11 or higher
Note ARIA OIS for MO version 15.5: This Complete EHR is 2015 Edition
certified by an ONC-ATCB (Authorized Testing and Certification
Bodies) and is compliant with the standards, implementation
specifications, and certification criteria adopted by the U.S. Department
of Health and Human Services (HHS) Secretary and meets the
definition of “certified EHR technology”. The certification is available at.
http://www.varian.com/ARIA/MOMU. This certification does not
represent an endorsement.by the U.S. Department of Health and
Human Services.

Recommended System Requirements
ARIA OIS for MO’s system requirements are maintained on Varian’s website at the
following location:
https://www.varian.com/oncology/products/software/information-systems/aria-medical-
oncology?cat=resources
Changes in ARIA OIS for Medical Oncology Database Hot Fix 2

from the Previous Release
E-Prescribing
In a previous release, the SPI that was sent in the header of the XML refill response
message was set based on the logged-in user (who must also be a prescriber). The
SPI that is sent in the header of the XML refill response message should be the
provider that is in the prescriber segment of the refill request message. Regardless of
which prescriber replies to the refill request, the SPI in the header should match the
prescriber in the prescriber segment from the refill request. This issue has been
resolved. DR 157295
Changes in ARIA OIS for Medical Oncology Database Hot Fix 1

from the Previous Release
Communications
In a previous release, users were not able to send a CCDA through the outbound
transition of care functionality. When the user selected a referred-by provider, a
message appeared indicating that the referred user did not have a direct address.
This issue existed for Medical Oncology-only users. This issue has been resolved. DR
156049
Drug Administration
In a previous release, the Lynx Mobile webservice was not functioning in 15.x
environments. This service is called by third parties to get drug and schedule data but
was never updated to use the application framework for 15.x, and therefore was
unable to connect to the database. This issue has been resolved. DR 155391
Medication Orders
In a previous release, there was a database error message that was displayed to the
user when accessing the medication history from the drug orders workspace. This
issue has been resolved. DR 155450

Security
In a previous release, the application version check that happens when the Medical
Oncology application is started, failed after 15.5 TPMS was installed. Instead of being
able to successfully launch Medical Oncology, the user saw a version mismatch error
message and the application closed. This issue has been resolved. DR 155449
New Features and Enhancements in ARIA OIS for Medical

Oncology Version 15.5
ARIA MO Version 15.5 New Main Features
General Modifications made in this release support the new criteria for the 2015
Edition of the MIPS/QPP program. This version of software complies with
necessary criteria as a certified electronic health record technology. For
more information about QPP, consult this webpage: https://qpp.cms.gov/
The AJCC 8th Edition

Although the Online Help and Instructions for Use refer to AJCC v8, this
functionality will be available in a hotfix release.
Australian Localization
Australian National Guidelines for Units of Measure & Frequencies

The Australian Commission on Safety and Quality in Health Care has released a set of
national guidelines for displaying clinical medicine information, such as frequencies
and units of measure. With the 15.5 release of ARIA OIS Medical Oncology, an
optional SQL script will be provided upon request which will update ARIA’s standard
listing of units of measure and frequencies to meet the guidelines outlined in the
national guidelines document. The SQL script may be applied at the request of any
customer utilizing FDB AUS and ARIA OIS for MO version 15.5 and later.
Treatment Tab Modifications

A new institution-specific configuration option has been added to ARIA Security that
will control the visibility of the Treatment tab checkbox next to pending or previously
ordered drugs that are not on the scheduled regimen.
Duplicate entries for additional ordered drugs have been removed from the Treatment
tab. Once an order for “Other” drugs has been placed for the treatment day on a
subsequent cycle, the ‘Not Ordered’ record will no longer be visible on the Treatment
tab. Only the record corresponding to the ordered drug will be visible, because the
drug will be in pending or ordered status.

Detailed Dose Recording Modifications
Header details have been modified to display dispensed details more clearly. If the
drug has been dispensed, the dispensed details appear under the drug followed by the
order details. The order details are prefixed with “Ordered”.
Additional validation logic has been added to the dose recording window, including
validation for inputting dose values larger than what was dispensed or ordered, and
validation logic for values entered that are less than zero. This logic includes user
options for saving or not saving dose amount messages upon confirmation.
Drug Administration Additional Details Modifications

To improve clarity of dispensed and ordered drugs in the drug administration area, two
modifications have been made to the details that are displayed in the Additional
Information window. If the selected drug has been dispensed, the dispensing details
are displayed first followed by the order details, and the order details are now prefixed
with “Ordered” instead of “Order”. D32723
C-CDA
C-CDA Sidebar
The C-CDA has been modified to provide better display customization. A new sidebar
allows users to customize the sections along with the order of the sections to be
displayed. The following new sections have been added to the C-CDA: Encounters,
Medical Equipment, Assessment, and Health Concerns. D15603
C-CDA Generation and incorporation

 This version includes a new Encounter attribute for a patient diagnosis that can be
assigned to represent the initial problem the patient presented. Selecting the
Encounter checkbox places the diagnosis in its own section of the C-CDA.
 When gender identity is selected for a patient, it is displayed as the birth sex for a
patient in the Social History section.
 For any drug related allergies, the ingredient is displayed along with the allergy. For
any diagnostic images, the narrative is displayed in the Results section.
 For any specimens collected with a test result, the specimen information is
displayed in the Results section.
 For any Inbound Transition of Care records, errors may be detected that will be
displayed on a new C-CDAs Error tab. D28500
Clinical Decision Support

For Clinical Decision Support rules, a new attribute is displayed that allows a user to
look up patient reference materials based upon the patient’s demographics,
medications and problems. The websites used are either Medline Plus or UpToDate®
(requires a paid subscription). D29004

Clinical Quality Measures
There are several changes for Quality measures in this release, including the following
additional Quality measures:
Measure Title Version
CMS 50 Closing the Referral Loop: Receipt of Specialist 5.0

Report
NQF 0018/CMS 165 Controlling High Blood Pressure 5.0
NQF 0022/CMS 156 Use of High-Risk Medications in the Elderly 5.1
NQF 0028/CMS 138 Preventive Care and Screening: Tobacco Use: 5.0
Screening and Cessation Intervention
NQF 0032/CMS 124 Cervical Cancer Screening 5.0
NQF 0034/CMS 130 Colorectal Cancer Screening 5.0
NQF 0069/CMS 154 Appropriate Treatment for Children with Upper 5.1
Respiratory Infection (URI)
NQF 0101/CMS 139 Falls: Screening for Future Fall Risk 5.0
NQF 0384/CMS 157 Oncology: Medical and Radiation - Pain Intensity 5.2
Quantified
NQF 0389/CMS 129 Prostate Cancer: Avoidance of Overuse of Bone Scan 6.0
for Staging Low-Risk Prostate Cancer Patients
NQF 0418/CMS 2 Preventive Care and Screening: Screening for 6.3

Depression and Follow-Up Plan
NQF 0419/CMS 68 Documentation of Current Medications in the Medical 6.1

Record
NQF 0421/CMS 69 Preventive Care and Screening: Body Mass Index 5.0
(BMI) Screening and Follow-Up Plan
NQF 2372/CMS 125 Breast Cancer Screening 5.0
 QRDA Category I (QRDA I) is an individual patient level report that contains quality
data for one patient for one or more eCQMs. This report has been updated to HL7
QRDA Category I, STU Release 3.1.

 QRDA Category III (QRDA III) is an aggregate quality report which contains quality
data for a set of patients for one or more eCQMs, advancing care information
measures, and/or improvement activities. This report has been updated to HL7
CDA® R2 Implementation Guide: Quality Reporting Document Architecture (QRDA
III), Release 1, STU Release 2 - US Realm.
New Feature: Import and Calculate

 Import and Calculate allows the user to import a data file for one or multiple patients
using a QRDA 1 report which is in the HL7 QRDA Category I, STU Release 3.1
format. Within ARIA, these codes are used to perform clinical quality measure
analysis and provide the ability for the user to export the cumulative summary as a
QRDA 3 using the HL7 CDA® R2 Implementation Guide: Quality Reporting
Document Architecture (QRDA III), Release 1, STU Release 2 - US Realm.
 There is a change to User Groups in Security and Data Admin related to quality
measures. Read Access and Full Access have been added for user rights in ARIA
Security.
Data Export
As part of Phase 3 of the ARRA HITECH Meaningful Use provisions, the Data Export
feature now includes the ability for users to schedule a data export event to run at a
predetermined time. This change adds additional search criteria to the Patient List
Query feature. This component is used by the Patient List and Patient Reminders
features.
Data Export Service

The Data Export Service is a Windows service installed as part of the Oncology
Services package.
When the service starts, it first checks for any exports that are marked as In Progress.
After any in-progress exports are completed, the service checks once per minute for
any scheduled export jobs that need to run. The Data Export Service will always ignore
purged, deleted, and test patients when searching for patient records. If Patient Data
Security is enabled, the service will filter the list of patients to export based on the user
who created the export job.
C-CDA Export
The C-CDA Export window now includes two new tabs for scheduling exports. The
export functionality allows users to schedule when the export shall occur: on a daily,
weekly or monthly basis. D28817
Diagnosis
 This release includes the ability to link one or more patient’s diagnoses or problems
to each prescribed agent in ARIA OIS MO. A user is now able to link one or more
diagnoses to each prescribed agent and remove a previously linked diagnosis from
a prescribed agent in the Drug Order workspace. A user can add, remove, and view
patient’s valid diagnoses or problems linked to prescribed agent in the Select

Diagnoses/Problems for the prescribed agent window, and can link or unlink a
patient’s valid diagnoses/problems to the selected prescribed agent. D32522
 This release includes a new Reconciliation Date for allergies and diagnoses. This
information provides the date of the last time a user reconciled this data for the
patient.
Direct Messaging
This release provides support for a provider to send and receive messages using the
Direct Edge Protocol.
Data Update
LOINC codes are required by ARIA for use in quality measures, vital signs, and lab
tests. To keep LOINC codes update to date, Data Update is used to load a full set of
LOINC codes. D28679
File Service Subfolder Repositories

Prior to this release, all documents that were either created or imported into ARIA OIS
Medical Oncology were saved in a single data directory located on the hospital’s
network.
With the release of ARIA OIS 15.5, modifications have been made to the File Server
web service that allow it to save files into and retrieve them from a subdirectory.
This modification to the File Server reduces the number of files within a single
directory.
The applications themselves are unware of the subdirectories and no longer need to
know where documents are being stored. Customers can change the directories for
new documents while still retrieving older documents. D31053
There is a new attribute in the header information of the patient document that allows a
user to identify whether the documentation was provided directly from the patient. This
new option is turned off by default until the user selects it.
For Equicare users, when a patient completes a questionnaire, a PDF copy will be
available as a patient-provided document.
Emergency Access
The Emergency Access feature of 2015 CEHRT requirements now require emergency
access privileges be available for appropriate users in case of an emergency. This
new feature allows a user to be a member of an emergency user group with
emergency access and elevated privileges. The emergency access group must be
configured for the individual user in Security (modify the user rights in the User
Registry). After configuration, the user can login in ARIA OIS MO with elevated rights
by selecting emergency access upon login. D31629

E-Prescribing
Design Modifications
 In ARIA OIS for MO, the notification icons in the Micro Help area at the bottom of
the application have been updated. A green pill capsule icon indicates there are
pending messages requiring action that are less than 24 hours old. A red pill
capsule icon indicates that there are pending messages requiring action that are
more than 24 hours old. A tooltip displays a count of the refill requests, change
requests, and age of the oldest message.
 The E-Prescribing message functionality has been updated to include three new
message types:
 RxFill messages from the Surescripts service will be available in the new
e-Prescribing History window when a user clicks the new yellow paper airplane
icon. These messages provide a snapshot view of the status of the e-
prescription, as well as the changes to that message over time. Statuses
include Not Dispensed, Partially Dispensed, and Completely Dispensed.
Information received also includes prescription refill and status of refills. When
“Denied – New Prescription to follow” is used, a notification shows the
prescription details of the new drug order.
 CancelRx messages may be automatically sent when a prescription that has
already been sent by e-Prescribing is errored or discontinued, if time has not
lapsed between the prescribed administration date and duration. The
prescriber will be presented with the option to send a CancelRx message to
the dispensing pharmacy to cancel the remainder of the prescription when
erroring or discontinuing an e-Rx order.
Once the message is sent, the pharmacy may send an Approved/Denied response
indicating the portion of the prescription that has been be cancelled. Alternatively,
a list of all errored or discontinued but sent e-prescriptions will be available in the
“Cancel Prescriptions” tab in the E-Prescribing Provider Queue and the Patient
Specific E-Prescribing Patient Summary windows. Cancel messages for previously
errored or discontinued prescriptions may also be initiated from the Cancel
Prescriptions tab using the Send Cancel button. Users who are discontinuing a
regimen will receive a notification that any sent e-prescribing PU-External drugs on
a scheduled regimen must be cancelled using the Send Cancel button in the e-
prescribing queue.
 RxChange messages are initiated by the outside pharmacy and appear in the
Change Requests tab. Types of RxChange message requests are:
 Prior Authorization –A pre-authorization number and comment are requested
 Generic Substitution –Up to 9 generic substitutions may be proposed
 Therapeutic Substitution –Up to 9 different changes may be proposed, or the
prescriber may make any change to any field and respond to the pharmacy
with those changes.
Prescribers may approve or deny proposed changes.
 Providers must be registered for the new e-prescribing routing message types in
ARIA MO Security upon upgrade to receive message notifications. This is

accomplished by updating the provider Surescripts registration to include the new
service levels for each institution where the provider is registered.
 The E-Prescribing Provider Queue has been updated to include new message
types and match the user interface used in ARIA for RO. The E-Prescribing
Provider Queue now has four tabs: Prescriptions, Refill Requests, Cancel
Prescriptions, and Change Requests. Each tab allows for a green or red pill capsule
icon to show the oldest age of message pending action. With this version of ARIA
MO, all tabs contain more columns available for each row so they match the
columns listed in the corresponding detail window. There are custom filters to select
date range and send statuses in agreement with the corresponding detail window.
 The patient-specific E-Prescribing Patient Summary window is now accessible in
the Medications area using a new E-Rx icon. This E-Rx icon is also available on the
toolbar. In addition, as with the Provider Queue, the Patient Specific E-Prescribing
Patient Summary window now has four tabs: Prescriptions, Refill Requests, Cancel
Prescriptions, and Change Requests. Each tab allows for a green or red pill capsule
icon to show the oldest age of message pending action. With this version of ARIA
MO, all tabs contain more columns available for each row so they match the
columns listed in the corresponding detail window. There are custom filters to select
date range and send statuses in agreement with the corresponding detail window.
 A new column, “Source”, has been added to the E-Prescribing Provider Queue, E-
Prescribing Drugs, E-Prescribing Refill Requests windows, and the patient-specific
E-Prescribing Patient Summary for the CCS environment. The column displays an
icon indicating whether a prescription or refill was originally created in another
application, such as prescriptions or refills created in ARIA OIS RO. These drug
orders can only be modified in the originating application. (Ref# D32046)
 In Security, options are now provided for an administrator to select a list of users
who are authorized to follow a provider’s e-Prescribing messages, or an
administrator can select a specific provider to be followed by a list of specific users
who need to see that provider’s’ notifications for e-Prescribing. A history of who has
been following that provider is available. When a user who is following multiple
providers’ e-prescribing messages opens the E-Prescribing Provider Queue, they
can view “Following Providers” in the menu along with an icon that opens a list of
providers that have been selected.
Attaching Diagnoses to e-Prescriptions

Users can now attach multiple Diagnoses to any prescribed agent using a new Dx icon
next to the agent selection area. The first two diagnoses will be sent with the e-
Prescribing message. All diagnoses will be saved to the patient prescription record.
These diagnoses may be printed on custom prescription printouts for Internal, PU-
Internal, and PU-External prescriptions.
E-Prescribing Surescripts Medication History

This release of ARIA OIS for MO allows users to query the Surescripts network to
retrieve the patient medication history and dispensing history. The Prescriber or
Attending/Primary provider must be registered for e-prescribing at the institution in
ARIA Security to view the Medication History button and window, and the patient must
provide consent to use this functionality. The registered user will receive a notification

and the ability to indicate that consent was received upon launching the Surescripts
Medication History window.
The Surescripts MedHx button is available in the Medication History window/tab, the
Modify Prescriptions window, and Pharmacy Dispensing window. The Surescripts
Medication History window displays previously dispensed drug details, including
quantity, last fill dates, prescriber names, and pharmacy information.
E-Prescribing Eligibility, Formulary, and Benefits

 This release allows a user to query the Surescripts network to retrieve the patient’s
list of payors for medications, and the respective formulary and benefit information
for each payor. The institution must be set to view the payors and benefits
information, and the prescriber or attending/primary provider must be registered for
e-prescribing at the institution in ARIA Security, to view this information. D26298
 The payor, formulary, and benefits information is searchable and modifiable in any
drug ordering or pharmacy dispensing workflow where the Agent Selection window
is available. Formulary and benefits information is available for all Internal, PU-
Internal, and PU-External drugs, and will be attached to the outgoing messages for
drugs that are e-prescribed. The list of eligible payors applicable to both the
Provider and the Patient are listed for selection in a menu. Once a payor is
selected, the list of drugs with formulary preference and benefits information is
displayed with a list of alternative medications provided by either the payor or in the
Medi-Span Drug Database. Once the prescription is approved, the payor and
benefits for the drug selected will remain attached to the prescription and may be
viewed in the Dose Specification window. Payor and benefits information may be
printed on custom prescription printouts for Internal, PU-Internal, and PU-External
prescriptions. D26653
External Oral Liquid Agents

For 2015 CEHRT certification, when a provider who is registered for e-prescribing
places an external order for an agent that has both a liquid form and an oral route, the
selected units of measure must be milliliters (mL). A setting in ARIA Security enforces
this requirement. By default, this setting is turned on when there is at least one
provider who is registered as e-prescribing for an institution or hospital. D32967
Implantable Devices
This release allows users to enter and access a list of implantable devices for a patient
with a Unique Device Identifier (UDI), and retrieve information about the device from
the Global Unique Device Identification Database (GUDID). ARIA MO will look up
device information and automatically populate these fields from the FDA’s GUDID
website when a user enters the UDI associated with the patient’s implantable device.
D26063

MIPS ACI Dashboard
ARIA Security Changes

The new MIPS ACI dashboard can be accessed using File > MIPS ACI Dashboard
and supports the ACI and ACI Transition QPP programs.
 The compliance period registry has been updated to support group reporting and
TIN reporting. Older programs for Meaningful Use stage 1, 2, and modified stage 2
are now available in read-only mode (data cannot be updated). These programs
can be set to inactive as desired.
 Some activities like e-prescribing and transition of care must be associated with an
institution to determine under which compliance period/TIN group the activity falls.
By default, the institution is set to the logged-in institution for E-Rx activities, and all
others are set to the patient’s location.
Note Approved drug orders and transitions of care in the 2018 reporting
period completed prior to the v15.5 upgrade will be defaulted to
the visit location on the patient’s last appointment.
 ARIA MO 15.5 Security provides a new user preference setting to include or
exclude EPCS in e-prescribing calculations for the MIPS ACI and ACI Transition
dashboards.
General
 ARIA MO and RO 15.5 do not support any of the Public Health Registry reporting
measures.
 There is a new reconciliation date for allergies and diagnosis. This information
provides the date of the last time a user reconciled this data for the patient.
 The new MIPS ACI dashboard now supports advanced practitioner users. Staff
configured as Advanced Practitioners in Security can now compare their
performance against ACI and ACI transition measures in the MIPS ACI dashboard.
 The MIPS ACI dashboard includes a Refresh button to refresh data on the MIPS
ACI and ACI Transition compliance periods on demand. The Refresh button is
controlled by the Full Access user right to the Meaningful Use dashboard.
MIPS ACI Dashboard

 There are two new dashboards available that can be configured: ACI Transition
Measures, and ACI Measures.
 The dashboards can be configured in ARIA MO Security as a Group reporting
compliance period or individual reporting compliance period. A TIN (Tax ID
Number) can be assigned to a compliance period, which can be used for group
reporting purposes.
 The dashboard Performance tab displays the base, bonus, performance, and total
ACI scores for the group or selected provider.
 The dashboard Manual Entry tab displays the binary (yes/no) measures required for
the ACI Transition/ACI programs, but may not be automatically calculated by the
software. A user can record whether these measures have been met, and the ACI /

ACI Transition scores are updated accordingly. As an example, this includes
Security Risk Analysis, Registry reporting, and CEHRT Improvement activity.
 The dashboard header information displays the installation dates of the 2015
CEHRT version and the 2014 CEHRT version. The 2014 CEHRT version is
displayed for ACI Transition compliance periods and can be configured in Data
Admin.
Note Compliance periods that have been setup for older CMS programs
(Meaningful Use stage 1, stage 2, Modified stage 2) will now be
available in read-only mode. New compliance periods cannot be
created for older CMS programs, as only ACI Transition and ACI
are supported moving forward.
MIPS Calculation Update

There has been an update to calculation of the following measures in the ACI
transition and ACI programs:
 Patient-provided education
The ACI Transition measure requires that the provider use the CEHRT to identify
patient-specific education resources and provide access to the materials no earlier
than the first day of the calendar year and no later than the last day of the calendar
year of the performance period. The ACI measure requires that the provider use
the CEHRT to identify patient-specific education resources and provide electronic
access to the materials during the reporting/performance period.
 View/Download/Transmit
The ACI and ACI transition measures now require the patient be able to view,
download, or transmit their health information via API during the performance
period to populate and record the numerator.
 Clinical Information Reconciliation
This ACI measure now requires that medications, allergies, and
problems/diagnoses be reconciled for transitions of care received for a patient. This
measure requires that reconciliation be performed no earlier than the first day of
the calendar year of the reporting period and no later than the last day of the
reporting/performance period.
 Patient Electronic Access
 This ACI transition measure is computed on portal access provided to the
patient within 4 business days of their encounter with the provider during the
reporting period.
 This ACI measure will be computed on portal access provided to the patient
within 2 business days of their encounter with the provider during the reporting
period.
Note The work week is assumed to include Monday through Friday and
exclude weekends (Saturday/Sunday). The software does not
account for holidays.

Patient Generated Health Data
 This is a new measure for the ACI program. The measure can be met by including
any patient-specific document in the Documents workspace, inserting a patient-
provided link in the Communications workspace, or any patient-provided
document/questionnaire sent to ARIA from a patient portal.
 Within certain workspaces (Drug orders, Transition of Care), there is a selection for
a MIPS reporting location. QPP (Quality Payment Program) participants may need
to select a value so that the appropriate function is captured for the ACI (Advancing
Care Information) and ACI Transition measures. This action ensures providers get
credit when reporting for attestation purposes for QPP.
Patient Health Information

The Patient Health Information Capture feature allows users to identify, record, and
access information directly and electronically that was shared by a patient or an
authorized representative, and reference and link to patient health information
documents. Patient-provided documents can be marked as such in the Notes
workspace. D30989
Patient Family History

The first-degree familial relation can now be mapped to SNOMED codes. SNOMED
codes have been added to the familial relation table for first-degree familial relations.
However, these are not accessible in the front end. The family health history data that
is associated with patients is mapped back in the database to the familial relation table
that has SNOMED codes for the first-degree familial relations. D32158
Patient Social History

The social history window now includes a field where users can record the last time a
patient’s smoking status and alcohol use was reviewed. These dates, referred to as
the smoking last screened and alcohol last screened dates, can be modified by the
user and are intended to be used as a reference in day-to-day operations.
When a patient’s smoking code or alcohol code is changed, the corresponding date
automatically updates to the current date, though it can be manually set again if
needed. These dates also appear in that patient’s summary, allowing users to view the
previous screening dates at a glance. D14570
The smoking and alcohol areas have been updated to provide better support for
calculation of when a patient began or quit these activities. The years will be updated
automatically for the user without any user intervention. D26784
User Mapping Utility

When upgrading to ARIA MO 15.5, users must be given Shared Framework accounts;
this can be done while linking them to existing Medical Oncology and Active Directory
accounts. For sites with large quantities of user accounts to manage, this requires a
significant amount of time be spent on manual account creation. The MO to AD User

Mapping Utility automates this workflow to a significant extent through the following
process:
 Identify and present the user with a list of existing MO accounts.
 Present existing, matching AD accounts as suggestions for linking.
 Allow the user to confirm which AD/MO account matches they want to create
associated SF accounts for.
 Programmatically create the SF accounts specified.
This utility is intended to be run after the upgrade process as a last step in transferring
users to the new environment. Prior to use of the MO to AD User Mapping Utility, the
SF to AD user mapping utility must be run and the Varian Database and SF upgrades
must be fully completed. D31768
User Privileges
There are new features added for auditing reports which are to comply with one of the
MIPS ACI DASHBOARD – Audit Reports. These are the changes to User Privileges:
 User’s User Group
The feature of displaying the changes to the user’s user group in Security enables
the user to view the auditing details of who accessed and made the changes to the
user’s user group.
 User Group’s Access
The feature of displaying the changes to user group’s access in Security enables
the user to view the auditing details of who accessed and made the changes to
user group’s access. D31046
 New User right for MIPS ACI Dashboard
There is a new Full access right added for the Meaningful Use Dashboard in v15.5.
This right should be checked for users that wish to refresh data on the dashboard.
Changes for ARIA OIS for Medical Oncology Version 15.5 from
the Previous Release
Agenda
 In a previous release, the agenda tasks (in Security) could be set up with longer
lengths than Manager supported on the Patient Agenda window. This issue has
been resolved. DR 134771
 In a previous release, Agenda items could be displayed twice for the following
items: Current Medications, Gyne History, Chief Complaint/HPI, and
Plan/Impression. This issue has been resolved. DR 146368
 In a previous release, the user received multiple error messages and subsequently
Manager crashed when clicking on 'Current Medications' task in Patient Agenda.
This issue has been resolved. DR 154007

Allergies
In a previous release, the adverse reaction icon did not appear on the Treatment tab if
the character case of the adverse reaction did not exactly match the character case of
the agent (e.g. DOXOrubicin and Doxorubicin). The adverse reaction icon should
appear when the spelling is the same, regardless of the case. This issue has been
resolved. DR 148737
Communications
 In a previous release, users may have been rejected by ARIA when going to the
Patient Info Request and then selecting Print to print out a copy. This issue has
 In a previous release, the "Results" section of an outbound Transition of Care
included test components that did not have a result value entered for them. This
 In a previous release, a user could select the "Preferred" checkbox for one of the
providers’ email addresses, making it the default address for communication.
However, if this was done for their Direct address, email communication failed. This
was because Direct was not actually email, but a separate service provided by
HISPs to fulfill the ARRA HITECH standard. So, if Direct was selected as the
preferred address, emails sent by the system to that provider did not go through.
 In a previous release, the direct address had to be the "Preferred" email (in the
Modify User window) to be able to create/send a direct message. A Direct address
had to be checked off as "Preferred" for the provider, or else Direct Messages could
not be sent. This resulted in issues with EPCS registration. This issue has been
resolved. DR 142938
 In a previous release, direct messaging web service calls required the "Full Access
to Data Admin" user rights privilege in service portal. Users who did not have this
privilege saw an empty providers list when opening the messaging window, and
were not able to send secure/direct messages. The web service needed to be
updated with more appropriate user rights. This issue has been resolved. DR
153955
 In a previous release, the "Results" section of an outbound Transition of Care
included test components that did not have a result value entered for them. This
Diagnosis
In a previous release, there were spelling mistakes for "dx site message" in diagnosis
work space. This issue has been resolved. DR 147221
Dispensing
 In a previous release, if a user's direct address was selected as the "Preferred"
email address (on the Modify User window), email functions were disrupted. If

Direct was selected as the preferred address, emails sent by the system to that
provider did not go through. This issue has been resolved. DR 143161
 In a previous release, there were issues with incorrect diluent volume when
removing an agent from shared bag during dispensing. This issue has been
resolved. DR 143162
 In a previous release, the scroll bar was missing from the status menu in the
Pharmacy Dispensing window. Without a scroll bar, it was not obvious that there
were additional values. The values that were not visible were: Not Disp. - D/C,
Pending - D/C*, Verified - D/C*, Dispensed - D/C*, and Not Disp. - D/C*. This issue
has been resolved. DR 143981
 In a previous release, the product inventory quantity could be calculated incorrectly
for any agent that uses multi-use products with an agent above it on the dispensing
window that uses single-use vials. This issue has been resolved. DR 144376
 In a previous release, when the user closed the Dispensing Dosage Specification
window, a confirmation message was not displayed informing the user that dose
rounding was applied to the admin dose. This issue has been resolved. DR 145810
 In a previous release, the dispensing admin instructions were automatically reset to
ordered admin instructions when subsequent agents/doses in the same diluent bag
were modified. While dispensing Multi Agent Bags, changes to Admin Instructions
were being overwritten by the next agent when opened. This created a loop of
correction in the administration instructions. This issue has been resolved. DR
148550
 In a previous release, pharmacy dispensing labels did not print data for any of the
data tags related to the dispensed agent details until dispensing was saved. Thus,
when there was no status for a dispensed agent, the labels did not include data for
these data tags. The dispensing details for an agent/dose needed to be saved at
least once, which changed the status to pending for all the data tags to correctly
print their data. This issue has been resolved. DR 150596
 In a previous release, when printing the dispensing label, there was a database
error depending on the user that was chosen as the prepared-by user. The
database error happened for clients that were in production for over 15 years (that
is, before the userid was a uniquely generated value), or for Varian-configured
users. This issue has been resolved. DR 153164
Documents
 In a previous release, when a PDF note was sent as a reminder with an
attachment, clicking on the note in the reminder window did not show the PDF.
Instead, the user saw text that stated there was a PDF document for the note. This
 In a previous release, the All Primary Diagnosis tag item did not work as expected.
It displayed "There is no information available" even though a primary diagnosis
existed. This issue has been resolved. DR 142974
 In a previous release, the Physician-Attending data tag did not populate data into a
note. When a user created a document template with the Physician-Attending data
tag, the item populated with 'There is/are no Physician-Attending/s recorded for this
patient.” This issue has been resolved. DR 142979

 In a previous release, spell check highlighted more text than just the misspelled
word, and replaced the entire highlighted section with the new spelling. This caused
spell checking to break the data tags in a Note or Preparation Method Template.
 In a previous release, the unapproved footer was not added when printing an
entered note and the Security setting was selected to print an unapproved footer.
 In a previous release, during the erroring process of an approved PDF image
document, the user was asked if they wanted a pending copy. When the user
clicked Yes, the error messages opened in succession. At the end of the process,
the original PDF was errored and removed from the list of notes. However, the new
pending copy was not created. This issue has been resolved. DR 150752
 In a previous release, when attempting to load a historical (pre-15.0)
image/scanned document in ARIA Manager, the application was unable to display
the document. The application displayed the following error message instead:
"Error: uf_load. Please contact your local IT support group or super user." This
 In a previous release, a user was unable to view documents created in RO from the
Notes window in MedOnc. When the user clicked View on a Word document,
nothing happened. This issue has been resolved. DR 153807
 In a previous release, Image or PDF files added through the Document Service
could not be viewed in MO or RO. Opening a file opened a window but the contents
were not displayed. This issue has been resolved. DR 153953
 In a previous release, the MedOncology install package did not deploy MS Office
Interops 15.0 DLL. This DLL is necessary to be able to view ARIA PM documents in
MedOnc. When trying to open word documents in MO Manager, an error was
displayed stating: "Could not load file or assembly 'Microsoft.Office.Interop.Word,
Version 15.0.0.0'. This issue has been resolved. DR 154499
Drug Administration
 In a previous release, the 'X/Y Given' label on the Treatment tab on the Medications
window was incorrect when there were multiple agents ordered on the same
prescription (Rx). Medications Treatment tab was displaying incorrect 'Given' values
after doses were recorded or errored out in Drug Admin. This issue has been
resolved. DR 143011
 In a previous release, there were Database locks while Immunization Information
window remained open. The locks remained active while the user completed the
details on the Immunization Information window and were not released until the
user clicked the Skip or Save button on the Immunization Information window. This
 In a previous release, in the Drug Administration window, when a dose was
discontinued, its 'D/C' status only appearing in black and bold. This issue has been
resolved. DR 143924
 In a previous release, the message about the cumulative dose exceeded was not
being triggered in the Drug Administration under some scenarios when the case of
the agents did not match exactly. The dose limit message appears when ordering

the agent, regardless of the case of the agents. This issue has been resolved. DR
144888
 In a previous release, all the dose recordings for a non-treatment plan agent were
not created if they were scheduled for after the end date of the treatment plan. This
 In a previous release, when approving a dose recording for an immunization agent,
the Immunization Information window opened regardless of the ARRA/HITECH
setting (in Security). When approving a dose recording of a vaccine/ agent labeled
as immunization in Security a Vaccine Registry page appeared when the dose was
approved. This issue has been resolved. DR 149290
 In a previous release, the drug administration co-sign window did not accept a
case-insensitive user ID. This issue has been resolved. DR 149821
 In a previous release, in the Drug Administration window, when the user clicked the
Co-Sign button, the User Authentication window did not default with a Domain or
User ID. This issue has been resolved. DR 149822
E-Prescribing
 In a previous release, the checkboxes on the ERX user registration window were
not displaying the disabled state. This issue has been resolved. DR 143699
 In a previous release, if the user printed a pickup-external controlled substance with
a previously attached pharmacy before it was e-prescribed, the 'Send' button was
not disabled and the 'Drug has been printed' icon did not appear. This allowed the
user to click the 'Send' button, bringing up the 'Send Prescription' window when it
should have been disabled for printed prescriptions. This issue has been resolved.
DR 148034
 In a previous release, the EPCS audit log should have captured when a user
logged out of the application; however, these events were not captured. There were
also events in Security that were not captured: launching the LAC (Logical Access
Control) window and changing a provider's EPCS service level (either adding or
removing EPCS service level). This issue has been resolved. DR 148035
 In a previous release, the E-Prescription Admin Instructions Separator was deleted
when the user clicked OK to close the Medical Management Characteristics window
in Security, without making any changes to the E-Prescription Admin Instructions
Separator. The user had to open the window and reselect the E-Prescription Admin
Instructions Separator. This issue has been resolved. DR 154182
 In a previous release, when a user ordered agents through the Drug Selection
window and tried to lookup the Representative Formulary for agents, the NDC
matching did not always find the best match and the wrong NDC could be
associated and sent with the formulary request, which returned incorrect benefit
coverage. This issue has been resolved. DR 154800
 In a previous release, the NADEAN and GHB validation were not correctly
triggering in all scenarios when replying to e-prescribing change requests. The user
could select a different medication and otherwise freely alter the drug that was
returned in the response to a therapeutic interchange change request. This drug
needed to be validated. The validation done on the GHB and NADEAN pharmacy

instructions required for certain medications was not sufficient to ensure that all
requirements are met. This issue has been resolved. DR 154806
Flow Sheet
In a previous release, when test results had trailing zeros to the right of the decimal
point, those trailing zeros were not displayed. For example, a test result value that was
returned (via an interface) as 9.50 appeared as 9.5 instead. This issue affected
multiple windows within Manager. This issue has been resolved. DR 146474
Installation
 In a previous release, the MedOnc Installer set up the old/13.7 ODBC DSN entry
rather than the new rxreport ODBC DSN entry for 15.0 (and above). The MO
installer currently sets up an ODBC DSN for XMGR. This is required as of 15.0.
 In a previous release, the barcode fonts needed for Crystal Reports, were missing
from the installer. Certain Crystal Reports depend on specific non-Windows
barcode fonts. This issue has been resolved. DR 138491
Labels
 In a previous release, there were issues with two sets of data tags on prescription
dispensing labels: Prescription Label Details, Total IV Bag Volume and Drug Batch
Dispensing Label (which is actually 10 data tags). The 'Prescription Label Details'
data tag did not print on pharmacy dispensing labels. This happened regardless of
whether the dispensing was pending, verified or dispensed. This issue has been
resolved. DR 146864
 In a previous release, if a user double-clicked the Print button on the Prescription
Dispensing window, Manager crashed. In the Dispensing window, clicking "Print"
for dispensing label and then "Print" again while labels were printing resulted in an
error message and disconnection from the application. This issue has been
resolved. DR 147098
 In a previous release, there were issues with the admin route and dispensed admin
route data tags on the pharmacy dispensing label (and syringe dispensing label).
 In a previous release, when a data tag was replaced on a label, if the data
contained multiple lines, all the data (from the data tag) was placed on a single line.
This issue happened only when both the Delete If Empty and Wrap Text
checkboxes were checked. This issue has been resolved. DR 149537
Manager
In a previous release, the Select Default Printer window cut off the first character of the
printer name if there was only one printer in the list. This issue has been resolved. DR
113500

Meaningful Use
In a previous release, the Patient Data tab on the meaningful use dashboard window
displayed duplicate rows for the same patient after scheduling an event for the patient
with a billing code of 99212, then approving and linking to a diagnosis. This issue has
Medication Orders
 In a previous release, the maximum single dose for an unscheduled agent (set on
the plan agent window, in Planner) was not capping the dose when it was ordered
in Manager. Note that the dose was capped, according to the maximum single
dose, for scheduled agents. This issue has been resolved. DR 144884
 In a previous release, the administration dose did not calculate correctly (based on
the ordered dose) when reordering a pickup-external agent from the list at the
bottom of the Orders/Rx tab on the Medication window. This issue has been
resolved. DR 145142
 In a previous release, the frequency and admin instructions labels and fields (with
their data) overlapped in the View Medication window. This issue has been
resolved. DR 146222
 In a previous release, when a single prescription contained multiple support
regimens, the text and first support regimen display name overlapped on the
Orders/Rx tab of the Medications window. This issue has been resolved. DR
147056
 In a previous release, when Manager was back-calculating the order dose (from a
user-entered admin dose), Manager did not yield the entered admin dose again on
the Adjust Dose window. This issue has been resolved. DR 152788
Medications
 In a previous release, the Intent to Treat Order doesn't display in the Start
Treatment tab after creation. The Start Treatment tab remains empty and does
display the newly-created "intent to treat" order. This issue has been resolved. DR
116878
 In a previous release, the action word was missing from the course description
(depending on the format chosen for the course description) when using one of the
FDB drug databases. This issue has been resolved. DR 143917
 In a previous release, the application exhibited slow response times when a patient
had many current medications. This issue has been resolved. DR 145136
 In a previous release, for the Favorite Agents Selection from Prescription Details,
there was a slow response time when opening the Favorite Agents Selection from
Prescription Details. This issue has been resolved. DR 146860
 In a previous release, some sites experienced slower response time when opening
a patient if the patient had many current medications. This issue has been resolved.
DR 148841

Open Patient
 In a previous release, the patient age was calculated/displayed past age of death
(in some windows/reports). The age of a patient increased even after the patient
was set as deceased. The age was calculated based on the patient’s birthday and
today’s date. The calculation did not consider if the patient was deceased. This
 In a previous release, patients with a closed status were not displayed on the Visit
tab (of the Open Patient window). This issue has been resolved. DR 144338
 In a previous release, the patient tracking abbreviation did not show on the Visit tab
(of the Open Patient window) if two users were updating the patient tracking for the
same patient at the same time (and updating different tracking items for the
patient). This was mainly an issue if the second person saving the patient tracking
did not have the latest time for their update. If the second user who closed the
Patient Tracking window had a later time than the first user, then the abbreviation
updated correctly. But if the second user had an earlier time that the first user, the
abbreviation on the Open Patient window (on the Visit tab) was empty. This issue
Patient History
 In a previous release, a database error occurred when adding a cancer diagnosis in
Medical Problems: when adding a cancer ICD code for medical problems, a null
column exception occurred. This issue has been resolved. DR 143835
 In a previous release, it is possible to have medical history rows duplicate when the
Modify Medical History window is opened and OK is clicked to close the window.
The user does not need to make any changes in the window to cause the rows to
duplicate. This issue has been resolved. DR 153163
Patient Merge
In a previous release, the Patient Merge utility failed due to obsolete database tables
for quality measures. This issue has been resolved. DR 144579
Physician Orders
In a previous release, only the first instance of the Transcribed Physician Order
window closed when transcribing multiple physician orders from the Untranscribed
Orders tab of the Physician Orders window. The subsequent instances of the
Transcribed Physician Order window did not close when either OK, Cancel or the X in
the control menu was clicked. This issue has been resolved. DR 143167
Plan Management
 In a previous release, a toxicity risk rule did not successfully execute in Manager.
 In a previous release, a treatment plan agent's rounding is not found when the
agent is on a phase that was copied from another phase. A column (dec_cd) is not

set when the phase is copied. Instead the column is set to null. This is causing the
rounding to not be found for the plan agent. This issue has been resolved. DR
149285
Plan Rules
 In a previous release, the rules engine in MedOnc did not properly convert numeric
values when the dose ordered in Manager differed from the unit of measure
specified in the rule in Planner. The rules engine was initially designed on the
premise that only Varian staff would have access to it and they would ensure that
rules were configured with the same unit of measure that would be ordered in
Manager. This issue has been resolved. DR 140889
 In a previous release, "Drug Order - Drugs" rules Drug Order Management plans
only executed successfully for Medi-Span agents. For a non-Medi-Span agent
created in the agent formulary, a Drug Order - Drugs rule always failed. This issue
 In a previous release, the duration rule for drug orders did not account for the unit of
measure of weeks or days. Conversion between the two is required. This issue has
Planner
 In a previous release, rules written in Planner using age with a comparison operator
of '=' and a unit of measure of years, did not trigger the current notification in
Manager. This issue has been resolved. DR 148560
 In a previous release, when a user tried to delete a phase from a plan an error was
thrown, the app crashed, and the phase never got deleted. This issue has been
resolved. DR 148674
Plans
 In a previous release, the Plan Summary could show information from an incorrect
release. When a plan was approved and amended and the summary is changed,
the summary from the amended plan may have been displayed on patients who
were on the approved plan. This issue has been resolved. DR 112908
 In a previous release, when the user amended a regimen by updating an existing
plan agent and changing the agent name and the dosage, the new cycle/day
ordered for the patient (once the amendment is accepted) had the updated agent
name but the previous agent's dosage. This issue has been resolved. DR 144893
 In a previous release, a treatment plan with non-cyclical decision days did not order
all agents, for all cycles and days, until the next cycle/day that contained a decision
day. This left some agents as non-ordered. This issue did not happen with cyclical
decision days. This issue has been resolved. DR 150458
Provider Approval
 In a previous release, the Date Range filter on the Visit Billing Event Approval
window did not correctly filter the rows in the window. A user could experience an

issue where the provider approval could not filter using the past date. This issue
 In a previous release, Provider approval was slow to return a count of several items
in the window. Procedures stored in the database related to the Provider Approval
window ran slowly, taking anywhere from 10 - 30 seconds to complete. This issue
Providers
In a previous release, the Provider Registry window Search button only searched on a
provider's last name. If the user entered a last name, a comma, and a first name, the
first name was properly parsed and used to further filter the list of providers. This issue
Quality Measures
 In a previous release, CPT did not display the registered trademark (®) symbol,
impacting quality measures. This issue has been resolved. DR 129277
 In a previous release, if the reconciliation date had a time entered the QM logic
failed. This issue has been resolved. DR 129341
Questionnaires
In a previous release, one Print Preview showed the full name with all the details, while
another Preview showed the user name cut off after an apostrophe. This issue has
Regimens
 In a previous release, the BSA (in the Dose Calculation Management window) was
still capped when starting a regimen that did not have a BSA cap, if the prior
regimen that was started and cancelled (or discontinued) had a BSA cap. This
 In a previous release, the Regimen Summaries were truncated if the length of the
summary exceeded 5 or 6 pages. This issue has been resolved. DR 144133
 In a previous release, the initial dose for future cycles and days did not correctly
carry the adjusted dose forward from cycle 1 day 1 (C1D1) when the delay regimen
feature was used and C1D1 was moved before the start date of the plan. Instead,
the initial dose was reverted to the dose defined in Planner (for the regimen). This
 In a previous release, Planner crashed in the Add Event window when trying to add
a scheduled event to a regimen with a schedule type of 'Linear - Neg. Days' if the
new scheduled event started on a negative cycle day and used the days of week
frequency choice (and the required start day) choices. The error message was not
a user-friendly error message—it was an array boundary exceeded message.
Planner crashed after the user clicked OK to close the message. This issue has

 In a previous release, support regimens appeared above the date header row. This
 In a previous release, when a patient was under two years old, the patient's age
was calculated to the number of months. However, the calculation was only
considering the number of months between the current month and the month the
patient was born. The calculation needed to also consider the specific day of the
month. The calculated age was incorrect when the current month was later in the
year than the birth month. If the current month was on, or before, the birth month,
the age was calculated correctly. This issue affects both the demographics window
and the age-based doses in regimens. This issue has been resolved. DR 149749
 In a previous release, a user could receive an error when ordering future cycles and
days of age based regimen, if the support regimen was ordered along with the main
regimen. This issue has been resolved. DR 151086
 In a previous release, "Ad hoc agents" were listed twice on the Treatment tab after
some, but not all, of the ad hoc agents were ordered for a cycle/day, once with an
ordered status and once with a not-ordered status. This issue has been resolved.
DR 152614
 In a previous release, the initial dose for future cycles and days did not correctly
carry forward the adjusted dose from cycle 1 day 1 (C1D1) when the adjust date
was used on the dose recording windows to move C1D1 before the start date of the
plan. Instead, the initial dose was reverted to the dose defined in Planner (for the
regimen). This issue has been resolved. DR 153329
Registration
In a previous release, Manager crashed when attempting to create a new patient if
there were any system-generated patient IDs configured in Security. The crash
occurred after clicking the New button on the Open Patient. The user was shown an
unhandled database error. However, the unhandled database error closed quickly and
then Manager also closed. The New Patient window was not shown to the user. This
Reminders
In a previous release, untranscribed physician Orders were not populated in the
reminders tab of the Open Patient window. This issue has been resolved. DR 147849
Reports
 In a previous release, merged patients were visible within the Patient Listing -
Duplicate Name and DOB report (d_rpt_activept_dups). This issue has been
resolved. DR 139877
 In a previous release, there was an exclusive database lock when a Crystal Report
was previewed or printed. The report was launched from the Reports window and
the database lock remained until the user closed the Print Preview window and the
Reports window. The result of this database lock meant that no other user could
print/preview a report in the Reports window until the user causing the database
lock closed the Reports window. This issue has been resolved. DR 143488

 In a previous release, the user received an error message when previewing any
Crystal Report (from the Reports window) and the printer that was selected as the
default printer (for MedOnc) was the last printer listed in the Actual Printer Name
drop-down (on the Printer Setup window). The error message said, 'Unable to set
the default printer entry in the windows registry.'. The error message did not cause
Manager to crash, but the report was not printed. This issue has been resolved. DR
154006
Security
 In a previous release, User details, created by FirstTimeUser app, could be
overwritten when a new user was added (in the Shared Framework portal and Data
Admin). The First Time user application added a space before the last name
(userid.user_last_name). Also, the First Time user application used a different set
of user IDs than RO or MO, causing users added in Data Administration to possibly
overwrite some of the user information. This issue has been resolved. DR 149394
 In a previous release, User details, when attempting to associated a
SharedFramework (SF) user to an ARIA OIS Medical Oncology user in ARIA
Security: If the SharedFramework user(s) contained a comma in the display name,
then the list of available users was populated with an incorrect value. Instead of
being populated with their domain account, they were populated with the internal
UserCUID value preventing the user from knowing which account they were
selecting. This issue has been resolved. DR 150118
 In a previous release, the VarianDB Server name was not saved when the First
Time User (FTU) mapping utility was closed and re-opened. The user had to re-
enter the value when the utility was re-started. This issue has been resolved. DR
151579
 In a previous release, in the MedOnc Mapping Utility application, after the initial
dialog window with DB connection information was passed, the program loaded MO
user information from the Varian DB. If the login user Id, display name, first name,
or last name contained the special characters '*' or '(' or ')' the program crashed as
it tried to query the Active Directory. This issue has been resolved. DR 151878
 In a previous release, in the MedOnc Mapping Utility application (on the test
environment), loading Active Directory users never completed on program load if
the user had manually saved in a previous session. This error happened when
there was a small number of user defined in the Windows Active Directory. This
 In a previous release, User details, in the MedOnc Mapping Utility application, the
user could not deselect the option after confirming a suggested link. This issue has
 In a previous release, in the MedOnc Mapping Utility application, an error was
displayed after confirming a mapping and attempting to save the data. A folder and
file: C:\MOtoADMappingUtility and moMapping.enr file was asked for when trying to
confirm mapping. This issue has been resolved. DR 151952
 In a previous release, the MedOnc Mapping Utility application did not check for
duplicate Ad Accounts in all scenarios. There were several locations where The MO
Mapping utility did not correctly check for duplicate values. This issue has been
resolved. DR 151959

 In a previous release, the MedOnc Mapping Utility application recommended users
if they were already linked, and if they were already linked when doing advanced
matching. The application then allowed these users to be linked a second time
which resulted in broken accounts. This issue has been resolved. DR 151961
 In a previous release, the MedOnc user mapping tool failed to launch with the error
"Can't connect to Portal. An error occurred while trying to get Portal users. User
account is disabled." This occurred when one or more users were disabled in portal
and prevented installers or hospital IT from launching the utility. This issue has
 In a previous release, Manager checked the user privileges of the user logged into
Windows, rather than the user logged into the app, when opening any .NET
window. On shared workstations, this could lead to users having insufficient or
excessive permissions, allowing them to access functionality they should not be
able to access, or preventing them from completing their workflows. This issue has
 In a previous release, the Crystal Report Service Account Credentials were limited
by their length to about 30 for the user ID and 18 for the password. The issue was
that the fields did not scroll horizontally if the user needed to enter more characters
than could fit in the visible width of the field. This issue affected only MO Security
and not RO DataAdmin. This issue has been resolved. DR 154108
Service Portal
In a previous release, with Windows Integrated Authentication (WIA) mode disabled in
the Varian Service Portal, printing in MedOnc did not work on some Windows
operating systems including, but not limited to, Windows Server 2008 R2 and Windows
Server 2012 R2. Many print buttons throughout the application were disabled (greyed
out) and those that could be pressed did not result in the print job being sent to the
printer. This issue has been resolved. DR 153954
Settings
In a previous release, some institution settings, such as the Patient ID fields on the
Institution settings "Varian Only" tab, did not get copied over to the target institution
from the source. This issue has been resolved. DR 118948
Tests / Labs
In a previous release, the IEM read-only lock icon was not visible in the Test Results
window when the user preference "Show Comments in Results Display" was selected.
Toxicities
In a previous release, there was no validation check for a toxicity assessment being
saved without any components being graded. When entering a new toxicity if the user
didn't grade any component and click OK, a new toxicity was created without anything
graded, which could cause the toxicities heading to disappear from the patient agenda.

Modifying the toxicity and grading a component caused the heading to reappear in the
agenda. This issue has been resolved. DR 141560
Users
 In a previous release, users were unable to save when linking a user within
Security. The user appeared in the User list as well as in the Varian Service Portal
but when linking was attempted (using drop down, users name appeared in list), the
link was not saved. This issue has been resolved. DR 148561
 In a previous release, when only a direct address email exists and a new email was
added, the preferred checkbox was not automatically checked for the new row.
Also, when there was only a direct address email and it was not marked as
preferred, the user received an error message stating that one email had to be
marked as preferred. This issue has been resolved. DR 153330
Known Issues for ARIA OIS for Medical Oncology Version 15.5
ADT
The inpatient bed icon should be removed if the admission entry in the ADT window is
marked in error. This will be resolved in a future release. DR 106629
Agenda
 When reviewing the patient agenda, the "Visit Summary" seems to be looking for
specific Note Types to change the status from "Missing Visit Note" to "Approved".
The Visit Summary item in the agenda is not updating when a Physician Progress
Note is entered/approved. This will be resolved in a future release. DR 118431
 When a user inactivates a Visit Reason and then goes to Agenda User Tasks or
similar areas, the Visit Reason dropdown list will include the inactivated item. This
will be resolved in a future release. DR 127168
 The Patient Agenda window displays the Billing Events agenda item as approved
even though the visit billing is not yet approved for today's visit. This issue will be
resolved in a future release. DR 144091
Allergies
When a user tries to add an allergy for a drug that is more than 50 characters long the
user will receive an error. This will be resolved in a future release. DR 139289
Billing
 Users can approve billing charges without billing account numbers using the
Additional Billing Charges window. This will be resolved in a future release. DR
99274

 If a prescription is reissued and the prescription is changed from pick-up internal to
pick-up external, the billing event is not correctly reversed. This will be resolved in a
future release. DR 109735
 A pending agent billing event not added back to billing when dispensing is errored.
This will be resolved in a future release. DR 109736
 An approved medication billing event is being updated when a nurse approves a
dose recording. This will be resolved in a future release. DR 109737
 When using the diagnosis button in the billing event window, additional diagnoses
are being added and the sequence numbers are incorrect. This will be resolved in a
 The account field always displays as inactive (by showing the red asterisk) when
the Modify/View Billing Event window is opened from the Billing Manager Review
window. This will be resolved in a future release. DR 132287
 A user reported that an incorrect CPT code 96360 was assigned to administration
time of exactly 30 mins. This will be resolved in a future release. DR 132954
 If a patient has an inactive diagnosis code appearing first in their diagnosis code
list, it is auto selected when they select the diagnosis button on the additional billing
charges window. Users sometimes move quickly through this window which allows
this default to be selected. This will be resolved in a future release. DR 133329
 The Billing Events window should only update a patient's diagnosis to uncheck the
External Source check box (on the Diagnosis window) when an interfaced
diagnosis is associated with the billing event. Currently, the code is always updating
the diagnosis to set the External Source to uncheck (when it is already unchecked).
 The '# Units' field (on the Billing Event window) does not recommend the lowest
possible value when there are multiple rows configured in the agent billing
information (in Security) for a given agent. This will be resolved in a future release.
DR 145425
Communications
 An error occurs when generating a Visit Summary Patient communication CCD and
there are certain test results for the visit that contain dashes. The CCD will not
display in Manager because the CCD cannot handle dashes in the description field.
 A user received a Database error when trying to print mailings for a patient
communication list. This will be resolved in a future release. DR 108516
 A user reported that the Patient Care Summary printing of the test results section
goes off the screen to the right. If there are more test results than space on the
report, the data is being cut-off. This will be resolved in a future release. DR 113576
 A user received an Array error when sorting by Delivery Method in the Outbound
Transition of Care window. This will be resolved in a future release. DR 116755
 Communication preferences are not being saved for some patients on the
preferences tab of the demographics window. This will be resolved in a future
release. DR 118389

 Inactive users are available to be assigned as delegates when assigning delegates
for a direct message. This will be resolved in a future release. DR 124336
 The patient Communication message field in Manager is limited to 255 characters.
The corresponding message field in Planner where this is created is unlimited. If a
message is created in Planner that is greater than 255 characters, an SQL
truncation error is generated and the user cannot complete the action of sending
the patient communication. This will be resolved in a future release. DR 124540
 When creating a C-CDA document for a patient with an excessively long name, an
exception error can occur due to the length of the C-CDA document's name that
would be created. This will be resolved in a future release. DR 128485
 On the Select Recipient window, the provider's phone number shows their fax
number when their preferred type is fax. If a provider has a work number and a fax
number set up in Security and their Fax is their preferred contact method. In the
provider search, it will show the Phone Number as the fax number. This will be
 When creating a new Direct message, the "select Recipient" window shows all
users and providers regardless if they are “active” or “inactive”. This list should only
be showing the ones that are “active”. This will be resolved in a future release. DR
129387
 A CCDA may fail to be properly/fully displayed if it contains certain Unicode
characters. In the Clinical Summary generated from Info Request if it creates an
xml file it may use improperly encoded Unicode characters causing an error that
says, "An Invalid character was found in text content." This will be resolved in a
 When a user creates a Direct Message from the Messages tab, launches a contact
search, and clears the check boxes for both “Show External Providers Only” and
“Show contacts with a Direct Address only”, the list will populate blank entries at the
top. The other entries will still populate lower down. This will be resolved in a future
release. DR 135980
 When creating an Inbound Transition of Care and the user opens the window to
select the referring provider it can show inactive providers, which appear as inactive
in the Provider Registry window, but appear the same as active providers in the
selection window. This will be resolved in a future release. DR 136780 136780
 The "Results" section of an Outbound Transition of Care is not showing test results
in chronological order. Instead the dates in the table header appear in a 'random'
order. Currently the order is based on the order the test results were created in.
 The Patient Search window gets stuck on an hourglass (i.e. it's frozen) when trying
to load a third (3rd) CCDA document from a direct message. The first two CCDA
can be loaded fine, but the third one will consistently (for this client) cause the
freeze. This issue will be resolved in a future release. DR 151521
 When viewing an existing outbound transition of care (in the Outbound Transition of
Care window), the receiving provider in the details section (the lower part of the
window) may not be correctly displayed and thus not match the receiving provider
display in the top grid. This happens at client sites where the list of providers in the
receiving provider drop-down is very large and the list takes longer to retrieve from

the database than all the other data in the details section. This issue will be
 The user receives an error message when closing pdf file attached to a
direct/secure message. These messages are opened/viewed from the Messages
tab on the Open Patient window. This issue will be resolved in a future release. DR
152826
Correspondence
 If the user sends an unapproved note via the Correspondence window (mail or fax)
it does not show the unapproved note footer even if this option is enabled in
Security. This will be resolved in a future release. DR 116778
 Organizations no longer appear in the provider registry after upgrading to 11
MR4.1. The organizations still appear in the database and can be found by
searching for organization ID but not by the organization name. This will be
 There is a black background (and black text) for out-of-range test results (i.e. L, H,
LL or HH results) in the tabular simplified format on the print-out from
correspondence management window. This will be resolved in a future release. DR
131652
 Expired referrals for the patient (based on data in the Referral tab of the Modify
Patient window) are appearing in correspondence window. This issue will be
 When a user tries to print to the default correspondence printer, several error
messages are displayed and print does not occur. This is an issue with workstation
centric printing enabled and the system option to not check if the printer is online at
start up. This issue will be resolved in a future release. DR 154177
Custom Browser
When using the custom browser launch window, a database exception is received
when the “patient ID parm” is configured to use an institution level patient ID and a
patient has an ID configured for multiple institutions. This will be resolved in a future
release. DR 123769 123769
Data Update
 Some agents lose their classification after a Medi-Span Data Update is completed.
This will be resolved in a future release. DR 96680 96680
 While doing Medi-Span Update in Security the user received the following error:
“The file temp_agt does not contain data in the expected format.” This message
needs to be more detailed so the user can pass along details to Varian Support.

Diagnosis
 It was reported that longer ICD-10-CM diagnosis codes (of 6 or more characters)
may be truncated on Exam & Patient Summary windows. This will be resolved in a
 Intermittently when a user is within the Modify Billing Events window they are
reporting related check boxes missing from the related diagnosis. Voiding the
pending event and creating a new event will resolve this for a patient. This will be
 There are buttons that are not visible on both the Immunization Information window
and the Diagnosis window when using the windows resolution that ARIA Manager
supports. For the Immunization Information window, the OK and Cancel buttons
might not be visible and on the Diagnosis window, the Save and Cancel buttons
might not be visible. This issue will be resolved in a future release. DR 143285
 When staging an ICD-10-CM diagnosis of C48.1 the user is unable to select a T3
option. This will be resolved in a future release. DR 148811
 The Dx Site default for ICD-10-AM diagnosis code C43.0 shows as "Lip and Oral
Cavity" rather than as "Melanoma". This issue will be resolved in a future release.
DR 153429
 The T and G values shown on the Staging tab for a diagnosis of C49.A3
Gastrointestinal Stromal Tumor (GIST) do not accurately reflect the values from the
AJCC 7th edition. This issue will be resolved in a future release. DR 153575
 There are two issues when showing the staging for C91.10. First, there should only
be two choices in the scheme drop-down. There is an incorrect third choice for
'CML' being shown. Second, the choices that are displayed when Binet is chosen
are not correct. The values being shown are the same as the values for Rai. This
issue will be resolved in a future release. DR 153819
Dispensing
 If a patient is on a regimen containing a bag with multiple agents with
concentrations, deleting an agent and then approving the order will result in the
total bag volume displaying an incorrect amount in the modify dose window. The
total bag volume will show up correctly after the drug is dispensed. This will be
 When a drug order is created its dispensing location is calculated based on the
patient's visits. If the patient has a visit at an institution not linked to any dispensing
locations, such as a Radiation Scheduling institution, it will fail to apply the location
to the drug order and the order will not show in the Pharmacy Dispensing window.
 Users reported internal medication orders may use an incorrect visit to find the
dispensing location. The dispensing location is using the default set for scheduling.
When a patient has a scheduled visit on or before the date of a drug order, the most
recent one is used to determine the default dispensing location for all drugs that do
not have an agent level dispensing location. This is taking precedence over the
patient’s institution or the currently logged in institution. This will be resolved in a

 The linked dispensing location is not being used for drugs in the agent formulary
without a strength and unit of measure defined. As a result, the institution / visit
based dispensing location is being used for these drug orders. This will be resolved
in a future release. DR 121271
 When an institution has agent-level dispensing enabled, a drug can be dispensed
multiple times if multiple users enter dispensing information at the same time. This
 A user received an error when attempting to print a label for a dispensed drug. This
error occurs when a drug that had previously been dispensed at the agent level is
later dispensed at a dose level. This will be resolved in a future release. DR 122979
 The app_msg 2883 is missing from the applications static data. This causes an
error to appear whenever drugs are dispensed at the agent level with IEM
communicating with a pharmacy system (RDE). This app message is supposed to
be a warning message that reads: 'Drugs dispensed at the agent-level will not be
communicated to pharmacy systems. Do you wish to continue?’ This will be
 The infusion type data tag is not printing on dispensing labels. Only the dispensed
infusion type prints appropriately. This issue will be resolved in a future release. DR
128829
 Depending on the product inventory items and the quantities for each item, the step
of 'determining quantity' (as seen in the micro-help bar) on the New/Modify
Dispensing Details window can take several minutes. Users reported seeing a 5 to
6-minute delay in the Dispensing window when dispensing Darbepoetin 500 mcg.
 The preparation time can be defaulted ahead of dispensing time, which cannot be
approved. The user will get a validation error, unless the time are adjusted prior to
clicking Approve. This issue will be resolved in a future release. DR 144638
 The "Prepared by" and "Dispensed by" fields should continue to update the
prepared by or dispensed by user for each additional rows that were just updated
(from blank) as long as the focus remains on the prepared by or dispensed by field.
This issue will be resolved in a future release. DR 145429
 There may be a delay in determining the default product inventory quantities
upwards of seconds/minutes. This delay depends on the number of inventory
products that are configured. This issue will be resolved in a future release. DR
148287
 Both the reconstitution information & the expiry date are not printing on the
(custom) pharmacy worksheet when status for the dispensing of the agents/doses
is (only) verified. The reconstitution information & the expiry date do print
successfully when the dispensing of the agents/doses is approved. This issue will
be resolved in a future release. DR 153325
Documents
 The paste icon on the Tests window does not correctly paste the 'other tests' data
tag into the note. Only the date is pasted into the note. This will be resolved in a

 The Visit date changes to the current date on all pages but the first page of the
note. This will be resolved in a future release. DR 108346
 There is a need to add additional logic to all data tags that retrieve cosign
information on dose recordings to handle the scenario where there is more than
one cosign found for any single dose recording. This will be resolved in a future
release. DR 111106
 In a CCS environment, the “approved by the author” data tag will pull a Radiation
Oncologist’s set of results (RoS/PE) in when the results are done on the same day
by a physician with the same classification as the Medical Oncologist. This will be
 The CCD logic was hard-coded to look only for one specific ID type. The code in
Manager is more flexible. It looks first for the ID marked as the display ID. If it does
not find an ID marked as the display ID, it looks for the ID marked as primary. The
CCD logic needs to change to do the same type of logic. This will be resolved in a
 Clicking cancel, when approving multiple notes from the Note Approval window,
does not cancel the approval of all further notes. For example, a user highlights all
notes to review and begin their review. The user is interrupted, so closes the
window. Instead of going back to the note approval window so they can accomplish
other tasks in Varian, like the software did in previous versions, they are asked to
approve all the other highlighted notes. This will be resolved in a future release. DR
112913
 In a seamless CCS environment, when the user attempts to print a Radiation
Oncology document from within Manager the printer dialog hides behind the
application. This issue does not occur in a regular, non-seamless environment. This
 In a seamless CCS environment, when the user attempts to print a Radiation
Oncology document from within Manager the printer dialog hides behind the
application. This issue does not occur in a regular, non-seamless environment. This
 When a record in the Batch Scan window contains more than three documents; the
user can only see three of them as there is no scroll bar on this data window. This
 A user is getting the following error message when attempting to open a note
template with a questionnaire: Sub query returned more than 1 value. This is not
permitted when the sub query follows =, !=, <, <= , >, >= or when the sub query is
used as an expression. This will be resolved in a future release. DR 114100
 If a user selects to print multiple notes of varying note types, then Aria will use the
header/margin settings of one note type for all the notes in the print job (rather than
changing for each note printed). This will be resolved in a future release. DR
114403
 It was found in a recent release that a couple of dose recording data tags are no
longer populating with co-signed information. The user can manually add this
information to the document as a workaround. This will be resolved in a future
release. DR 116159
 Randomly ROS/PE text is overlapping consistently for a user running on Citrix. This

 When a user makes a switch between multiple pages in notes when an image has
been annotated, it can cause an error. This will be resolved in a future release. DR
120885
 A user reported the “All Primary Diagnosis” data tag repeats diagnosis data when
added to a note. This will be resolved in a future release. DR 122911
 The "Visit Provider" data tag not pulling the correct name within a Note header for
the current day unless there is a scheduled visit for that day. This will be resolved in
a future release. DR 125890
 When looking at the schedule for patient visits the logic filters out visits of type
Open Chart, so the user does not see those in the UI. However, when running a
note/note template using the <%Next Visit%> data tag, the Open Chart visit gets
pulled into the note as '<date> (not booked)'. This leaves the user questioning
where the next visit date is coming from. This will be resolved in a future release.
DR 126870
 When the user has Notes preference “Suppress Printing of Author Section”
unchecked in Security, it does not print the author section for approved documents
when the print preview is not shown. This will be resolved in a future release. DR
128962
 A user reported that the “Referred By” provider changes when loading a pending
Inbound Transition of Care. This only occurred if the user clicked multiple times
while waiting. This will be resolved in a future release. DR 129143
 A user reported not seeing electronic signatures included for notes printed from the
Correspondence window. This will be resolved in a future release. DR 129208
 When using a template in sentence form with medical and surgical histories, if there
are values with new line characters in the text box, the new line characters are
ignored, starting the next line with no space between the previous lines. When
using a template in both sentence and itemized format with medical and surgical
histories, if none of the "quick pick" check boxes are selected it adds an extra white
space at the front of the string. For a sentence, the white space is a space, while for
itemized the white space is a new line. This will be resolved in a future release. DR
132117
 A period and space are added to the front of the Social History data tag (in the
Notes), when only smoking status is filled in for the patient. This will be resolved in
 If a user creates a note that pulls Physical Exam data over before the user enters in
the Physical Exam information, it will not populate within the note, but Review of
Systems will still populate as expected. The user can get the Physical Exam
information to populate if the user waits until they have all the Physical Exam
information and then they open a document template, or if they are in the Modify
Note window and they select Physical Exam from the component section. This will
 Clinical document requests appear with the creator's discipline rather than the
provider's discipline it was created under, when looking up the clinical document
request in the Notes window. This will be resolved in a future release. DR 136775
 The Attending Physician (note) data tag lists physician once for each phone number
that the attending physician has recorded, even though phone number is not part of

the data displayed for the data tag. This will be resolved in a future release. DR
142407
 The family history data tag does not format details into complete sentences when
there are multiple rows for the same type of relationship (e.g. multiple brothers or
multiple aunts). The first sentence that provides a summary of the alive or
deceased status is acceptable. The following sentences that detail the medical
background are not well-written. This will be resolved in a future release. DR
142856
 When approving a note that contains a large memory image in the (custom)
header/footer, an error occurs and Manger will close. This will be resolved in a
 There are several data tags are not respecting the font defined in the note and/or
component templates. Instead of respecting the font chosen in the note and/or
component template, the font is reset to Arial. This issue will be resolved in a future
release. DR 149008
 When viewing an approved note, that was approved with an "approval footer",
shows a few lines of blank lines at the start/top of the note. This issue will be
 For some users, note templates that are configured in the Favorite Document
Templates window are not showing in the list of note templates in the Select Note
Templates window, when creating a new note. The list of note templates is being
incorrectly associated to an inactive copy of the user in the Favorite Document
Templates window. When creating a new note, the Select Note Templates’ logic is
correctly looking for the active user. But, it is failing to find any note templates
because they were incorrectly saved in the database. This issue will be resolved in
 There is different logic used when determining which test results are 'abnormal'
when looking for abnormal values only on the "New/Modify Test Results" window
and for the data tags in the "Notes". The 'Other Tests' data tag does not include
abnormal values when the test is a subjective test result. This is normally set in the
test result window through a drop-down list. This issue will be resolved in a future
release. DR 154564
Drug Administration
 If a user creates numerous prescriptions so that the resulting general orders
becomes too large for the General Orders tab in the Drug Admin window, the user
will receive an error message which terminates Manager. This will be resolved in a
 Users report having issues when trying to print out information from the
documentation piece in Drug Administration. The issue relates to longer text from
the drug administration documentation that may be cut-off when it is printed. This
 The Scheduled Drug Orders report is not displaying “pickup internal” drugs that are
ordered during an “open chart” visit. This will be resolved in a future release. DR
123062

 A user reported the Dose Recordings report only displays the end time for specified
admin routes. The current list of routes (most specific to Medi-Span) that will cause
the end time to display on the print-out are: Intravenous, Intramuscular,
Subcutaneous, Injection, NG / IV, NG / PO, IV / PO, IV / IM, IV / PO / IM, Intra-
Arterial. This will be resolved in a future release. DR 124394
 The number of doses given ("0/1 Given") can be incorrectly displayed on Treatment
tab of Medications window. This will be resolved in a future release. DR 129343
 When modifying the controls for a user group, the “up/down” (drug) arrow buttons
are not available in the list of controls. This applies to the Drug Admin window, the
Prescription window and the Dispensing window. As such, clients are not able to
restrict access to these buttons from view only user groups. This will be resolved in
 When a patient is discontinued from a regimen (that had at least two cycles
ordered) and then started on a treatment plan (that has no visit scheduled yet), the
Ad hoc agent is missing from drug administration window. This will be resolved in a
Education / Counseling
 Users report text is reformatted on the patient education printouts from what is
originally set in Security. This will be resolved in a future release. DR 106656
 In some environments, the MedLinePlus education resources do not open when the
user clicks View on the Education Resources window. Internet Explorer appears but
does not navigate to the website unless the Internet Explorer window was already
open. This will be resolved in a future release. DR 122711
 The user is unable to access full textual result in "Flowsheet Result Detail - Subj.
Tests" screen when text result is less than 256 characters. When result is 256
characters or more, the full result populates a notepad in that screen that can be
opened and read. When the result is less than 256 characters, the notepad is not
created. This will be resolved in a future release. DR 138673
E-Prescribing
 The list of e-prescriptions is not properly refreshed when a date is manually entered
on the e-prescriptions tab of the Medications window. This will be resolved in a
 When an e-prescribed agent is re-issued, or reordered from the same day, the e-
prescription pharmacy select window is not being opened as part of the approval
process. This will be resolved in a future release. DR 107453
 When selecting an institution "specialty" in the E-Prescribing Registry setup of
Security a database error will occur. This will be resolved in a future release. DR
108713 108713
 The user should not be shown the Send Prescriptions window if the agent doesn’t
have an NDC code. The workflow that is causing this issue is switching an internal
agent to a pick-up external agent using the pen icon, on the Modify Prescription
window. This issue will be resolved in a future release. DR 117031

 There was a change in v11MR5 and v13.6 to make the drop-down search for an
NDC case-insensitive on the strength value (for strengths such as "324 (65 Fe)").
However, this change was not applied to the GPI search for an NDC. The GPI
search is still case-sensitive on the strength value. For example, the GPI search will
not consider “324 (65 fe)” to be a match on “324 (65 Fe)” and therefore will not find
an NDC for the agent. This will be resolved in a future release. DR 118527
 When a narcotic drug is in the e-prescribing queue but doesn't have a “Narcotic
Drug” reason “not sent” saved in the database, the user can't click OK in the Send
Prescription window to have the 'Narcotic Drug' reason “not sent” saved to the
database and to remove the drug from the queue. This will be resolved in a future
release. DR 123110
 A user reported that an external pick up prescription was entered into the patient
chart. A pharmacy was selected, but the script was marked "Do Not Send". The
prescription was not printed and the pharmacy received the prescription. This will
 Quantity and unit of measure are not sent on e-prescription when the agent is
added via a “favorite” agent that only has quantity and no unit of measure selected.
 If a user enters double quotes ("") in the optional administration instructions field for
a pick-up external agent in the Add/Modify Dosage Specification window then ARIA
Manager will crash after the OK button is clicked. This issue will be resolved in a
 The unit of measure (UoM) for the dose can be incorrectly displayed (i.e. shorten) in
the auto-generated admin instructions when the dose and the beginning of the unit
of measure match the strength that was ordered. This will be resolved in a future
release. DR 141329
 When a narcotic drug order is reordered using the "Reorder" button, the application
does not properly check that the drug should not be sent. If the user approves this
order, the drug does not get the "do not send" reason, and it is not removed from
the unsent prescriptions queue automatically. This issue will be resolved in a future
release. DR 154506
Flow Sheet
 When right clicking on subjective test results without specific results, only
comments, no menu appears to view the additional detail. This will be resolved in a
 The user is unable to access full textual result in "Flowsheet Result Detail - Subj.
Tests" screen when text result is less than 256 characters. When result is 256
characters or more, the full result populates a notepad in that screen that can be
opened and read. When the result is less than 256 characters, the notepad is not
created. This will be resolved in a future release. DR 109829
 Different base components may sometimes have the same institution component
name in the component name registry in Aria MO Security, but every base
component should have a separate row in the flow sheet in Manager regardless.
Results should always appear in the flow sheet in the category assigned to that
base component according to the institution test type in the component name

registry. It appears that is not how ARIA OIS for MO is functioning. If the institution
component name is the same, results display on the same flow sheet row. This will
 Notes created in ARIA OIS for RO don't open through the Flow Sheet in Manager,
but do open properly through Notes. This will be resolved in a future release. DR
133258
 The Visit Date header (on the Flow Sheet) is blank when the visit has a cycle
number but no cycle day saved. This will be resolved in a future release. DR
134050
Impression / Plan
It is possible to create 2 plan/impression or chief complaint/CPI entries for a patient on
the same visit on either the exam window or the history window when two users are
editing the patient simultaneously. This will be resolved in a future release. DR 118465
Journal
If the current user's user group does not have the “Full Access” to Journals, but still
has “Read-Only” Access, the user can enter the Journal sections and add/modify. This
Labels
 Invalid patient IDs should not be used in data tags when printing labels. This will be
 When printing a label for a prescription where the drug has no diluent and is added
from a support regimen, the total volume field appears null even if the drug has a
volume specified. This will be resolved in a future release. DR 121952
 When printing dispensing labels the "Number of copies" cannot be modified from
the default value when the printing window opened. This will be resolved in a future
release. DR 148820
License
All these issues are related to the fact that there is one base component linked to two
different facility components. This will be resolved in a future release. DR 141267
Manager
 When a user is printing a jpeg format image document it spools the print job into a
huge size. This will be resolved in a future release. DR 107832
 Manager isn’t saving the selected scanner. Selecting Scanner Devices only works
after selecting a scanner the second time. This will be resolved in a future release.
DR 109630

 The Select Default Printer window cuts off the first character of the printer name if
there is only one printer in the list. This will be resolved in a future release. DR
113500
 The effective date is only accurate to the minute with the database server time. It
should be accurate down to the second. This will be resolved in a future release.
DR 117329
 When ARIA OIS for MO is run on a machine that has regional settings of English
(United Kingdom) there is a database error that is thrown either on opening a
patient record or ordering a treatment plan for the patient. This will be resolved in a
 When a user tries to log in from the Application Lock window it will cause the ARIA
application to crash. This will be resolved in a future release. DR 133007
Meaningful Use
 Narcotics are included in the e-prescribe denominator. The stored procedure
references the med_name table to determine if a drug is a narcotic. If the drug is
found and is a narcotic, it is excluded from the denominator. The issue occurs when
Medi-Span deletes a narcotic drug during a quarterly update. The prescribed
narcotic is not found (as it is no longer in med_name) and it now is included in the
denominator. This will be resolved in a future release. DR 110708 110708
 When a patient's clinical summary values are 0/1, a blank cell is displayed in the
patient data tab (not 0/1). This will be resolved in a future release. DR 119851
 It is possible that some patients are shown twice on the patient data tab of the
meaningful use dashboard. This issue will be resolved in a future release. DR
122209
Medication Orders
 There is an issue with regimens where the phase is flagged as with a schedule type
of 'Linear - Neg. Days' and the starting day is a negative number. The regimen must
also have agents scheduled on a cycle day with a negative number. This will be
 When ordering a Cycle 4 Day 1 agent a message indicates the GFR value has
expired and lists the agents that could not be added to the order. This will be
 Dose recording rows are not created when an agent is ordered q14 days for 28
days, every other week. After ordering drugs, they are not showing in the drug
admin window. This will be resolved in a future release. DR 106995
 For Treatment Plan, the dose rounding logic is using the order dose rather than the
administration dose to determine the default rounding. This will be resolved in a
 The Salbutamol inhaler administration form is not being listed (for FDB). This will be
 The GFR collected date is not updated when GFR is recalculated. After ordering
regimen to the patient and utilizing new Creatinine value in the subsequent cycles,
the GFR's collected date remains as the initial collected date. As a result, the expiry

of GFR message will come earlier as specified GFR's "Age xx days" dose
management setting in Security. This will be resolved in a future release. DR
123973
 The Scheduled Drug Orders window does not filter preparation type correctly for
Aseptic drug preparation. This will be resolved in a future release. DR 124186
 It was reported that the immunization icon and message are not appearing on a
prescription reissue / reorder. This will be resolved in a future release. DR 126320
 When the user adjusts the ordering dose of a zero-dose plan agent in Adjust Dose
window, it does not recalculate the Admin dose. But when the user does it in the
Modify Dosage Specification window, the admin dose is calculated properly. Also, if
the user changes directly the Admin dose in Adjust Dose window, the Ordering
dose will be recalculated and the new Admin dose will reflect in the prescription.
 The user receives an unhandled database error when they order a First Databank
(FDB) agent with an agent name longer than 50 characters. This will be resolved in
 ARIA OIS for MO may incorrectly calculate or save ZERO value on cycle day when
approving an ad hoc or cycle scheduled agent order with the days of a week
scheduled for a range of days on a patient who is on a treatment plan. This causes
a foreign key database error because no cycle day of zero value is stored in the
patient's treatment plan time period table that is referenced by the patient treatment
plan cycle action table. This will be resolved in a future release. DR 129174
 The approve time and created time on the 1st day of the cycle are the same. But
the 8th day has a different approve time and creation time. In this work flow, the
user approves before an actual order is created. But the created time and approve
time should be consistent across all days within one cycle. This will be resolved in a
 There is a possibility that the agents can appear in a different display order on a
prescription print-out versus on the New/Modify/Review Prescriptions window. This
 There is no unit of measure for ‘mg/nosepc’, which is a new unit measure for agents
that can be administered in each nasal cavity. This will be resolved in a future
release. DR 142600
 For linear negative regimen, the 'cycle day' display on the Orders/Rx tab (of the
Medications window) does not display for zero or negative days. For example, cycle
one, day one displays as '<regimen name> - Cycle 1 Day 1'. But for zero or
negative days, the display appears as '<regimen name> - Cycle 1'. The part for the
cycle day does not appear. This issue will be resolved in a future release. DR
145471
 When Manager is back calculating the order dose (from a user entered admin
dose), Manager may not yield entered admin dose again on the Adjust Dose
window. This issue will be resolved in a future release. DR 152788
 The last ordered information is not saved when pending prescription is opened and
then approved without making any further changes to it. In this case, when the
Review Prescription Details window is opened, the last ordered section will not be
visible (because the last ordered information was not saved to the database). This

Medications
 It was reported that very long course descriptions may be truncated on the
Medications window. This will be resolved in a future release. DR 102930
 When a user is attempting to modify the master favorite agents list but the user is
unable to make any modification. This is because the master favorite agents list is
assigned to a provider. This will be resolved in a future release. DR 112721
 In previous versions of ARIA OIS for MO, users could supply their own name for
Medi-Span agents. The agt_name and agt_name_trans mapped these user-
supplied names to their Medi-Span agent name through the columns agt_name and
medi_drug_name. Varian no longer provides this support. Screening and e-
prescribing link right from the agent name to the med_name table, and Data Update
sets the agt_name in agt_name_trans equal to the medi_drug_name. The
medi_drug_name column should be removed. This will be resolved in a future
release. DR 120459
 Not all the dispensing options are shown in the agent selection window when using
FDB (USA, CAN, AUS). Several results may be returned but only a portion of them
may have dispensing strengths. They all should have at least 1 dispensing option.
FDB UK uses a completely different set of tables and may not be affected. This
 Frequencies in admn_dose_frq_unit without a match in admn_frq_hhmm are
causing the ARIA system to terminate. This will be resolved in a future release. DR
123115
 It was reported that the Scheduled Drug Orders report does not show records with
a non 00:00 time. This will be resolved in a future release. DR 126163
 When a regimen is automatically ended, the logic does not update tentative agents
(on the Medication History tab) to inactive. Note that active agents are correctly
updated from active to inactive. This will be resolved in a future release. DR 131654
 The user may get an error message when adding dose recordings for immunization
drugs, depending on the data saved in the country data table at the client site. This
is the error message received when dose recording an immunization drug from
Drug Administration window: “An item with the same key has already been added.”
 When the user is viewing a delay treatment reason (in the Delay Treatment
window) for regimen, the Ordered by field will show the internal ID rather than the
provider name when the ordered by providers userid is under 10 characters. Typical
ARIA OIS for MO userid are 10 characters and the typical ARIA OIS for RO userid
are not (i.e. CCS userid are not). This will be resolved in a future release. DR
133185
 ARIA OIS for MO crashes when the plan that the user is using doesn't have a
phase_seq_no = 1. The system is looking for a 1 in the phase and when it divides
by zero the system will crash. This will be resolved in a future release. DR 134473
 When ordering drugs that have an apostrophe (single quote) in the agent name,
ARIA Manager may crash. This issue will be resolved in a future release. DR
138945
 An empty favorite agent’s folder may display to the user. This will be resolved in a

 When starting a regimen that contains an age/weight based agent and a support
regimen (on the same prescription) it will cause an error when the user attempts to
order future cycles/days for the regimen that contains the age/weight based agent.
The user will get an error message and will not be able to order future cycles/days.
 The drug Folinic acid is incorrectly mapped to a generic agent of folic acid. This is
causing a dose limit warning to appear when ordering Folinic acid. The dose limit
warning says the dose limits come from folic acid. This will be resolved in a future
release. DR 140118
 When a user order’s cycles out of order for a support regimen, it can add extra
cycle to end. This will be resolved in a future release. DR 141265
 When the security setting in med management for course description format is set
for prescriptions to use action words, in cases where the form is considered a
device, it will create the course description with the form listed twice. This will be
 Prescriptions with refills are only being considered Active for the original length of
the order, not taking refills into consideration. This will be resolved in a future
release. DR 142078
 When ordering an ad-hoc agent on a one cycle treatment plan that has no cycle
day visit scheduled and no planned/scheduled agents, errors will occur. This will be
 The Change All and Change Unset buttons (in the Modification Reason group box
on the Adjust Dose window) do not add or change the reason to any agent that has
had their dose increased. This will be resolved in a future release. DR 143216
 The agent formulary does not enforce that the rounding method and round to
nearest fields are the same for agent formulary rows with the same agent name,
dosage form, strength and (strength) unit of measure. The route is not used to
determine the rounding. This will be resolved in a future release. DR 147541
 When utilizing "Dose Banding" it is possible for doses to be calculated to -1 when
multiple formulary rows exist of the same agent and form but different routes. This
 A user may receive an error message when attempting to approve a support
regimen with ad hoc agent, that have been saved as pending and is not being
modified. This issue will be resolved in a future release. DR 148556
 The drug screening interactions override reason is only displayed on last
prescription when approving a split order. The drug screening interactions override
reason should be displayed on all prescriptions created from the split order. This
 The last reconciled date is not updating when a non-provider creates a new 'as per
patient medication' in the medication history work space. This issue will be resolved
 The start date, in the medication history list, is incorrectly updating if a second
instance of a pick-up external agent is ordered, and it has dose recordings (either
dose level or agent level) and the first instance of the agent did not have dose
recordings. This issue will be resolved in a future release. DR 151610

 When there is a max single dose value configured (in Planner) for a planned agent
and that agent is ordered as a flat dose (e.g. 2 mg rather than 1 mg/m2), then the
user is shown the warning message on the Add/Modify/Dispensing Dose
Specification window regardless of whether the ordered dose is above or below the
max single dose. The max single dose is working correctly when the planned agent
is order as an ordered dose (e.g. 1 mg/m2) that is then calculated to an admin dose
(e.g. 2 mg, for a patient with a BSA of 2.00). This issue will be resolved in a future
release. DR 152382
Online Help
 The Flow Sheet Graph Window section in the online help does not show a minimum
or maximum range on the graph or reference a minimum or maximum. This will be
 The online help does not explain how IBW is calculated or what is returned patients
under 60 inches in height in the Medical Management Characteristics dialog box.
 The Security Help File for tag "“<%Approved/Signed Date%>" is incorrect as the
data tag from security reflects effective date in Notes footer where as it should
display current date as per the help file. This issue will be resolved in a future
release. DR 151751
Open Patient
 In a CCS environment users are unable to search by SSN in Manager when data is
updated by ARIA Oncology Information System (OIS) for Radiation Oncology. This
 When searching for patients on the Open Patient window by social security number,
users may not receive any information. This will be resolved in a future release. DR
121272
 Manager crashes if an apostrophe is included in a patient's ID. This will be resolved
 Using a Non-USA Windows date format (i.e. MM/DD/YYYY), in the Windows
regional setting, causes database errors when the day of the month is after the 12th
day. This occurs because the code is incorrectly using the day as the month and
this causes issues with values between 13 and 31. This will be resolved in a future
release. DR 143521
 A new patient can be created with two active primary IDs (e.g. MRN's) when there
is an outbound ADT interface configured. When a patient has multiple active
primary IDs, this will cause database errors in various windows. This issue will be
 If an agent has an apostrophe in the name, an invalid syntax database error will be
displayed when opening a patient that has been ordered that agent. This issue will
 The performance to load/refresh the Visit tab on the Open Patient window takes an
increasingly greater amount of time depending on the number of visits required to

be retrieved at a given institution. This issue will be resolved in a future release. DR
149815
 The patient status icons are not displaying on the Patient tab of the Open Patient
window after using the My Recently Opened Patients window. This issue will be
 The patient status icons are not visible on Patient tab (on the Open Patient window)
after a search is done for one or more patient. This issue only occurs when there
are no visits showing on the Visit tab. If there are visits showing on the visit tab,
then the patient status icons correctly appear on the Visit tab after searching for a
patient. This issue will be resolved in a future release. DR 152947
Patient Check-In
When Manager is configured to send scheduling messages upon checking, and a
patient is checked in, the Scheduling interface trigger is created before all necessary
data is updated. This will be resolved in a future release. DR 142443
Patient History
 Providers are reporting getting an error when updating the patient data on review of
systems. This is caused by the ability to modify the classification of 'History
Elements' as is it linked to the tab on the Patient History window. This will be
 If two users enter a patient's family or social history at the same time, both records
are saved and the patient shows two distinct histories. This will be resolved in a
 Need to restore missing "Add to Note" functionality/icon to Family History area. This
 The Modify Family History window does not save changes to SNOMED code
selection unless another change is also made to the row as well. This will be
 The patient Comment Edit Window and Patient Comment Window areas in the user
group access do not disable the “inactivate” button even though there is a check
box for it. A user is still able to inactivate a comment from this tab without access.
 The "Reviewed/Updated" flags don't get set when a patient's family history is
updated via the Agenda window or the Patient History window's family tab. This will
 When Review of System data tags are added to a note template, the appropriate
values are retrieved when using the template in the Notes window, but no data is
retrieved when it is used in the Chief Complaints, HPI, Impression, or Plan
windows. This will be resolved in a future release. DR 129131
 In Gynecologic History, if Para is greater than Gravida and 0 is entered into the # of
interrupted pregnancies, a message will appear saying the # of abortions must be
between 0 and the difference between gravida and para. Actually, 0 is an
appropriate selection in the case of multiple births. This will be resolved in a future
release. DR 131927

 The patient history information that populates in the note template via data tags is
not the same patient history information that is documented in the patient chart.
Patient Merge
 An issue was found when performing a patient merge with Quality Measures data,
QM NFQ 0419 - Met box does not update properly for the master patient after the
merge because the numerator is not met. This has been resolved in a future
release. DR 117836
 When a patient merge fails, the clinical description, for the diagnosis, becomes
blank. This will be resolved in a future release. DR 141332
 When a user tries to do a patient merge on patients that have data in the messages
table, an error message is displayed saying 'Cannot insert duplicate key in object
'dbo.message'. This issue will be resolved in a future release. DR 154390
Patient Summary
 In the "Patient history" window, if the “No Known Allergies” check box is checked
and an Adverse Reaction is documented, the "Adverse Reaction" will not display in
the Patient Summary. If the “No Known Allergies” box is manually unchecked, the
Adverse Reactions will appear on the Patient Summary. This will be resolved in a
 It was reported that Medication orders are not consistently appearing on the Patient
Summary Treatment details tab. When ordering a regimen’s Cycle 1 Day 1 with
internal and external agents, the external agent may not appear on the Patient
Summary. This will be resolved in a future release. DR 121324
 There is a discrepancy between Patient Summary's Treatment Details and
Treatment tab of the Medications window after regimen cycle days' agents first
ordered and cycle start date (cycle's target date in Scheduling) had been adjusted.
Pharmacy
 The user reported that they cannot pharmacy-approve a prescription that has been
dispensed, dose-recorded, and then both the dose recording and the dispensing
are marked in error. The prescription is no longer listed in the Pharmacy Approval
Window. This will be resolved in a future release. DR 131139
 The Scheduled Drug Orders window doesn't show future pending agent when there
is no visit scheduled for the administration date of the agent. This will be resolved in
Physician Orders
 If the user clicks the Use Latest button on the Physician Orders window, the orders
may not be populated if the most recent visit only has orders which are ad hoc (not
using a predefined type) or errored. The system attempts to find the most recent
visit that has an order, but the visit check does not consider the type or status of the

order and may select physician orders that cannot be copied forward. This will be
 A user was being prompted for a value for a patient when linking a physician order
to a prescription. This will be resolved in a future release. DR 127868
 The Physician Order icon in the micro help bar does not check user group access
before opening the Physician Order Transcription window. This allows a user
without access to the menu to open this window by using the micro help icon. This
 When adding Detail Description for an order in Physician Order Detail Window, if
information is entered in the optional Order Text Long window and OK is selected, a
red asterisk will not appear in Manager for the same order and institution. This will
 All physician orders, for a split order prescription (Rx), are not marked as
transcribed. The user needs to go to the Physician Orders window and manually
mark the physician orders as transcribed. This issue will be resolved in a future
release. DR 143980
 When transcribing a physician order from a planned, but unscheduled visit, without
opening the patient chart a database error will occur. This will be resolved in a
 When printing a physician order using a custom Crystal Report the performance
can be slow for other reports being run at the same time. This issue will be resolved
 There are three similar workflow that cause the 'Do you want to save your changes'
message to incorrectly appear when closing the Physician Orders window. The
message is not causing any incorrect data to be saved, or not saved. The message
is an extra click when closing the window. This issue will be resolved in a future
release. DR 153774
Plan Definition
When the user is ordering a medication to be given weekly x 6 months, only 6 doses of
the medication is added to Drug Administration. The issue is that a month and a year
is not a specific enough duration and Manager does not handle these values correctly.
Plan Management
When adding a non-clinical trial patient to a treatment plan and then converting that
patient to be a clinical trial patient, the user receives a database error. This will be
Plan Questionnaires
The Questionnaire Analysis window is missing the last item in each pick list style
question. This will be resolved in a future release. DR 142767

Plan Rules
 In Drug Order Management, if a user sets up rules to trigger based on age, when it
checks against the patient's age it may trigger early for greater than (>)
comparisons or may not trigger for less than (<) comparisons when it should,
depending on the number of leap years the patient has lived through. This will be
 In setting up a regimen, the user may be unable to save a plan rule with a long
diluent name description, resulting in an error message. This issue will be resolved
Plan Schedule
 The starting day on the phase marked as 'Linear - Neg. Days', cannot be changed if
the plan was created by copying an amended regimen. There are instances where
an amended version (version later than v.1) of a “Linear - Neg day regimen needs
to be copied and the starting day changed. The current functionality limits this
capability and only allows this change to be made on a copy of version 1. This will
 The user cannot change the 'Starting on' drop-down for day of the week back to
'blank' on the Schedule Events window in Planner. In the Schedule Events window
of Planner, if the user changes the "Starting on" drop-down to any day of the week
other than the blank value, the user becomes unable to change the value back to
blank. This will be resolved in a future release. DR 135482
 If a user selects the cancel button after updating some data and then selects cancel
on the pop-up (do you want to save changes) this will cause the user to receive a
NULL object reference error in schedule edit. This will be resolved in a future
release. DR 140267
Planner
 When importing an approved plan, the previous version is not marked as Amended
if the older version is below 10 and the new version above 10. The imported plan is
flagged as Amended and the older version remains marked as Approved. This will
 The Agent Dose Banding window may display the wrong dosage form and UOM.
 When the user is on a Data Window that allows you to save via the “Save As”
window, and the user chooses the PDF file type, the PDF file is created, but
remains empty (0 KB). This will be resolved in a future release. DR 129163
Plans
 There is an issue with unicode characters in data columns and the system not able
to retrieve the data in these circumstances. Cycles might not be correctly displayed
in the Treatment tab when the regimen's name is written in another language. This

 When a user amended plans, the audit history was not fully updated. This will be
 A user received an unhandled database error when the user tried to add a cycle
that had already existed during that user's session. This will be resolved in a future
release. DR 126873
 A treatment plan with non-cyclical decision days is not ordering all agents, for all
cycles and days, until the next cycle/day that contains a decision day. This can
leave some agents as non-ordered. This issue does not happen with cyclical
decision days. This issue will be resolved in a future release. DR 150458
Provider Approval
 If the user has set the effective date to a time in the future and confirms a diagnosis
or toxicity assessment via Provider Approval, the Last Modified date in the audit
history dialog shows the effective date/time instead of the actual date/time. This will
 The Test Result Image Links window displays an error message when it is closed
from the Provider Approval window (and no patient is open) and then Manager
terminates. This will be resolved in a future release. DR 132087
 When a user reassigns test results to be approved by a different provider, the last
modified audit row does not reflect the reassignment. This will be resolved in a
Providers
 The Provider Registry search functionality does not work as expected. When
searching for <LastName> in lowercase, more search results are returned for
<LastName>,<FirstName>, where the first letter is capitalized, than when searching
for <LastName>, <FirstNameInitial> in lowercase. For example, when searching for
“allen”, more search results are returned for “Allen, Adrian” rather than searching for
“allen, a”. This will be resolved in a future release. DR 129199
 In the provider registry, by not ensuring that the provider to organization link has the
"Send: Fax" selection to a provider or organization with a fax number, when
selecting the preferred method of correspondence to fax IEM will send out a fax
with the phone number of -1. This will be resolved in a future release. DR 133529
Questionnaires
 When printing a questionnaire, a numeric field value is getting cut off. When the
questionnaire is viewed in notes, it displayed correctly. This will be resolved in a
 In Task List, when a questionnaire has been "entered”, if the visit is canceled prior
to erroring that questionnaire, the questionnaire remains on the task list as an
"entered" status. This will be resolved in a future release. DR 113130
 An issue occurs when the same questionnaire is created twice on a patient, but
approved out of sequence and not all questions are answered. In this scenario, the
notes data tag will pull in the responses to the questions on the older questionnaire

(with the higher questionnaire ID, since they were approved out of order) that did
not have responses on the latest questionnaire (with the lower questionnaire ID).
Regimens
 If a patient is put on both a regimen and a support regimen the message to inform
the user if they want to auto-end the regimen on the last cycle day does not appear.
 There is a need to suppress the informational message about the different GFR
formula when the plan being discontinued does not have a GFR formula defined for
it. This will be resolved in a future release. DR 112893
 The user may receive a database error if the user is attempting to delay a regimen
that the patient has started for the second time that day. This will be resolved in a
 The user should not be allowed to start a patient on a new regimen and delete all
the planned/regimen agents (and leave only unscheduled agents) on the drug
order. This will be resolved in a future release. DR 118284
 User receives a message that BSA will be recalculated when discontinuing a
regimen ordered Cycle 1 Day 1 for the patient that does not have BSA defined in
Planner. This will be resolved in a future release. DR 120098
 When modifying a regimen, a user who cannot approve the change themselves
needs to enter a physician order for the change. If this order is set as having
'approval on file' the physician order will not appear in the selected provider’s
approval queue. This will be resolved in a future release. DR 122283
 A patient can end up with multiple “Intent to Treat” physician’s orders if the patient
is opened by two (or more) users at same time. This will be resolved in a future
release. DR 131881
 It is possible for Cycle 1 Day 1 to have an incorrect date when opening a pending
regimen prescription where Cycle 1 Day 1 only contains pickup agents (i.e. “pickup-
internal” agents). This will be resolved in a future release. DR 134539
 The message asking the user if they want to automatically end a regimen is
appearing when only a support regimen is ordered, for the same cycle number and
day number as the last cycle/day of the regimen. The message asking the user if
they want to automatically end a regimen should only appear when the regimen is
ordered. This will be resolved in a future release. DR 136661
 Plans with longer display names may have one word on the plan's display name
duplicated on the Orders/Rx tab of the Medications window. Also, the cycle and day
information may not display for plans with longer display names. This will be
 When transcribing an “intent to treat” physician order, the patient is started on the
version of the regimen that was saved when the physician order was created. There
is no notification on the first order that an amendment has been approved for the
regimen. There will be an indication of an amendment to the regimen for the second
cycle/day ordered. The dose amounts in an amended regimen are not referenced in
Manager on the first prescription (when starting the regimen). The issue occurs

when an “intent to treat” physician order is created prior to amending the regimen.
 After ordering a Carboplatin regimen that is originally AUC (CrCl), but changing it to
instead use AUC (EDTA) as the dosage unit, the future cycles will still have the
CrCl button displayed and not the EDTA button. This will be resolved in a future
release. DR 141972
 A planned agent can be placed in an incorrect diluent bag when an agent under
other drug ordered is ordered on two different cycle days. This issue will be
Registration
 On the Patient Key Configuration window in Security, patient IDs can be marked as
required to make sure that the patient has a valid and current value entered. In
Manager, on the Modify Patient window on the Patient IDs tab, it is only checked to
ensure that the user has entered a value for the required patient ID. It is not
checked if the patient ID is marked as valid, this will be resolved in a future release.
DR 102418
 The user is not allowed to make a manual entry in the occupation and education
level drop down boxes on the patient demographics window. This issue will be
Reminders
 A Personal Reminder is sent to a user. That user is then inactivated. When
returning to Reminders in Manager, the inactivated user is shown as code in the
Reminders Recipient field. This will be resolved in a future release. DR 105362
105362
 A user reported when printing a prescription then pushing the Reminders button (on
their toolbar) before the hourglass goes away, the prescription printing will result in
Manager closing. This will be resolved in a future release. DR 113480 113480
 When a user selects the “Show Current Institution” check box on New Reminders, a
data base error may occur. This will be resolved in a future release. DR 123960
 The recipient drop-down is not correctly filtering when the ‘Show Current Institution’
check box is checked (on the New/Modify Reminder window). Instead of showing a
filtered list of recipients who have an institution of practice that matches the
institution that the user is currently logged into, the drop-down is empty. This will be
 When viewing a reminder where the recipient is an inactive, this results in the
recipient field being populated with userId + isntID which is of no value (and
confusing) to the end user. This issue will be resolved in a future release. DR
146601
Reports
 The Patient Calendar of Events report uses a hard-coded m/d/y date format to
calculate the date range for its events. If the system is using a different format it

may fail due to parsing errors in the date. This will be resolved in a future release.
DR 118613
 The Institution's Date Format Settings in Security are not respected in the patient
search window, which is launched from the Reports window. The Date Format for
the Date of Birth field in the reports window remains as "mm/dd/yyyy" regardless of
the date format selected in Security >Institution>Settings >Format window. This will
be resolved in a future release. DR 121064 121064
 When 2 (or more) parameters are configured with the same display type, and the
display type opens a search window (via the flashlight icon), the last parameter row
for the report will be populated with the row selected in the search window. The row
with the flashlight that the user clicked on is not set. This will be resolved in a future
release. DR 124445
 When the user is printing multiple agents (from a prescription) using a (custom)
Crystal Report the user will encounter a database error. The exact limit depends on
the IDs of the selected agents. The user should be able to print between 10 and 12
agents without encountering this issue. This will be resolved in a future release. DR
142206
 The appointment schedule report is repeating a patient ID in the header, without a
label, rather than printing the configured patient ID (with its label) in the header of
the report. This only happens when printing from the Open Patient window or the
Reports window. When the schedule report is printed from the Patient Schedule
window, all the patient's ID are correctly printed (and labeled) on the report. This
 The "Schedule - Patient" report does not return any data, for any patient. This
affects all clients who are running 13.6 (and above). This issue will be resolved in a
Review of Systems
If a user enters data in Review of Systems/Physical Exam for a scheduled patient and
then the user cancels and reschedules the patient's visit, the user is unable to delete
the RoS/PE data previously entered on the cancelled visit. This will be resolved in a
Scheduling
 The Appointment Schedule report is not consistent with the displaying of the patient
ID information. This will be resolved in a future release. DR 112907
 In a CCS environment if a patient has a radiation oncology visit the same day as
the regimen Target Date, then the radiation oncology visit will link to the regimen
Target Date. This will be resolved in a future release. DR 114314
 If the user attempts to reschedule a plan visit, a split visit which is partially cancelled
can be created. The user is then unable to cancel the remaining part of the visit.
 It is possible to overbook a location in the schedule windows (when configured to
not allow overbooking) if two users save to the same location/time slot
simultaneously. This issue will be resolved in a future release. DR 131985

 When in a patient's schedule, if the user selects a visit and clicks the Cancel button
it will open the cancel window if the window shows other visits that can be selected.
If the user expands one of the other visits it will show all the appointments of the
visit as selected, but if the user selects Okay to cancel it won't cancel the visit the
user expanded. If the user deselects and reselects an appointment of the visit the
appointment will be canceled when OK’d. This will be resolved in a future release.
DR 134270
 A user reported patient scheduling expanded view pop-up can appear when user
has moved to an empty grid or outside of the grid. The details in the pop-up will
refer to the closest cell to where the mouse currently is, rather than the last valid
cell the user was hovering over. This will be resolved in a future release. DR
141862
 When a user reviews cycle/day visits (from a regimen) with no internal type agents
that are scheduled, the visits will be shown in the Patient Schedule window as
target visits. This will be resolved in a future release. DR 141877
 Manager can delete an open chart visit if a user is closing this open chart visit, that
IEM just created, if IEM is still in the middle of processing the remainder of the
message and has not yet saved and committed the new note linked to this open
chart visit. This issue will be resolved in a future release. DR 151297
 When opening the Provider Schedule report from the Open Patient window there is
an issue where the providers name and institution name was cut off in the header of
the report. This issue is due to the client having a long institution name and the
application does not adjust the text to fit in the space that has been allotted for it.
Security
 When logging into Security and Planner the Medi-Span license or expiry message
should not occur for sites that are set to FirstDatabank. There is no functional
impact but it causes significant and undue confusion for the users. This will be
 When adding a new user, the user is unable to add ID keys until the new user is
saved unless the provider check box is checked before the physician discipline is
chosen. This is also an issue in a CCS environment when a Doctor User is created
in ARIA OIS for Radiation Oncology and this user is then opened in ARIA OIS for
MO: The ID Keys tab is empty until unchecking and re-checking the Provider check
box. This will be resolved in a future release. DR 111376
 A user is unable to modify the Drug Administration Document Registry window if the
user has lots of filled in “IV” questionnaires for patients. This will be resolved in a
 Users receive an error when clicking the Formulary Dispensing Link map button in
Security. This will be resolved in a future release. DR 117563
 Users can create two compliance periods with the same name. When this happens
on the ARIA RO side, a message box is displayed stating that two compliance
periods cannot have the same name. However, this message box is not displayed
on the ARIA MO side. This will be resolved in a future release. DR 122197

 When a user logs into a parent institution in Security that does not have any
locations set up from the location registry, the user will receive an error when they
attempt to navigate to Scheduling->Location Registry -> Tracking Type Relations...
window. This will be resolved in a future release. DR 123968
 A user was prevented from adding new races or ethnicities in the Demographic
Registry in Security. This issue affects ARIA OIS for MO -only sites. This will be
 It was reported that various exception errors can occur when attempting to copy
medical problem or surgical procedure lists to other institutions. This will be
 In the Toxicities tab of the Medical Management window in Security, the Copy to
Inst button can lead to a database error preventing adding toxicities to some
institutions. This happens when the source and target institution have a similar
number of related toxicity values. This will be resolved in a future release. DR
136335
 A user incorrectly gets a message about updating the diagnosis codes for all
patients when changing the performance status scheme. This message should only
appear when the diagnosis code is changed. This will be resolved in a future
release. DR 139461
 When a user/provider is created FIRST in Data Administration and then selecting
the user in Security and linking the userid, the Physicians are not showing from the
list of Physicians available for patient. This issue will be resolved in a future release.
DR 140404
 A user reported the display order of institutions is not consistent from list to list. For
example, on the institution select window and the switch institution list (in Manager).
The list should be sorted based on the order that the institutions were added to the
database. This will be resolved in a future release. DR 141844
 When the user adds specific toolbar links in the workup menu, the mappings are
incorrect and the toolbar items are disabled. The incorrect toolbar to menu
mappings are: Adding the Patient Messages toolbar links to the Immunization menu
item. Adding the Inbound Transition of Care toolbar links to the Patient Messages
menu item. Adding the Outbound Transition of Care toolbar links to the Inbound
Transition of Care menu item. In each case the toolbar item and the (incorrect)
corresponding menu item is always disabled. This will be resolved in a future
release. DR 142694
 The Drug Desc ID field on the New/Modify Agent Formulary window is no longer
updating each quarterly Medi-Span update that is processed. This field is now
obsolete and it should be removed from the window. This will be resolved in a
 When users export a large volume of C-CDA’s, it takes significantly longer than
processing each patient individually. This will be resolved in a future release. DR
145215
 When the user deletes multiple application/institution combinations in the same edit
session, only the last application/institution combination that the user deleted is
actually deleted from the database. All the other application/institution combinations
are restored. The user must delete only one application/institution combination per
edit session. This issue will be resolved in a future release. DR 148184

 When upgrading to 13.6 it is possible for certain rights access to inadvertently be
granted to existing user groups. This will be resolved in a future release. DR
148829
 The MO user mapping tool in 15.1 MR1 (U2) currently takes only the first part of the
Fully Qualified Domain Name (FQDN) and uses this as the basis for all user names
it saves in the database when you hit confirm mapping. This issue will be resolved
 In a CCOW configured environment, Manager does not properly close its
connection to the CCOW (Caradigm) vault when the user closes Manager using the
File/Exit menus. This causes the clean-up of the online log to not complete
successfully. When the user next launches Manager, they are incorrectly should the
prompt that they are already logged in. This issue will be resolved in a future
release. DR 153912
 The 'Change Password' menu option is still accessible in the application even
though this functionality is no longer used in the Active Directory configuration. This
Settings
 In Security, Modify User Group window, when the "Show/Apply Regimen
Amendments" option is unchecked, users expect that access to this menu option
will be restricted in the Medications Window Treatment tab. However, the menu
option was accessible. This will be resolved in a future release. DR 117915
 In versions prior to 13.6 MR1, the PTKEYCDSIN and PTKEYCDSSN ini parms
were not in the database by default. This led to Manager using the default SIN and
SSN pt_key_cd values of 41 and 42, respectively. In version 13.6MR1 and later, the
ini parms are set when the user makes other changes in the Institution Settings
window (in Security). However, if these values are added into the database, by
default with a value of 0. This issue will be resolved in a future release. DR 151584
Tests / Labs
 If there is an ARIA OIS for Radiation Oncology set of vital signs, then there is a
value in the database for the height and the weight, but the BSA will be null. When
this same set of vital signs is opened in AIRA OIS for Medical Oncology in view
mode, ARIA OIs for MO is going to follow its logic and calculate and show the BSA
(because it is null). This will be resolved in a future release. DR 102293
 A user reported Test names do not print correctly when the associated base
component name has more than 20 characters in an unbroken sequence (without
spaces) and the facility component name exceeds 20 characters. This will be
 A user reported that it is possible to show the check box beside the wrong
test/group when ordering tests. If the user saves and re-opens the test order, the
right test group is saved. But it looks confusing to select the test group that the user
wants to order. Then user will see the window show the checkmark beside a
different test (or test group). But, the window ultimately is saving the correct test
group that was initially selected. This will be resolved in a future release. DR
126387

 It was reported that test results for individual components in a combined test order
can be collected at different times. This date and time are saved separately for
each result but a date collected is displayed for the entire order in multiple places.
The date shown for some test orders is inconsistent because the same logic is not
being used in all cases. In the case of patient history test window, the latest date
collected for a given test order is displayed. The requisition view / edit window
currently displays the first date returned from the database. This will be resolved in
 When a user manually enters minimum and maximum (min/max) values, the values
may be cut off, depending on how many digits are entered and the test results
format chosen. This will be resolved in a future release. DR 138670
 A user reported having issues when the same base component is linked to more
than one facility component. 140442
 There is an incorrect database mapping for the units of measure for 'ISR' and for
'kcal/100 G'. This occurred after the upgrade to version 13. This issue will be
 A test result row for Cr Clearance (est) is not ordered/created when using the
Assessment > GFR menu if the patient's gender is a value other than male or
female. This will be resolved in a future release. DR 149448
 There is an issue where a specific workflow for accessing a patient’s tests results in
a null object reference error. A user may receive this error while navigating in the
scheduling workspace, selecting a test and modify the test results and then
cancelling or closing the window. This issue will be resolved in a future release. DR
153644
Toxicities
 Objective toxicities listed in Planner and Security are not available to be used in
Manager when creating a new toxicity. Objective toxicities are only generated by
test results. They cannot be selected nor do they appear in Manager when trying to
create a new toxicity for a patient. The selections available in Manager are only
subjective toxicities. This will be resolved in a future release. DR 106584
 When a patient is currently on a Treatment Plan and an entered (but not approved)
toxicity assessment is marked in error, a new pending toxicity assessment should
not be created. This will be resolved in a future release. DR 113128
 The NCI CTCAE V4.03 SI grading scheme incorrectly grades the objective toxicity
component of Cholesterol. The incorrect ranges will cause almost every patient to
get assessed with a grade 4 value for this (objective) toxicity component. This will
Users
 When a user highlights a user in Security and selects Modify, and then clicks on the
audit note pad icon, the user receives an error. This will be resolved in a future
release. DR 109885
 When a user opens User Registry and selects a user who has not been modified,
and the user clicks Modify, which will open the Name Change Log window (“A” icon

beside Add button), the user will receive an error and the application will close. This
Vital Signs
Vital signs can be approved after deleting (or blanking out) all test values because the
BSA/BMI values get set to zero rather than NULL. A message should appear telling
the user that the test cannot be approved because there are no values entered. This
Contact Varian Customer Support

Varian Customer Support is available on the internet, by e-mail, and by telephone.
Support services are available without charge during the initial warranty period.
The MyVarian website provides contact information, product documentation, and other
resources for all Varian products.
1. Go to www.MyVarian.com.
2. Choose an option:
 If you have an account, enter your User login information (email and password).
 If you do not have an account, click Create New Account and follow the
instructions. Establishing an account may take up to two working days.
3. Click Contact Us at the top of the window to display customer support and training
options, and international e-mail addresses and telephone numbers.
4. From the Contact Us page, choose an option:
 Call Varian Medical Systems support using a phone support number for your
geographic area.
 Complete the form corresponding to your request for use on a call with a live Varian
representative; then follow the instructions to complete the remote connect options,
and click Submit.
You can order documents by phone, request product or applications support, and
report product-related issues. Links on the MyVarian website navigate to other support
resources for products, services, and education.
5. To find documents, click Product Documentation.
Online documents in PDF format include customer technical bulletins (CTBs,) manuals,
and customer release notes (CRNs).

ARIA OIS For Medical Oncology 15.5 Customer Release Note

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ARIA OIS For Medical Oncology 15.5 Customer Release Note

Transféré par

Droits d'auteur :

Formats disponibles

ARIA Oncology

Information System for

P1026016-003-C APRIL 2018

Manufacturers Varian Medical Systems, Inc.

2 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

CAUTION US Federal law restricts this device to sale by or on the order of a

Copyright © 2016–2018 Varian Medical Systems, Inc.

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 3

4 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 5

6 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 7

WARNING This customer release note is intended for medical

WARNING A warning describes actions or conditions that can result in

CAUTION A caution describes actions or conditions that can result in

Notice A notice describes a practice not related to physical injury to

Note A note describes information that may pertain to only some

8 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

ARIA Oncology Information System for Medical

System Components / Compatibility

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 9

Changes in ARIA OIS for Medical Oncology Database Hot Fix 2

Changes in ARIA OIS for Medical Oncology Database Hot Fix 1

10 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

New Features and Enhancements in ARIA OIS for Medical

ARIA MO Version 15.5 New Main Features

The AJCC 8th Edition

Australian National Guidelines for Units of Measure & Frequencies

Treatment Tab Modifications

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 11

Drug Administration Additional Details Modifications

C-CDA Generation and incorporation

Clinical Decision Support

12 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

Measure Title Version

CMS 50 Closing the Referral Loop: Receipt of Specialist 5.0

NQF 0018/CMS 165 Controlling High Blood Pressure 5.0

NQF 0022/CMS 156 Use of High-Risk Medications in the Elderly 5.1

NQF 0032/CMS 124 Cervical Cancer Screening 5.0

NQF 0034/CMS 130 Colorectal Cancer Screening 5.0

NQF 0418/CMS 2 Preventive Care and Screening: Screening for 6.3

NQF 0419/CMS 68 Documentation of Current Medications in the Medical 6.1

NQF 2372/CMS 125 Breast Cancer Screening 5.0

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 13

New Feature: Import and Calculate

Data Export Service

14 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

File Service Subfolder Repositories

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 15

16 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

Attaching Diagnoses to e-Prescriptions

E-Prescribing Surescripts Medication History

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 17

E-Prescribing Eligibility, Formulary, and Benefits

External Oral Liquid Agents

18 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

ARIA Security Changes

MIPS ACI Dashboard

ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY 19

MIPS Calculation Update

20 ARIA ONCOLOGY INFORMATION SYSTEM FOR MEDICAL ONCOLOGY

Patient Health Information

Patient Family History