MOSAIQ and ARIA Audit Log Requirements for Radiation Oncology Compliance

You rely on MOSAIQ and ARIA as your Oncology Information System (OIS) backbone, tightly connected to the Electronic Medical Record (EMR). To meet radiation oncology compliance, your audit logs must be accurate, interoperable, and secure while supporting Quality Assurance (QA), Treatment Verification Logs, and Workflow Automation. The guidance below defines what to capture, how to protect it, and how to use it.

Audit Log Data Integrity

Principles you must enforce

• Completeness: capture every security- and safety-relevant event across MOSAIQ and ARIA, including reads, writes, approvals, deletes, and electronic signatures.
• Accuracy: use synchronized timestamps with time zone and millisecond precision; prevent clock drift with enterprise NTP.
• Immutability: store logs append-only with tamper-evident hashing and write-once (WORM/object lock) retention.
• Traceability: link each event to a patient, plan, device, and user to reconstruct the clinical narrative end-to-end.

Minimum fields for MOSAIQ and ARIA audit events

• Event metadata: event ID, timestamp (UTC and local), source system (MOSAIQ/ARIA), workstation/device ID, IP, application/version.
• User context: user ID, role, authentication method (including MFA), session ID, location.
• Patient context: MRN, encounter/visit, plan ID, course/fraction, beam/field where applicable.
• Action details: action type (view/create/update/delete/approve/reject/export), reason code, previous value/new value, outcome (success/failure) with error codes.
• Safety signals: Treatment Verification Logs (delivery start/stop, overrides, gating status, imaging approvals, interruptions, tolerance checks).
• Integrity markers: record sequence, cryptographic hash, and parent/child correlation IDs.

Technical safeguards for integrity

• Database controls: use Structured Query Language (SQL) Server Security features—Transparent Data Encryption (TDE), Always Encrypted for sensitive columns, SQL Server Audit at server and database scope, Row-Level Security, and least-privilege roles.
• Tamper evidence: append-only storage policies, checksum/hashing of log batches, and signed export bundles for external review.
• Resilience: redundant log collectors, message queue backpressure handling, and immutable backups with periodic restore testing.
• Validation: automated reconciliation between clinical events and audit counts, alerting on gaps, time skew, or out-of-order sequences.

Compliance with Federal Security Policies

Control objectives to satisfy

• Audit controls: capture who accessed what, when, where, why, and how—covering EMR integrations, orders, plan changes, approvals, and treatment delivery.
• Integrity and non-repudiation: ensure records cannot be altered without detection; preserve chain-of-custody for regulatory or legal review.
• Monitoring and response: retain security-relevant events and forward them to your SIEM for correlation, alerting, and incident handling.

Policies and frameworks to align with

• HIPAA Security Rule requirements for audit controls, access control, integrity, and transmission security across your OIS and EMR.
• NIST-aligned practices for logging, event correlation, and retention to support federal program participation and security assessments.
• Federal and Department Privacy Policies defining acceptable use, minimum necessary access, breach reporting, and secondary use restrictions.
• 21 CFR Part 11 expectations (where applicable) for audit trails and electronic signatures in regulated research workflows.

Evidence you should maintain

• Documented logging policy, control mappings, and data dictionaries for MOSAIQ and ARIA event types.
• Procedures for periodic review, access recertification, and exceptions management.
• SIEM dashboards and sample investigations demonstrating detection, triage, and resolution of audit alerts.

Integration of MOSAIQ and ARIA Systems

Unifying event semantics

• Create a crosswalk that normalizes action verbs (e.g., PLAN_APPROVE, FIELD_EDIT, IMAGE_VERIFY, TREATMENT_OVERRIDE) across both systems.
• Adopt a shared correlation key combining MRN, encounter, plan ID, and device UID to stitch events into a single patient timeline.

Interfacing patterns

• Leverage HL7 (ADT/ORM/ORU) for patient and order context, DICOM-RT for plan/delivery artifacts, and available APIs for enriched audit export.
• Use near–real-time streaming or scheduled ETL into a central audit repository, with idempotent upserts and duplicate suppression.
• Maintain interface heartbeat and acknowledgment logs to prove delivery and detect gaps.

Quality gates for integrated logs

• Correlation integrity: every treatment delivery event must match a verified plan approval event and an active order.
• Temporal consistency: enforce monotonic sequence numbers and bounded skew across MOSAIQ and ARIA.
• Error quarantine: isolate malformed events, capture root cause, and reprocess after remediation.

Record Retention and Access Controls

Patient Record Retention for audit data

• Retain audit logs at least for the duration of your Patient Record Retention schedule; many programs keep 7–10 years for adults and longer for minors in line with institutional policy.
• Preserve legal holds and research-related records beyond baseline retention when required.
• Use immutable storage (WORM/object lock) and versioned backups; verify restorability through periodic drills.

Access governance

• Role-based access control with separation of duties: administrators, auditors, physicists, therapists, and privacy officers have distinct, least-privilege rights.
• Break-glass workflows with automatic justification capture and heightened auditing.
• Workflow Automation for provisioning, deprovisioning, and quarterly access recertification.

Structured Query Language (SQL) Server Security essentials

• Encrypt in transit (TLS 1.2+), enable TDE at rest, and apply Always Encrypted for identifiers (e.g., MRN) where feasible.
• Harden authentication with contained users, secure service accounts, password vaulting, and MFA on administrative interfaces.
• Enable SQL Server Audit, restrict ad hoc queries on raw audit tables, and provide read-only audit views for investigators.

Quality Assurance through Audit Logs

Using logs to strengthen clinical safety

• Cross-check Treatment Verification Logs against approved plans to detect wrong-patient, wrong-plan, or wrong-field risks.
• Trend overrides, imaging reattempts, and interruptions to target training or workflow fixes.
• Automate pre-treatment checks that flag plan edits after approval or dose parameter deviations.

Operational analytics

• Monitor time-to-approval, queue times, and fraction start delays to reduce bottlenecks.
• Correlate incident reports with audit events to drive corrective actions and process control charts.

Data Flow and Interoperability Management

End-to-end flow you should map

• EMR order → OIS (MOSAIQ/ARIA) scheduling → treatment planning → plan approval → delivery → verification → documentation and billing.
• For each hop, define the emitting system, transport, schema, retry policy, and audit checkpoints.

Designing for reliability

• Use queue-based ingestion with exactly-once processing semantics and dead-letter handling.
• Measure lag, loss, and duplication; alert when SLAs or completeness thresholds are breached.
• Version your schemas and maintain backward compatibility during upgrades.

Protection of Sensitive Patient Information

Privacy-by-design controls

• Collect the minimum necessary identifiers; tokenize or pseudonymize audit exports used for analytics.
• Align data elements and access to Federal and Department Privacy Policies, including secondary use and disclosure restrictions.

Security hardening

• Encrypt data in transit and at rest; manage keys in an HSM or approved key vault with rotation and dual control.
• Isolate audit infrastructure on segmented networks; restrict administrator access and monitor with EDR and DLP.
• Continuously patch OIS components, databases, and OS layers; validate vendor updates in a non-production environment first.

Monitoring and response

• Forward logs to a SIEM; create detections for anomalous access, mass exports, off-hours approvals, and repeated overrides.
• Test incident playbooks covering privacy events, integrity alerts, and data exfiltration attempts.

Conclusion

To achieve radiation oncology compliance, configure MOSAIQ and ARIA to emit complete, immutable, and correlated audit trails; centralize them securely with Structured Query Language (SQL) Server Security controls; and use the data to enforce access, strengthen QA, and protect privacy. When integrated with your EMR and Workflow Automation, audit logs become a reliable, interoperable source of truth for both safety and governance.

FAQs

What are the federal audit log requirements for radiation oncology systems?

You need audit controls that record who accessed or changed protected health information, when, from where, and why. Logs must capture reads and writes, approvals and electronic signatures, and security events, with integrity safeguards and timely monitoring. Align your controls to HIPAA, relevant NIST-aligned logging practices, and—if applicable—21 CFR Part 11 expectations for audit trails.

How do MOSAIQ and ARIA ensure compliance with privacy regulations?

MOSAIQ and ARIA provide detailed auditing, role-based access, and integration with enterprise identity and SIEM. When you enable encryption, enforce least privilege, and centralize logs with Structured Query Language (SQL) Server Security features, the OIS platforms help you meet HIPAA and Federal and Department Privacy Policies while maintaining patient safety and operational transparency.

What data must be retained in audit logs for radiation oncology?

Retain event metadata (timestamps, source, device), user identity and role, patient and plan context, action type with reason codes, previous/new values, and outcome. Include Treatment Verification Logs—delivery start/stop, overrides, imaging approvals, interruptions—and integrity markers like sequence numbers and hashes. Keep logs for at least your Patient Record Retention schedule, extending for legal holds or research as required.

How is audit log data integrated between MOSAIQ and ARIA?

Normalize event vocabularies, assign shared correlation IDs (MRN, encounter, plan ID, device), and move data via HL7/DICOM interfaces or available APIs into a central repository. Use idempotent ETL or streaming, deduplicate duplicates, verify acknowledgments, and continuously reconcile completeness to ensure a seamless, patient-centric audit timeline across both systems.