Term

Definition

ClosedDateTime

The date when the event was resolved. If the event hasn't been resolved, the default value for this field is: 99991231.

CompletedActionsPlans

The number of action plans completed for this event.

DateTimeOfEvent

The date when the event happened.

Dayoftheweek

The name of the day in which the event happened. For example, 1.Monday, 2.Tuesday, etc.

DaysSinceLastEvent RaisedOfType

Number of days since the last event of this type was created. This number counts from the latest data refresh, which normally happens once a day. Note: The measure is DaysSinceLastEventRaisedOfType (there is a blank space in the previous column for display purposes only).

DescriptionOfEvent

The description of the event.

EventDayOfWeek

The day of the week the event happened.

EventId

The unique number for an event added at the end of the Radar Healthcare URL. For example, the last 4 digits at the end of this fake URL would be the eventId:  yourorganisation.radarhealthcare.net/incident/1234

EventIsOpen

Notes if the event is still not resolved.

EventSubType

The subtype of event.

EventTime

The time the event happened.

EventType

The type of event.

EventUID

The main, unique number that identifies an event. Events, or incidents, are one of the key elements in your data.  Typically, they are things like accidents, compliments, or complaints, but they can be anything that is relevant to your organisation.

ImpactLevel

The impact or consequence of the event.

IsConfidential

Notes if this this a confidential event.

IsPositiveEvent

Notes if this this a positive event.

LiklihoodLevel

The likelihood of the event happening.

Location

The name of the location that this event is associated with.

LocationUID

A unique number that identifies the location that this event is associated with, used for data security.

Organisation

The name of your organisation.

OrganisationCode

A short code that identifies your organisation, used for data security.

OrganisationId

A unique number that identifies your organisation, used for data security.

OrganisationKey

A unique number that identifies your organisation, used for data security.

OutstandingActionPlans

The number of action plans still to be completed for this event.

RaisedDateTime

The date when the event was created in Radar Healthcare.

RaisedDayOfWeek

The day of the week the event was created.

RaisedTime

The time the event was created.

Reference

A unique code for this event, made up of letters (defining the event type) and a number (automatically assigned).

Region

The name of the region that this event is associated with.

RegionUID

A unique number that identifies the region that this event is associated with.

ReportedBy

The name of the user who reported the event.

RequiredFormDuration

The number of minutes it took to complete the form required to create an event.

RequiredFormStatus

The status of the required form, such as completed or abandoned.

RiskScore

Total risk score for the event.

TimeToCompleteDays

The number of days it took for the incident to be resolved.

TimeToCompleteHours

The number of hours it took for the incident to be resolved.

TimeToRaiseHours

The amount of hours between when the event happened and when it was created.

TimeToRaiseMinutes

The number of minutes between when the event happened and when it was created.

UpdatedDateTime

The last time the event was updated.

WorkflowStatus

The status of the event, such as planned, pending, overdue or completed.

Term

Definition

_OrganisationId

A unique number that identifies your organisation, used for data security.

AssignedManagerName

The name of the manager of the user assigned to this workflow step.

AssignedName

The  name of the user assigned to a particular workflow step.

assigneelastlogon

Date and time when the assigned user last logged on.

CompletedDateTime

The date and time when the workflow was completed.

completedemailaddress

The email address of the user who completed a particular workflow step.

CompletedManagerName

The name of the manager of the user who completed this workflow step.

CompletedName

The name of the user who completed a particular workflow step.

CreatedDateTime

The date and time when the workflow was created.

CurrentStage

Current step in the workflow.

CurrentStageIndicator

Notes if a workflow step is the current step.

DescriptionOfEvent

The description of the event.

DueDateTime

The date and time when this workflow was due to be completed.

earlylatetime

Time between when a task was completed and when it was due. A negative number means the event was completed before it was due (early). A positive number means the event was completed after it was due (late). The number itself is the number of hours early or late.

EmailAddress

The email address of the user assigned to a particular workflow step.

EventStatus

The status of the event, such as planned, pending, overdue or completed.

EventType

The type of event.

EventUID

The unique number that identifies the event, used in this table to link the event with the specific workflow.

FormTemplateName

The name of the form template, used internally.

hourssincelaststep

Number of hours since the last step in the workflow was completed.

lag1completedtime

The date and time when the previous step in the workflow was completed.

Reference

A unique code for this event, made up of letters (defining the event type) and a number (automatically assigned).

timesincelaststep

Number of days since the last step in the workflow was completed.

TimetoCompleteTask

Time it took to complete a workflow step.

UserActive

Notes if the assigned user is active.

wastheworkflowstepLate

Notes if the workflow task was completed late.

WorkflowAction

Describes the main action from this workflow: trigger an action plan, raise a task to be edited, triggered an investigation, etc.

WorkflowActivityName

Name used internally for a workflow trigger.

WorkflowController

How the workflow was triggered. For example, triggered by a form where there was a specific answer, by an investigation, by the incident type, etc.

WorkflowDefinition

The name of this workflow.

WorkflowDescription

The name of the workflow step.

workflowprocessfollowed

Notes if the workflow was followed.

Workflowstatus

The status of the workflow, such as pending, overdue, planned, complete, etc.

WorkflowStepPropertiesKey

A unique number for the parent workflow step (not the specific instance linked to an event)

WorkflowStepUID

A unique number for this specific workflow step (not the parent workflow step).

Term

Definition

EventUID

The unique number that identifies the event, used in this table to link the event with its tags.

Tag

The tags assigned to this event. Tags are a way of grouping locations, documents or any other data together based on a theme. In reporting, tags can be used to filter data.

TagSource

The place where the tag was created: form, location or region.

TagType

The type of tag: module, location or region.

Term

Description

Assigned to

Name of the user that this task is assigned to.

AssignedToUserUID

A unique number that identifies the user that this task is assigned to, used for data security.

Comments

Comments related to the task.

CompletedDate

Date when this task was completed.

Created on

Date when this task was created.

Createdby

Name of the user who created this task.

DueDate

Date when this task is due to be completed.

Event Id

A unique number that identifies the event that this task relates to.

EventType

The type of event that this task relates to.

Id

A unique number that identifies an event task.

Last updated

Date when this task was last updated.

Location

The name of the location that the event for this task is associated with.

LocationUID

A unique number that identifies the location that the event for this task is associated with, used for data security.

Priority

Notes the priority level of this task.

Region

The name of the region that the event for this task is associated with.

Status

The status of the task, such as complete, overdue, planned or pending.

Task Details

Description of the task, set by the user who creates the task.

Term

Description

_RecordStatus

The status of the audit. The possible options are 0 (archived) and 2 (active).

Abandoned

Notes if the audit has been abandoned (typically before completion).

AbandonReason

The reason why the audit was abandoned, from the comment typed by the user who abandoned it.

ActionPlanEndDate

The date when the action plan associated to this audit was completed.

ApprovedByUser

The name of the user who approved the audit.

ApprovedDate

The date when the audit was approved. Approving an audit is a compliance step set when creating the audit. A choice is made at that point about whether the relevant line manager needs to approve the audit (to ensure there are no empty answers, for example) or whether users can approve their ow audits.

AuditID

A code that identifies an audit, typically added at the end of the audit's URL.

AuditsAwaitingApproval

Notes whether an audit is awaiting approval or authorisation.

AuditsIncomplete

Notes whether an audit is still to be completed.

AuditsSelfApproved

Notes whether an audit has been approved by the same user who answered the audit questions.

AuditStage

The stage the audit is in. In legacy audits, the possible stages are: unknown, not started, locked, audit in progress, action plan required, action plan in progress, awaiting authorisation and audit complete. In the new enhanced audits, the possible stages are: not started, authorisation, action plan in progress, audit in progress, audit complete and audit closed.

AuditsWithActionPlanRequired

The number of audits with an action plan associated to them.

AuditsWithMajorNonConformities

The number of audit responses with major non-conformities or failures. These are defined when creating an audit.

AuditsWithUnacceptableScore

The number of audits with a score lower than a set threshold. This threshold is set when creating an audit.

AuditTypeName

The name of the score scheme or system for the audit.

AuditUID

The main, unique number that identifies an audit. Audits are carried out by internal or external parties to ensure the accuracy, compliance and reliability of an organisation's financial records, transactions and processes. In the audit tables, you will find measures and options to create and carry out different types of audit for your organisation.

CompletedByUser

The name of the user who completed the audit.

CreatedDate

The date when the audit was created.

DaysOverdue

The number of days after the due date it took to complete the audit. If the audit was not overdue, the value here is null.

DueDate

The date when the audit is due to be completed.

EndDate

The date when the audit was completed.

EnhancedAuditFlag

Notes if the audit is standard or enhanced.

IsConfidential

Notes if the audit is confidential. This field is used to show or hide confidential audit information.

Location

The name of the location that this audit is associated with.

LocationUID

A unique number that identifies the location that this audit is associated with, used for data security.

NoCorrect

The number of positive answers in the audit. Positive answers, or passes, are defined when an audit is created and the scoring mechanism is selected.

Organisation

The name of your organisation.

OrganisationCode

A short code that identifies your organisation, used for data security.

OrganisationId

A unique number that identifies your organisation, used for data security.

OutstandingActionPlans

The number of action plans still to be completed for the audit.

Owner

The name of the person who owns the audit.

Region

The name of the region that this audit is associated with.

RegionUID

A unique number that identifies the region that this audit is associated with.

Result

The overall result of the audit. An audit's result is calculated from the scoring system and set when creating the audit.

Reviewer

The name of the person with the role of reviewing the audit.

Score

The overall score of the audit, calculated after the audit is complete and displayed as a percentage.

StartDate

The date when the audit is due to start.

Subject

The name of any custom list added to an audit. For example, service users, staff or locations.

SubjectItem

The name of any custom list item added to an audit. For example, a service user, a member of staff or a location.

TemplateName

The name of the audit.

TimeToCompleteDays

The time it took to complete the audit, in days.

TotalApplicableQuestions

The number of answered questions in the audit. These are questions with an answer other than "not applicable" or "n/a".

WhenAbandoned

The date when the audit was abandoned.

Term

Description

AuditUID

The main, unique number that identifies an audit, used here to identify the relevant tags from the tag table.

OrganisationCode

A short code that identifies your organisation, used for data security.

Tag

The tags assigned to this audit. Tags are a way of grouping locations, documents or any other data together based on a theme. In reporting, tags can be used to filter data.

TagSource

The place where the tag was created: form, location or region.

TagType

The type of tag: module, location or region.

Term

Description

AuditUID

The main, unique number that identifies an audit, used here to display the relevant failed questions.

CommentText

The comment that the user answering the audit wrote for the specified question.

FailedQuestions

The number of  failed questions in the audit. What is classed as failed is defined when the audit is created.

FailedQuestionText

The text for the failed question.

OrganisationCode

A short code that identifies your organisation, used for data security.

PassedQuestions

The number of  passed questions in the audit. What is classed as passed is defined when the audit is created.

QuestionGUID

The main, unique number that identifies the question.

Section name

The name of the audit section that the failed question belongs to.

SectionTotalFailedQuestions

The number of failed questions in this section of the audit.

SectionUID

The number that identifies a specific audit section.

TotalApplicableQuestions

The number of questions in the audit that were answered with anything other than N/A.

TotalAvailableQuestions

The number of questions in the audit.

Term

Description

Accountable

The name of the person accountable for the risk.

Approval state

The approval status for the risk. For example: awaiting approval, draft, not applicable and not approved.

Approver

The name of the person that can approve a risk.

Assurances

Any measures that have been put in place to mitigate the risk.

Category

The category of the risk, such as business interruption, health and safety or patient safety. Risk categories are set by your organisation.

Consequence score

The current consequence score for the risk.

Consulted / Informed

The name of the person or people that need to be consulted or informed about the risk.

Controls implemented

The number of controls already implemented for the risk. Controls are mitigating factors for the risk.

Controls outstanding

The number of controls not yet completed for the risk. Controls are mitigating factors for the risk.

Created by

The name of the user who created the risk.

Created on

The date when the risk was created.

Created With Board Assurance Framework

Notes if the risk was created within the Board Assurance Framework. If it was, assurance details such as objectives, accountability and others will appear in the PDF export and the overview tab of the risk.

Current score

The current score of the risk, as defined by the person reviewing the risk.

Date approved

The date when the risk was approved.

Date risk identified

The date when the risk was noticed.

Date scored

The date when the risk was scored.

Description

The description of the risk.

GapsInAssurances

Any gaps in the assurances associated to the risk.

Last Review Date

The date when the risk was last reviewed.

Latest comment

The text from the latest comment on the risk.

Level of risk

A value defined by your organisation to categorise risks. It can be based on any measures relevant for your organisation, such as risk likelihood, appetite or whether it impact strategic objectives. Typically, these levels might be high, medium, low; or level 1, 2, 3, but it can be anything your organisation decides.

Likelihood score

The current likelihood score for the risk.

Likely outcome

A comment specifying the likely outcome of a risk. For example, injury to residents or staff, compliance failures, damage to property, etc.

Monitoring Committee

The selected monitoring committee for the risk.

Next review date

The date when the risk is due to be reviewed next.

OrganisationCode

A short code that identifies your organisation, used for data security.

Original consequence score

The consequence score of the risk, as set when it was initially created.

Original likelihood score

The likelihood score of the risk, as set when it was initially created.

Original score

The score of the risk, as set when it was initially created.

Overall assurance

The overall level of assurance for this risk, based on how relevant the controls are, if they have been planned or implemented, if they are being monitored, etc. The values for this measure are set by your organisation.

Owner

The name of the user owning the risk. This user is responsible for reviewing risk, setting targets and other actions.

Reference

A unique code for this risk, made up of letters (defining the risk type) and a number (automatically assigned).

Risk appetite

An indication of how important the risk is for your organisation. The possible values are: no appetite, lower, medium and significant. The choice of appetite is typically based on the overall risk score, the strategic objectives it may link to and other key indicators chosen by your organisation.

Risk closed date

The date when the risk was closed.

Risk response

The main action for the risk, based on risk appetite. For example: treat, put in controls, tolerate, transfer risk to different department, terminate risk.

RiskUID

The main, unique number that identifies a risk. A risk is the potential for harm or negative impact that can arise from an organisation's processes, operations, or environment.  In the risk tables, you will find measures and options to register, monitor and mitigate risk in your organisation.

Scope

Notes whether the risk applies to the whole organisation, a region or a particular location.

Scope name

If the scope for this risk is region or location, this is the name of that region or location.

ScopeUID

The main, unique number that identifies a scope.

Status

The status of the risk. For example: draft, pending, awaiting approval, etc.

Strategic Objectives

The objectives associated with the risk. Also referred to as Objectives in the Risk Register. These objectives are set by your organisation and are typically linked to other assurance data such as controls or accountability.

Strategic risk

Notes whether a risk impacts strategic measures for the organisation.

Target consequence score

The target consequence score for the risk.

Target likelihood score

The target likelihood score for the risk.

Target met

Notes whether the target has been met for this risk. Targets are defined by the risk owner when creating the risk.

Target score

The target score for the risk.

Title of risk

The name for the risk.

Uncontrolled risk

Notes whether there are controls recorded for the risk.

Term

Description

Comment

The content of any comments left by the user who completed or is responsible for a task associated with a risk.

Description

The description of the risk task.

Id

A number that identifies a task.

OrganisationCode

A short code that identifies your organisation, used for data security.

Risk Id

A number that identifies the risk that the specified task is associated with.

Status

The status of the risk task. For example: closed, overdue, pending and planned.

Task owner

The name of the person required to complete the risk task.

Term

Description

AdequacyStatus

Defines if this control is likely to help mitigate the risk. For example: adequate, not adequate, not applicable (if not defined).

AssuranceStatus

Defines the status of the assurances for this risk control. For example: low, medium, high or not applicable.

Comment

The content of any comments left by the user who completed or is responsible for a control associated with a risk.

CommentDate

If there is a comment for this risk control, this is the date when the comment was made.

Control owner

The name of the person owning the risk control. Your organisation defines whether this is the person required to implement the control, or the person responsible for overseeing the implementation.

Term

Description

OrganisationCode

A short code that identifies your organisation, used for data security.

RiskUID

The unique number that identifies the risk, used in this table to link the risk with its tags.

Tag

The tags assigned to this risk. Tags are a way of grouping locations, documents or any other data together based on a theme. In reporting, tags can be used to filter data.

TagSource

The place where the tag was created: form, location or region.

TagType

The type of tag: module, location or region.

Term

Description

ActionUID

The main, unique number that identifies an action plan. An action plan is a collection of actions that need to be completed, often to resolve an event or perform an audit. However, action plans can also stand alone, not linked to events or audits, to showcase organisational change or capture a new process, for example.

ActionID

A unique number that identifies an action plan.

ActionPlanSource

Notes where the action plan was created: event, audit, scheduled task or n/a (when the action plan stands alone).

AssignedTo

The name of the user required to complete the action plan.

AuditsLinkedTo

A number indicating how many audits are linked to the action plan. This number can be used as a priority measure for the action plan: if an action plan has many audits linked to it, perhaps it needs to be completed as soon as possible, so the score for all of those audits gets updated.

CompletedDate

The date when the action plan was completed.

CreatedDate

The date when the action plan was created.

DaysOverdue

The number of days the action plan is overdue by. If the action plan is not overdue yet, the value in this field is "not applicable". If the action plan is overdue by less than half a day, the value is 0 (zero).

Description

The text describing the action plan, what it entails and what needs to be done.

DueDate

The date by which the action plan needs to be completed.

EventsLinkedTo

A number indicating how many events are linked to the action plan. This number can be used as a priority measure for the action plan: if an action plan has many events linked to it, perhaps it needs to be completed as soon as possible, so all of those events are resolved as a consequence.

IsOpen

Notes whether the action plan is open (not completed yet).

LastComment

The text from the last comment made in the action plan.

LastUpdate

The date when the action plan was most recently updated. The changes when an action is completed, when the action plan status changes or when there is a new comment.

LinkedEventAudit

The event type or audit template linked to the action plan. It only takes the first event or audit into consideration.

Location

The name of the location that this action plan is associated with.

LocationUID

A unique number that identifies the location that this action plan is associated with, used for data security.

Organisation

The name of your organisation.

OrganisationCode

A short code that identifies your organisation.

OrganisationId

A unique number that identifies your organisation, used for data security.

Overdue flag

Notes whether the action plan is overdue.

Priority

A number defining the priority level for the action plan. The priority appears on the user's list of tasks, and it can be used as a filter. The possible value are low, medium and high.

Reference

A unique code for this action plan, made up of letters (defining the risk type) and a number (automatically assigned).

Region

The name of the region that this action plan is associated with.

RegionUID

A unique number that identifies the region that this action plan is associated with, used for data security.

ScheduledTasksLinkedTo

A number indicating how many scheduled tasks are linked to the action plan. This number can be used as a priority measure for the action plan: if an action plan has many scheduled tasks linked to it, perhaps it needs to be completed as soon as possible, so all those tasks get resolved.

Status

The status of the action plan. For example: complete, overdue, pending and planned.

TimeToCompleteDays

The number of days it took to complete the action plan.

TimeToCompleteMinutes

The number of minutes it took to complete the action plan.

Term

Description

ActionUID

The main, unique number that identifies an action plan, used in this table to link the action plan with its tags.

OrganisationCode

A short code that identifies your organisation.

Tag

The tags assigned to this action plan. Tags are a way of grouping locations, documents or any other data together based on a theme. In reporting, tags can be used to filter data.

TagSource

The place where the tag was created: form, location or region.

TagType

The type of tag: module, location or region.